ELF Data Specifications Presentation to: Author: Date: INSPIRE conference Anja Hopfstock (WP2), Antti Jakobsson (ELF project director) 16 th June 2014
Why extending INSPIRE? INSPIRE too much too little INSPIRE is a huge investment for MS but Not necessarily harmonised content Too many options, no quality criteria, nolevelofdetailcriteria No real cross border solutions ( where practicable Too many delivery methods, not necessarily as a service No rules on access conditions
Why ELF? European users needs! Online access to up to date reference data from authoritative public authorities Interoperable (Harmonised and Cross border) data content Quality and metadata Full coverage of Europe Support common international standards Management of national data through interoperable process INSPIRE helps, but does not provide a solution
WP2 ELF Specifications Master Regional/Global
Be clear about what NMCAs provide Seamless and consistent across borders Consistent between themes Requirements in data provision: LoD, MD, DQ Move from national to European classifications Requirements in data provision: LoD Associations Consistent between resolutions Define core content Use agreed classifications Up to date, maintained and quality ensured Requirements in data provision (update cycle, data quality)
INSPIRE data model/schema status Apr 2014: Approved INSPIRE data model r4618 and GML application schema files Discrepancies between IR, data model and schema files All Annex I themes: Codelist encoding changed from gml:codetype to gml:referencetype Missing GML application schemas handling placeholders and candidates (AU, SU, HY, LC, SR, TN) INSPIRE application schema will be updated & published after MIG decision Extended data models considered as draft Updates of Annex I: overall process for xml schema maintenance in INSPIRE are currently being discussed. INSPIRE MIG will use the revision process to better understand schema life cycle and release strategy requirements.
ELF data model/schema status Published ELF schemas temporary solution due to availability of INSPIRE schemas Concern: current implementation leads to duplication of services scale dependent application schemas Take into account the different starting points and thematic scope for Master and Regional/Global level of detail Be clear in the specification and data model what NMCAs can deliver at each level of detail in order to better accommodate the harmonisation of NMCA data, the development of Geo Tools as well as the ELF Services To specify the product as detailed as possible in the UML (and GML) application schema to ease the reading of the data specification and enable automatic quality control to the largest possible extent Result: a set of UML and GML application schema files for each level of detail Concern: increases the work for implementers as well as data publishers and users as specific tools and software support are needed for each scale
Discussion OptionA INSPIRE/ELF model and schemas To create INSPIRE GML application schema files from the latest INSPIRE UML application schemas and use as foundation for ELF UML and GML application schema files Data modelling approach a set of UML and GML application schema files for each level of detail OptionB To strictly use published INSPIRE UML and GML application schemas as the foundation for ELF A single scale independent UML model for all level of details
From isolated components to integrated, cross border seamless authoritative reference data Thank you!