START Conference Manager    

Mapping Between Community and Inspire Data Specifications – An example from the EMODNET community

Keiran Millard

(Submission #453)


Abstract

This papers looks at a practical example of mapping between a data specification used by the EMODNET community and the equivalent Inspire Data Specification. The example highlights many of the decisions that need to be taken during the mapping process and various approaches that can be taken to address the problem of poor matching between dataset features. During 2015-2016, the work of the marine and atmospheric Inspire thematic clusters has highlighted the largest challenge faced by data providers in complying with Inspire is understanding how to map their data specification to an equivalent Inspire specification. Issues that can make this is difficult process can include: • Matching the scope to an equivalent Inspire scope, especially when the source datasets map to more than one Inspire Theme. • Matching features and attributes to Inspire equivalents, especially when the source dataset contains features and attributes that extend the Inspire data model; or are defined differently Whilst approaches to deal with these above situations are established, it is beneficial to provide a tangible, practical example of these solutions in practice to provide guidance to others looking to undertake similar exercises. Importantly, this also illustrates the role of Inspire in solving issues if data interopability. Inspire is not a ‘one size fits all’ solution for data interoperability, but part of wider framework for the management of environmental data. As such data policy decisions as well as technical considerations feature in developing an optimal data mapping strategy.

Categories

Topic Area:  [2.6] Challenges in creating spatial environmental (reference) data sets
Abstract Type:  Oral Presentation

Additional fields

Comments:   Robert has asked Cluster facilitators to submit a paper related to issues in their community

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