"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

Adding a Coverage entry to GeoNetwork

Contents

Overview:

Adding Coverage entries to a GeoNetwork instance can be added manually as well using GeoNetwork's THREDDS Catalog Harvester. We will be covering both methods.

Adding entries manually

The following describes how to manually add a coverage into GeoNetwork. This is normally used when the coverage is not accessible via a THREDDS catalog.

Below is a list of the fields, their description, the approach to insert the data and examples to accomplish this.

Section: Identification Info

Field Title
Description Name by which the cited resource is known as
Direction Under the Identification Info field, give your map a name. There will be a default name of your data. Use free text to describe your map here.
Example Mean Sea Level Pressure
Source From the custodian of the dataset
Obligation highly recommended

Field Date
Description the exact date of creation, publication or revision on your map
Direction Indicate the exact date of creation, publication or revision on your map
Example 2010-09-01T09:46:03
Source From the custodian of the dataset or from the portal deployment teame
Obligation highly recommended

Field Date Type
Description The Type of Date
Direction Indicate the type of date used; creation, publication or revision
Example Creation: Date identifies when the resource was brought into existence
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Abstract
Description Brief narrative summary of the content of the resource.
Direction Enter some description of the map
Example MDU portal composes the AuScope Portals Resources combined with the MDU internal resources. It has a private and public collection of data, and using the Australian Access Federation, users may access the protected data.
Source From the custodian of the dataset.
Obligation highly recommended

Field Status
Description The current status of the dataset.
Direction Specify the status of your map within the following options: completed, historical archive, obsolete, ongoing, planned, required, under development.
Example Completed: Data has been completed.
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Point of Contact
Description Party that is responsible for the dataset information
Direction Enter all mandatory information and others you have at hand for the contact of the person(s) associated with this resources of the map. Note that some fields are only conditionally mandatory, such as Organization Name if Individual Name and Position are not entered.
Example

Individual name

Terry Rankine

Organisation

CSIRO

Role

Point of contact: Party who can be contacted for acquiring

knowledge about or acquisition of the resource

Voice

61 8 6436 8601

Facsimile

61 8 6436 8555

Delivery Point

26 Dick Perry Ave

City

Kensington

Administrative area

WA

Postal code

6151

Country

Australia

Electronic mail address

Terry.rankine@csiro.au

Source From the custodian of the dataset or from the portal deployment team
Obligation mandatory or highly recommended

Field Other constraints
Description Additional constraints
Direction Copyrights and other additional information can be added here
Example Copyright Commonwealth of Australia 2010, Bureau of Meterology (ABN 92 637 533 532)
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Spatial representation type
Description Method used to spatially represent geographic information
Direction Enter Spatial representation type of dataset
Example Grid
Source From the custodian of the dataset
Obligation highly recommended

Field Access constraints
Description Access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource
Direction Enter an access constraint here, such as a copyright, trademark, etc. to assure the protection of privacy and intellectual property.
Example Digital map: Map represented in raster or vector form
Source From the custodian of the dataset
Obligation mandatory or highly recommended

Field User Constraints
Description User constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource
Direction Enter a user constraint here to assure the protection of privacy and intellectual property.
Example N/A
Source From the custodian of the dataset
Obligation Optional

Field Other Contraints
Description Any Other constraints that applies to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource
Direction Enter other constraint here to assure the protection of privacy and intellectual property. Note that this field is conditionally mandatory if Access and Use constraints are not entered.
Example N/A
Source From the custodian of the dataset.
Obligation Optional

Field Spatial representation type
Description How the spatial information are represented.
Direction Select, from the drop-down list the method used to spatially represent your data. The options are: vector, grid, text table, stereo model, video.
Example Vector: Vector data is used to represent geographic data
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Language
Description The language used in the resource.
Direction Select the language used within your map
Example English
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Character set
Description Dataset character set.
Direction Select the character set used within your map
Example UTF8: 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Topic category code
Description The <ISO_Topic_Category> field is used to identify the keywords in the ISO 19115 - Geographic Information Metadata (http://www.isotc211.org/) Topic Category Code List. It is a high-level geographic data thematic classification to assist in the grouping and search of available geographic data sets.
Direction Specify the main ISO category/ies through which your map could be classified
Example Boundaries
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Extend
Description extent information including the bounding box, bounding polygon,
vertical, and temporal extent of the dataset
Direction Enter the longitude and latitude for the map or select a region from the predefined drop-down list. Make sure you use degrees for the unit of the geographic coordinates as they are the basis for the geographic searches.
Example

North

4.875

South

-55

East

169.875

West

92

Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Section: Distribution Information

Field Name
Description

Name of the data transfer format(s)

Direction Enter the name of the data transfer format
Example Web Coverage Services
Source From the custodian of the dataset.
Obligation highly recommended

Field Version
Description

Version of the format (date, number, etc.)

Direction Enter version of the format
Example WCS 1.1
Source From the custodian of the dataset.
Obligation highly recommended

Field Transfer options
Description Resource Locator
Direction

Enter information about online resources for the map, such as where a user may download it, etc. This information should include a link, the link type (protocol) and a description of the resource.

Example

http://siss2.anu.edu.au/thredds/wcs/bom/bom.nc/ (OGC-WCS Web Coverage Service (ver 1.1.0)

http://siss2.anu.edu.au/thredds/dodsC/bom/bom.nc (Web address)

Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Section: Data quality info

Field Code
Description

The spatial and temporal reference system used

Direction Describe the spatial and temporal reference system used
Example WGS 1984
Source From the custodian of the dataset.
Obligation highly recommended

Section: Data Quality Info

Field Hierarchy level
Description Hierarchical level of the data specified by the scope
Direction

Specify the hierarchal level of the data (dataset series, dataset, features, attributes, etc.) and provide a general explanation on the production processes (lineage) used for creating the data. The statement element is mandatory if the hierarchical level element is equal to dataset or series. Detailed information on completeness, logical consistency and positional, thematic and temporal accuracy can be directly added into the advanced form.

Example Service: Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case
Source From the custodian of the dataset.
Obligation highly recommended

Field Statement
Description General explanation of the data producer knowledge about the lineage of a dataset
Direction

General explanation of the data producer_s knowledge about the lineage of a dataset

Example Service: Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case
Source From the custodian of the dataset.
Obligation Conditional

Section: Metadata

Field File Identifier
Description File identifier of the metadata to which this metadata is a subset
Direction Auto Populated?
Example 25985126-8508-46eb-be6f-ce872685af90
Source Populated by GeoNetwork
Obligation highly recommended

Field MetaData language
Description Language used for documenting this metadata
Direction Enter Language used for documenting this metadata
Example English
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Character set
Description The metadata character set used.
Direction Enter the metadata character set used.
Example UTF8: 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Hierarchy level
Description Scope to which the metadata applies (see annex H for more information about metadata hierarchy levels) .
Direction Enter the scope for the metadata.
Example Service: Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Date stamp
Description The date that the metadata was created.
Direction Enter the date that the metadata was created.
Example 2011-07-28T15:31:51
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Metadata standard Name
Description The standard that is used for the metadata
Direction Enter the standard that is used for the metadata
Example ISO 19115:2003/19139
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Metadata standard Version
Description The version of the standard that is used for the metadata.
Direction Enter the version of the standard that is used for the metadata.
Example 1.0
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

THREDDS Catalog Harvester

The following describes how to configure the GeoNetwork THREDDS catalog harvester as well as THREDDS catalog.xml so that coverage entries can be automatically added into GeoNetwork. The following guide is based off the current stable built (2.6.4) and there are significant changes made in trunk (currently 2.7)

Catalog.xml: Metadata configuration/insertion

In this type of harvesting, the harvester crawls through the THREDDS catalog, extracting metadata for the datasets and services described in it.

Edit the catalog.xml found in $THREDDS_DIRECTORY/content/data/data/catalog.xml:

   <dataset name="BOM Data">
    <metadata inherited="true">
      <serviceName>all</serviceName>
      <authority>unidata.ucar.edu:</authority>
      <dataType>Grid</dataType>
      <!--Abstract-->
      <documentation type="summary">
         Mean Sea Level Pressure Apr 2009 Australia
      </documentation>
      <documentation type="rights">
         Copyright Commonwealth of Australia 2010, Bureau of Meterology (ABN 92 637 533 532)
         http://www.bom.gov.au
         Please note the Copyright Notice and Disclaimer statements relating to the use of the information provided by the Bureau of Meterology and their site's Privacy and Accessibility statements. Users of these datasets are deemed to have read and accepted the conditions described in the Copyright, Disclaimer, and Privacy statements. Please also note the Acknowledgement notice relating to the use of information on their site.
         Sharing of the grid files as sample grids for demonstration purposes is permitted.
         The Bureau of Meterology will not take the responsibility if the grids are downloaded and manipulated.
         Any use of the grid files must adhere to the Bureau of Meterology's copyright clauses.
      </documentation>
      <creator>
         <name>Bureau of Meterology</name>
         <contact url="http://www.bom.gov.au"
                  email="A.Abhayasinghe@bom.gov.au"
         />
      </creator>
      <publisher>
         <!--Organisation name-->
         <name vocabulary="DIF">Bureau of Meterology</name>
         <contact url="http://www.bom.gov.au/" email="A.Abhayasinghe@bom.gov.au"/>
      </publisher>
      <timeCoverage>
         <end>present</end>
         <duration>7 days</duration>
      </timeCoverage>
    </metadata>
         <datasetScan name="Bom Data" path="bom" dirLocation="content/bom/data" filter=".*\.nc$" />
  </dataset>

The following documentation will step you through GeoNetwork's THREDDS Catalog Harvester configuration:

http://geonetwork-opensource.org/manuals/trunk/users/admin/harvesting/index.html#more-about-harvesting-unidata-dataset-discovery-metadata-with-the-thredds-harvester

The following fields in catalog.xml maps to the fields in a GeoNetwork Entry:
Insert Abstract here Identifcation info - Abstract
Insert Name here Point of Contact - Organisation name
<contact url="Insert Url here" Point of Contact - Online Resource URL
<contact email="Insert email here" Point of Contact - Email
You would still have to manually edit each entry to update the metadata for the above (see manual entry) fields, such as "Point of contact - Individual name"

Reference:

http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/InvCatalogSpec.html#publisher

http://geonetwork-opensource.org/manuals/trunk/users/admin/harvesting/index.html#more-about-harvesting-unidata-dataset-discovery-metadata-with-the-thredds-harvester

http://geonetwork-opensource.org/stable/users/admin/harvesting/index.html

http://geonetwork-opensource.org/manuals/trunk/users/quickstartguide/new_metadata/index.html#entering-metadata-for-your-map

 
Topic revision: r8 - 07 Sep 2011, DerrickWong
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).