PermitInformation
PermitInformation is used to provide details about the permits required to access or use a controlled zone.
The purpose of PermitInformation is to offer specific information about the nature, requirements, and conditions of the necessary permits. This helps users and systems understand which permits are required and how they can be obtained or used.
Applications:
- Type of permit: Specifies the type of permit, such as an environmental sticker, parking permit, or loading/unloading permit.
- Validity of the permit: Information about the duration, geographical coverage, and any restrictions of the permit.
- Obtaining the permit: Details on how and where the permit can be applied for or acquired.
- Permit requirements: Specific criteria that must be met to obtain the permit, such as vehicle emission levels or usage purposes.
- Control information: Information required for enforcement purposes, such as a unique identification number or QR code.
The PermitInformation provides a standardized way to communicate essential details about permits, ensuring efficient regulation and understanding of access to controlled zones. This helps road users and organizations comply with regulations and supports streamlined enforcement.
The structure is as follows in relation to TrafficRegulation:
Attributes
Attribute | Type | Required | Domain | Description |
---|---|---|---|---|
id | String | Yes | See explanation | A unique identifier from the data provider |
version | String | Yes | 1 or higher | A unique version number from 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 five-character code. These five characters are assigned by NDW. After these five characters, an underscore _
follows, after which the data provider may add its own identification to create a unique ID.
Elements
Element | Type | Required | Domain | Description |
---|---|---|---|---|
applicationRequired | Boolean | No | false, true | Indicates whether applying for the permit is necessary |
description | MultilingualString | No | N/A | Textual description of the permit |
locationRelatedPermit | Boolean | No | false, true | Indicates whether the permit applies to a specific location or route in the zone |
maxDurationOfPermit | Duration | No | N/A | The maximum validity duration of a permit, in hours |
whereToApplyForPermit | URL | No | N/A | URL of the authority where a permit application can be submitted |
whereToCallForPermit | String | No | N/A | Phone number to contact the authority |
permitOwnerType | PermitOwnerTypeEnum | No | vehicle, vehicleOwner, vehicleOccupant | The purpose of the permit |
urlForFurtherInformation | URL | No | N/A | More information about the permit and the application process |
howToObtainPermit | MultilingualString | No | N/A | Information on how to obtain the permit |
permitType | PermitTypeEnum | Yes | electronic, paper, sticker, other | The type of permit |
disabledParkingPermit | Boolean | No | false, true | Indicates whether the permit is a disabled parking permit |
permitSubjectToFee | PermitSubjectToFee | No | N/A | Access is allowed for a fee |
Sub-element PermitSubjectToFee
The purpose of PermitSubjectToFee is to indicate that a payment is required for the permit and to provide details about the nature of these costs. This helps both users and systems understand and comply with financial obligations.
Element | Type | Required | Domain | Description |
---|---|---|---|---|
amountDue | AmountOfMoney | No | Decimal | The amount due in euros |
maximumAccessDuration | Duration | No | N/A | Maximum allowed time in a ControlledZone after first entry |
minimumTimeToNextEntry | Duration | No | N/A | Minimum time between two visits to a ControlledZone |
paymentInformation | URL | No | N/A | Link to the website where payment information can be found |