Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The generated netCDF file should be CF-compliant #20

Open
hans-permana opened this issue Dec 9, 2015 · 1 comment
Open

The generated netCDF file should be CF-compliant #20

hans-permana opened this issue Dec 9, 2015 · 1 comment

Comments

@hans-permana
Copy link
Contributor

A check has been performed in one of the generated data cube files using an online checker (http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl) and there are a couple of warnings:

CHECKING NetCDF FILE: /tmp/10715.nc
=====================
WARNING: Cannot determine CF version from the Conventions attribute; checking against latest CF version: CF-1.6
Using CF Checker Version 2.0.9
Checking against CF Version CF-1.6
Using Standard Name Table Version 30 (2015-12-03T08:05:16Z)
Using Area Type Table Version 3 (8 July 2015)

WARNING (2.6.1): No 'Conventions' attribute present

------------------
Checking variable: lat
------------------
WARNING (3): No standard_name or long_name attribute specified

------------------
Checking variable: start_time
------------------
WARNING (3): No standard_name or long_name attribute specified
INFO: attribute 'calendar' is being used in a non-standard way

------------------
Checking variable: BurntArea
------------------
ERROR (8.1): BurntArea must be of type byte, short or int

------------------
Checking variable: lon
------------------
WARNING (3): No standard_name or long_name attribute specified

------------------
Checking variable: end_time
------------------
WARNING (3): No standard_name or long_name attribute specified
INFO: attribute 'calendar' is being used in a non-standard way


ERRORS detected: 1
WARNINGS given: 6
INFORMATION messages: 2
@forman
Copy link
Member

forman commented Jul 13, 2016

@hans-permana: check if we can automate CF-compliancy checks

@forman forman removed the mustfix label Aug 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants