1. Lessons learnt from ELF
Presentation based on earlier presentations given on WP2 and WP3 meetings.
Eionet NRC EIS meeting 2015
Heidi Vanparys
26th of November 2015
22 February, 2019

2. Lessons learnt from ELF
What is ELF?
Extension of INSPIRE data specifications
Code lists
Validation of services
Topographic BaseMap
Some conclusions
22 February, 2019

3. European Location Framework
History of ELF
22 February, 2019

4. European Spatial Data Infrastructure with a Best Practice Network
22 February, 2019

5. Co-funded by the European Commission September 2008 – February 2011
Project
Co-funded by the European Commission
September 2008 – February 2011
Consortium of data providers, developers, academics and commercial software, companies
22 February, 2019

6. ELF, INSPIRE og Geodatabanken
Products:
EuroDEM (ground surface topography)
EuroBoundaryMap
EuroRegionalMap
EuroGlobalMap (available as ‘Opendata’)
ELF, INSPIRE og Geodatabanken
22 February, 2019

7. 22 February, 2019

8. 22 February, 2019

9. 22 February, 2019

10. Project & infrastructure/platform Co-funded by the European Commission
March 2013 –
Consortium of data providers, developers, academics and commercial software, companies
“One reference geoinformation source for Europe”
Project not yet finished: no final conclusions or ”lessons learnt” yet
many of the same partners
22 February, 2019

11. 22 February, 2019

12. To provide E.L.F data specifications based on INSPIRE specifications
WP2 (Anja Hopfstock, BKG, Germany (also facilitator of Topographic & Cadastral Data Cluster)):
To provide E.L.F data specifications based on INSPIRE specifications
To provide data maintenance and processing specifications for the geo-tools
To provide product and service specifications for the E.L.F services
WP3 (Roy Mellum, Kartverket, Norge):
To provide data via national services (based on E.L.F specifications)
To provide secured, cascaded E.L.F services based on the national services.
To provide an Open Source based cloud service platform.
22 February, 2019

13. Deliverables ELF Administrative BaseMap ELF Topographic BaseMap
ELF Cadastral Index Map
Web Feature Services from NMCA’s through cascading service
ELF Geolocator
...
ELF Basemap: view service supporting multiple scale levels
Web Feature Services from the NMCA’s
ELF Geolocator: geocoding service based on AD, EG and AU
ELF Cadastral Index Map: view service showing footprints of cadastral parcels + AU, AD, BU + links to national services for more information
22 February, 2019

14. 22 February, 2019

15. Extension of INSPIRE data specifications
22 February, 2019

16. INSPIRE Generic Conceptual Model
22 February, 2019

17. Types of extensions to INSPIRE
Identification of
Extensions
Data Specification
Data Model
Corresponding concepts
Common part
Data Quality conformance criteria
Simple inheritance / specialisation
Criteria for data capture
concepts present in INSPIRE but missing in existing data
Restricted part
Application schema excluded from ELF
Feature types ignored
Data types, attributes, associations
constraint
concepts present in existing data but missing in INSPIRE
Extended part
New theme
Add application schema
New feature types
Add feature type
New data types or attributes
Add data type or attribute
New associations
Add association
11th of March 2015

18. ELF UML modelling principles
To achieve INSPIRE compliancy in data modelling the following principles should be observed:
Extensions shall not
Change the specification but normatively reference it with all its requirements
Set any additional requirements that break any requirement of the INSPIRE data specification
Add concepts that overlap with existing INSPIRE concepts
Make a pure INSPIRE implementation non-conformant to the ELF specifications
22 February, 2019

19. ELF UML modelling principles
To achieve INSPIRE compliancy in data modelling the following principles should be observed:
Extensions may
Add new application schemas importing INSPIRE or other schemas as needed
Add new types and constraints in the new application schemas
extend INSPIRE code lists if not centrally managed
See more on
22 February, 2019

20. Define additional attributes Add constraints
Subtype all INSPIRE feature types valid for ELF (topographic reference data)
Define additional attributes
Add constraints
Define new ELF classifiers (feature types, data types, code lists)
Associate feature types (not in figure)
Note that the additional attributes are optional
11th of March 2015

21. Code lists
22 February, 2019

22. Code lists: issues
How to implement code lists and a code list registry?
How to extend existing INSPIRE code lists?
22 February, 2019

23. Encoding Simple Knowledge Organization System (SKOS)
RDF vocabularies provide a schema for the Web of Data
like a relation database has a schema
like an XML document can have a schema (XSD)
OWL = Web Ontology Language → ontologies
SKOS = Simple Knowledge Organization System → thesauri, taxonomies, classification schemes, subject heading lists, …
Inline with what is happening in INSPIRE and in the geospatial community in general
22 February, 2019

24. Tools + SKOSEd plugin ShapeChange Known in the geospatial community
Other open source tools
Commercial applications
ShapeChange
22 February, 2019

25. See more on https://service. projectplace. com/pub/english
22 February, 2019

26. 22 February, 2019

27. 22 February, 2019

28. Minimal configuration
Best Practice Recipes for Publishing RDF Vocabularies:
22 February, 2019

29. Extensions of code lists
22 February, 2019

30. Extension of code lists
Explicitly state what INSPIRE concepts are used as well in ELF code lists:
<rdf:RDF [...] xml:base="
[...]
<skos:Concept rdf:about="
<skos:inScheme rdf:resource="NaturalObjectTypeValue" />
<skos:topConceptOf rdf:resource="NaturalObjectTypeValue" />
</skos:Concept>
22 February, 2019

31. Relationship between code lists
How to express. Ongoing work and discussions in MIG-T, the INSPIRE Maintenance Group. One relationship type for all?
22 February, 2019

32. Validation tools for NMCA’s
Test
Validator
Tools used
Hosted by
URL
OGC conformance
OGC CITE Tests for WFS 2.0, GML 3.2, WMS 1.3, WMTS 1.0
TEAM Engine, Test NG
OGC, local tests possible
Service metadata
INSPIRE Geoportal Metadata Validator
JRC
INSPIRE/ELF requirements on services, schemas and GML encoding
ETF WebApp configured with INSPIRE/ELF-specific tests
ETF, soapUI, BaseX
interactive instruments, local tests possible
22 February, 2019

33. 22 February, 2019

34. Validation of services
22 February, 2019

35. 22 February, 2019

36. 22 February, 2019

37. 22 February, 2019

38. 22 February, 2019

39. 22 February, 2019

40. https://github.com/Geonovum/etf-test-projects-inspire
22 February, 2019

41. parameter outputFormat removed
22 February, 2019

42. 22 February, 2019

43. 22 February, 2019

44. Experience so far 1st requirement: data should follow the schema
not easy to understand the errors found
in-depth knowledge of WFS 2.0 specification needed
tools cannot handle authentication layers
many of the issues are platform-specific and cannot be solved by the NMCA’s
22 February, 2019

45. Topographic BaseMap
22 February, 2019

46. Zoom levels 2K to 72 K : (mainly) national data
Zoom levels 144K to 40 M : EG products
BaseMap is a pyramid of digital maps displaying ELF based data, at different levels of zoom
Content: themes EL, AU, BU, LC, HY, TN and GN
Themes AD and CP to be dealt by ELF Cadastre
WMTS service build on a cascade of national ELF Basemap WMS’s
Main use cases: Consultation & Background map for applications
Zoom levels 2K to 72 K : (mainly) national data

47. 22 February, 2019

48. 22 February, 2019

49. BaseMap model
Only geometry + attributes relevant for visualisation/cartography
22 February, 2019

50. Source data for BaseMap:option 1 (use ELF data and simplify it)
NMCA data
Harmonised
ELF data (GML)
Flattening and simplification process
Transformation process
WFS
NMCA data
EuroGeographic products
Common portrayal rules (SLD)
Centralized
Harmonised
BaseMap data (format xxx)
WMTS
Cascaded
WMS
National
WMS
Based on Dominique Laurents presentation at the 4th wp3 workshop

51. Common portrayal rules (SLD)
Source data for BaseMap: option 2 (transform existing data to BaseMap model)
Common portrayal rules (SLD)
NMCA data
Centralized
Harmonised
BaseMap data (format xxx)
Transformation process
National
WMS
Cascaded
WMS
NMCA data
EuroGeographic products
WMTS
Based on Dominique Laurents presentation at the 4th wp3 workshop

52. Precise mapping WFS
22 February, 2019

53. Precise mapping BaseMap
22 February, 2019

54. Source data for BaseMap: option 3 (use existing data and translate SLD)
NMCA data
Centralized
National
WMS
Cascaded
WMS
WMTS
NMCA data
Portrayal rules in national terminology
Common portrayal rules (SLD) in ELF/BaseMap terminology
Translation process
Based on Dominique Laurents presentation at the 4th wp3 workshop

55. Conclusions
22 February, 2019

56. Disclaimer
The ELF project has not finished yet, so no official conclusions, these are my personal conclusions.
22 February, 2019

57. ELF WP2 Thematic experts and GI infrastructure experts needed
Pure INSPIRE implementation must be ELF compliant in order to gain acceptance amongst all the ELF partners
Dependent on the status of INSPIRE GML application schemas
still a lot of unanswered questions within INSPIRE
code lists
encoding of voidable reasons
...
Final specifications should be ready as soon as possible, partners are hesitating to implement draft specifications
status GML application schemas: not yet final version / not yet published
22 February, 2019

58. Danish Geodata Agency
Thematic experts and GI infrastructure experts needed
Processes need to be integrated in the infrastructure of the organisation in order to be sustainable, avoid one shot tasks
22 February, 2019

59. More about ELF http://elfproject.eu/ http://locationframework.eu/
22 February, 2019