Re: [thredds] THREDDS Catalog - service element

• To: thredds@xxxxxxxxxxxxxxxx
• Subject: Re: [thredds] THREDDS Catalog - service element
• From: Ethan Davis <edavis@xxxxxxxxxxxxxxxx>
• Date: Tue, 12 Jul 2011 17:08:16 -0600

Hi Glenn,

You are interpreting the documentation correctly. The depth to which a
"service" element is nested shouldn't matter. It is a bug in our THREDDS
catalog handling code. I have added it to our issue tracking system. You
can follow this issue here:

https://www.unidata.ucar.edu/jira/browse/TDS-193

Thanks for reporting this bug.

Ethan

On 6/29/2011 5:27 AM, Comiskey, Glenn wrote:
> Hi,
>  
> It is my understanding that once a "service" has been defined within a
> catalog it can be referenced regardless of whether it is nested as part
> of "serviceType=Compound" or not, i.e. to quote Dataset Inventory
> Catalog Specification Version 1.0
> (http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#service)
>  "Nested
> /service/ elements may also be used directly by /dataset/ or /access/
> elements, and so must have unique names."
>  
> Given the following "service" THREDDS v4.2.6 catalog declarations:
>  
>   <service name="all"  serviceType="Compound" base="">
>     <service name="most" serviceType="Compound" base="">
>       <service name="iso"  serviceType="ISO"         
> base="/thredds/iso/"       />
>       <service name="odap" serviceType="OpenDAP"     
> base="/thredds/dodsC/"     />
>       <service name="ncss" serviceType="NetCDFSubset"
> base="/thredds/ncss/grid/" />
>       <service name="ncml" serviceType="NCML"        
> base="/thredds/ncml/"      />
>       <service name="uddc" serviceType="UDDC"        
> base="/thredds/uddc/"    />
>       <service name="wcs"  serviceType="WCS"         
> base="/thredds/wcs/"       />
>       <service name="wms"  serviceType="WMS"         
> base="/thredds/wms/"       />
>     </service>
>     <service name="http" serviceType="HTTPServer"
> base="/thredds/fileServer/" />
>   </service>
>  
> I would expect to be able to specify any of the delcared "name" values
> as part of a dataset's "serviceName" attribute or part of an "access"
> element, i.e. serviceName="odap", serviceName="iso", serviceName="http".
> However, I find I can only use values "all", "most" and "http", i.e. the
> uppermost compound service (all), its nested compound and child
> declarations (most, http), but not the nested, nested child declarations
> (iso, odap, ncss, ncml, uddc, wcs, wms).
>  
> Is this a case of my understanding regarding the use of "service"
> declarations being wrong, or is something amiss?
>  
> Kind regards,
>  
> Glenn Comiskey
> Data System Administrator
>  
> Fugro Global Environment & Ocean Sciences
> Fugro House, Hithercroft Road
> Wallingford, Oxfordshire OX10 9RB, UK
> Registration No: 2985431 / VAT No: GB 655475606
>  
> Tel: +44 (0) 1491 820500 (Switchboard) / Tel: +44 (0) 1491 820559
> (Direct) / Fax: +44 (0) 1491 820599
> E-mail: _g.comiskey@geos.com_ <mailto:g.comiskey@g.comiskey@xxxxxxxx>/
> Website: _www.geos.com_ <http://www.geos.com/>
>  
> Please note:
> 
>     *
>       The information contained in this message is privileged and
>       confidential and intended only for the use of the addresses.  If
>       you are not the intended recipient you should not read, copy,
>       distribute or otherwise use the information;
>     *
>       Fugro Global Environment & Ocean Sciences accepts no
>       responsibility for loss or damage of any kind arising from the use
>       of this message;
>     *
>       If you have received this message in error, please note the sender
>       immediately and delete the message.
> 
> 
>  
> 
> 
> 
> _______________________________________________
> thredds mailing list
> thredds@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit: 
> http://www.unidata.ucar.edu/mailing_lists/ 

• References:
  • [thredds] THREDDS Catalog - service element
    • From: Comiskey, Glenn