Re: [CF-metadata] CF calendars (was: problem with times in PSD dataset)

2012-12-17 Thread Cathy Smith (NOAA Affiliate)
Cecelia I support 1) mostly for backward compatibility. I would also strongly encourage but not demand that users change their base dates to after 1800 when it makes sense to do so. And, I (again) want to make sure that LTMs and their time values are addressed before any decisions are made as to

Re: [CF-metadata] CF calendars (was: problem with times in PSD dataset)

2012-12-17 Thread Cathy Smith (NOAA Affiliate)
, Cathy Smith (NOAA Affiliate) wrote: Cecelia I support 1) mostly for backward compatibility. I would also strongly encourage but not demand that users change their base dates to after 1800 when it makes sense to do so. And, I (again) want to make sure that LTMs and their time values

Re: [CF-metadata] CF calendars (was: problem with times in PSD dataset)

2012-12-10 Thread Cathy Smith (NOAA Affiliate)
Jonathon We have the issue that we store many long terms means (subdaily,daily, monthly...). These long terms means have no years per se though the rest of the date is an actual 'date'. We have been storing them as year 1 generally speaking (usually base 1-1-1) as we want to avoid using a date

Re: [CF-metadata] [netcdf-java] problem with times in PSD dataset

2012-12-06 Thread Cathy Smith (NOAA Affiliate)
John There is some meteorological data that is available pre-Gregorian calendar (paleo data, some temperature datasets) and of course there are other scientific fields where data is pre-1500 (e.g. astronomy, archeology) . Given that netCDF files with data dates spanning ~1550 probably already