{"id":7923,"date":"2024-05-27T11:42:29","date_gmt":"2024-05-27T11:42:29","guid":{"rendered":"https:\/\/wetransform.to\/?post_type=news-and-events&p=7923"},"modified":"2024-06-17T12:31:43","modified_gmt":"2024-06-17T12:31:43","slug":"inspire-schema-updates","status":"publish","type":"news-and-events","link":"https:\/\/wetransform.to\/de\/neuigkeiten-veranstaltungen\/inspire-schema-updates\/","title":{"rendered":"INSPIRE Schema Updates"},"content":{"rendered":"

In 2015, all INSPIRE application schemas were updated to align with changes in the INSPIRE Implementing Rules and the Technical Guidelines<\/a>, resulting in many major version updates (v3.x to v4.0).<\/p>\n

Fast forward to February 2024, and the release of a number of major version INSPIRE application schema updates<\/a> (v4.x to v5.0) has been announced. The first major version update in nearly a decade.<\/p>\n

Major version updates can include breaking changes that are not backwards compatible. Examples of breaking changes are the removal of mandatory properties or the changing of type or property names. This means that data harmonized using v4.0 schemas, which currently have a v5.0 available, must be re-transformed using an updated transformation project to be compliant against the latest version of the schema. <\/p>\n

Breaking changes have also been introduced to v4.0 schemas, although no major version change was made. One example of this is the INSPIRE Planned Land Use (PLU) v4.0 schema- the existing schema was updated with a breaking change that requires an updated transformation project, re-transformation and re-publishing of related resources and services. The Planned Land Use v4.0 schema update is relevant for all implementers harmonizing XPlanung data. <\/p>\n

The Joint Research Commission (JRC) has indicated that the new schema versions will be used in the 2025 Monitoring.<\/a> <\/p>\n

The official INSPIRE Validator has incorporated the new schema versions; currently data which is compliant against older schema versions will validate against the test "Validation against declared schema" in the Conformance Class INSPIRE GML application schemas<\/a>, however it will not validate against the "Validation against INSPIRE official schema" test in the theme-specific conformance classes that have experienced a schema update, for example Conformance Class 'GML application schema, Protected Sites<\/a>. <\/p>\n

\u201cWhat do I do now?\u201d<\/h2>\n

The first step in the schema update process is to determine whether the schema updates affect the data you have harmonized or are planning to harmonize.<\/p>\n

The table below lists the schemas that were updated and a description of the changes that were made. Additionally, the latest schema version is provided:
\nINSPIRE Schema Updates 2024<\/a><\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Schema<\/strong><\/th>\nChange description<\/strong><\/th>\nChange Type<\/strong><\/th>\nLatest version<\/strong><\/th>\n<\/tr>\n<\/thead>\n
ad<\/td>\nChanged the datatype for the "building" association of the Address feature type.<\/td>\nnon-breaking change<\/td>\nv4.1<\/td>\n<\/tr>\n
au<\/td>\nRemoved enumeration from schema and changed encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
BaseTypes.xsd<\/td>\nRemoved VerticalPositionValue enumeration from BaseTypes schema.<\/td>\nbreaking change<\/td>\nv4.0<\/td>\n<\/tr>\n
ef<\/td>\nAdded a new attribute "thematicId" to the spatial object type AbstractMonitoringObject.<\/td>\nnon-breaking change<\/td>\nv4.1<\/td>\n<\/tr>\n
el-cov<\/td>\nChanged encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
ElevationBaseTypes.xsd<\/td>\nRemoved enumeration from schema.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
el-tin<\/td>\nChanged encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
el-vec<\/td>\nRemoved enumeration from schema and changed encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
hh<\/td>\nAdded new attributes to the EnvHealthDeterminantMeasure feature type, added new feature types, and removed some data types.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
hy<\/td>\nUpdated to version 5.0 since the schema imports the hy-p schema that was updated to version 5<\/td>\nnon-breaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
hyp<\/td>\nChanged the data type of the geometry attribute of the DrainageBasin feature type.<\/td>\nnon-breaking and breaking changes<\/td>\nv5.0<\/td>\n<\/tr>\n
lcv<\/td>\nAdded association role to the LandCoverUnit feature type.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
mu<\/td>\nChanged encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv4.0<\/td>\n<\/tr>\n
nz-core<\/td>\nRemoved enumeration from schema and changed encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
ObservableProperties.xsd<\/td>\nRemoved enumeration from schema and changed encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv4.0<\/td>\n<\/tr>\n
pf<\/td>\nChanged the definition of the ProductionInstallation feature type.<\/td>\nnon-breaking change<\/td>\nv4.1<\/td>\n<\/tr>\n
plu<\/td>\nFixed the typo in the attribute "backgroudMapURI" of the data type BackgroundMapValue.<\/td>\nbreaking change<\/td>\nv4.0.1<\/td>\n<\/tr>\n
ps<\/td>\nFixed typo in inspireId, added a new attribute, and moved attributes to data type.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
sr<\/td>\nChanged the stereotype of the ShoreSegment object from featureType to datatype.<\/td>\nbreaking change<\/td>\nv4.0.1<\/td>\n<\/tr>\n
su-vector<\/td>\nAdded a new attribute StatisticalUnitType to the VectorStatisticalUnit feature type<\/td>\nnon-breaking change<\/td>\nv4.1<\/td>\n<\/tr>\n
tn<\/td>\nRemoved enumeration from schema and changed encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
tn-a<\/td>\nChanged the datatype for the "controlTowers" association of the AerodromeNode feature type.<\/td>\nnon-breaking change<\/td>\nv4.1<\/td>\n<\/tr>\n
tn-ra<\/td>\nRemoved enumerations from schema and changed encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
tn-ro<\/td>\nRemoved enumerations from schema and changed encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
tn-w<\/td>\nRemoved the abstract stereotype for the TrafficSeparationScheme feature type. Removed enumerations from schema and changed encoding of the attributes that refer to enumerations.<\/td>\nnon-breaking and breaking changes<\/td>\nv5.0<\/td>\n<\/tr>\n
us-govserv<\/td>\nUpdated the version of the imported us-net-common schema (from 4.0 to 5.0)<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
us-net-common<\/td>\nDefined datatype for the authorityRole attribute. Change encoding of the attributes that refer to enumerations.<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
us-net-el<\/td>\nUpdated the version of the imported us-net-common schema (from 4.0 to 5.0)<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
us-net-ogc<\/td>\nUpdated the version of the imported us-net-common schema (from 4.0 to 5.0)<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
us-net-sw<\/td>\nUpdated the version of the imported us-net-common schema (from 4.0 to 5.0)<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
us-net-th<\/td>\nUpdated the version of the imported us-net-common schema (from 4.0 to 5.0)<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n
us-net-wa<\/td>\nUpdated the version of the imported us-net-common schema (from 4.0 to 5.0)<\/td>\nbreaking change<\/td>\nv5.0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Included in the v2024.1 schema release are many schemas which had enumerations removed. Enumerations were retired and changed into codelists, resulting in breaking changes for schemas which used enumerations.<\/a> <\/p>\n

INSPIRE schema change proposals are reviewed on a rolling basis, and updates can occur at any time. It\u2019s a good idea to check the INSPIRE-MIF application schemas GitHub repository<\/a> on a regular basis to check the status of on-going schema change proposals.<\/p>\n

The hale\u00bbconnect platform<\/a> will be updated to include the new INSPIRE application schema versions on June 21, 2024. Once available, users will be able to select v5.0 schemas when creating a new schema.<\/p>\n

\"screenshot<\/p>\n

Recommendations and Webinar<\/h2>\n

We strongly recommend users to begin to:<\/p>\n