forked from ioos/catalog
-
Notifications
You must be signed in to change notification settings - Fork 0
Luke Campbell edited this page Sep 21, 2016
·
4 revisions
- Where can I find data?
- The primary place to find data is data.ioos.us
- How can I register my data?
- At registry.ioos.us you can register for an account. After the account has been reviewed you will be granted the ability to register harvest endpoints and review data submissions to the IOOS Catalog.
- How long does it take to harvest?
- Using the registry user interface you can immediately harvest data into the registry and see any processing errors. The IOOS Catalog which runs on CKAN will download all datasets from the registry daily. However, an administrator can manually harvest if need be.
- I put my data in a WAF, but it isn't showing up in the catalog
-
The most likely reason is that there are parsing errors. You can see any
errors in the registry. If the XML document is formatted incorrectly or
missing critical data then the dataset can't be displayed in CKAN.
There is also a chance that when the registry attempted to harvest the XML documents, there was a network interruption. This information is also available on the registry. - Datasets are being created with duplicate file identifiers
-
Summary: the NERACOOS WAF, generated by the ncISO.jar application
(http://www.ngdc.noaa.gov/eds/tds/) was not producing unique
<fileIdentifer> elements in the ISO XML. This causes CKAN problems,
correctly.
TDS direct file access is constructed by: <code>serverRoot + serviceBasePath + dataset urlPath
A NERACOOSExample. <pre><service name="iso" serviceType="ISO" base="/thredds/iso/"/> <dataset name="met" ID="SOS_DSG_B01_MET_Historic_Realtime_Agg" urlPath="UMO/DSG/SOS/B01/Met/HistoricRealtime/Agg.ncml”>
<a href="http://www.neracoos.org/thredds/iso/UMO/DSG/SOS/B01/Met/HistoricRealtime/Agg.ncml">http://www.neracoos.org/thredds/iso/UMO/DSG/SOS/B01/Met/HistoricRealtime/Agg.ncml</a> This returns a correct ISOXMLfile but the <code>fileIdentifier</code> is B01, not hte datasetID. The work around is to append a query string <code>?catalog=<catalog_url>&dataset=<ID></code> forcing access thry the TDScatalog. <pre>Also of note, is that the <a href="https://github.com/asascience-open/thredds_crawler">thredds-crawler</a> uses the query string to set the <code>fileIdentifier</code> as well.