Hi Jay,
If the time resolution in no greater than "years", then you might get
away with storing in units similar to "years since 2000-1-1", with most
of the coordinate values being negative (starting from -12000). Note,
however, that with these units one wouldn't be able to reliably
determine the actual date (below the annual resolution). In this case I
think you could omit the "calendar" attribute. Note that if the
paleodata represented temperatures for the quarter year period of April,
May, June, then you would want to store time-bounds as (assuming units
of "years since 2000-1-1"):
-11999.75, -11999.5, (this is for year 12000 BP (where present is year
2000); I might be a year or 2 off here, but you get the idea)
-11998.75, -11998.5,
.
.
.
-0.75, - 0.5,
0.25, 0.5,
.
.
.
.
10.25, 10.5,
11.25, 11.5 (this is for year 2011, for the period approximately in the
range April 1 - June 30)
The coordinate values could be assigned to the middle of each interval
(i.e., -11999.625, -011998.625, ... 10.375, 11.375)
If you need to get the actual date correct, at least throughout the
post-gregorian period (i.e., after 1582-10-15), then you should set
calendar to "proleptic_gregorian", and be careful to set your basetime
after 1582-10-15, I think. I don't think you can count on dates being
correct for times earlier than 1582-10-15, but maybe some software does
this right.
regards,
Karl
On 3/10/11 3:55 PM, Karl Taylor wrote:
Could someone please advise Jay?
thanks,
Karl
-------- Original Message --------
Subject: PALEO..
Date: Thu, 10 Mar 2011 11:37:51 -0800
From: Jay Hnilo <[email protected]>
To: Taylor, Karl Taylor <[email protected]>
Hi Karl,
If you happen to have some paleo data--how do you put it into
netcdf--knowing it goes from 10000 years ago to present day?
I'm asking mainly about the time.units, time.calendar, time coordinate values..
Thanks,
Jay
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
