INSPIRE data usability beyond formal conformance Giacomo Martirano www.epsilon-italia.it
1/22
INSPIRE data usabilitybeyond formal conformance
Giacomo Martiranowww.epsilon-italia.it
2/22
Impacts of metadata editing on data discovery
Impacts of correct encoding option on data display in GIS environment
Impacts of a «low committed» mapping on data exploitation by user communities
Outline
3/22Impacts of metadata editing on data discovery
4/22Impacts of metadata editing on data discovery
https://msdi.data.gov.mt/geoserver/MITA_WMS/wms?service=WMS&version=1.3.0&request=GetCapabilities
5/22Impacts of metadata editing on data discovery
https://msdi.data.gov.mt/data/HB.HabitatDistribution.gml
6/22Impacts of metadata editing on data discovery
7/22
Selecting the correct encoding option in your transformation prevents yourharmonised data to become not accessible
Paying attention to CRS encoding in yourtransformation avoids displaying yourharmonised data in the wrong place
Impacts of correct encoding option on data display in GIS environment
8/22
‘by reference’ mapping option :the LandCoverUnits are addressed by means of xlink:href each LandCoverUnit will become a stand-alone feature member in the final INSPIRE GML dataset.
LC encoding «by reference»
9/22LC encoding «by reference»
10/22
Embedded encoding “By reference” encoding
LC encoding «by reference»
11/22
Coordinate Reference System identifiers: Implementation proposed by the
Technical Guidelines (see A.8.2 CRS http URI test: ) require the use of EPSG identifiers in the form of http URIs. Currently some GIS software tools do not correctly handle EPSG identifiers, above all in the form of http URIs and therefore use the default (Lon Lat) order causing incorrect display of GML files in GIS maps
CRS ENCODING
12/22
urn:ogc:def:crs:EPSG::4258 http://www.opengis.net/def/crs/EPSG/0/4258
CRS ENCODING
13/22
Impacts of partial data validation on data exploitation by user communities
Impacts of mis-used voidable attributes on data exploitation by user communities
Impacts of a «low committed» mapping on data exploitation by user communities
14/22Impacts of a «low committed» mapping on data exploitation by user communities
15/22Impacts of a «low committed» mapping on data exploitation by user communities
16/22Impacts of a «low committed» mapping on data exploitation by user communities
17/22Impacts of a «low committed» mapping on data exploitation by user communities
18/22Impacts of a «low committed» mapping on data exploitation by user communities
19/22Impacts of a «low committed» mapping on data exploitation by user communities
20/22
This gml passes schema validation tests!!!
Impacts of a «low committed» mapping on data exploitation by user communities
21/22
Don’t let your conformant dataset feel like an empty box!
Share all available information …
‘Voidable’ is not ‘Optional’:
Impacts of a «low committed» mapping on data exploitation by user communities
22/22
THANK YOU!
Giacomo Martiranog.martirano@epsilon-italia.itwww.epsilon-italia.itwww.inspire-helpdesk.eu