TrafficRegulationOrder
The TrafficRegulationOrder within the ControlledZoneTablePublication aims to provide the official legal basis for traffic rules or access restrictions within a ControlledZone. This can include:
- Restrictions on access for certain vehicle categories.
- Speed limits within specific areas.
- Rules for parking or lane usage.
- Time-bound restrictions (e.g., only applicable during peak hours).
The TrafficRegulationOrder ensures that the restrictions in a ControlledZone are legally enforceable and provides a formal reference for enforcement and communication to road users and traffic systems.
Attributes
Attribute | Type | Required | Domain | Description |
---|---|---|---|---|
id | String | Yes | See explanation | A unique identification of the data provider |
version | String | Yes | 1 or higher | A unique version number of the data provider |
id
The id attribute assigns a name (identification) to the trafficRegulationOrder. The following has been agreed upon. The ID starts with a 5-character code. These five characters are assigned by NDW. After these 5 characters, an underscore (‘_’) is added, and the data provider can append the identification themselves to create a unique ID.
Elements
Element | Type | Required | Domain | Description |
---|---|---|---|---|
issuingAuthority | MultilingualString | Yes | N/A | The competent authority that issued the traffic regulation order |
regulationId | String | Yes | N/A | An (external) unique identifier of the traffic regulation order |
status | TrafficRegulationOrderStatusEnum | Yes | planned, madeButNotImplemented, madeAndPartiallyImplemented, madeAndImplemented, partiallyWithdrawn, withdrawn | The current lifecycle status of the traffic regulation order |
implementedLocation | LocationReference | No | N/A | The actual (executed) location where the traffic regulation applies |
trafficRegulation | TrafficRegulation | Yes, 1 or more | N/A | Legal agreement or order that restricts or prohibits the use of the road network |
Example
XML Example
<d2:payload xmlns:tro="http://datex2.eu/schema/3/trafficRegulation" xmlns:loc="http://datex2.eu/schema/3/locationReferencing" xmlns:cz="http://datex2.eu/schema/3/controlledZone" xmlns:comx="http://datex2.eu/schema/3/commonExtension" xmlns:com="http://datex2.eu/schema/3/common" xmlns:d2="http://datex2.eu/schema/3/d2Payload" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="cz:ControlledZoneTablePublication" lang="nl" modelBaseVersion="3" xsi:schemaLocation="http://datex2.eu/schema/3/d2Payload LevelC_3_D2Payload.xsd">
<com:publicationTime>2024-11-13T09:00:50.000356907Z</com:publicationTime>
<com:publicationCreator>
<com:country>nl</com:country>
<com:nationalIdentifier>NDWNL</com:nationalIdentifier>
</com:publicationCreator>
<cz:headerInformation>
<com:informationStatus>real</com:informationStatus>
</cz:headerInformation>
<cz:controlledZoneTable>
...
<cz:trafficRegulationOrder id="NDW11_989846cf-0343-4abc-b169-1a2ddaf497d9_TRO" version="1">
<tro:issuingAuthority>
<com:values>
<com:value lang="nl">Amsterdam</com:value>
</com:values>
</tro:issuingAuthority>
<tro:regulationId>stcrt-2020-32736</tro:regulationId>
<tro:status>madeAndImplemented</tro:status>
<tro:trafficRegulation id="NDW11_989846cf-0343-4abc-b169-1a2ddaf497d9_TR" version="1">
...
</tro:trafficRegulation>
</cz:trafficRegulationOrder>
</cz:urbanVehicleAccessRegulation>
<cz:urbanVehicleAccessRegulation id="NDW11_500de66b-b51e-465f-8309-6d5eda0de5a1" version="1">
..
</cz:urbanVehicleAccessRegulation>
</cz:controlledZoneTable>
</d2:payload>