Information for dataproviders

This page helps you to determine whether the legal obligations of the European Delegated Regulations apply to your organization and provides you with the necessary information to proceed with registering your datasets and services. By ‘registering’ we mean making them accessible by creating the possibility to request and obtain data in a digital machine-readable format via the NAP ITS. You do not need to make the datasets directly available at this website.

Quickly navigate to following topics on this page:

Do you still have questions after reading this page ? Do not hesitate to contact the NAP Helpdesk: contact@transportdata.be or to consult the FAQ.

  

If your organisation is active in the mobility sector in Belgium, it should most probably register datasets and services on the NAP ITS. Content on the NAP ITS can be grouped into four NAP types, each based on a European Delegated Regulation:

  • Multimodal travel information services (MMTIS; EU 2017/1926 and its amendment EU 2024/490)
  • Real time traffic information services (RTTI; EU 2015/962 )
  • Safety related traffic information (SRTI; EU 886/2013)
  • Information services for safe and secure truck parkings (SSTP; EU 885/2013)

Each of these Delegated Regulations separately define the actors that need to register datasets and services on the NAP ITS:

  • For MMTIS:
  • Transport authority: any public authority responsible for the traffic management or the planning, control or management of a given transport network or modes of transport, or both, falling within its territorial competence;
  • Transport operator: any public or private entity that is responsible for the maintenance and management of the transport service;
  • Transport on demand service provider: any public or private provider of transport on demand service to users and end-users, including travel and traffic information thereof;
  • Infrastructure manager: any public or private body or undertaking that is responsible in particular for establishing and maintaining transport infrastructure, or part thereof.

 

  • For RTTI:
  • Road authority: any public authority responsible for the planning, control or management of roads falling within its territorial competence;
  • Road operator: any public or private entity that is responsible for the maintenance and management of the road;
  • Service provider: any public or private provider of a real-time traffic information service, excluding a mere conveyer of information, to users and end-users;
  • Digital map producers: Any digital map producer that disseminates real-time traffic information.

 

  • For SRTI:
  • Public and/or private road operators: any legal or natural person participating in the provision of road safety-related minimum universal traffic information services;
  • Service providers: any legal or natural person participating in the provision of road safety-related minimum universal traffic information services;
  • Broadcasters: broadcasters dedicated to the provision of traffic information.

 

  • For SSTP:
  • Public or private parking operators: any public or private body or undertaking that is responsible in particular for establishing and maintaining safe and secure truck parkings, or part thereof;
  • Service providers: any public or private body that provides safe and secure truck parking information services to users.

  

The first step into defining your legal obligations is to determine in which Delegated Regulation(s) your organization is taking part as an actor (see the previous section). Be aware that your organization might have legal obligations defined by multiple Delegated Regulations.

Each of the Delegated Regulations separately defines which datasets and services the respective  actors need to register. For convenience, we provide a summary below. A complete overview can be found in the official publications of Delegated Regulations themselves.  If after consulting this overview you would have any further questions regarding your legal obligations, please contact the NAP Helpdesk (contact@transportdata.be).

 

Transport authorities, transport operators, transport on demand service providers and infrastructure managers (as defined here) are required to register datasets and services for all transportation modes, such as:

Type

Examples

Scheduled

Air, rail including high speed rail, conventional rail, light rail, long-distance coach, maritime including ferry, metro, tram, bus, trolley-bus,…

Demand-responsive

Shuttle bus, shuttle ferry, dial-a-ride services, taxi, car-sharing, car-pooling, car-hire, bike-sharing, bike-hire,…

Personal

Car, motorcycle, bicycle, scooter, walking…

 

The Delegated Regulation distinguishes between static and dynamic travel and traffic data. At the moment, it is mandatory to register most of the static data described in the service levels 1-3 (see annex and table below) for the whole Belgian transport network. For point 1.1(d)(ix), point 1.2 (a)(i),(iii),(vii) and (c)(i),(ii) and point 1.3 (a)(ii),(iii) and (c)(iii) the deadline is the 1st of December 2024.

 

Level of Service

Examples of demanded datasets

Level of Service 1

Address, topography, timetables, facilities, accessibility, pedestrian network,…

Level of Service 2

Park & Ride stops, bike sharing stations, refuelling stations where and how to buy tickets, standard fares, on-board Wi-Fi,…

Level of Service 3

Passenger classes fare, special fare products, aggregated products combining different products such as parking , how to pay, to book, to calculate an environmental factor,…

Level of Service 4

Historic travel and traffic data on delays, observed data on delays and passing times, observed data on cancellations, information on parking tariffs

 

From the 1st of December 2025 it will also be mandatory to register dynamic travel and traffic data for service level 1 for the comprehensive TEN-T network. Next, the data categories described in service level 2 for the comprehensive TEN-T network must be registered on the NAP ITS by the 1st of December 2026. Finally the dynamic travel and traffic data must be registered for the whole Belgian transport network by the 1st of December 2028. For a complete overview of all the types of dynamic data per service level please consult the annex of the MMTIS amendment.

The different deadlines are summarized in the timeline below. However, please note that there is no need to wait till the respective deadlines. The earlier you register your datasets and/or services and the more accurate the metadata you provide, the greater the likelihood that your datasets and services will be integrated in journey planning and other travel information services by third parties.

 

The Delegated Regulation specifies which data should be provided in which format (in its articles 4 and 5). For your convenience we provide a summary below. When changes occur or inaccuracies are detected, the data shall be updated in a timely manner.

 

Data type

Format

Spatial network

  • Inspire (Article 7 of Directive 2007/2/EC)

Static and dynamic travel and traffic data for road transport

  • Datex II  through minimum national profiles

Static travel and traffic data – other transport modes than road transport

  • NeTEx CEN/TS 16614 and subsequent versions through minimum national profiles;
  • technical documents defined in Regulation (EU) No 454/2011 and subsequent versions (specific for trans-European rail system);
  • or any machine-readable format fully compatible and interoperable with those standards and technical specifications.

Dynamic travel and traffic data – other transport modes than road transport

  • SIRI CEN/TS 15531 and subsequent versions through minimum national profiles;
  • technical documents defined in Regulation (EU) No 454/2011 (specific for trans-European rail system);
  • or any machine-readable format fully compatible and interoperable with those standards or technical documents.

 

If your organization registers a dataset or service on the NAP ITS for the category MMTIS, it needs to submit a complementary Declaration of Compliance. Read more about it here.

 

Road authorities, road operators (as defined here) are required to register the following data:

  • a) Static road data: It is mandatory to register data for the types presented in the table below. The data should be provided in a standardized format (if available), otherwise the data should  be provided in any other machine readable format.

Type

Examples

Road network links and their physical attributes

Geometry, road width, number of lanes, gradients, junctions,...

Road classification

 

Traffic signs reflecting traffic regulations and identifying dangers

Access conditions for tunnels, access conditions for bridges, permanent access restrictions, other traffic regulations,...

Speed limits

 

Traffic circulation plans

 

Freight delivery regulations

 

Location of tolling stations

 

Identification of tolled roads, applicable fixed road user charges and available payment methods

 

Location of parking places and service areas

 

Location of charging points for electric vehicles and the conditions for their use

 

Location of compressed natural gas, liquefied natural gas and liquefied petroleum gas stations

 

Location of public transport stops and interchange points

 

Location of delivery areas

 

 

  • b) Dynamic road status data: It is mandatory to register data for the types presented in the table below. The data should be provided in DATEX II or any other machine readable format fully compatible and interoperable with DATEX II.

Types

Road closures, lane closures and bridge closures

Overtaking bans on heavy goods vehicles

Roadworks

Accidents and incidents

Dynamic speed limits

Direction of travel on reversible lanes

Poor road conditions

Temporary traffic management measures

Variable road user charges and available payment methods

Availability of parking spaces

Availability of delivery areas

Cost of parking

Availability of charging points for electric vehicles

Weather conditions affecting road surface and visibility

 

  • c) Traffic data: It is mandatory to register data for the types presented in the table below. The data should be provided in in DATEX II or any machine readable format fully compatible and interoperable with DATEX II.

Types

Traffic volume

Speed

Location and length of traffic queues

Travel times

Waiting time at border crossings to non-EU member States

 

If your organization registers a dataset or service on the NAP ITS for the category RTTI, it needs to submit a complementary Declaration of Compliance. Real-time information service providers and digital map producers are also required to submit a Declaration of Compliance, even though they do not need to register datasets or services. Read more about it here.

Note that from the 1st of January 2025, it will become mandatory to register a number of new data types, as described in detail in the annex of the new Delegated Regulation for RTTI (EU 2022/670).

 

Public and private road operators and/or service providers need to set up or use the means to detect a series of road safety related events or conditions for the TEN-T network (with the exclusion of the urban nodes).

Registration of the detected road safety related events or conditions on the NAP ITS by the public and private road operators and/or service providers is mandatory. The data should be provided in in DATEX II or any machine readable format fully compatible and interoperable with DATEX II.

Specific access requirements for the exchange and re-use of the data registered on the NAP-ITS apply. These include, amongst others, the dissemination on a non-discriminatory basis and dissemination within a timeframe that ensures the timely provision. See Article 7 of the Delegated Regulation for a full overview.

SRTI data includes different types of road safety related events or conditions:

Types

Temporary slippery road

Animal, people, obstacles, debris on the road

Unprotected accident areas

Short-term road works

Reduced visibility

Wrong-way driver

Unmanaged blockage of a road

Exceptional weather conditions

 

The information for all data types should thereby include:

  • The location of the event or condition
  • The category of the event or conditions and where applicable a short description
  • Driving behavior advice, where appropriate

Note that the information should be withdrawn if the event or condition cease to subsist, or shall be modified if there is a change in the event or condition.

If your organization registers a dataset or service on the NAP ITS for the category SRTI, it needs to submit a complementary Declaration of Compliance. Broadcasters are also required to submit a Declaration of Compliance, even though they do not need to register datasets or services. Read more about it here.

 

Public or private parking operators and service providers need to collect data on safe and secure public and private parking areas for trucks and commercial vehicles on the TEN-T network.

Registration of the collected data on the NAP ITS by the public or private parking operators and service providers is mandatory. The data should be provided in DATEX II or in any other internationally compatible format in order to ensure interoperability of the information services across the Union.

SSTP data includes:

1. Static data related to the parking areas, including (where applicable):

  • Identification information of parking area
  • Location information of the entry point in the parking area
  • Primary road identifier1/direction, and Primary road identifier2/direction if same parking accessible from two different roads
  • If needed, the indication of the exit to be taken/Distance from primary road
  • Total number of parking places for trucks
  • Price and currency of parking places

 

2. Information on safety and equipment of the parking area:

  • Description of security, safety and service equipment of the parking including national classification if one is applied
  • Number of parking places for refrigerated goods vehicles
  • Information on specific equipment or services for specific goods vehicles and other

3. Dynamic data on availability of parking places:

Including whether a parking is full, closed or number of free places which are available.

For dynamic data, public and private operators and/or services providers are required to update their information no less than once every 15 minutes

 

If your organization registers a dataset or service on the NAP ITS for the category SSTP, it needs to submit a complementary Declaration of Compliance. Read more about it here.

  

 

The registration procedure is also clearly explained in our instruction video.

If you have any questions or troubles when filling in the metadata form, please contact our NAP helpdesk at contact@transportdata.be.