Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Hi GN and ANZLIC metadata lists,
I attach 2 templates which may be useful resource should you need to describe
Vertical Extent of a dataset (min/max) in metres relative Mean Sea Level (MSL).
would apply for marine (oceanic) data.
The ISO19139 template follows the standard ISO19139 profile. The ISO19139-MCP
template is suitable for the using the Austalian Marine Community profile (MCP).
XML in the template is using codeSpace attribute identifiers in URN form taken
the EPSG registry at http://www.epsg-registry.org/ e.g the codeSpace for
The vertical extent element uses a Vertical CRS of 'mean sea level depth' which
EPSG code: EPSG::5715.
This Vertical CRS in turn uses a Vertical CS of EPSG::6498 which uses a
Coordinate System Axis named 'Gravity-related depth' EPSG::9905.
A Vertical Datum of 'mean sea level' EPSG::5100 is used. This is a generic
datum with applicable area of whole world. MSL is usually a tidal datum which is
the arithmetic mean of hourly heights of the sea
at the tidal station observed over a period of time (preferably 19 years).
However note that for code 5100 EPSG say in the 'remarks' that:
"msl has geographic and temporal components. Users are advised to not use this
generic vertical datum but to define specific instances of msl based on
of these components; for instance "msl at xxx during 19yy".
Either template (ISO19139 or ISO1939-MCP) may be imported directly into the
ANZMEST 1.4.x version of Geonetwork or the ISO19139 template only into the
geonetwork 2.6.4. On import specify the type as 'Template'. After import it will
available for use from the 'New Metadata' link.
PS: Thanks to JH for advice on the correct URN syntax to use with the