Menu
▾
▴
Re: [GeoNetwork-users] BlueNetMEST Vertical Extent Editor in MarineCommunity Profile
|
From: andrew w. <aw...@me...> - 2010-06-21 22:38:31
|
Andrew,
Thanks, yes the gml id's are random, I just made them up
for the template. It seems the only constraint on them is
that you don't have duplicate gml id's in the same XML
document.
Andrew
----- Original Message -----
From: Andrew Watkins
To: andrew walsh
Cc: geo...@li...
Sent: Tuesday, June 22, 2010 6:50 AM
Subject: Re: [GeoNetwork-users] BlueNetMEST Vertical Extent Editor in MarineCommunity Profile
Thanks, I had come up with something very similar and it was great to have some confirmation.
Are the gml ids intentionally random ? <gml:VerticalCRS gml:id="fdhfjd">
Andrew
Andrew Watkins
Systems Development Team Manager
National Institute Water & Atmospheric Research (NIWA).
>>> On 18 Jun 10 at 12:37 PM, in message <25E2664AD8F342FC8E2D4812901BB3FE@awalsh1>, "andrew walsh" <aw...@me...> wrote:
Hi Andrew,
Yes, I too found errors in this template so I set about correcting it.
A template you could use is attached. It would be suitable for datasets
with depths relative to Mean Sea Level. It has 'msl depth' (EPSG:5715)
as its vertical co-ordinate reference system (See the
EPSG registry site at http://www.epsg-registry.org/, click 'retrieve by
code' and enter
code 5715)
To answer your questions:
Q. Is this correct? Should the template have a default vertical datum, or
should the schema allow verticalDatum to be absent?
A. The vertical datum element is mandatory according to the schema. So its
needed.
>
> 1. What Vertical Datum should be used for depths relative to mean sea
> level?
A. There is a vertical datum for Mean Sea Level. Its named 'mean sea level'
and has
EPSG code 5100. See the EPSG registry site at http://www.epsg-registry.org/,
click 'retrieve by code' and enter code 5100.
Note that EPSG advises to state the context/definition of the msl, they note
in 'Remarks':
"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
knowledge of these
components; for instance "msl at xxx during 19yy".
You could put the msl definition into the <gml:anchorDefinition> as I have
done on the
attached template.
> 2. How do we indication the unit of measure for depth - it may be in
> metres, feet or even fathoms.
A. I have used metres, see the xml attribute gml:uom="m" in the VerticalCS
element
for EPSG:6498. Metres seems to be the official unit of measure for this
VerticalCS,
not sure how you would code feet or fathoms, perhaps a comment is needed if
you used
feet or fathoms.
HTH,
Andrew Walsh
----- Original Message -----
From: "Andrew Watkins" <a.w...@ni...>
To: "geonetwork-users Users" <geo...@li...>
Sent: Friday, June 18, 2010 8:27 AM
Subject: [GeoNetwork-users] BlueNetMEST Vertical Extent Editor in
MarineCommunity Profile
>
> We have a project here using the BlueNetMEST version of geonetwork. Staff
> are entering metadata for datasets and other resources collected during
> the Ocean Survey 2020 Bay of Islands project.
> They are using the Marine Community Profile MCP Template : MCP19139 - CORE
> (+ Vertical Extent) Metadata for Marine Geographic Datasets (v1.3 19139)
>
> If I validate the unedited template I can see the mandatory elements I
> need to enter: date, spatial resolution Equivalent scale, Denominator,
> geographic bounding box, vertical extent min, max and CRS
>
> All but one of these fields have recognisable edit boxes and can be filled
> in except the gml:VerticalCRS which reports ERROR(1)
> org.xml.sax.SAXParseException: cvc-complex-type.2.4.b: The content of
> element 'gml:VerticalCRS' is not complete. One of
> '{"http://www.opengis.net/gml":verticalDatum}' is expected. (Element:
> gml:VerticalCRS with parent element: gmd:verticalCRS)
>
>
>
> At the end of the section there is a prompt Choice [+] and a drop list if
> I choose gml:VerticalDatum I get a new set of fields and although the xsd
> validates I then get a schematron error report.
>
> This is the xml created: <gmd:verticalCRS><gml:VerticalCRS
> gml:id="balderdash"><gml:identifier
> codeSpace="urn:ogc:def:cs:EPSG::">5712</gml:identifier><gml:scope>Australia</gml:scope><gml:usesVerticalCS>
> <gml:VerticalCS gml:id="d24e207a1049886"><gml:identifier
> codeSpace="urn:ogc:def:cs:EPSG::">6499</gml:identifier><gml:axis>
> <gml:CoordinateSystemAxis gml:id="d24e210a1049886"
> gml:uom="m"><gml:identifier
> codeSpace="urn:ogc:def:axis:EPSG::">5711</gml:identifier><gml:axisAbbrev>AHD</gml:axisAbbrev><gml:axisDirection
> codeSpace="urn:ogc:def:axisDirection:EPSG::">up</gml:axisDirection></gml:CoordinateSystemAxis>
> </gml:axis></gml:VerticalCS>
> </gml:usesVerticalCS><gml:verticalDatum>
> <gml:VerticalDatum gml:id="d7e346a1049886"><gml:identifier
> codeSpace=""/><gml:scope/></gml:VerticalDatum>
> </gml:verticalDatum></gml:VerticalCRS></gmd:verticalCRS>
> </gmd:EX_VerticalExtent> </gmd:verticalElement></gmd:EX_Extent>
>
> Is this correct? Should the template have a default vertical datum, or
> should the schema allow verticalDatum to be absent?
>
> 1. What Vertical Datum should be used for depths relative to mean sea
> level?
> 2. How do we indication the unit of measure for depth - it may be in
> metres, feet or even fathoms.
>
>
> Thanks Andrew
>
>
>
>
>
>
> Andrew Watkins
> Systems Development Team Manager
> National Institute Water & Atmospheric Research (NIWA).
>
>
>
> NIWA is the trading name of the National Institute of Water & Atmospheric
> Research Ltd.
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> GeoNetwork-users mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>
>
NIWA is the trading name of the National Institute of Water & Atmospheric Research Ltd.
|