Information for dataproviders

This page helps you to determine whether the European Delegated Regulations apply to your organization and explains how to register your datasets and services on the Belgian NAP ITS.

By ‘registering’ we mean providing the necessary information (metadata) about your datasets or services and providing a link that allows users to access the data or service. You do not need to upload or store datasets directly on 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 organization creates or manages mobility related data for Belgium, you are most probably required to 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 2022/670)
  • Safety related traffic information (SRTI; EU 886/2013)
  • Information services for safe and secure truck parkings (SSTP; EU 885/2013)

Additionally, the data categories described in the regulation for Alternative Fuels Infrastructure (AFIR; EU 2023/1804) should be registered on the NAP ITS.

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 and management of traffic flows;
  • Service provider: any public or private provider of a real-time traffic information service, excluding a mere conveyer of data to data users;
  • Tolling operator: any public or private entity taking the role of toll service provider or toll charger;
  • Recharging and refuelling-related stakeholders;
  • Holder of in-vehicle generated data: any entity engaged in in-vehicle generated data collection and/or aggregation.

 

  • For SRTI:
  • Road operator: any public or private entity that is responsible for the maintenance and management of the road and management of traffic flows;
  • Service provider: any public or private provider 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 the static data described in the service levels 1-4 (see annex of the Delegated Regulation and the table below) for the whole Belgian transport network. 

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

 

Since the 1st of December 2025 it is 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.

There is only an obligation to digitize data if it is not yet available in a digital format for the “crucial data types”. The other data types should only be registered on the NAP if they already exist in a digital format. 

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 might need to submit a complementary Declaration of Compliance. Read more about it here.

 

Data holders—including road authorities, road operators, holders of in-vehicle generated data, tolling operators, service providers and recharging and refueling-related stakeholders (as defined here) —are required to make the following data, corresponding metadata and information on the quality of the data accessible on the NAP for the comprehensive TEN-T network, the motorways and primary roads. From the 1st of January 2028, the required data should be available on the NAP for the entire road network. 

There is only an obligation to digitize data if it is not yet available in a digital format for the “crucial data types”. The other data types should only be registered on the NAP if they already exist in a digital format. 

 

  • a. Data on infrastructure (the data should be provided in a standardized machine readable format such as INSPIRE-conform formats, TN-ITS, or DATEX II).

Types

Road network links and their physical attributes (geometry, road width, number of lanes, gradients, junctions)

Road classification

Location of tolling stations

Location of service areas and rest areas

Location of recharging 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 refueling points and stations for all other fuel types

Location of delivery areas

 

  • b. Data on regulations and restrictions (the data should be provided in a standardized machine readable format, e.g. TN-ITS or DATEX II).

Crucial types

Examples

Static and dynamic traffic regulations

Access conditions for tunnels and bridges, Permanent access restrictions, Speed limits, Freight delivery regulations, Overtaking bans on heavy goods vehicles, Weight/height restrictions, One-way streets, Boundaries of restrictions, Direction of travel on reversible lanes

Traffic circulation plans

 

Other types

Examples

Traffic signs reflecting traffic regulations and identifying dangers

Access conditions for tunnels and bridges; Permanent access restrictions; Other traffic signs reflecting traffic regulations

Static and dynamic traffic regulations

Other than the crucial traffic regulations referred to above

Tolled roads

Identification and applicable fixed user charges and available payment methods

Variable road user charges and available payment methods

 

 

  • c. Data on state of the network (the data should be provided in a standardized machine readable format, such as DATEX II or other compatible machine readable format).

Crucial types

Road and lane closures

Roadworks

Temporary traffic management measures

Other types

Bridge closures

Accidents and incidents

Poor road conditions

Weather conditions affecting road surface and visibility

 

  • d. Data on real-time use of the network (the data should be provided in a standardized machine readable format, such as DATEX II or a compatible machine readable format).

Type

Traffic volume

Traffic speed

Location and length of traffic queues

Travel times

Waiting time at border crossings to non-EU member States

Availability of delivery area’s

Availability of recharging points and stations for electric vehicles

Availability of recharging points and stations for alternative fuel types

Price of ad hoc recharging/refueling

 

Please note that registering data regarding recharging points and alternative fuel types on the NAP is also requested by the Delegated Regulation AFIR (EU) 2023/1804 . 

If your organization registers a dataset or service on the NAP ITS for the category RTTI, it might need to submit a complementary Declaration of Compliance. Digital map producers and other RTTI-data users are also required to submit a Declaration of Compliance, even if they do not register datasets or services. Read more about it here.

 

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 or re-uses a dataset or service on the NAP ITS for the category SRTI, it might need to submit a complementary Declaration of Compliance. 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 might need to submit a complementary Declaration of Compliance. Read more about it here.

You can register a dataset or service for your organization on the NAP ITS by following these steps, also clearly illustrated in our instruction video.

  • First create a personal account by clicking on the Register button on the homepage. Follow the displayed steps and do not forget to confirm your account by clicking on the link in the confirmation email sent to your mailbox. Depending on your mailbox settings you might find this email in the spam folder.
     
  • Log in with your account on the NAP ITS to create an organization or join an existing organization.
  • To create a new organization, click on the Add organization button on https://www.transportdata.be/organization. Follow the displayed steps and provide the metadata for your organization. Click Save Organization. The metadata of your organization and the Declaration of Compliance can later be changed in the overview of your organization by clicking the Manage button.
  • To join an existing organization, navigate to your organization's page by browsing through Organizations and click on the Request membership button. The administrator of the organization will receive an e-mail and will review your membership request.
  • Once you are a member of an organization, make sure you are logged in and navigate to the Datasets tab and click on the Add dataset button to register a new dataset or service.​​​​
  • Provide the metadata related to the dataset or service including licensing information. For this, we provide a convenient template that should be filled in, in line with the co-ordinated European profile (i.e. the Co-ordinated Metadata Catalogue).  When finishing your work, please make sure to set the visibility of your dataset or service to “Public” so that the metadata is publicly visible on the NAP ITS.
  • Note that it is not mandatory to disclose your data in an open-source manner. If you dont, data users will have to contact you prior to making use of your data. Make sure to provide accurate contact details for your dataset in the metadata.
  • Following, click the Next: add data button to link one or multiple resources to your dataset or service. Generally, a resource is a URL linking to an external location (for example your organization’s website) where the dataset or service is hosted. Smaller companies that do not have the capabilities to host datasets themselves have the opportunity to upload these datasets directly on the NAP ITS.
  • Submit the declaration of compliance of your organization. If you have already submitted a declaration of compliance, update it if necessary.
  • Repeat the steps above for each dataset or service you need to register.

Yes, for the Delegated Regulations RTTI and MMTIS you can authorize a third party to register your datasets and services on Transportdata.be. This party is considered as a proxy and needs to follow the normal procedure for registering an organization account and datasets on the NAP. Submitting the declaration of compliance belongs to the tasks of the proxy as well.

In addition, the proxy needs to upload the filled out proxy agreement (in pdf) on its organization account. This way, we are aware that your organization’s data are registered through the proxy and that the duties of both parties are clearly defined. You can download a template for the proxy agreement here.

Please note that if your organization has data to be registered on the NAP, but which is not included in the agreement with the proxy, your organization still needs to register these data separately on the NAP.

 

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.