Hi all,
I'm trying to get the INSPIRE module in shape before I propose its graduation to official extension (many people use it, it's a shame to have it as an unsupported module). The recent WFS additions did not have tests, and that made it impossible to graduate the module (not enough test coverage) so I added some tests. Looking into it I tried to make a simple schema validation of the output, and to my surprise, it failed due to a mandatory element being absent (!!)
The element is the spatial dataset identifier, which is actually a list of code/namespace pairs: <inspire_dls:SpatialDataSetIdentifier> <inspire_common:Code>mycode</inspire_common:Code>
<inspire_common:Namespace>http://myuri.org</inspire_common:Namespace> </inspire_dls:SpatialDataSetIdentifier> <inspire_dls:SpatialDataSetIdentifier>
<inspire_common:Code>mycode2</inspire_common:Code> <inspire_common:Namespace>http://myuri.org</inspire_common:Namespace> </inspire_dls:SpatialDataSetIdentifier>
The docs I've found around are not telling me much about what this is though. 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)?
All I could find in the download services spec is: The Spatial Data Set Identifier parameter is defined in the Network Service regulation [INS NS] as “The Spatial Data Set Identifier parameter shall contain the Unique Resource Identifier of the Data Set”
The following table demonstrates how the Spatial Data Set Identifier is mapped between the Atom and WFS based Technical Guidance and the corresponding ISO metadata of the spatial data set. 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.
However the above leaves me none the wiser.... Anybody knows more? Cheers Andrea
== GeoServer training in Milan, 6th & 7th June 2013! Visit http://geoserver.geo-solutions.it for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy
phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 ------------------------------------------------------- ------------------------------------------------------------------------------ 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 |
> 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 |
On Mon, Apr 22, 2013 at 1:55 PM, Passmore, James H. <[hidden email]> wrote:
It surely does, thank you :-)
Cheers Andrea == GeoServer training in Milan, 6th & 7th June 2013! Visit http://geoserver.geo-solutions.it for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy
phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 ------------------------------------------------------- ------------------------------------------------------------------------------ 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 |
In reply to this post by geowolf
The spatial dataset identifier is a mandatory element (Unique Resource Identifier) required in the INSPIRE/ISO metadata file created for the dataset.
So, when creating the metadata file for each dataset a Unique Resource Identifier is provided in the form of either RS_Identifier or MD_Identifier. If a value for a codeSpace is provided, then the data type for the identifier should be RS_Identifer, which is substitutable for the usual MD_Identifier
(source: http://inspire.jrc.ec.europa.eu/documents/Metadata/INSPIRE_MD_IR_and_ISO_v1_2_20100616.pdf, page 18)
In RS_identifier form which is preferable(?): <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>daf473d4-275d-48b4-a40b-5101684ff7f7</gco:CharacterString>
</gmd:code> <gmd:codeSpace> <gco:CharacterString>http://www.rae.gr</gco:CharacterString> </gmd:codeSpace> </gmd:RS_Identifier>
or <gmd:identifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>http://www.rae.gr#daf473d4-275d-48b4-a40b-5101684ff7f7</gco:CharacterString>
</gmd:code> </gmd:RS_Identifier> </gmd:identifier> <gmd:identifier> The gmd:code should then map to inspire_common:Code and the the gmd:codeSpace maps to inspire_common:Namespace
At the end, the Download Service metadata should include a list in of the datasets against it operates on. Not sure, but maybe it should be configured at the service level, allowing adjustments similar to WMS (authority, add layer identifiers)
Here is the dls_schema http://inspire.ec.europa.eu/schemas/inspire_dls/ Hope it helps On Mon, Apr 22, 2013 at 6:55 AM, <[hidden email]> wrote: Send Geoserver-devel mailing list submissions to Theodoros Vakkas Head of Geoinformatics Dpt e-mail: [hidden email] Mobile: +30 6936 950 603
Geospatial Enabling Technologies 42 Posidonos Av., 17675, Kallithea, Attica, Greece Tel: +30 (210) 66 64 192 Fax: +30 (210) 66 63 979 ------------------------------------------------------------------------------ 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 |
Free forum by Nabble | Edit this page |