John,
I think your only option is to use some F-TDS or NCML magic to
replace the time axis with one that is defined with double values of
the form "hours since 1970-01-01".
Make sense? If not, I can send you an example.
Roland
Hi
All,
I have a dataset whose time axis includes ISO 8601 datetime
strings (e.g. "2010-12-21T00:00:00Z") that is not displaying in
LAS. I get an error:
**ERROR: illegal limits: CRW_HOTSPOT does not exist at T=-6.3143E+10
Axis extremes are T=0.5:1042.5
This error shows axis extremes (0.5:1042.5) that use only the time
variable's indices. That plus the strange T=-6.3143E+10 seems to
suggest that LAS is not understanding the format of the time axis
strings. How can I tell it that the axis is using ISO 8601
datetime strings? When configuring this dataset in LAS, I used
this but I tried various permutations of the units setting:
<time-t-dhw type="t" units="days" display_lo="2000-12-02"
display_hi="2010-12-13" default="last">
<arange start="2000-12-02" size="1042" step="3.5" />
</time-t-dhw>
And here is the link to the dataset in our THREDDS Data Server
(TDS):
http://oos.soest.hawaii.edu/thredds/idd/satellite.html?dataset=dhw
An additional wrinkle to getting this dataset into LAS is that the
time axis is bi-weekly. Will LAS limit the list of available days
in the pull-down to those that are actually contained in the
dataset?, or will there be a lot of days listed for which there
are no data and the user will get an error?
Thanks,
John Maurer
Hawaii Ocean Observing System (HiOOS)
University of Hawaii
|