Integration Between A Better Routeplanner (ABRP) and DGT 3.0 Platform

Dear ABRP Team,

I would like to propose that A Better Routeplanner (ABRP) explore a potential integration with the DGT 3.0 mobility data platform developed by the Spanish Directorate General of Traffic (DGT). DGT 3.0 is a connected vehicle platform designed to share and consume real‑time traffic and mobility data across the Spanish road network, with the objective of improving traffic safety and offering timely notifications of road conditions. DGT

Why This Integration Could Be Valuable

Integrating ABRP with DGT 3.0 could provide the following benefits:

1. Real‑time traffic and incident data — DGT 3.0 distributes information on road incidents, works, events, and other condition changes across the network. DGT

2. Improved route planning for EV drivers — Combining ABRP’s routing and energy management with live traffic data would help EV drivers optimize routes for safety and efficiency.

3. Enhanced user experience — Access to authoritative mobility data from a national authority can increase user confidence and accuracy of predictions.

About DGT 3.0

DGT 3.0 is a platform that connects multiple actors in the mobility ecosystem — including vehicle manufacturers, application providers, fleet managers, infrastructure operators, and navigation service providers — via standardized interfaces for sharing and consuming traffic information in real time. It supports API REST and MQTT communication models depending on use cases. DGT

The documentation for various services is publicly listed by DGT and accessible through code repositories such as:

• DGT 3.0 technical documentation page:
  https://www.dgt.es/muevete-con-seguridad/tecnologia-e-innovacion-en-carretera/dgt-3.0/ DGT

• GitHub repositories with example specifications for specific use cases (e.g., low emission zones, roadside warnings, event notifications):
  https://github.com/dgt30-esp/averias‑en‑carretera
  https://github.com/dgt30‑esp/zbe
  (and other service repos listed on the official site) DGT

How to Start Integration

To begin integration with DGT 3.0, the following steps are generally required:

1. Review service documentation — Identify which DGT 3.0 services are most relevant to ABRP (e.g., traffic incidences, works, hazard warnings).

2. Apply for access — DGT requires a connection request submission and validation process through their access form (linked on the DGT 3.0 page). DGT

3. Technical onboarding — Systems integrating with DGT 3.0 are typically configured with a whitelisted backend IP and authenticated with a Digital Certificate X.509 v3, as detailed in the platform’s technical documentation. DGT

4. Develop API connectors — Based on the API specifications (REST/MQTT) provided in the documentation repositories, implement endpoints that can consume or share data between ABRP and DGT 3.0.

Closing

I believe that establishing this connection would position ABRP as a forward‑looking EV routing service with authoritative traffic insights from a national mobility data platform. If you need more detailed references to specific API schemas or support on DGT 3.0 onboarding, I can help gather technical links and guidelines.

Thank you for considering this proposal.

Sincerely,