If you build routing, dispatch, or telematics software for European trucking, the routing algorithm is rarely what slows the roadmap down. The road data is. A truck plan from Rotterdam to Bucharest crosses a dozen jurisdictions, and each one publishes what's happening on its roads — incidents, tolls, restrictions, charging — its own way, on its own schedule, under its own rules. Below are the five problems that come up in nearly every conversation we have with European fleet and logistics-software teams. None are exotic. All of them quietly burn engineering time.
1. Twenty-Seven Countries, Twenty-Seven Access Points
The EU ITS Directive did get every Member State to stand up a National Access Point (NAP) publishing road data, mostly as DATEX II. That sounds like a solved problem until you actually connect to a second country. The standard leaves room, and the NAPs use all of it — different DATEX profiles and versions, different authentication, different update cadences, different ideas of what a given field means. And plenty of operationally useful data never travels as DATEX II at all: it sits on municipal open-data portals or in national feeds that predate the plumbing.
So a team that wants genuine continental coverage ends up writing and maintaining a separate integration per country, then babysitting all of them as feeds quietly change shape. This is the problem that eats the most time, because it never finishes. We wrote up how we normalize DATEX II across the European NAPs and how the non-DATEX sources fold into the same schema — the short version is that the per-country mess becomes one consistent events and features contract, and keeping the adapters alive becomes our problem instead of yours.
2. The Toll Bill Changes at Every Border
There is no single European toll. There are vignettes, distance-based schemes, per-axle HGV charges, urban congestion fees, and tunnel and bridge tolls — each country with its own model, its own vehicle classes, and its own emission-class surcharges. A route that looks cheapest on distance can be the most expensive once the tolls land, and the difference between a 5-axle Euro VI rig and a smaller van is real money on every leg.
For a planner, an estimate that ignores vehicle class is an estimate that's wrong at invoice time. For a software team, pricing a cross-border route by hand means modelling a dozen national toll systems and keeping them current as rates change. We pulled this together so a route comes back with a vehicle-class-aware toll breakdown per country — see vehicle-class-aware toll costs across Europe.
3. Where the Clock Runs Out — and Whether There's Parking
EU Regulation 561/2006 driving-time rules and the chronic shortage of secure truck parking are really one problem wearing two hats. Knowing a driver will hit the daily driving limit at 18:40 is only half of it. The half that strands a truck — or forces an unsafe roadside stop — is whether there's a legal, reachable place to take the break when the clock runs out, and that answer needs both the driving-time projection and live parking data on the same corridor.
Most teams solve the first half and discover the second half at the lay-by. We tied them together: send the driver's clock with the route and get back every required break, each paired with the parking reachable before the deadline and a feasible flag when none is. That's the subject of break planning under EU 561/2006.
4. The Ban You Didn't Know About Until the Border
Cross-border trucking runs on a patchwork of national restrictions that no consumer map knows about: weekend and night driving bans, sectoral and sector-specific bans on Alpine corridors, low-emission zones in city centres, country-by-country weight and dimension limits, and seasonal restrictions. A plan that's legal in one country can be illegal across the line at the same hour — and the penalty for finding out the hard way is a fine, a forced wait, or a turned-back load.
The operational need isn't "a list of every rule in Europe." It's "tell me about the restrictions and variable-message signs on this corridor, before the driver gets there" — restrictions and signage from the official national feeds, normalized into the same queryable features the rest of the API speaks, filterable by country and bounding box. One schema for a German night ban and an Austrian sectoral ban means you check one place instead of twenty-seven.
5. Charging an Electrifying Fleet, Across the Gaps
As fleets electrify, "where can this vehicle actually charge on the corridor" becomes a routing input, not a nice-to-have. The EU's AFIR regulation now obliges charge-point operators to publish live per-connector status through the NAPs — that's the gold standard, and where a country carries it we serve it. But AFIR coverage is only as complete as each NAP's rollout, and several countries don't expose a mature EV feed yet.
So the honest answer is two layers, surfaced so you can tell them apart: live status where AFIR carries it, and an openly-licensed charging registry — coordinates, connector standards, power ratings — where it doesn't. Every charger says which guarantee it's giving you. We covered the live side in AFIR Article 20 EV-charging telemetry and the coverage side in folding open data into one European API.
The Common Thread
Every one of these is the same shape of problem: the data exists, but it's fragmented across national authorities, published in incompatible formats, governed by different licenses, and only useful once it's joined to a route and kept fresh. Each one is solvable in-house — and each one, solved in-house, becomes a permanent maintenance commitment that competes with the product you actually sell.
That's the entire premise of NAPSPAN: do that aggregation once, for everyone, and hand you one normalized API — events, features, tolls, restrictions, charging, routing with corridor hazards — instead of twenty-seven integrations to keep alive. The data is served from Europe, every source is license-classified before it ships, and you spend your engineering time on the part that makes your product yours.
Try It
-
API docs —
events,features, routing, and the?country=/?type=filters in one reference - Live map — see the normalized data across the European NAPs
- Free API key — no card, 14-day trial
One API instead of twenty-seven integrations. Continental coverage — incidents, tolls, truck restrictions, EV charging, and routing — normalized into one GeoJSON schema and served from Europe. Free 14-day trial. No card. Get a free API key or read the docs.
Originally published on napspan.com.
Top comments (0)