StaticRdfCatalog: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
| Line 14: | Line 14: | ||
In order for the WCS service to work it must know which DAP data sets are to be served as WCS coverages. There are a number ways that data sets can be identified. | In order for the WCS service to work it must know which DAP data sets are to be served as WCS coverages. There are a number ways that data sets can be identified. | ||
==== Coverage ==== | ==== Coverage ==== | ||
A Coverage element identifies a single DAP data set that is to served as a WCS coverage. The Coverage element must contain the fully qualified data access URL for a DAP data set that is to be served as a coverage. This URL will be examined and the software will attempt to get the RDF version of the data set's DDX from the DAP server. | A Coverage element identifies a single DAP data set that is to served as a WCS coverage. The Coverage element must contain the fully qualified data access URL for a DAP data set that is to be served as a coverage. This URL will be examined and the software will attempt to get the RDF version of the data set's DDX from the DAP server. | ||
<Coverage>http://localhost:8080/opendap/data/nc/examples/200803061600_HFRadar_USEGC_6km_rtv_SIO.nc.ddx</Coverage> | <Coverage>http://localhost:8080/opendap/data/nc/examples/200803061600_HFRadar_USEGC_6km_rtv_SIO.nc.ddx</Coverage> | ||
| Line 25: | Line 23: | ||
A ThreddsCatalog element identifies a THREDDS catalog which contains DAP data access URLs that point to DAP data sets that will be served as WCS coverages. Each DAP data set in the catalog will be served as a separate Coverage. The ''recurse'' attribute determines if the software will follow '''catalogRef'' links in the THREDDS catalog to ingest the entire catalog hierarchy starting at the provided node. | A ThreddsCatalog element identifies a THREDDS catalog which contains DAP data access URLs that point to DAP data sets that will be served as WCS coverages. Each DAP data set in the catalog will be served as a separate Coverage. The ''recurse'' attribute determines if the software will follow '''catalogRef'' links in the THREDDS catalog to ingest the entire catalog hierarchy starting at the provided node. | ||
<ThreddsCatalog recurse="false" >http://test.opendap.org:8080/opendap/coverage/catalog.xml</ThreddsCatalog> | <ThreddsCatalog recurse="false" >http://test.opendap.org:8080/opendap/coverage/catalog.xml</ThreddsCatalog> | ||
| Line 31: | Line 28: | ||
An RdfImport element identifies a single RDF file to load directly into the repository. This is a mechanism for loading additional OWL ontologies and inference rules into the system at start-up. The RdfImport element must contain the fully qualified URL for an RDF file. | An RdfImport element identifies a single RDF file to load directly into the repository. This is a mechanism for loading additional OWL ontologies and inference rules into the system at start-up. The RdfImport element must contain the fully qualified URL for an RDF file. | ||
<RdfImport>http://iri.columbia.edu/~benno/opendaptest/daptestAll.owl</RdfImport> | <RdfImport>http://iri.columbia.edu/~benno/opendaptest/daptestAll.owl</RdfImport> | ||
Revision as of 18:31, 30 December 2009
Overview
What makes a Dataset a coverage?
Supported Conventions
CF-1.0 Convention
Augmenting Dataset Metadata with NcML
Configuration
Adding Data Sets To The Catalog.
In order for the WCS service to work it must know which DAP data sets are to be served as WCS coverages. There are a number ways that data sets can be identified.
Coverage
A Coverage element identifies a single DAP data set that is to served as a WCS coverage. The Coverage element must contain the fully qualified data access URL for a DAP data set that is to be served as a coverage. This URL will be examined and the software will attempt to get the RDF version of the data set's DDX from the DAP server.
<Coverage>http://localhost:8080/opendap/data/nc/examples/200803061600_HFRadar_USEGC_6km_rtv_SIO.nc.ddx</Coverage>
ThreddsCatalog
A ThreddsCatalog element identifies a THREDDS catalog which contains DAP data access URLs that point to DAP data sets that will be served as WCS coverages. Each DAP data set in the catalog will be served as a separate Coverage. The recurse attribute determines if the software will follow 'catalogRef links in the THREDDS catalog to ingest the entire catalog hierarchy starting at the provided node.
<ThreddsCatalog recurse="false" >http://test.opendap.org:8080/opendap/coverage/catalog.xml</ThreddsCatalog>
RdfImport
An RdfImport element identifies a single RDF file to load directly into the repository. This is a mechanism for loading additional OWL ontologies and inference rules into the system at start-up. The RdfImport element must contain the fully qualified URL for an RDF file.
<RdfImport>http://iri.columbia.edu/~benno/opendaptest/daptestAll.owl</RdfImport>
Overriding Default Paths
PeristentContentPath
<PeristentContentPath>/Users/ndp/OPeNDAP/Projects/Hyrax/swdev/ioos/apache-tomcat-6.0.14/content/opendap/WCS/StaticRDFCatalog</PeristentContentPath>
ResourcePath
<ResourcePath>/Users/ndp/OPeNDAP/Projects/Hyrax/swdev/ioos/apache-tomcat-6.0.14/webapps/opendap/WCS/</ResourcePath>
Controlling Repository Update Behavior
<useUpdateCatalogThread updateInterval="90" />
Example Configuration
<Handler className="opendap.wcs.v1_1_2.DispatchHandler">
<prefix>WCS</prefix>
<ServiceIdentification>/Users/ndp/OPeNDAP/Projects/Hyrax/swdev/ioos/apache-tomcat-6.0.14/content/opendap/WCS/ServiceIdentification.xml</ServiceIdentification>
<ServiceProvider>/Users/ndp/OPeNDAP/Projects/Hyrax/swdev/ioos/apache-tomcat-6.0.14/content/opendap/WCS/ServiceProvider.xml</ServiceProvider>
<OperationsMetadata>/Users/ndp/OPeNDAP/Projects/Hyrax/swdev/ioos/apache-tomcat-6.0.14/content/opendap/WCS/OperationsMetadata.xml</OperationsMetadata>
<WcsCatalog className="opendap.semantics.IRISail.StaticRDFCatalog">
<useUpdateCatalogThread updateInterval="90" />
<PeristentContentPath>/Users/ndp/OPeNDAP/Projects/Hyrax/swdev/ioos/apache-tomcat-6.0.14/content/opendap/WCS/StaticRDFCatalog</PeristentContentPath>
<ResourcePath>/Users/ndp/OPeNDAP/Projects/Hyrax/swdev/ioos/apache-tomcat-6.0.14/webapps/opendap/WCS/</ResourcePath>
<RdfImport>http://iri.columbia.edu/~benno/opendaptest/daptestAll.owl</RdfImport>
</WcsCatalog>
</Handler>
