Please note: The algorithm descriptions in English have been automatically translated. Errors may have been introduced in this process. For the original descriptions, go to the Dutch version of the Algorithm Register.

Traffic control centre for monitoring (i)-VRIs and traffic flows

The traffic control centre is linked via fibre optics to all VRI`s. This allows the VRI to report if there is a disruption. (broken lights, stuck push buttons, etc.) In addition, traffic flows can be monitored and used for analysis.

Last change on 1st of September 2025, at 9:33 (CET) | Publication Standard 1.0
Publication category
Other algorithms
Impact assessment
Field not filled in.
Status
In use

General information

Theme

  • Space and Infrastructure
  • Traffic

Begin date

11-2019

Contact information

dataloket@oss.nl

Responsible use

Goal and impact

The purpose of this algorithm is to test and control the traffic controls. Also the operation and fault management of the traffic lights

Considerations

These algorithms provide insight into traffic and traffic flows at a traffic light. The disadvantages of this algorithm is that it can sometimes give false reports. A failure of a loop, for example, can give an unjustified report of a redditor.

Human intervention

The algorithm collects the data and presents it in a dashboard. This data is used by municipal employees to review and monitor traffic policies, settings and flow.

Risk management

The municipality complies with applicable legislation regarding disclosure of data to third parties and data retention.

Legal basis

The Road Traffic Act 1994 (WVW) is the basis for all traffic rules. The basic principle here is the smoothness and flow of traffic and that no one should cause a nuisance or danger on the road.

Links to legal bases

Road Traffic Act: https://wetten.overheid.nl/BWBR0006622

Elaboration on impact assessments

No direct personal data such as name and address details are stored or processed in an (i)-VRI. The (i)-VRI does receive anonymised position and priority messages from road users. These are used for traffic control but are not otherwise stored. They cannot be traced back to a natural person. The log data stored from a traffic control may contain indirect personal data. In combination with camera images, for example, it can be established whether a particular vehicle drove through a red light, for example. These indirect personal data are not provided to third parties. However, they can be requested by the police.

Operations

Data

The data used by the algorithm is the real-time data measured by the control system itself using detection loops and pushbuttons, among others. Once an RSI is accessed on the national network and becomes a full (i)-VRI, the following applies. Data retrieved via national UDAP. This specific dataflow (origins from mobiles and on-board computers) are designated as (potentially) person traceable data. All parties processing this data have signed a data processor agreement. The core of iVRIs is the integration of various data sources. These include:

1. Sensors: These are placed at intersections and detect the presence and speed of vehicles.

2. Connected vehicles: Modern vehicles often transmit data about their location and speed.

3. Mobile apps: Think of navigation apps that share real-time traffic information.These data streams are collected and analysed in a central system, where decisions are made about traffic light cycles. Within the municipality of Oss, we currently only have VRI`s and iVRI ready installed, with no connection to UDAP

Technical design

Traffic lights collect data and through the algorithm this is translated into information about the traffic light, its use and the handling of traffic flows. This data appears in a predefined dashboard.

External provider

Suppliers may be: Technolution with MobiMaestro STATS or Vialis with Traffic Information via Verkeer.nu

Similar algorithm descriptions

  • Intelligent traffic lights can detect various mobilities with sensing loops and push buttons and connect to in-car systems and navigation apps. To see traffic "coming" at an earlier stage and regulate it even smarter.

    Last change on 8th of November 2024, at 13:26 (CET) | Publication Standard 1.0
    Publication category
    High-Risk AI-system
    Impact assessment
    DPIA
    Status
    In use
  • Intelligent traffic lights can detect various mobilities with sensing loops and push buttons and connect to in-car systems and navigation apps. To see traffic "coming" at an earlier stage and regulate it even smarter.

    Last change on 19th of June 2025, at 12:37 (CET) | Publication Standard 1.0
    Publication category
    High-Risk AI-system
    Impact assessment
    Field not filled in.
    Status
    In development
  • Whereas ordinary traffic lights register by detection loops (sensors in the road) that traffic is passing over, 'smart' traffic lights additionally register via apps what kind and how much traffic is coming. This allows traffic lights to see traffic "arriving" earlier and thus determine how long the traffic light is on green.

    Last change on 14th of March 2025, at 9:08 (CET) | Publication Standard 1.0
    Publication category
    Impactful algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • Whereas ordinary traffic lights register by detection loops (sensors in the road) that traffic is passing over, 'smart' traffic lights additionally register via apps what kind and how much traffic is coming. This allows traffic lights to see traffic "arriving" earlier and thus determine how long the traffic light is on green.

    Last change on 2nd of April 2025, at 14:10 (CET) | Publication Standard 1.0
    Publication category
    Impactful algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • Intelligent traffic lights can detect various mobilities with sensing loops and push buttons and connect to in-car systems and navigation apps. To see traffic "coming" at an earlier stage and regulate it even smarter.

    Last change on 1st of September 2025, at 9:24 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use