START Conference Manager    

INSPIRE data usability beyond formal conformance: what’s new one year later.

Fabio Vinci, Giacomo Martirano and Stefania Morrone

(Submission #299)


Abstract

The creation of INSPIRE compliant data and their publication by means of INSPIRE compliant network services are necessary but not sufficient conditions for cross-domain/cross-boundary data interoperability and usability. Examples of technical obstacles hindering the true usability of INSPIRE data were presented at the INSPIRE Conference 2016, together with practical solutions to overcome them. One year later, what’s new on this topic? Is there any new burning issue demanding our attention? Are data providers considering INSPIRE an opportunity to gain efficiency in their business processes rather than just a set of complex legal obligations to fulfil? Are they aware that just following simple recommendations, the usability of their INSPIRE data can significantly increase? Just to provide a few examples, let’s consider the following issues: • Persistent identifiers: gml-id, gml-identifier and inspireId: The creation of persistent identifiers for the spatial objects is one of the most crucial challenges in the implementation of INSPIRE and they are essential for the reuse of INSPIRE data by other communities. The implementers have to guarantee that the identifiers refer unambiguously to the same resources over time. Best practices need to be shared aiming to the definition of commonly agreed encoding rules. • Webservices exposing INSPIRE data: The deployment of compliant network services is not fully supported by current software tools, that are not yet mature to deal correctly with complex data structures. Different gml encoding options may result in different behaviours of the served features. • Code lists extension: How can data providers extend the INSPIRE code lists e.g. adding values commonly used by a thematic community? How can they address code list values published in national registers in their INSPIRE conformant datasets? Best practices and recommendations from the Technical Guidelines & Best Practices for INSPIRE registers and registries need to be implemented. • Metadata: Using network services endpoints in the “reource locator” metadata element, as well as proper keywords, can singificantly increase data discoverability and reuse.

Categories

Topic Area:  [2.5] Technical solutions for optimizing and/or extending the INSPIRE technical framework
Abstract Type:  Oral Presentation

Additional Fields

 
Comments:   Conformance; Data usability; Best practices; Network services: GML encoding; Codelists extension


START Conference Manager (V2.61.0 - Rev. 4840)