Skip to end of banner
Go to start of banner

AusSeabed Local Hub Technical Requirements

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

The Local Hub must provide three services:

  • publication of ISO19115-3 metadata through a catalogue service - nominally GeoNetwork

  • publication of Web Mapping Service and Web Coverage Service according to AusSeabed protocols

  • direct download of Local Hub products through HTTP protocol

The Local Hub must also provide a description of their holdings in an Excel format that can be read by the Exploring For The Future Portal.

Publication of ISO19115-3 metadata

Most large organisations that distribute spatial data catalogue the existence of that data using a metadata catalogue system such as GeoNetwork. AusSeabed Local Hubs must provide a catalogue that can be harvested by AODN (and others) using GeoNetwork.

General Background

There are several metadata standards for describing spatial data, but ISO19115 continues to grow in popularity. The standard itself provides a wide range of flexibility in the forms of XML that it accepts. It is rarely possible for a system to understand the semantics of every component of XML that meets the standard. Likewise, the standard permits different ways of representing the same information. What has emerged are profiles of the ISO19115 that have agreed meaning among subsets of the spatial community. These can also include variations such as additional mandatory fields. In AusSeabed’s case the most notable is the marine community profile (ISO19115-3) that is designed for marine purposes (most notably documenting marine specimen samples). Worthy of similar mention is GA’s Community Profile that forces some metadata tags to be mandatory.

Technical Details

Geonetwork provides at least three method of editing metadata: a) a simple interface; b) the full interface; and c) an XML editor. Most metadata can be entered in the simple interface; however, a number of fields require the full editing interface or XML editor (or import) including:

Attribute

Location in XML

Interface

Abstract

IdentificationInfo/Abstract

Simple

Title

IdentificationInfo/Citation/Title

Simple

Start Date

IdentificationInfo/Extent/TemporalExtent/TimePeriod/BeginPosition

Simple

End Date

IdentificationInfo/Extent/TemporalExtent/TimePeriod/EndPosition

Simple

Vessel

Acquisition Information/Platform/Identifier

Full/XML

Instrument

Acquisition Information/Platform/Instrument/Identifier

Full/XML

Vessel and instrument should also link to a valid vocabulary entry in a vocabulary server. E.g.

<mcc:code>
<gcx:Anchor xlink:href="http://vocab.nerc.ac.uk/collection/C17/current/09SS">Southern Surveyor</gcx:Anchor>
</mcc:code>
  • No labels