> What I'm wondering most is, is it something that should be configured at a
global level (WFS admin panel), or is it more something that it makes sense
to configure on a layer by layer basis (layer config panel)?
As this is really metadata about the service, I would expect that that you would configure it at the global layer and not on a layer by layer basis. The identifiers in the SpatialDataSetIdentifier section relate to dataset metadata identifiers (for each dataset operated on by the service).
> The Spatial Data Set Identifier parameter maps to either the RS_Identifier or the MD_Identifier
depending on what type of Spatial Data Set Identifier is used in the corresponding ISO metadata.
An RS_Identifier section of a dataset metadata record might look like:
<gmd:identifier>
<gmd:RS_Identifier>
<gmd:code>
<gco:CharacterString>13480203</gco:CharacterString>
</gmd:code>
<gmd:codeSpace>
<gco:CharacterString>
http://data.bgs.ac.uk/id/dataHolding</gco:CharacterString>
</gmd:codeSpace>
</gmd:RS_Identifier>
</gmd:identifier>
So I assume that would correspond to something like:
<inspire_dls:SpatialDataSetIdentifier>
<inspire_common:Code>13480203</inspire_common:Code>
<inspire_common:Namespace>
http://data.bgs.ac.uk/id/dataHolding</inspire_common:Namespace>
</inspire_dls:SpatialDataSetIdentifier>
An MD_Identifier section of a dataset metadata record might look like:
<gmd:identifier>
<gmd:MD_Identifier>
<gmd:code>
<gco:CharacterString>9df8df51-6342-37a8-e044-0003ba9b0d98</gco:CharacterString>
</gmd:code>
</gmd:MD_Identifier>
</gmd:identifier>
So I assume that would correspond to something like:
<inspire_dls:SpatialDataSetIdentifier>
<inspire_common:Code>9df8df51-6342-37a8-e044-0003ba9b0d98</inspire_common:Code>
<inspire_common:Namespace></inspire_common:Namespace>
</inspire_dls:SpatialDataSetIdentifier>
Hope this helps
,,,
James (o o)
======================oOO==(_)==OOo===
James Passmore
GIS and WWW Specialist
Geoscience Products and Services,
British Geological Survey,
http://www.bgs.ac.uk/+44 (0)115 936 3125
@nmtoken
This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Locked
