[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TDS Aggregation Catalog

Daniel Holloway wrote:

On Apr 21, 2006, at 3:59 PM, John Caron wrote:

Hi Dan:

There's enough differences with the old AS to mess with your mind, see below.

<variableAgg name="T" />
<netcdf location="1999/1/f99001082417.hdf" coord="/ 1999/01/01:08:24:17 GMT" />

These need to have the full URL in the nested netcdf, we dont factor out the service anymore:

<netcdf location="http://dods.gso.uri.edu/dods-3.4/nph-dods/ 1999/1/f99001082417.hdf" coord="/1999/01/01:08:24:17 GMT" />

The time coordinates should be in ISO format:


And change the time coordinate variable:

        <dimension name="time" length="0"/>
        <variable name="time" type="String" shape="time" >
           <attribute name="_CoordinateAxisType" value="Time" />

        <dimension name="time" length="0"/>
        <dimension name="dateLen" length="20"/>
        <variable name="time" type="char" shape="time dateLen" >
           <attribute name="_CoordinateAxisType" value="Time" />

If you need to stick to the udunits "seconds since 1970-1-1 0:00", yuo'll have to generate the correct value yourself. If thats impossible, we'll have to see about adding dateFormat back in.


Thanks for the information. What will the 'time' access look like by default? Will it be a 'string' type? If I have to I can probably generate the udunits 'secs since' value in the script that generates the catalog itself.

theres not really a default. the first suggestion is to make it into a String, the second into a char. Our CDM stuff now uses ISO strings or udunits. If you need udunits, then you should calculate the value and put it in thw coord attribute, and then keep your original coordinate variable definiiton.



<netcdf location="1999/1/f99001181038.hdf" coord="/ 1999/01/01:18:10:38 GMT" />
<netcdf location="1999/1/f99001195049.hdf" coord="/ 1999/01/01:19:50:49 GMT" />
<netcdf location="1999/1/f99002081244.hdf" coord="/ 1999/01/02:08:12:44 GMT" />

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.