Changes to the INSPIRE cchemes: What do they mean and how to adapt?

Fecha de la noticia: 02-12-2024

map of Europe

In February 2024, the European geospatial community took a major step forward with the first major update of the INSPIRE implementation schemes in almost a decade. This update, which generates version 5.0 of the schemas, introduces changes that affect the way spatial data are harmonised, transformed and published in Europe. For implementers, policy makers and data users, these changes present both challenges and opportunities.

In this article, we will explain what these changes entail, how they impact on data validation and what steps need to be taken to adapt to this new scenario.

What is INSPIRE and why does it matter?

The INSPIRE Directive (Infrastructure for Spatial Information in Europe) determines the general rules for the establishment of an Infrastructure for Spatial Information in the European Community based on the Member States' Infrastructures. Adopted by the European Parliament and the Council on March 14, 2007 (Directive 2007/2/EC), it is designed to achieve these objectives by ensuring that spatial information is consistent and accessible across EU member countries.

A key element of INSPIRE is the “application schemas”.These schemas define how data should be structured to comply with INSPIRE standards, ensuring that data from different countries are compatible with each other. In addition, the schemes make data validation easier with official tools, ensuring their quality and compliance with European standards.

What changes with the 5.0 upgrade?

The transition to version 5.0 brings significant modifications, some of which are not backwards compatible. Among the most notable changes are:

  • Removal of mandatory properties: this simplifies data models, but requires implementers to review their previous configurations and adjust the data to comply with the new rules.
  • Renaming of types and properties: with the update of the INSPIRE schemas to version 5.0, some element names and definitions have changed. This means that data that were harmonised following the 4.x schemas no longer exactly match the new specifications. In order to keep these data compliant with current standards, it is necessary to re-transform them using up-to-date tools. This re-transformation ensures that data continues to comply with INSPIRE standards and can be shared and used seamlessly across Europe. The complete table with these updates is as follows

Schema

Description of the change

Type of change

Latest version

ad

Changed the data type for the "building" association of the entity type Address.

Non-disruptive

v4.1

au

Removed the enumeration from the schema and changed the encoding of attributes referring to enumerations.

Disruptive

v5.0

BaseTypes.xsd

Removed VerticalPositionValue enumeration from BaseTypes schema.

Disruptive

v4.0

ef

Added a new attribute "thematicId" to the AbstractMonitoringObject spatial object type

Non-disruptive

v4.1

el-cov

Changed the encoding of attributes referring to enumerations.

Disruptive

v5.0

ElevationBaseTypes.xsd

Deleted outline enumeration.

Disruptive

v5.0.

el-tin

Changed the encoding of attributes referring to enumerations.

Disruptive

v5.0

el-vec

Removed the enumeration from the schema and changed the encoding of attributes referring to enumerations.

Disruptive

v5.0

hh

Added new attributes to the EnvHealthDeterminantMeasure type, new entity types and removed some data types.

Disruptive

v5.0

hy

Updated to version 5.0 as the schema imports the hy-p schema which was updated to version 5.

Disruptive y non-disruptive

v5.0

hyp

Changed the data type of the geometry attribute of the DrainageBasin type.

Disruptive y non- disruptive

v5.0

lcv

Added association role to the LandCoverUnit entity type.

Disruptive

v5.0

mu

Changed the encoding of attributes referring to enumerations.

Disruptive

v4.0

nz-core

Removed the enumeration from the schema and changed the encoding of attributes referring to enumerations.

Disruptive

v5.0

ObservableProperties.xsd

Removed the enumeration from the schema and changed the encoding of attributes referring to enumerations.

Disruptive

v4.0

pf

Changed the definition of the ProductionInstallation entity type.

Non-disruptive

v4.1

plu

Fixed typo in the "backgroudMapURI" attribute of the BackgroundMapValue data type.

Disruptive

v4.0.1

ps

Fixed typo in inspireId, added new attribute, and moved attributes to data type.

Disruptive

v5.0

sr

Changed the stereotype of the ShoreSegment object from featureType to datatype.

Disruptive

v4.0.1

su-vector

Added a new attribute StatisticalUnitType to entity type VectorStatisticalUnit

Non-disruptive

v4.1

tn

Removed the enumeration from the schema and changed the encoding of attributes referring to enumerations.

Disruptive

v5.0

tn-a

Changed the data type for the "controlTowers" association of the AerodromeNode entity type.

Non-disruptive

v4.1

tn-ra

Removed enumerations from the schema and changed the encoding of attributes referring to enumerations.

Disruptive

v5.0

tn-ro

Removed enumerations from the schema and changed the encoding of attributes referring to enumerations.

Disruptive

v5.0

tn-w

Removed the abstract stereotype for the entity type TrafficSeparationScheme. Removed enumerations from the schema and changed the encoding of attributes referring to enumerations

Disruptive y non disruptive

v5.0

us-govserv

Updated the version of the imported us-net-common schema (from 4.0 to 5.0).

Disruptive

v5.0

us-net-common

Defined the data type for the authorityRole attribute. Changed the encoding of attributes referring to enumerations.

Disruptive

v5.0

us-net-el

Updated the version of the imported us-net-common schema (from 4.0 to 5.0).

Disruptive

v5.0

us-net-ogc

Updated the version of the imported us-net-common schema (from 4.0 to 5.0).

Disruptive

v5.0

us-net-sw

Updated the version of the imported us-net-common schema (from 4.0 to 5.0).

Disruptive

v5.0

us-net-th

Updated the version of the imported us-net-common schema (from 4.0 to 5.0).

Disruptive

v5.0

us-net-wa

Updated the version of the imported us-net-common schema (from 4.0 to 5.0).

Disruptive

v5.0

Figure 1. Latest INSPIRE updates.

  • Major changes in version 4.0: although normally a major change in a schema would lead to a new major version (e.g. from 4.0 to 5.0), some INSPIRE schemas in version 4.0 have received significant updates without changing version number. A notable example of this is the Planned Land Use (PLU) scheme. These updates imply that projects and services using the PLU scheme in version 4.0 must be reviewed and modified to adapt to the new specifications. This is particularly relevant for those working with XPlanung, a standard used in urban and land use planning in some European countries. The changes made to the PLU scheme oblige implementers to update their transformation projects and republish data to ensure that they comply with the new INSPIRE rules.

Impact on validation and monitoring

Updating affects not only how data is structured, but also how it is validated. The official INSPIRE tools, such as the Validador, have incorporated the new versions of the schemas, which generates different validation scenarios:

  • Data conforming to previous versions: data harmonised to version 4.x can still pass basic validation tests, but may fail specific tests requiring the use of the updated schemas.
  • Specific tests for updated themes: some themes, such as Protected Sites, require data to follow the most recent versions of the schemas to pass all compliance tests.

In addition, the Joint Research Center (JRC) has indicated that these updated versions will be used in official INSPIRE monitoring from 2025 onwards, underlining the importance of adapting as soon as possible.

What does this mean for consumers?

To ensure that data conforms to the latest versions of the schemas and can be used in European systems, it is essential to take concrete steps:

  • If you are publishing new datasets: use the updated versions of the schemas from the beginning.
  • If you are working with existing data: update the schemas of your datasets to reflect the changes you have made. This may involve adjusting types of features and making new transformations.
  • Publishing services: If your data is already published, you will need to re-transform and republish it to ensure it conforms to the new specifications.

These actions are essential not only to comply with INSPIRE standards, but also to ensure long-term data interoperability.

Conclusion

The update to version 5.0 of the INSPIRE schemas represents a technical challenge, but also an opportunity to improve the interoperability and usability of spatial data in Europe. Adopting these modifications not only ensures regulatory compliance, but also positions implementers as leaders in the modernisation of spatial data infrastructure.

Although the updates may seem complex, they have a clear purpose: to strengthen the interoperability of spatial data in Europe. With better harmonised data and updated tools, it will be easier for governments, businesses and organisations to collaborate and make informed decisions on crucial issues such as sustainability, land management and climate change.

Furthermore, these improvements reinforce INSPIRE's commitment to technological innovation, making European spatial data more accessible, useful and relevant in an increasingly interconnected world.


Content prepared by Mayte Toscano, Senior Consultant in Data Economy Technologies. The contents and points of view reflected in this publication are the sole responsibility of its author.