AM_ManagementRestrictionOrRegulationZone_allow zero-to-many specialisedZoneType

[sMorrone]

Change proposal description

Allow multiple occurrences of the specialisedZoneType element

Proposed solution

Technical details

Current definition
<element minOccurs="0" name="specialisedZoneType" nillable="true" type="gml:ReferenceType">
should be updated as follows:
<element maxOccurs="unbounded" minOccurs="0" name="specialisedZoneType" nillable="true" type="gml:ReferenceType">

Additional information

Proposal reason

This change proposal is needed to fit specific use cases, as specified below:

1. The attributes zoneType and specialisedZoneType are contextually aligned (the specialisedZoneType further specialises the type of management, regulation or restriction zone provided in the zoneType) .
   Currently, the zoneType attribute can be provided with the multiplicity one-to-many (many top level classes), therefore the specialisedZoneType attribute should be provided with the multiplicity "zero-to-many" to be able to include specialised values of all top level classes provided in the zoneType, whenever this is applicable.

2. A specific area can be at the same time subject to various restrictions / regulations or management regimes which may define diverse activities within those areas. This can lead to several regimes in the area, therefore multiple specialised zones could be assigned under the same top level class of zoneType defined by a competent authority.

Example from the Environmental Noise Directive (END) reporting

The END requires protection of quiet areas in open country and inside agglomerations. In the END reporting data model, the quiet areas are modelled as an extension of the INSPIRE AM ManagementRestrictionOrRegulationZone.
A competent authority may delineate a quiet area in the following ways:

a) quiet area in open country

• zoneType: noiseRestrictionZone (http://inspire.ec.europa.eu/codelist/ZoneTypeCode/noiseRestrictionZone)

• specialisedZoneType: quietAreaInOpenCountry (http://dd.eionet.europa.eu/vocabulary/inspire/SpecialisedZoneTypeCode/quietAreaInOpenCountry)

b) quiet area inside agglomeration(s)

• zoneType: noiseRestrictionZone (http://inspire.ec.europa.eu/codelist/ZoneTypeCode/noiseRestrictionZone)

• specialisedZoneType: quietAreaInAgglomeration (http://dd.eionet.europa.eu/vocabulary/inspire/SpecialisedZoneTypeCode/quietAreaInAgglomeration)

c) quiet area which spatial extent covers the areas outside and inside agglomeration(s). In this particular case, the INSPIRE AM attributes could be provided as following:

• zoneType: noiseRestrictionZone (http://inspire.ec.europa.eu/codelist/ZoneTypeCode/noiseRestrictionZone)

• specialisedZoneType: quietAreaInOpenCountry (http://dd.eionet.europa.eu/vocabulary/inspire/SpecialisedZoneTypeCode/quietAreaInOpenCountry)

• specialisedZoneType: quietAreaInAgglomeration (http://dd.eionet.europa.eu/vocabulary/inspire/SpecialisedZoneTypeCode/quietAreaInAgglomeration)

Addressed schema

https://inspire.ec.europa.eu/schemas/am/4.0/AreaManagementRestrictionRegulationZone.xsd

Impact on INSPIRE TG / IR

This change proposal impacts the Technical Guidance document as well as the UML diagram.

Change proposer

European Environment Agency

[fabiovinci]

Sub-group meeting on 11.11.2024:
The Sub-group reviewed the change proposal and decided to approve it.
The change proposal will be presented for approval at the upcoming MIG-T meeting.

[sMorrone]

The MIG-T members approved the change proposal at the 80th MIG-T meeting. The two-week period for objections by MIG members expired without any comments, so the proposal is now endorsed.