Open neishm opened 9 years ago
There are also issues with climatologies along StandardTime axes, so this behaviour would be good to clean up. I'd like to see this in 1.1.
Lokoing at the CF conventions document (http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html#climatological-statistics), this is more complicated than I thought. There can be "climatologies" over seasons or other arbitrary time divisions). It's not clear to me how to encode this information in the time axis (for example, data averaged into January, February, etc. for the years 2000-2005). There's no way this will be done by release 1.1.
Original issue 64 created by neishm on 2014-12-03T15:28:54.000Z:
PyGeode sometimes doesn't detect when a netcdf dataset is a climatology. It only considers something to be a climatology if the reference year is zero, and the data doesn't extend beyond a year from that point. The logic should be changed to look for a "climatology" attribute (as defined by the cfmeta standard), and respect the associated bounds.