DOT-NL
Functional FAQ
Why do I have to share charging point locations and tariffs?
Under the European Alternative Fuels Infrastructure Regulation (AFIR), sharing location data and tariffs for public electric charging points is mandatory for all EU Member States. AFIR aims to ensure that consumers and other end users have sufficient information about the location and characteristics of publicly accessible charging infrastructure. The Dutch government’s implementation, under the leadership of the Ministry of Infrastructure & Water Management, is the DOT-NL platform, which is managed by NDW. By establishing harmonized specifications for the format, frequency, and quality of data, reliable information can be provided.
Who does this obligation apply to?
This obligation applies to all Charge Point Operators (CPOs) within the Netherlands that operate publicly accessible charging points. Aggregators and service providers (for example, those supplying systems for CPOs) do not have this obligation. However, aggregators may submit data on behalf of CPOs; the CPO remains responsible for the data.
What does the obligation to share data entail?
For a full description, we refer to the AFIR documentation from the European Union. In short, it concerns the real-time sharing of location, availability, and tariff information of charging infrastructure. The AFIR provisions are elaborated in three interconnected regulations, which can be downloaded here.
From which date does this regulation apply?
All relevant regulations are in force. The AFIR regulation has applied since April 2024, and the delegated and implementing acts have applied since 14 April 2025.
Who is primarily responsible for making the data available?
Responsibility lies with the operators of publicly accessible charging and refuelling points or, if agreed otherwise, with the owners of those points.
Must this data be provided free of charge?
Yes. The regulation states that both static and dynamic data must be made available free of charge.
What is a publicly accessible charging point?
A publicly accessible charging point is a charging point located on a site to which everyone has access. This access may also be indirect, for example if access to a site can be obtained by becoming a member or customer of an organization. This means that charging points behind barriers on business parks and in parking garages may also fall under this definition. For a detailed explanation, see the European Commission’s guidance under questions 2.7 to 2.18.
How do I connect to the NAP (to supply data)?
By contacting NDW, a connection can be arranged. Technical documentation for integration is also available here.
Where can I find technical documentation to supply or consume data?
NDW technical documentation can be found at:
Who are the users of the NAP?
The data can be consumed free of charge by anyone. Examples of users include:
- Car manufacturers and navigation service providers, for route planning
- Charging and data providers, for price comparisons or publishing charging maps
- Researchers, for conducting studies
- Governments, for informing policy, evaluating policy, or supporting enforcement
In addition, there are two types of data suppliers:
- Charge Point Operators: they are the data owners in the NAP and carry the legal obligation
- Aggregators: support CPOs in supplying data; the CPO remains responsible for the submitted data
I have complaints about data quality — where can I go?
NDW manages the DOT-NL platform. Data quality is part of the European AFIR regulation and is therefore also the responsibility of the data owner. It is possible to report poor data quality to NDW, but ultimately responsibility lies with the supplying party, the data owner. NDW does not perform post-processing on the data in the end product (for the GeoJSON publication, NDW does apply processing, as this is a summary of supplied data).
What roles do NDW / I&W / the Supervisory Authority have in the process?
- The Ministry of Infrastructure & Water Management is the commissioning authority of the DOT-NL platform and is responsible for implementing the AFIR legislation in the Netherlands.
- NDW is the operator of the data platform, commissioned by the Ministry of I&W.
- A supervisory authority oversees compliance with the legal obligations for data provision and data quality. If data does not appear to comply, the authority may conduct further investigations and ultimately impose sanctions.
Who can I contact if I have questions?
Does this dataset contain personal data?
No, this dataset does not contain personal data.
Does this data contain commercially sensitive information?
No, this data does not contain commercially sensitive information.
I am missing a charging point in the dataset — how can it be added?
Charging point operators are required to list all publicly accessible charging infrastructure in the National Access Point. You can inform the operator that a charging point is missing from the NDW dataset. You can also notify NDW that certain infrastructure is missing; NDW will then follow up with the operator.
Can I retrieve historical data from DOT-NL?
No, this is not possible. There is no historical database set up for this data.
Can I receive the data in another format?
No, this is not possible. We currently offer OCPI (the industry standard) and GeoJSON (easy to process). A DATEX II delivery is forthcoming to comply with the European regulation. No other data formats are planned.
Can I also receive the data via PUSH?
No, not yet. According to the planning, this will become possible toward the end of 2026, in OCPI format.
What is the role of an aggregator?
We cannot provide an overview of this. However, we can clarify that NDW does not offer services to CPOs. We limit ourselves to the statutory duty of bringing together and publishing data at an access point. We also do not modify data. Editing data for data quality purposes or connecting CPOs to DOT-NL are examples of services that aggregators may offer.
Is an IDRO registration required when supplying data?
Yes, when supplying data, NDW requires an IDRO registration. The reason is that the formatting of charging point IDs requires the first part of the ID to be assigned in an IDRO. We are aware that an IDRO registration in any European Member State is sufficient; therefore, a registration specifically for the Benelux IDRO is not required.
What is the difference between static and dynamic data?
Static data changes relatively infrequently (such as location and address), while dynamic data reflects the current status (such as availability and pricing). This is further specified in the aforementioned European delegated and implementing acts.
How quickly must data changes be applied?
Static data must be updated as soon as a change occurs and at the latest within 24 hours after the change. Given its real‑time nature, dynamic data must be updated within one minute of a change.
How do Member States verify whether the data is correct?
Member States must establish procedures for regular checks of the data and the APIs exposed via their NAPs. In the case of widespread and persistent problems, Member States are obliged to address data delivery in their National Access Points. If the content of the data is incorrect, the supervisory authority will engage with the CPOs.
Can I also download this data for all of Europe?
Yes. Every CPO active in Europe is required to make its data available via the NAPs, as specified in AFIR. In addition, the European Commission will provide a common European access point by 31 December 2026 containing information about the NAPs. It is not yet known whether, in the future, data from data owners can also be accessed directly through this point.
Which parties are connected to the NAP?
| Party | PartyId |
|---|---|
| Fastned | FAS |
| Allego | ALL |
| Blink Charging | BLK |
| BP Pulse | BPE |
| ChargePoint | CPI |
| Circle K | CKE |
| E.ON Drive | UFC |
| Electra | ELD |
| Eneco | ENE |
| Equans | LMS |
| IONITY | IOY |
| Tango Electric | Q8E |
| Jolt Energy | JEG |
| Lidl | LDL |
| PowerGO | PGO |
| Shell Recharge | TNM |
| Total Energies | GFX |
| Ubitricity | UB2 |
| Porsche | 911 |
| Q-Park | QPA |
| Interparking | IPK |
| North Sea Port | LIT |
| Laadnet | LNT |
| Vattenfall | NUO |
| IPCharging | IPC |
| E-Volt | EVT |
| Road | EFL |
| Tesla | TSL |
| AgriSnellaad | AGO |
| PowerLand | PWL |
| MobilityPlus | MBP |
| Optiload | OPL |
| Daen Mobility | DAE |
| Mobiflow | MBF |
| Smappee NV | SMP |
| e-RS | ERS |
Technical FAQ
Is having a connection to the NAP (DOT-NL) sufficient to comply with the DATEX II obligation under AFIR?
If NDW, the operator of the NAP, can convert the OCPI submission into all mandatory DATEX II fields required under AFIR, then submitting OCPI data to the Dutch NAP is sufficient.
Which OCPI version does the NAP use?
The DOT-NL platform currently exclusively uses OCPI version 2.2.1. This does not fully meet the European AFIR requirements, which is why there are plans to migrate the platform to OCPI version 2.3 in the near future. DOT-NL will then also provide (eventually) the translation from OCPI to DATEX II format to comply with AFIR.
Why do you not use the OCPI credentials module?
We have chosen to use an OAuth2 implementation to push data to the DOT-NL platform. For pull deliveries, we therefore request the Token-C directly.
Is a data validation schema available for data submission?
Certainly. At ingestion, we validate whether the data complies with the OCPI 2.2.1 specification. This schema is available via: DOT-NL data submission.
Which party_id must be present in the data?
The party_id of the CPO must be present in the data. It is permitted to submit data for a CPO via an aggregator, but the party_id of the CPO must then be included in the data.
What quality requirements must the data meet?
Data must meet five core values: completeness, accuracy, consistency, timeliness, and reliability.
What exactly does the requirement of “completeness” mean?
This means that all data types required by AFIR must be made available. Operators may also voluntarily share additional data.
What is meant by “consistency” of data?
Consistency means that the data complies with the prescribed format and that any duplicate or overlapping data is removed.
How is the “reliability” of data verified?
Operators or owners must regularly check the data for errors and inconsistencies. They must establish quality control mechanisms at the source.
Which technical format is mandatory for data exchange?
From 14 April 2026, the use of the DATEX II format (specifically CEN/TS 16157-10:2022) is mandatory for all data types. Data must be submitted to the NAP in OCPI 2.2.1, after which NDW translates it from OCPI to DATEX II to comply with AFIR.
Is there a transition period for the technical format?
Yes. Although the regulation enters into force in 2025, the complex DATEX II format only needs to be fully applied from 14 April 2026. Any transition to another OCPI version will be communicated well in advance.
May an operator outsource the provision of data?
Yes. Another entity may set up an API to grant data users access on behalf of operators. This does not relieve the operator of responsibility for data quality.
I already share my data with the LINDA platform. Why do I also need to connect here?
LINDA is organized by Dutch municipalities and provinces in cooperation with the NAL (National Agenda for Charging Infrastructure) and focuses on monitoring data for internal use. It therefore concerns different (non-public) data and does not meet the AFIR requirements.