"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 GeoServer wms entry to GeoNetwork

Contents

Overview:

Harvesting is the process of collecting remote metadata and storing them locally for a faster access. This is a periodic process to do, for example, once a week. Harvesting is not a simple import: local and remote metadata are kept aligned. Using some magic, one GeoNetwork node is capable of discovering metadata that have been added, removed or updated in the remote node.

GeoNetwork is able to harvest from the following sources (for more details see below):
  1. Another GeoNetwork node (version 2.1 or above).
  2. An old GeoNetwork 2.0 node.
  3. A WebDAV server.
  4. A CSW 2.0.1 or 2.0.2 catalogue server.
  5. An OAI-PMH server.
  6. An OGC service using its GetCapabilities document. These include WMS, WFS, WPS and WCS services.
GeoNetwork offers a harvest service that, among other, follows a OGC WMS or WFS GetCapabilities URL and transforms the response into an ISO 19139 metadata record. Bear in mind that the resulting ISO metadata record is only as good as the GetCapabilities response and that the metadata can never be entirely ISO 19139 conformant without dummy values due to limitations of the OGC GetCapabilities schema.

GeoNetwork offers a handy user interface to add those "GeoNetwork Harvesting Nodes" and also exposes their functionality through a even handier XML service. See chapter 19.3 on "Harvesting Services" of the GeoNetwork opensource V 2.4 The Complete Manual. Following are my notes on creating an OGC harvesting node through GeoNetwork's harvesting service.

For more information about GeoNetwork harvesting, visit https://twiki.auscope.org/wiki/Grid/GeoNetworkHarvestingInvestigation

Procedure:

The idea here is to correctly configure GeoServer so that when we configure GeoNetwork to harvest information from GeoServer wms, it will extract information from the wms GetCapabilities response.

The three main files we need to configure in GeoServer are

wms.xml

global.xml

featuretype.xml

Below are the fields and its corresponding example or you may refer to https://twiki.auscope.org/wiki/Grid/EarthResourceDeployments.

Section: Identification Info

Field Title
Description Name by which the cited resource is known as
Direction In wms.xml, give your wms a title using the example below
Location wms.xml
Example <title>Geoscience Australia Geotransects Web Map Service</title>
Source From the custodian of the dataset
Obligation highly recommended

Field Abstract
Description Brief narrative summary of the content of the resource.
Direction In wms.xml, Enter some description of the map
Location Wms.xml
Example <abstract>Seismic geotransect data for a strategically selected suite of corridors across Australia that cross major geological features.</abstract>
Source From the custodian of the dataset.
Obligation highly recommended

Field Keywords
Description Commonly used words(s) or formalised word(s) or phrase(s) used to describe the subject
Direction In wms.xml, enter keywords to describe the service
Location Wms.xml
Example

<keywords>

<string>WMS</string>

<string>GEOSERVER</string>

</keywords>

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 In wms.xml, enter any constraints that applies to using the service.
Location Wms.xml
Example <accessConstraints>NONE</accessConstraints>
Source From the custodian of the dataset
Obligation highly recommended

Section: All contact point

Field Contact
Description Party responsible for the information.
Direction In global.xml, enter all mandatory information and others you have at hand for the contact of the person(s) associated with this wms.
Location global.xml
Example

<contact>

<address>100 mystreet st</address>

<addressCity>East Perth</addressCity>

<addressCountry>Australia</addressCountry>

<addressPostalCode>6004</addressPostalCode>

<addressState>Western Australia</addressState>

<contactFacsimile>+61 8 9111 9999</contactFacsimile>

<contactOrganization>Geological Survey of Country X</contactOrganization>

<contactVoice>+61 8 9222 1111</contactVoice>

<contactPosition>Project Leader</contactPosition>

<contactPerson>Michael Jordan</contactPerson>

<contactEmail>Michael.Jordan@countryX.gov.au</contactEmail>

</contact>

Source From the custodian of the dataset
Obligation highly recommended

Section: Related datasets

Field Title
Description Name by which the cited resource is known as
Direction In featuretype.xml, give your wms a title using the example below
Location featuretype.xml
Example <title>Geoscience Australia Seismic Geotransect Data</title>
Source From the custodian of the dataset
Obligation highly recommended

Field Abstract
Description Brief narrative summary of the content of the resource.
Direction In featuretype.xml, Enter some description of the map
Location featuretype.xml
Example <abstract>Seismic geotransect data for a strategically selected suite of corridors across Australia that cross major geological features.</abstract>
Source From the custodian of the dataset
Obligation highly recommended

Field Geographic bounding box
Description Bounding box of the feature layer
Direction In featuretype.xml, populate the bounding area of the feature
Location featuretype.xml
Example

<latLonBoundingBox>

<minx>115.853</minx>

<maxx>145.33</maxx>

<miny>-37.142</miny>

<maxy>-17.08</maxy>

<crs>EPSG:4326</crs>

</latLonBoundingBox>

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

Summary:

Reference:

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

http://lab.usgin.org/node/317

 
Topic revision: r4 - 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).