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

Re: Resolution for geospatial coverage

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: Resolution for geospatial coverage
  • Date: Thu, 18 Aug 2005 17:13:01 -0600
carl wolfteich wrote:
Greetings. My question concerns resolution for the geospatial coverage element for a dataset I am including in a thredds catalog. Assuming non-global coverage I see how to assign resolution for the northsouth and eastwest elements of coverage. But when I click on the link for "complete metadata" for the dataset, the resolution is not included. In contrast, the resolution for timeCoverage is listed under "complete metadata". Can I be assured that the resolution for geospatial Coverage is being read even though it is not being included in the readout for "complete metadata" like the timeCoverage resolution is? And as a followup question, in the Catalog Spec. Version 1.0 it does not include a provision for assigning resolution for global coverage, when using the shorter version: 
<geospatialCoverage>
<name vocabulary="Thredd">global</name>
</geospatialCoverage>
Was this provision just left out and you can just add the resolution element similar to non-global coverage? Since neither is listed under "complete metadata", I wasn't sure. Thanks. 



Hi carl:
Its just an oversight that the html is not displaying the resolution; we will fix this in our latest version. It is still in the xml. 

I guess you would have to add the resolution like this:

<geospatialCoverage>
<eastwest>
 <start>0.0<start>
 <size>360.0</size>
 <resolution>2.0</resolution>
</eastwest>
<name vocabulary="Thredds">global</name>
</geospatialCoverage>
We can add it to the list of issues as to whether to allow resolution without the start, size.