Difference between revisions of "INSPIRE"

From OSGeo
Jump to navigation Jump to search
Line 10: Line 10:
 
=== The INSPIRE Components ===
 
=== The INSPIRE Components ===
 
There are five major components:  
 
There are five major components:  
−
# Metadata. Well, we know that [http://www.slideshare.net/arnulfchristl/the-potential-of-metadata-geoweb-2010 Metadata is data] and so on. Intriguing topic. The current interpretation of INSPIRE clobbered metadata long enough with ISO profiles to almost kill it.  
+
# [http://inspire.ec.europa.eu/metadata/6541 Metadata]. Well, we know that [http://www.slideshare.net/arnulfchristl/the-potential-of-metadata-geoweb-2010 Metadata is data] and so on. Intriguing topic. The current interpretation of INSPIRE clobbered metadata long enough with ISO profiles to almost kill it.  
−
# Network Services. Performance, uptime, bindings, etc. & still under work.
+
# [http://inspire.ec.europa.eu/spatial-data-services/580 Network Services]. Performance, uptime, bindings, etc.
 
#* Discovery Services. Probably something like Catalog Services but it is as yet unclear why they should: ...making it possible to search for spatial data sets and services on the basis of the content of the corresponding metadata and to display the content of the metadata
 
#* Discovery Services. Probably something like Catalog Services but it is as yet unclear why they should: ...making it possible to search for spatial data sets and services on the basis of the content of the corresponding metadata and to display the content of the metadata
 
#* View Services.  Straight forward: Digital maps served through WMS 1.3 / ISO 19128. ...making it possible, as a minimum, to display, navigate, zoom in/out, pan, or overlay viewable spatial data sets and to display legend information and any relevant content of metadata;
 
#* View Services.  Straight forward: Digital maps served through WMS 1.3 / ISO 19128. ...making it possible, as a minimum, to display, navigate, zoom in/out, pan, or overlay viewable spatial data sets and to display legend information and any relevant content of metadata;
 
#* Download Services. Straight forward: Digital data served through WFS 2.0 / ISO 19142) -> see [http://inspire-forum.jrc.ec.europa.eu/mod/groups/topicposts.php?topic=3309&group_guid=2484 this discussion] ...enabling copies of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly;
 
#* Download Services. Straight forward: Digital data served through WFS 2.0 / ISO 19142) -> see [http://inspire-forum.jrc.ec.europa.eu/mod/groups/topicposts.php?topic=3309&group_guid=2484 this discussion] ...enabling copies of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly;
−
#* Transformation Services. Rubbish. The original idea was that a web service would be able to transform existing data by mamber staed on-the-fly for further processing. This is usually done offline in the basement on number crunchers. ...enabling spatial data sets to be transformed with a view to achieving interoperability
+
#* Transformation Services. The original idea was that a web service would be able to transform existing data on-the-fly for further processing. This is usually done offline in the basement on number crunchers. ...enabling spatial data sets to be transformed with a view to achieving interoperability
 
#* Services ... allowing spatial data services to be invoked. (I never really got this one?)
 
#* Services ... allowing spatial data services to be invoked. (I never really got this one?)
−
# Data and Service Sharing. Licenses, copyright, all the fun stuff that prevents us from using data in our software.  
+
# [http://inspire.ec.europa.eu/data-and-service-sharing/62 Data and Service Sharing]. Licenses, copyright, all the fun stuff that prevents us from using data in our software.  
−
# Data Specification. The tricky bit is the harmonization of data that is need prior to setting up the actual service. This currently requires lots of transformations with GML 3.2.1 (and not enough software packages supporting 3.2.1 does not help either)
+
# [http://inspire.ec.europa.eu/data-specifications/2892 Data Specification]. The tricky bit is the harmonization of data that is need prior to setting up the actual service. This currently requires lots of transformations with GML 3.2.1 (and not enough software packages supporting 3.2.1 does not help either)
−
# Reporting and Monitoring. This is more domain specfic to EU public administrations. Not clear yet whether any software will be involved in this. But the monitoring services will be of help to control things.
+
# [http://inspire.ec.europa.eu/monitoring-and-reporting/69 Reporting and Monitoring]. This is more domain specfic to EU public administrations. Not clear yet whether any software will be involved in this. But the monitoring services will be of help to control things.
  
 
=== Scope ===
 
=== Scope ===

Revision as of 06:27, 14 June 2017

INSPIRE is a European-based approach at solving interoperability issues for geospatial data. Join the INSPIRE Mailing list.

Introduction

INSPIRE (Infrastructure for Spatial Information in Europe) is an initiative launched by the European Commission and developed in collaboration with EU Member States and accession countries. It aims at making available relevant, harmonized and qualitative geographic information to support formulation, implementation, monitoring and evaluation of Community policies with a territorial dimension or impact. INSPIRE intends to trigger the creation of a European spatial data infrastructure (SDI) that delivers to the users integrated spatial information services linked by common standards and protocols. The Directive came into force on 15 May 2007 and will be implemented in various stages, with full implementation required by 2021.

The INSPIRE geoportal provides the means to search for spatial data sets and spatial data services, and subject to access restrictions, to view spatial data sets from the EU Member States within the framework of the INSPIRE Directive.[1]

The INSPIRE Components

There are five major components:

  1. Metadata. Well, we know that Metadata is data and so on. Intriguing topic. The current interpretation of INSPIRE clobbered metadata long enough with ISO profiles to almost kill it.
  2. Network Services. Performance, uptime, bindings, etc.
    • Discovery Services. Probably something like Catalog Services but it is as yet unclear why they should: ...making it possible to search for spatial data sets and services on the basis of the content of the corresponding metadata and to display the content of the metadata
    • View Services. Straight forward: Digital maps served through WMS 1.3 / ISO 19128. ...making it possible, as a minimum, to display, navigate, zoom in/out, pan, or overlay viewable spatial data sets and to display legend information and any relevant content of metadata;
    • Download Services. Straight forward: Digital data served through WFS 2.0 / ISO 19142) -> see this discussion ...enabling copies of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly;
    • Transformation Services. The original idea was that a web service would be able to transform existing data on-the-fly for further processing. This is usually done offline in the basement on number crunchers. ...enabling spatial data sets to be transformed with a view to achieving interoperability
    • Services ... allowing spatial data services to be invoked. (I never really got this one?)
  3. Data and Service Sharing. Licenses, copyright, all the fun stuff that prevents us from using data in our software.
  4. Data Specification. The tricky bit is the harmonization of data that is need prior to setting up the actual service. This currently requires lots of transformations with GML 3.2.1 (and not enough software packages supporting 3.2.1 does not help either)
  5. Reporting and Monitoring. This is more domain specfic to EU public administrations. Not clear yet whether any software will be involved in this. But the monitoring services will be of help to control things.

Scope

Datasets in scope of INSPIRE are ones which come under one or more of INSPIRE theme.[2] The INSPIRE Directive defines 34 spatial data themes needed for environmental applications, grouped in 3 Annexes. The themes and links to more information are listed on the INSPIRE website

OSGeo's involvement

There is no coordinated effort at involving OSGeo as an organization in the INSPIRE initiative but many OSGeo projects are already tied into processes and the emerging INSPIRE architecture. A formal meeting of OSGeo representatives with people (from JRC) involved in INSPIRE was planned for the end of 2008 but never happened. In 2010, JRC and OSGeo joined forces to make an Open Source Mash-up at the INSPIRE conference possible.

FIT/GAP analysis

How good does Open Source GIS software fit into the INSPIRE picture? Can it be used as a software stack to build INSPIRE SDI's? It would be interesting to make a fit/gap analysis between what the INSPIRE standards require and what the OSGeo stack provides. Also, a plan could be made up to fill in the gaps (in time). The reasoning behind this is that the regular customers will not be able to make this analysis by themselves, so it would be good to have something written up.

Who is interested in collaborating in such a fit/gap analysis?


What is already available?

For a more detailed list of INSPIRE Open Source tools, reference is made to the INSPIRE tools inventory wiki page.

JRC is also providing INSPIRE tools to implementers and users:

What is still missing?

For a more detailed list of missing functionalities, in the realm of INSPIRE, in existing Open Source tools, reference is made to the INSPIRE tools inventory wiki page.

  • Comprehensive tutorial / how to / white paper on security of SDIs.
  • An INSPIRE-flavoured version of the OSGeoLive environment would be beneficial for them who are confronted with INSPIRE and could also be used to promote OSGeo.
  • To illustrate the use of Open Source software packages in the context of INSPIRE implementations and usage, it would be helpful to provide an INSPIRE sample dataset. See INSPIRE data experiments for concrete actions on this.
  • Some stuff emerging now through ESDIN deliverables. Find more information on the requirements in the ESDIN Wiki.
  • CSW INSPIRE extensions in GeoServer

What is in progress?

Presentations

Use Cases


Conference

See also

Blogosphere
OSGeo INSPIRE Initiatives
  1. ↑ http://inspire-geoportal.ec.europa.eu/
  2. ↑ http://inspire.ec.europa.eu/data-specifications/2892
Retrieved from "http://wiki.osgeo.org/w/index.php?title=INSPIRE&oldid=107183"