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

Allow alternate spec for time origin: "hours since 2011-03-08T12:00:00Z" #1078

Closed
karlmsmith opened this issue Nov 23, 2017 · 1 comment
Closed

Comments

@karlmsmith
Copy link
Contributor

karlmsmith commented Nov 23, 2017

Reported by @AnsleyManke on 9 Mar 2011 19:28 UTC
Hein Zelle reports is for data from GRIB files, served by a THREDDS server,

I'm having trouble accessing a THREDDS (OpenDAP) dataset through
ferret.  We export our GFS data files (GRIB2) through thredds. 
Ferret reads and uses the data just fine, but it gets confused 
about the time axis.  THREDDS specifies it as follows:


time: Array of 32 bit Integers [time = 0..0]

long_name: "forecast time"
units: "hours since 2011-03-08T12:00:00Z"
GRIB_orgReferenceTime: "2011-03-08T12:00:00Z"
GRIB2_significanceOfRTName: "Start of forecast"
_CoordinateAxisType: "Time"


Ferret doesn't seem to like that T in the units string.  It parses
the date part, and ignores the time, leading to a time origin of
2011-03-08 00:00 (!)


Creating a NetCDF file with a units string that contains a T, as in
units: "hours since 2011-03-08T12:00:00Z"

and ran it through the CF checker. The checker does not complain about this style of writing the date/time string (though it does return an error if the string has a colon, as in 2011-03-08:12:00:00).

It's a simple matter to allow for this in the Ferret code, and is not prohibited by the CF standard, so change Ferret to allow such date strings.

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1806

@karlmsmith
Copy link
Contributor Author

karlmsmith commented Nov 23, 2017

Comment by @AnsleyManke on 9 Mar 2011 21:57 UTC
Done; change is in tm_break_fmt_date.F

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

1 participant