Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/us-net-tc/ containing schemas not included in IR.

Issue faced

The application schema Telecommunications network is only proposed in the Technical guidance and it is not included in the Implementing Rules.
To be in line with the scope of the "official" schema repository - contains only those data models that are contained in the amendment to the Implementing Rules for Annex II+III themes, including the updates of the Annex I data themes - the application schema Telecommunications network should not be present in the schema repository but only in the draft one.

Proposed solution

Remove the folder from the schema repository and move the content in the draft-schema repository.

Additional information

Impact on INSPIRE TG / IR

No

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/nz/ containing a very old/draft schema.

Issue faced

The presence of the folder may lead to confusion because the schema version is "0.0" and the namespace (i.e. nz) is wrong and no more used.

Proposed solution

Remove the entire folder.

Additional information

Impact on INSPIRE TG / IR

No

The telecommunications.xsd has been removed from its original URL. We operate data services that reference this schema.
This action has an impact on our legally mandated cable and pipeline information services.

Change proposal description

Quickly put the telcommunications.xsd back to its original URL to repair the unintended impact

Issue faced

dead link since 16-11: http://inspire.ec.europa.eu/schemas/us-net-tc/4.0/TelecommunicationsNetwork.xsd

Validation and dataservices based on this schema fail to work.

Expected behaviour

Current behaviour

dead link since 16-11: http://inspire.ec.europa.eu/schemas/us-net-tc/4.0/TelecommunicationsNetwork.xsd

Steps to reproduce

Proposed solution

move: https://inspire.ec.europa.eu/schemas/2021.1/us-net-tc/4.0/TelecommunicationsNetwork.xsd
back to: http://inspire.ec.europa.eu/schemas/us-net-tc/4.0/TelecommunicationsNetwork.xsd

Technical details

Additional information

Proposal reason

Back ground:

In the Netherlands we run a cable and pipeline excavation damage data service based on INSPIRE data specs. The use of this service is legally mandated. The service uses the INSPIRE 4.0 xml schemas, for data specs and validation. It was noticed by operators that since nov 16 the telecom xsd was not available any more. This was communicated to Geonovum (the INSPIRE implementation coordinator and related cable and pipeline standard office).

What to do now? Our most optimal solution is that the XSD is placed back again to its original URL. This would evade a lot of communication and unforeseen complications.

By the way, we consider the use of these INSPIRE schema's a great example of an INSPIRE implementation success.

Addressed schema

Impact on INSPIRE TG / IR

Change proposer

Paul Janssen
Geonovum, Netherlands

References

More detailed documentation

I noticed this event #37 related to this issue

Change proposal description

Proposal is modify the TimeLocationValueTriple in the https://inspire.ec.europa.eu/schemas/omso/3.0/SpecialisedObservations.xsd. It is currently derived from wml2:TimeValuePair , proposal is to derive it from wml2:MeasurementTVP .

Issue faced

The datatype TimeLocationValueTriple provided in the current SpecialisedObservations schema only covers the spatiotemporal aspects, thus not allowing for the provision of a value.

Expected behaviour

The TimeLocationValueTriple allows for provision of time + value + location of a measurement

Current behaviour

in the SpecialisedObservations schema, the TimeLocationValueTriple data type only provides time + location

Proposed solution

Underlying issue had to do with errors in WaterML 2.0 with TimeValuePairType with only time. Proposal is to use same fix already used for WaterML 2.0 i.e. the introduction of the the MeasureTVPType (with both time and value). Deriving the TimeLocationValueTriple from MeasureTVPType will solve current issue.

Technical details

Additional information

Proposal reason

proposal is needed because of a bug

Addressed schema

https://inspire.ec.europa.eu/schemas/omso/3.0/SpecialisedObservations.xsd

Impact on INSPIRE TG / IR

no impact

References

More detailed documentation

Proposed modifications to the TimeLocationValueTriple are highlighted in the below screenshot (on the left the current data type, on the right the modified one)

and provided here:
http://datacove.eu/data/documents/TimeLocationValueTriple.xsd

Change proposal description

This change proposal addresses a bug in the Geophysics application schema, in which no type is provided for the distributioninfo element. The schema should be amended adding the missing type i.e. MD_Distributor.

This proposal has been already included in the Change proposals on the IR submitted to 7th MIG meeting (see All change proposal document and Change Proposal Consolidated excel file.)

Addressed schema

https://inspire.ec.europa.eu/schemas/ge_gp/4.0/GeophysicsCore.xsd

Impact on INSPIRE TG / IR

No impacts.

Change proposer

EuroGeoSurveys.

References

More detailed documentation

The change proposal is a long-standing one, also discussed in the INSPIRE Community Forum under the Earth Science Cluster.
INSPIRE Community Forum discussion : https://wayback.archive-it.org/12090/20210120110926/https://inspire.ec.europa.eu/forum/file/view/163756/inspire-dataspecification-ge-v30-geology-cluster-updates-v8-for-mig-t

Change description

Add a new attribute "thematicId" to the spatial object type AbstractMonitoringObject.

Implementation of change

• Add new attribute:

Additional information

Related TG issue

EF - Changes from 1089 amendment #145

Addressed schema

https://inspire.ec.europa.eu/schemas/ef/4.0/EnvironmentalMonitoringFacilities.xsd

Change proposal description

The attribute riverBasinDistrict should be encoded in the right way.

Issue faced

The attribute riverBasinDistrict is not encoded correctly because its multiplicity is 0..1 and the dataType is a codelist.

Proposed solution

It should be encoded in this way:

Technical details

Related pull request: #2

Additional information

Proposal reason

Bugfix

Addressed schema

https://inspire.ec.europa.eu/schemas/pf/4.0/ProductionAndIndustrialFacilities.xsd

Impact on INSPIRE TG / IR

No impact on TG/IR.

Change description

Change the definition of the ProductionInstallation feature type.

Implementation of change

• Update the definition with the new value:

Additional information

Related TG issue

PF - Changes from 1089 amendment #146

Addressed schema

https://inspire.ec.europa.eu/schemas/pf/4.0/ProductionAndIndustrialFacilities.xsd

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/lc/ containing a very old/draft schema.

Issue faced

The presence of the folder may lead to confusion because the schema version is "0.0" and the namespace (i.e. lc) is wrong and no more used.

Proposed solution

Remove the entire folder.

Additional information

Impact on INSPIRE TG / IR

No

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/ugs/ containing a very old/draft schema.

Issue faced

The presence of the folder may lead to confusion because the schema version is "0.0" and the namespace (i.e. ugs) is wrong and no more used. In any case, the first draft version (i.e. 2.0) is available in the draft schema repository (https://inspire.ec.europa.eu/draft-schemas/us-govserv/2.0/).

Proposed solution

Remove the entire folder.

Additional information

Impact on INSPIRE TG / IR

No

Change proposal description

Update inspire_vs.xsd schema to include the SLD capabilities schema to allow validation of WMS GetCapabilities documents

Issue faced

Originaly report to INSPIRE-MIF : INSPIRE-MIF/helpdesk-validator#616
WMS GetCapabilites documents are not validated because the inspire_vs.xsd schema does not include the SLD schema

Expected behaviour

WMS GetCapabilites documents should successfully validate in the ETF Validator

Current behaviour

WMS GetCapabilites documents fail validation because the inspire_vs.xsd schema does not include the SLD schema

Steps to reproduce

Validate the WMS service from Lantmäteriet (Sweden) in the ETF Validator with the service URL
https://maps.lantmateriet.se/capabilities/elf/basemap/wms/v1?request=GetCapabilities&service=WMS&version=1.3.0
Test that fails:
at04-getcapabilities-xml-schema-validation > check-xml-schema-valid

Proposed solution

The inspire_vs.xsd schema should be modified to include the SLD capabilities schema (http://schemas.opengis.net/sld/1.1.0/sld_capabilities.xsd).

Technical details

Pull request for inspire_vs.xsd to import SLD_Capabilities schema is here
#50

Additional information

Proposal reason

The current version of inspire_vs.xsd schema does not include the SLD Capabilities schema

Addressed schema

https://inspire.ec.europa.eu/schemas/inspire_vs/1.0/inspire_vs.xsd

Impact on INSPIRE TG / IR

No impact as far as I know

Change proposer

Peter Bodley, Lantmäteriet, Sweden

References

Available implementation

#50

More detailed documentation

Dear all,

as @heidivanparys suggested in #547, Croatian language ("hrv") should be added to the https://inspire.ec.europa.eu/schemas/common/1.0/common.xsd.

For now, the INSPIRE Validator returns an error on Croatian language as seen below:

Change proposal description

In ElevationGridCoverage , ElevationTIN and ElevationVectorElements application schemas the 'endLifespanVersion' property has multiplicity equal to one.
Proposal is to set endLifespanVersion multiplicity to [0..1], coherently to multiplicity of this property in the other INSPIRE application schemas.

Issue faced

In most cases the endLifespanVersion is not known, but, since multiplicity of this element is 1, a value or a nilReason shall be provided.

Proposed solution

Add minOccurs=0 to the endLifespanVersion definition

Technical details

the current property definition

is changed to

Addressed schemas

https://inspire.ec.europa.eu/schemas/el-vec/4.0/ElevationVectorElements.xsd,
https://inspire.ec.europa.eu/schemas/el-cov/4.0/ElevationGridCoverage.xsd
https://inspire.ec.europa.eu/schemas/el-tin/4.0/ElevationTin.xsd

Impact on INSPIRE TG / IR

TG (related issue INSPIRE-MIF/technical-guidelines#25) and UML impacted

Change proposer

Proposal was discussed in the INSPIRE Community Forum.

References

More detailed documentation

https://wayback.archive-it.org/12090/20210119145601/https://inspire.ec.europa.eu/forum/discussion/view/266001/the-endlifespanversion-property-has-minimum-cardinality-equal-to-one-in-the-elevation-schema

There is a typo in the Dutch INSPIRE theme enumerations XSD (line 22), for theme Natural risk zones :

<xs:enumeration value="Gebieden met natuurrisico'es"/>

Should be:

<xs:enumeration value="Gebieden met natuurrisico's"/>

This is a problem, since GeoNetwork uses the correctly spelled version, which results in invalid metadata (ISO metadata and capabilities docs). At least this is the case for the GN version running at the Dutch national geoportal at https://nationaalgeoregister.nl/geonetwork.

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/er/ containing a very old/draft schema.

Issue faced

The presence of the folder may lead to confusion because the schema version is "0.0" and the namespace (i.e. er) is wrong and no more used.

Proposed solution

Remove the entire folder.

Additional information

Impact on INSPIRE TG / IR

No

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/sr/0.0/ containing a very old/draft schema.

Issue faced

The presence of the folder may lead to confusion because the schema version is "0.0" and the parent folder should contain only the official versions of the schemas.

Proposed solution

Remove the folder.

Additional information

Impact on INSPIRE TG / IR

No

Edit: this was to clarify and is answered with the comments:

Not yet a change proposal but rather a question:
I seem to remember that there was a discussion to replace CI_Citation as type for MaintenanceAuthority.authority because it does not really match the purpose. But I cannot find any documentation or disccusion on this any more.
The only thing I can find is this discussion on how to fill it but that does not address changing the schema.
Is anyone aware of such a discussion?

Thank you and all the best

Johanna

Change proposal description

Change the type used for MaintenanceAuthority.authority and OwnerAuthority.authority from gmd:CI_Citation to CI_ResponsibleParty

Issue faced

The type used for the attributes does not match their description.

Expected behaviour

The attributes should use CI_ResponsibleParty (defined as "identification of, and means of communication with, person(s) and organizations associated with the dataset")

Current behaviour

The two attributes mentioned (defined as "Identification of the maintenance authority." and "Identification of the owning authority.") are currently using gmd:CI_Citation (defined as "standardized resource reference") as type.

Proposed solution

Change the type for MaintenanceAuthority.authority and OwnerAuthority.authority from gmd:CI_Citation to CI_ResponsibleParty.

Additional information

Proposal reason

This change proposal is needed because the schema model does not fit the purpose.

Addressed schema

TN

Impact on INSPIRE TG / IR

IR on interoperability:

• 7.3.1.3 : Change Type in table from CI_Citation to CI_ResponsibleParty
• 7.3.1.5 : Change Type in table from CI_Citation to CI_ResponsibleParty

TG TN

• UML diagrams
• 5.3.2.1.3 Value type: CI_ResponsibleParty
• 5.3.2.1.5 Value type: CI_ResponsibleParty

Change proposer

Johanna Ott, wetransform GmbH

References

More detailed documentation

Discussion in Forum

Change proposal description

In May 2020 the issue Energy Resources: Missing nilReason for dateOfDetermination and dateOfDiscovery was opened in the INSPIRE Thematic Cluster. As it has not been solved this git issue was created.

Issue faced

The Energy Resources vector schema has issues concerning two properties that are defined differently in the according UML model :

1. RenewableAndWasteResource.dateOfDetermination: is missing nilReason definition (attribute nillable is set to 'true' for it though)
2. FossilFuelResource.dateOfDiscovery: is missing nilReason definition (attribute nillable is set to 'true' for it though)

Additional information

Proposal reason

Bugfix

Addressed schema

https://inspire.ec.europa.eu/schemas/er-v/4.0/EnergyResourcesVector.xsd

Impact on INSPIRE TG / IR

No impact on TG/IR.

Change description

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

Implementation of change

• Change the attribute name from "backgroudMapURI" to "backgroundMapURI":

Additional information

Related TG issue

LU - Planned Land Use - Changes from 1089 amendment #137

Addressed schema

https://inspire.ec.europa.eu/schemas/plu/4.0/PlannedLandUse.xsd

Change proposal description

This change proposal develops in the context of the reuse of INSPIRE for environmental reporting, more specifically in the framework of the alignment to INSPIRE of the reporting under the Environmental Noise Directive (END), in which the data model for the reporting of the Noise Contours of the Strategic Noise Maps builds on the INSPIRE Data Specification for the spatial data theme Human Health and Safety (HH).

This proposal has the twofold objective to:

1. allow, in agreement to what foreseen in the IR, the provision of the type of the noise source for noise intensity measures + the component and the media for the concentration measures (bug fixing)
2. introduce the concept of the 'category' of measure, aimed to model those health determinants measures that do not fit the ISO 19103 Measure Type (enhancement)

The modifications described in this change proposal:

• correct current INSPIRE application schema regarding the provision of noise and concentration measures + correct related GML application schema (xsd) accordingly;
• preserve backwards compatibility with the current GML application schema (https://inspire.ec.europa.eu/schemas/hh/4.0/HumanHealth.xsd);
• have been already implemented in the application schema used for the environmental reporting of END Noise Contours

Issue faced

Below the headings Expected behaviour, Current behaviour and Proposed solution have been duplicated to clearly differentiate the proposal for the resolution of the bug (bug) and the proposal for the introduction of the category of measure (enhancement).

Expected behaviour (bug)

According to the IR, the EnvHealthDeterminantMeasure spatial object has two specialisations aimed to the provision of

• the noise source type for noise intensity measures
• the component whose concentration is measured, and the media in which the concentration is measured for concentration measures

Current behaviour (bug)

In the current HH schema, the EnvHealthDeterminantMeasure spatial object allows to specify neither the source of the noise nor the component/ the media of the concentration.

Proposed solution (bug fix)

The specialisation of the ISO 19103 foreseen in the IR for the specific cases of the noise and concentration health determinants, describes:

• the noise ‘source’ as an attribute of the “UomNoise” type (sub-type of UnitOfMeasure)
• the ‘component’ and the ‘media’ of the concentration as attributes of the UomConcentration type (sub-type of UnitOfMeasure).

However, the ‘measure’ of the EnvHealthDeterminantMeasure spatial object is provided according to the ISO 19103, (and in the GML application schema the ‘measure’ attribute has gml:Measure data type), therefore neither the noise source nor the component and the media of the concentration can ever be provided.
The proposed correction is to specialise the ‘EnvHealthDeterminantMeasure’ feature type by means of two determinant-specific feature types:

• EnvHealthDeterminantNoiseMeasure (for provision of noise intensity measures)
• EnvHealthDeterminantConcentrationMeasure (for provision of concentration measures).

Find description of these specialising feature types below:
Name: Environmental Health Determinant Noise Measure (EnvHealthDeterminantNoiseMeasure)
Description: A noise measurement that is of interest for human health determinant analysis.
Attributes:
Attribute name: source
Attribute definition: The noise source type
Attribute type: NoiseSourceTypeValue

Name: Environmental Health Determinant Concentration Measure (EnvHealthDeterminantConcentrationMeasure)
Description: A concentration measurement that is of interest for human health determinant analysis
Attributes:
Attribute name: component
Attribute definition: The component whose concentration is measured.
Attribute type: ComponentTypeValue
Attribute name: media
Attribute definition: The media in which the concentration is measured.
Attribute type:MediaTypeValue

Expected behaviour (enhancement)

The proposed enhanced schema can model cases of health determinant measures not fitting the ISO 19103 Measure Type definition (value + unit of measure).
As an example, consider END Noise Contours maps, in which measures of the noise levels in a certain area are characterized by decibel ranges relating to specific sound level indicators (e.g. noise level = Lden 50-54).

Current behaviour (enhancement)

The 'measure' attribute of the EnvHealthDeterminantMeasure has ISO 19103 Measure Type and multiplicity 1.
This means that for a noise contour polygon characterised by a measure of the noise level= Lden 50-54, currently one can specify neither the noise level indicator (Lden) nor the range 50-54 (could provide either '50' db or '54' db)
(e.g. 50.0/hh:measure)

Proposed solution (enhancement)

Proposed solution is to extend the EnvHealthDeterminantMeasure feature type in a way that measures not fitting the ISO 19103 concept can be provided through code lists specifying measure categories.

An example of measure category is the Noise Indicator Range code list in the END Strategic Noise Maps data model, encoding all allowed values of (indicator, db range) couples e.g. Lden5054, Lnight4549, LdenGreaterThan75 etc.
Operating through code list has the advantage to use only one field to express the complete information related to the measure and to specify all allowed indicator /value combinations.

The proposed solution is to:

• add to the EnvHealthDeterminantMeasure the 'category' attribute, whose type is the MeasureCategoryTypeValue code list
• create the 'MeasureCategoryTypeValue' code list (empty code list to be used as a super-class for a number of specific code lists, like the above mentioned Noise Indicator Range in the scope of the Environmental Noise Directive reporting)
• add the constraint that environmental health determinant measure shall be provided, either as measure (attribute ‘measure’) or category of measure (attribute ‘category’) snd set multiplicity of 'measure' attribute to 0..1.

Attributes:
Attribute name: category
Attribute definition: The category of the environmental health determinant measure.
Attribute type: MeasureCategoryTypeValue
Code list:
Name: Measure Category Type (MeasureCategoryTypeValue)
Definition: The measure categories.
Extensibility: any
Description: Empty code list to be used as a super-class for a number of specific code lists (e.g. for the Environmental Noise Directive purposes, http://dd.eionet.europa.eu/vocabulary/noise/NoiseIndicatorRangeValue, http://dd.eionet.europa.eu/vocabulary/noise/NoiseIndicatorValue) whose values may be used to specify the attribute value.

Technical details

Related pull request: #5

Additional information

Proposal reason

This proposal is needed both because of a bug in the current HH schema and because the current EnvHealthDeterminantMeasure spatial object does not fit the specific use case of health determinants measures other than ISO 19103 concept. An example of this use case is the environmental reporting of noise contours of the Strategic Noise Maps under the Environmental Noise Directive obligation, in which measures of the noise levels in a certain area are characterized by decibel ranges relating to specific sound level indicators.
The proposed solution of INSPIRE HH enhancement has been included in the conceptual data model of the new Environmental Noise Directive reporting mechanism, following the requirements to align reporting obligations in the field of legislation related to the environment (Regulation (EU) 2019/1010 of the European Parliament and of the Council). The first reporting of the END Strategic Noise Maps according to this new reporting mechanism will be provided in 2022.

Addressed schema

https://inspire.ec.europa.eu/schemas/hh/4.0/HumanHealth.xsd

Impact on INSPIRE TG / IR

This change proposal impacts both, the Technical Guidance document (TG) and the Implementing Rules (IR). An IR Change Proposal was submitted in 2019,approved and included in the proposed revised INSPIRE Implementing Rules on Interoperability of spatial data sets and services (2020), currently pending in the adoption process.
Link to the IR Change proposal

Change proposer

European Environment Agency in collaboration with END thematic community and Epsilon Italia

References

Available implementation

Revised INSPIRE HH schema
UML of revised INSPIRE HH
UML of reporting data model for END Noise Contours

More detailed documentation

63rd INSPIRE MIG-T meeting presentation
INSPIRE Conference 2020 presentation
INSPIRE Community Forum Discussion on how to provide indicators and source in noise measures
INSPIRE Community Forum Discussion on provision of Priority Datasets related to END reporting
EEA Eionet Data Dictionary – Vocabulary (NoiseSourceTypeValue, NoiseIndicatorRangeValue, NoiseIndicatorValue)

There is a typo in the attribute nationalCadastalZoningReference in feature type CadastralZoning

Schema: cp/4.0/CadastralParcels.xsd
Line 549:
<element name="nationalCadastalZoningReference" type="string">
should be replaced by:
<element name="nationalCadastralZoningReference" type="string">

Change description

Add a new attribute “statisticalUnitType” to the VectorStatisticalUnit feature type.

Implementation of change

A new attribute in the application schema:

Additional information

Related TG issue

SU - Vector - Changes from 1089 amendment #134

Addressed schema

https://inspire.ec.europa.eu/schemas/su-vector/4.0/StatisticalUnitVector.xsd

Change proposal description

In the "UtilityNetwork" FeatureType (application scheme "Common Utility Network Elements") the data type of "authorityRole" is defined by the implementation rules and INSPIRE model as "RelatedParty". This is implemented in the INSPIRE schema XSD in form of a gml:ReferenceType.

Extract from the XSD:
<element maxOccurs="unbounded" name="authorityRole" type="gml:ReferenceType">

However a reference can only be set to a feature type, not to a data type. As it is not possible to create a RelatedParty object on top level in a gml:FeatureCollection, this is indeed a problem.

I suggest to change the schema that RelatedParty objects can be created inline.

Issue faced

RelatedParty objects cannot be referenced.

Expected behaviour

RelatedParty objects can be created inline.

Current behaviour

RelatedParty objects cannot be referenced.

Proposed solution

I suggest to change the schema that RelatedParty objects can be created inline.

Additional information

Proposal reason

This change proposal is needed because the schema model does not fit the purpose.

Addressed schema

us-net-common

Impact on INSPIRE TG / IR

Change proposer

Martin Quanz

References

Available implementation

More detailed documentation

The INSPIRE schemas were recently updated and it looks that XML schema validation error with keywordValueInspireTheme is an error in the updated schemas.

Change proposal description

The production schema directory(https://inspire.ec.europa.eu/schemas/common/1.0/enums/) should be provided with updated enum_inspireThemes_all.xsd

Issue faced

Type keywordValueInspireTheme is currently defined only in this draft schema: https://inspire.ec.europa.eu/draft-schemas/common/1.0/enums/enum_inspireThemes_all.xsd, so XML schema validation error occurs.

Expected behaviour

Current behaviour

Steps to reproduce

Proposed solution

The production schema directory(https://inspire.ec.europa.eu/schemas/common/1.0/enums/) schould be provided with updated enum_inspireThemes_all.xsd

Technical details

Additional information

Proposal reason

Addressed schema

https://inspire.ec.europa.eu/draft-schemas/common/1.0/enums/enum_inspireThemes_all.xsd

Impact on INSPIRE TG / IR

Change proposer

References

Available implementation

Change description

Change the stereotype of the ShoreSegment object from featureType to dataType.

Implementation of change

• Update the ShoreSegment object encoding accordingly:

Additional information

Related TG issue

SR - Changes from 1089 amendment [2] #150

Addressed schema

INSPIRE-MIF/technical-guidelines#150

Change proposal description

The three feature types AerodromeNode, DesignatedPoint and RunwayCentrelinePoint should inherit from TransportPoint instead of TransportNode.

Issue faced

The three types are currently inheriting from TransportNode. That means that they shall theoretically only be present where transport links connect or end. This is not the case in reality and the model should therefore be adapted.

Expected behaviour

AerodromeNode, DesignatedPoint and RunwayCentrelinePoint inherit from TransportPoint

Current behaviour

AerodromeNode, DesignatedPoint and RunwayCentrelinePoint inherit from TransportNode

Additional information

More detailed in formation can be found in this issue

Proposal reason

The current schema version does not fit specific use cases. See this issue for detailed explanations.

Addressed schema

TN-A

Impact on INSPIRE TG / IR

IR on interoperability

• 7.4.1.3. : "This type is a sub-type of TransportPoint"
• 7.4.1.13.: "This type is a sub-type of TransportPoint"
• 7.4.1.22.: "This type is a sub-type of TransportPoint"

TG TN

• UML diagrams
• 5.8.2.1.3: "Subtype of: TransportPoint"
• 5.8.2.1.13: "Subtype of: TransportPoint"
• 5.8.2.1.22: "Subtype of: TransportPoint"

Change proposer

Johanna Ott, wetransform GmbH for DFS (Deutsche Flugsicherung)

References

More detailed documentation

GitHub issue
INSPIRE Forum

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/wfd/ containing an old/draft schema related to an additional application schema that is not included in the IRs.

Issue faced

The presence of the folder may lead to confusion because the schema version is "0.0". Since it is an additional application schema, it is available in the draft schema repository (https://inspire.ec.europa.eu/draft-schemas/wfd/).

Proposed solution

Remove the entire folder.

Additional information

Impact on INSPIRE TG / IR

No

Change proposal description

This issue is related to MD TG change proposal #5, already endorsed by the MIG - see comment.
Needed modifications to common.xsd have already been implemented in the updated schema version available in the geoportal repository, where also related enum_nor.xsd and enum_ice.xsd can be found.

Proposed solution

The xsd files in the geoportal should be used to create a pull request to the schema repository.

Additional information

The change proposal impacts on the Validator - see issue #327, issue #706 and related pull request #690

Change proposal description

This change proposal originates in the context of the reuse of INSPIRE for the streamlining of environmental reporting. Proposal is:

• to add a thematic identifier element to the ProtectedSite feature type
• change legalFoundationDate element value type to 'Date'
• change the multiplicity of the elements legalFoundationDate and legalFoundationDocument, to support providing the dates and founding documents corresponding to several designations of the same spatial object.

Issues faced

• Protected sites usually carry different types of identifiers, e.g. national, international, European. It would be easier to combine thematic information with INSPIRE geospatial data through these thematic identifiers, that are already established and maintained, but current schema does not allow to provide them.
• The format of the legalFoundationDate element is unnecessarily detailed (i.e. up to the second)
• It is not possible to provide the dates and founding documents corresponding to several designations of the same spatial object.

Proposed solution

1. add a thematicId element to the ProtectedSite Feature Type
2. change the value type of the LegalFoundationDate element to Date
3. delete LegalFoundationDate and LegalFoundationDocument from the ProtectedSite feature type and add them to the DesignationType data type.

Technical details

change proposal UML available at https://www.epsilon-italia.it/public/PS-IR-ChangeProposal/

Additional information

Proposal reason

This change proposal is needed because the current schema version does not fit specific use cases related to environmental reporting.

Addressed schema

https://inspire.ec.europa.eu/schemas/ps/4.0/ProtectedSites.xsd

Impact on INSPIRE TG / IR

This change proposal impacts both on the Technical Guidance documents (TG) and the Implementing Rules (IR)

Change proposer

European Environment Agency

Change proposal description

Proposal is to add missing type to the 'EnvironmentalManagementFacility' element definition + add missing parts in the definition of 'parentFacility' element

Issue faced

EnvironmentalManagementFacility element is missing own type definition + parentFacility association has incomplete definition

Expected behaviour

it is possible to create environmental management facility objects and related parent facility objects.

Current behaviour

it is not possible to create environmental management facility spatial objects + it is not possible to specify parent facilities

Proposed solution

• add the type to the EnvironmentalManagementFacility element as follows:

• specify content of the parentFacility as follows:

Technical details

Related pull request: #3

Additional information

Proposal reason

bugfix

Addressed schema

https://inspire.ec.europa.eu/schemas/us-emf/4.0/EnvironmentalManagementFacilities.xsd

Impact on INSPIRE TG / IR

No impact

More detailed documentation

Relevant discussion in the INSPIRE Community Forum:
https://wayback.archive-it.org/12090/20210119192050/https://inspire.ec.europa.eu/forum/discussion/view/265816/error-in-the-environmental-management-facilities-application-schema

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/bu/ containing a very old/draft schema.

Issue faced

The presence of the folder may lead to confusion because the schema version is "0.0" and the namespace (i.e. bu) is wrong and no more used. In any case, the first draft version (i.e. 2.0) is available in the draft schema repository (https://inspire.ec.europa.eu/draft-schemas/bu/2.0/Buildings.xsd).

Proposed solution

Remove the entire folder.

Additional information

Impact on INSPIRE TG / IR

No

Change description

Change the datatype for the "controlTowers" association of the AerodromeNode feature type.

Implementation of change

• Change the datatype from the generic "gml:ReferenceType" to "bu-base:BuildingPropertyType":

Additional information

Related TG issue

TN - Air - Changes from 1089 amendment #141

Addressed schema

https://inspire.ec.europa.eu/schemas/tn-a/4.0/AirTransportNetwork.xsd

Dear all,

There seems to be an issue with EarthResource and the sourceReference element in MineralResources, defined in the UML as: sourceReference: DocumentCitation[1..*]

In the XSD, the reference to the DocumentCitation dataType gets lost (only mentioned in the appinfo tag), while the xlinks provided via the gml:AssociationAttributeGroup aren't of help as DocumentCitation is a dataType, thus cannot be referenced.

This is an issue, as we thus cannot provide this mandatory information. XSD Snippet showing the issue below

<element name="sourceReference" nillable="true" maxOccurs="unbounded"> <annotation> <documentation>-- Definition -- The source or reference for the Earth Resource.</documentation> <appinfo> <targetElement xmlns="http://www.opengis.net/gml/3.2">base2:DocumentCitation</targetElement> </appinfo> </annotation> <complexType> <complexContent> <extension base="gml:AbstractMemberType"> <sequence/> <attributeGroup ref="gml:AssociationAttributeGroup"/> </extension> </complexContent> </complexType> </element>

Many thanks,

Christian

Change proposal description

Add nillable attribute to HydrogeologicalObject.beginLifespanVersion and HydrogeologicalObjectManMade.validFrom in hydrogeology schema. Not sure if more actions are required to correctly implement the model from the UML diagram.

Issue faced

According to the UML diagram, both elements mentioned are voidable. That is not respected in the xsd and therefore, no nilReason can be provided.

Expected behaviour

It is possible to provide nilReason values for both voidable elements.

Current behaviour

It is not possible to provide nilReason values.

Proposal reason

Requirements cannot be fulfilled.

Addressed schema

https://inspire.ec.europa.eu/schemas/ge_hg/4.0/HydrogeologyCore.xsd

Change proposer

Johanna Ott (wetransform GmbH) for WIZIPISI (The Wroclaw Institute of Spatial Information and Artificial Intelligence)

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/su/ containing a very old/draft schema.

Issue faced

The presence of the folder may lead to confusion because the schema version is "0.0" and the namespaces (i.e. su and stat) are wrong and no more used.

Proposed solution

Remove the entire folder.

Additional information

Impact on INSPIRE TG / IR

No

Change proposal description

According to the implementing rules, RelatedParty.individualName, RelatedParty.organisationName and RelatedParty.positionName have PT_FreeText as type.
This is also true for other types defined in the INSPIRE models whereas others use CharacterString when text is required.
As the use of PT_FreeText does not always make sense but does for some use cases/countries, I would propose to allow both, PT_FreeText and CharacterString for all properties that currently use one of them. So far, I only met data providers who wanted to use CharacterString instead of PT_FreeText (not the other way around) but as I assume that PT_FreeText is in use and needed for some other countries/cases, I assume that allowing both would be the easiest solution)
The validator already accepts both (at least in cases where PT_FreeText is demanded in the IR, but CharacterString is used)

Issue faced

PT_FreeText is more complex but not neccessary/fully used in most of the cases.

Current behaviour

Some text properties use PT_FreeText, some use CharacterString. The validator does not check for it.

Proposed solution

PT_FreeText and CharacterString are both allowed for all properties that currently use either, or.

Additional information

Proposal reason

The current schema version does not support the use case that some providers only need simple text fields (CharacterString) whereas others need more complex ones (PT_FreeText).

Addressed schema

All schemas using PT_FreeText and/or CharacterString

Impact on INSPIRE TG / IR

The IR would need to be updated to allow the use of both wherever they occur.

Change proposer

Johanna Ott, wetransform GmbH (on behalf of various customers that want to use CharacterString instead of PT_FreeText in most of the cases).

References

More detailed documentation

This is a follow up ticket of this thread in the INSPIRE Thematic cluster.
It is created because of a proposal in this issue discussing the handling of the two types in the validator.
Both can be read/used as sources for more input/discussions that already took place.

Change description

All the enumerations shall be converted into codelists.
Below is the list of enumerations:

• VerticalPositionValue
• ComparisonOperatorValue
• LegalStatusValue
• TechnicalStatusValue
• ElevationPropertyTypeValue
• SurfaceTypeValue
• ContourLineTypeValue
• OriginValue
• DeterminationMethodValue
• ProtectionClassificationValue
• TransportTypeValue
• MinMaxTrackValue
• TrackGaugeCategoryValue
• FunctionalRoadClassValue
• MinMaxLaneValue
• SpeedLimitMinMaxValue
• CEMTClassValue

Implementation of change

• The enumerations shall be removed from the related XSDs since the values will be managed in the INSPIRE Registry:

• The encoding of the attributes which refer to enumeration shall be changed:

Additional information

Related TG issue

All data specifications - Convert enumerations into codelists #130

Addressed schema

The application schemas that define enumerations are:

• Base Types
• Observable Properties
• Administrative Units
• Elevation - Base Types
• Elevation - Vector Elements
• Hydro - Physical Waters
• Natural Risk Zones
• Protected Sites Simple
• Common Transport Elements
• Railway Transport Network
• Road Transport Network
• Water Transport Network

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/ge/ containing a very old/draft schema.

Issue faced

The presence of the folder may lead to confusion because the schema version is "0.0" and the namespace (i.e. ge) is wrong and no more used. In any case, the first draft version (i.e. 2.0) is available in the draft schema repository (https://inspire.ec.europa.eu/draft-schemas/ge/2.0/Geology.xsd).

Proposed solution

Remove the entire folder.

Additional information

Impact on INSPIRE TG / IR

No

Change proposal description

The attribute 'type' is currently not modeled via xlink structure.

Issue faced

Commonly attributes with codelists should be modeled via xlink structure. However this is not the case for the two FeatureTypes ProductionInstallation and ProductionInstallationPart.

Proposed solution

A solution for the FeatureType ProductionInstallation has already been proposed 2018 in the INSIPRE Thematic Cluster:
Correction of the schema http://inspire.ec.europa.eu/schemas/pf/4.0/ProductionAndIndustrialFacilities.xsd

It should be implemented for the FeatureType ProductionInstallationPart respectively.

Additional information

Proposal reason

Bugfix

Addressed schema

https://inspire.ec.europa.eu/schemas/pf/4.0/ProductionAndIndustrialFacilities.xsd

Impact on INSPIRE TG / IR

No impact on TG/IR.

References

Available implementation

Here a poposed fixed Schema for both FeatureTypes: ProductionAndIndustrialFacilities_fixed.zip

Change description

Remove “abstract” stereotype for the TrafficSeparationScheme feature type.

Implementation of change

• Remove the “abstract” stereotype in the application schema:

Additional information

Related TG issue

TN - Water - Changes from 1089 amendment #143

Addressed schema

https://inspire.ec.europa.eu/schemas/tn-w/4.0/WaterTransportNetwork.xsd

HI

The GML application schema xsd, https://inspire.ec.europa.eu/schemas/us-net-th/4.0/ThermalNetwork.xsd
extends the us common pipe class with ThermalPipe.

The ThermalPipe gets a property thermalProductType, which is defined as a codelist according teh data specifications.

https://inspire.ec.europa.eu/codelist/ThermalProductTypeValue

However, the xsd GML application schema is missing its type defintion:

type="gml:ReferenceType" for this element thermalProductType.

which we believe should be

Can this be confirmed, if is confirmed, be corrected?

tx

Luc Van Linden

Change proposal description

Remove the following folder https://inspire.ec.europa.eu/schemas/mu/3.0rc3/ containing a draft schema.

Issue faced

To be consistent with the other data themes, the draft schemas should only be available in the draft-schemas repository. In this case, it is already present https://inspire.ec.europa.eu/draft-schemas/mu/3.0rc3/.

Proposed solution

Remove the folder.

Additional information

Impact on INSPIRE TG / IR

No

Change description

Add association role to the LandCoverUnit feature type

Implementation of change

The 1089 amendment introduces a new association for the LandCoverUnit feature type, the association was already present but with no role:

Additional information

Related TG issue

LC - Changes from 1089 amendment #131

Addressed schema

https://inspire.ec.europa.eu/schemas/lcv/4.0/LandCoverVector.xsd

Change proposal description

Within the theme of Protected Sites the INSPIRE identifier is spelled as “inspireID” and not as “inspireId”. It is proposed to harmonise the name of the inspire identifier attribute and to use inspireId in the INSPIRE Protected sites theme.

This proposal has already been approved and is contained in the corrigendum on protected sites

Proposal reason

Harmonisation of the spelling of the inspireId attribute throughout the INSPIRE data themes.

Addressed schema

https://inspire.ec.europa.eu/schemas/ps/4.0/ProtectedSites.xsd

Impact on INSPIRE TG / IR

impacts the Technical Guidance documents (TG) and the Implementing Rules (IR)

Change description

Change the data type of the geometry attribute of the DrainageBasin feature type from "GM_Surface" to "GM_Object"

Implementation of change

Current encoding:

<element name="geometry" type="gml:SurfacePropertyType">
   <annotation>
       <documentation>-- Definition --The geometry of the drainage basin, as a surface.</documentation>
   </annotation>
</element>

New encoding:

<element name="geometry" type="gml:GeometryPropertyType">
   <annotation>
       <documentation>-- Definition --The geometry of the drainage basin, as a surface.</documentation>
   </annotation>
</element>

Additional information

Related TG issue

HY - Changes from 1089 amendment #127

Addressed schema

https://inspire.ec.europa.eu/schemas/hy-p/4.0/HydroPhysicalWaters.xsd

Change proposal description

Proposal is twofold:

1. modify the schema in the official repository adding the associations to OM_Observation objects foreseen in the IR (associations are present in the draft repository schema version);
2. modify the soilDerivedObjectObservation multiplicity from 1 to [1..*].

Issue faced

In the official schema,

• SoilSite is missing association soilSiteObservation with target OM_Observation
• SoilProfile is missing association soilProfileObservation with target OM_Observation
• ProfileElement is missing association profileElementObservation with target OM_Observation
• SoilDerivedObject is missing association soilDerivedObjectObservation with target OM_Observation

The soilDerivedObjectObservation multiplicity is 1. This means that if a SoilDerivedObject has n observations linked to it, one is forced to provide this same object n times.

As a side note, all the other abovementioned associations allow provision of multiple observations (multiplicity 0..*)

Expected behaviour

1. It is possible to provide the associations to OM_Observation objects using the official schema;
2. Same SoilDerivedObject can be linked to more observations.

Current behaviour

1. The associations to OM_Observation are included only in the schema in the draft repository, so it is not possible to provide them using the official schema;
2. The multiplicity of the soilDerivedObjectObservation is set to 1, so one is forced to create a soilDerivedObject for every observation related to it.

Proposed solution

Modify the schema in the draft repository regarding the multiplicity of the soilDerivedObjectObservation and endorse this as official schema.

Technical details

the soilDerivedObjectObservation in the draft schema should be modified adding maxOccurs="unbounded" minOccurs="1" to current definition.

related Pull Request #18

Additional information

Proposal reason

The first point of this change proposal is needed because of a bug in the official schema
The second point is an enhancement to current model

Addressed schema

https://inspire.ec.europa.eu/schemas/so/4.0/Soil.xsd

Impact on INSPIRE TG / IR

TG should be updated so that multiplicity for the "soilDerivedObjectObservation" is set to [1..*]

Change proposer

• Inspire Community Forum request for the bug fixing of the schema related to missing associations to OM_Observation (i.e. alignment of schema to IR and TG)
• Geological Survey of Sweden regarding the change to the multiplicity for the "soilDerivedObjectObservation" association. Original proposal was to change multiplicity to 0..* but, after community discussions in the Thematic Clusters, agreement was on 1..*.

References

More detailed documentation

https://wayback.archive-it.org/12090/20161216062201/https://themes.jrc.ec.europa.eu/discussion/view/3421/inspire-soil-theme-change-of-the-multiplicity-of-the-soilderivedobjectobservation

https://wayback.archive-it.org/12090/20210119211852/https://inspire.ec.europa.eu/forum/discussion/view/186450/missing-associations-to-om-observation-in-xsd

Change description

Change the datatype for the "building" association of the Address feature type.

Implementation of change

• Change the datatype from the generic "gml:ReferenceType" to "bu-base:BuildingPropertyType":

Additional information

Related TG issue

AD - Changes from 1089 amendment #140

Addressed schema

https://inspire.ec.europa.eu/schemas/ad/4.0/Addresses.xsd