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

Re: AggServer on Thredds 3.1

Bjørge Solli wrote:


I want to upgrade our current system based on thredds 2.0b and AggServer to the current thredds. My testsetup is running with thredds.war v3.1.

Do I still have to install AggServer to get its functionality or is it integrated in thredds? If yes, can I still use the same xml-files? If no, what do I have to change in my xmls to use this functionality without AggServer?

Bjørge Solli,
There is no AGG server in the current release of THREDDS 3.*, you need to wait for a few weeks for the next release of the THREDDS data server which includes AGG server, so you don't need to install another AGG server. The new AGG server is totally new designed and will not be compatible with old config file. The good new is the new AGG server is very easy to config, and it will come with a completed document.


<!DOCTYPE catalog SYSTEM "http://www.unidata.ucar.edu/projects/THREDDS/xml/AggServerCatalog.dtd";>
<catalog name="DODS Aggregation Server Catalog for MERSEA Class 2" version="0.6"
xmlns="http://www.unidata.ucar.edu/thredds"; xmlns:xlink="http://www.w3.org/1999/xlink";>

<dataset name="MERSEA CLASS 2 Aggregated files" dataType="Grid" serviceName="this">

<service name="this" serviceType="DODS" base=""/>

<service name="TOPAZ" serviceType="DODS"

<dataset name="Long Term Best Estimate" dataType="Grid" serviceName="this">

<dataset name=" moorings Long Term Best Estimate" urlPath="topaz_V1_mersea_nat_dc_class2_moorings_best_agg">
<metadata metadataType="Aggregation">
<aggregation serviceName="TOPAZ"
aggType="JoinNew" varName="time"
varType="int" varUnit="secs since 1970-01-01 00:00:00"
dateFormat="yyyy/M/d:hh:mm:ss z">
<fileAccess urlPath="moorings/topaz_V1_mersea_nat_dc_class2_moorings_b20030604_f200305289999.nc"

      coord="2003/05/28:00:00:00 GMT" />


<snip : more fileAccess and endtags>

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.