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

Re: THREDDS library



Hi Michael, a coupla questions:

1. Your catalog doesnt seem to have a service in it, so im unclear how you are 
using catalogs.

2. Are you calling InvCatalogFactory to parse the catalog, and then calling ThreddsMetadata.GeospatialCoverage.getEastWestRange() ?

3. Im thinking of having those routines return null when those fields havent 
been set. What do yu think?

Michael Burek wrote:

On Feb 10, 2006, at 1:31 PM, John Caron wrote:

Michael Burek wrote:

Hi,

Couple of things.

I think I found an anomaly in what gets returned in calls to the spatial coverage object. For a solar dataset we are hosting there are vertical coverage parameters, but no lat/long. In this circumstance when our metadata display software queries the lat/long it receives the maximum values: start -180, size 360, start -90, size 180. Seems that this might be a bug in the code, I'd like to receive some indication that the parameter was missing like NaN or a null object, or an exception.


sounds like a bug. if you can give us an example dataset, well get it fixed.


The catalog is in two files on our server. The problem is in the second catalog. I'm sending the first so that you can see the context.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<catalog name="Enlil" xsi:schemaLocation="http://www.unidata.ucar.edu/ namespaces/thredds/InvCatalog/v1.0 http://www.unidata.ucar.edu/ schemas/thredds/InvCatalog.1.0.xsd" xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance" xmlns="http://www.unidata.ucar.edu/namespaces/ thredds/InvCatalog/v1.0">
<dataset ID="cu.cires.enlil.m97may.code_1-mcp3mt-1_256x30x90" harvest="false" name="Code - grid 256x30x90 , processing element 1, model mcp3mt-1">
<metadata xlink:href="http://dataportal.ucar.edu/metadata// enlil/m97may/code_1-mcp3mt-1_256x30x90/code_1- mcp3mt-1_256x30x90.metadata.xml" metadataType="THREDDS" xmlns:xlink="http://www.w3.org/1999/xlink"/>
</dataset>
</catalog>



<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<metadata xsi:schemaLocation="http://www.unidata.ucar.edu/namespaces/ thredds/InvCatalog/v1.0 http://www.unidata.ucar.edu/schemas/thredds/ InvCatalog.1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xmlns="http://www.unidata.ucar.edu/namespaces/thredds/ InvCatalog/v1.0">
<date format="yyyy-MM-dd" type="created">2006-02-09</date>
<property name="upLimit" value="52"/>
<property name="downLimit" value="5"/>
<geospatialCoverage>
<updown>
<start>5.0</start>
<size>47.0</size>
<units>Meters</units>
</updown>
</geospatialCoverage>
<date format="yyyy-MM-dd" type="lastModified">2006-02-09</date>
</metadata>




Is there any plan yet to get the THREDDS library updated to jdom1.0?


the latest version (3.5) uses jdom 1.0.


Thanks!  I'll give it a try.



I'd like to make some time with you to talk about extensions we've made to THREDDS using property elements for access control and other functions, and if those changes should migrate into the schema.


good idea, the access stuff is on my TODO list. I was experimenting with adding it as an attribute on the dataset.





Thanks,


Michael






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.