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

Re: TDS Aggregation Catalog



Hi Dan:

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

Daniel Holloway wrote:
Hi John,

Thanks for replying so quickly. I'm still having a little difficulty, would you take a look at the catalog.xml file that I'm attaching to this message and let me know what I've done wrong. It validates but the dataset appears empty when I use a browser to look at the tomcat server. I have this catalog loaded at http:// dods.gso.uri.edu:8080/thredds/

I think the problem is most likely in that I'm using the <netcdf> element type but really am trying to point to a DAP-served data source. Also, there may be a problem with how I'm defining the 'time' coordinate dimension, and how that's formatted in the 'Coord' attribute. I've basically tried to weave in our older aggregation server catalog usage into the examples I could find for the TDS, and took liberties whenever I couldn't find a similar case.

    Thanks,

         Dan


------------------------------------------------------------------------

<catalog xmlns="http://www.unidata.ucar.edu/namespaces/thredds/InvCatalog/v1.0";
         xmlns:xlink="http://www.w3.org/1999/xlink";
         name="URI-THREDDS OPeNDAP Data Server" version="1.0.1">

<service name="opendap" serviceType="OPeNDAP" base="http://dods.gso.uri.edu/dods-3.4/nph-dods/"; />

The primary service needs to refer to the TDS, eg:

 <service name="opendap" serviceType="OPENDAP" 
base="http://server:port/thredds/dodsC/"; />


<dataset name="Pathfinder AVHRR Northwest Atlantic Aggregation (1km Declouded)" urlPath="Pathfinder/Northwest_Atlantic/6km/declouded"> <serviceName>opendap</serviceName>

     <netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2";>

        <dimension name="time" length="0"/>
        <variable name="time" type="int" shape="time" >
           <attribute name="units" value="seconds since 1970-1-1 0:00" />
           <attribute name="_CoordinateAxisType" value="Time" />
        </variable>

<aggregation dimName="time" type="joinNew" dateFormat="yyyy/M/d:hh:mm:ss z">

We dont currently support "dateFormat"


           <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:

  1999-01-01T08:24:17Z

And change the time coordinate variable:

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

or

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

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.


           <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" />
        </aggregation>
     </netcdf>
  </dataset>
</catalog>




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.