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

20051116: Point data served by opendap catalogs

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: 20051116: Point data served by opendap catalogs
  • Date: Wed, 16 Nov 2005 11:03:16 -0700
Hi Stu-

I said:

> I think the easiest solution would be to add in a new entry to
> your datasource.xml which would have id="HTTP.POINT" and then
> have the rest of the entry look the one you have for the local
> GEON files.  Then, in your catalog, add:
> 
> <serviceType>HTTP</serviceType>
> <dataType>Point</dataType>

This should read:

> <serviceName>httpnc</serviceName>
> <dataType>Point</dataType>

and then:

> for your metadata tag.  You'll need to define a service type
> for httpnc which would be the HTTP base for these files.  

For your server, it would look like:

<service name="httpnc" serviceType="HTTP" base="http://geon.unavco.org/data/"; />

Don Murray
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.