Truck Intelligence
Canadian truck networks, road and bridge restrictions, and vehicle-aware route validation layered onto unmap truck routing.
This page exists because the add-on is in preview, and the reason it is in preview is that its coverage is incomplete. So the coverage is the product documentation, not a footnote to it.
What this is not. It does not make a route legally or regulatorily compliant, and it is not a substitute for reading a posted sign. A driver and a carrier remain responsible for the vehicle on the road. What it does is tell you what was checked, what was not, and where the data came from.
Truck routing is not the add-on
mode=truck is included with normal routing on every plan, and always has been. Without Truck
Intelligence a truck route still gets:
- Valhalla truck costing
- the truck restrictions carried in the road network (OpenStreetMap)
- every vehicle profile parameter:
height,width,length,weight,axle_load,axle_count,hazmat,use_truck_route
Truck Intelligence adds the layer that is expensive to build and hard to reproduce: maintained Canadian government restriction data, validation against the vehicle you declared, and the coverage and provenance reporting that says how far to trust the answer.
A truck route is one call from your plan's allowance, with or without the add-on. There is no truck multiplier and no separate truck meter.
Without the add-on, the response says so
/route?mode=truck does not fail on a key without Truck Intelligence. It returns the same route,
and a truck block that reports honestly that nothing was checked:
{
"distanceMeters": 412903,
"durationSeconds": 16840,
"geometry": { "type": "LineString", "coordinates": [/* … */] },
"truck": {
"profile": { "height": 4.2, "weight": 38 },
"profileComplete": false,
"coverage": {
"truck_network": "not_checked",
"physical_restrictions": "not_checked",
"bridge_weight": "not_checked",
"bridge_clearance": "not_checked",
"hazmat": "not_checked",
"conditional_restrictions": "not_checked",
"temporary_restrictions": "not_checked"
},
"verification": "unknown",
"warnings": [{ "code": "TRUCK_INTELLIGENCE_NOT_ENABLED", "message": "…" }]
}
}Every class reads not_checked rather than osm_only. That distinction is deliberate: osm_only
is a claim about provenance, meaning we looked and what we found came from OpenStreetMap. Without
the add-on nothing looked, and describing a check that did not happen is the failure this whole
surface exists to avoid. validation is absent rather than an empty report, because an empty
conflicts list reads as "no conflicts", which is a claim rather than a silence.
Closures are not gated
Road closures published by a provincial authority appear in the top-level warnings array on
every mode, including mode=car, with or without the add-on. A shut road is shut to a car as
much as to a truck, and the routing graph is rebuilt weekly so it cannot carry a closure.
What the add-on buys on top of that is the comparison: whether a posted limit excludes the vehicle you declared.
Coverage
Coverage is per jurisdiction and per restriction class, because a province publishing one does not mean it publishes the others. Read this table before promising anything to a customer.
Static government data, by jurisdiction
| Jurisdiction | What is ingested | State |
|---|---|---|
| Nova Scotia | Road Weight Designations (gross weight, coordinate-bearing) | Proven end to end: 10,279 restrictions, 92.0% matched to road segments, verified to change routes |
| Québec | Réseau de camionnage access classes | Proven end to end: 263k restrictions injected, measured 34% faster truck routes |
| Alberta | Restricted bridge lists, per vehicle configuration | Ingested and placed to surveyed quarter sections; not yet matched to roads, so not applied |
| Alberta (municipal) | Grande Prairie, Lethbridge truck and dangerous-goods routes; the regional High Load Corridor | Ingested and conflated; truck routes applicable, dangerous-goods and corridor held (see below) |
| Ontario | 511 event feed | Closures only |
| British Columbia | Open511 DriveBC | Closures only |
| Everywhere else | none | Nothing. No claim is made. |
Live and seasonal restrictions, by jurisdiction
| Jurisdiction | Feed | What it yields |
|---|---|---|
| Ontario | 511 Ontario | Full closures. Its own restriction fields are null on every record. |
| Alberta | 511 Alberta | Closures and valued weight limits, compared against your vehicle |
| British Columbia | Open511 DriveBC | Closures only. Its prose carries real dimensional restrictions that we deliberately do not parse, because one record states a minimum ground clearance under the same keywords as two maxima, and 11 usable restrictions sit among 101 location offsets of identical shape. |
| Everywhere else | none | Nothing. Absence of a closure warning outside these three means nothing was checked. |
Restriction classes
| Class | State | Why |
|---|---|---|
Truck network (hgv) | Community-mapped, plus government designations where ingested | Covered wherever a jurisdiction above publishes it |
| Physical restrictions (height, width, length) | Community-mapped; real but uneven and concentrated in one province | No national inventory is published |
| Bridge weight | Community-mapped on very few segments | Canada publishes no national bridge inventory. A route with no weight exclusion does not mean the structures on it are rated for your load. |
| Bridge clearance | Community-mapped | As above |
| Dangerous goods | A single flag, never TDG classes | The engine collapses every hazmat sub-tag into one boolean, so per-class rules cannot be honoured |
| Conditional restrictions | Not modelled | The routing engine drops conditional restrictions at build time, so spring thaw and night-time bans cannot apply |
| Temporary restrictions | Checked per request in three provinces | See the table above |
Held deliberately
Two ingested datasets are not applied to routes, and that is a decision rather than a gap:
- Dangerous-goods designated routes. The engine has one hazmat flag and it means prohibited. A designation has nowhere to go, so recording it as one would invert the rule.
- The High Load Corridor. A corridor says where an over-height load may travel, not where a truck should. Telling the engine to prefer it would change routing for every truck on a misreading of the source.
Both are queryable in the audit trail and visible as known-but-not-applicable.
Provenance
Every authoritative restriction carries its source, the authority whose rule it is, the licence it arrived under, whether that licence was verified or merely accepted by a named person, and where its geometry came from. An approximate location says so: a restriction placed at the centroid of a surveyed quarter section is recorded as such, and a quarter section is a half-mile square, so its centre is within about 570 m of anything inside it. A restriction we hold and cannot place carries no coordinates at all rather than a guessed one.
Preview pricing
$49/month while coverage is incomplete, on any paid plan. One Canada-wide entitlement: there are no per-province SKUs, and a new jurisdiction joins this same add-on rather than becoming another line on your invoice.
Pricing will rise as coverage does. If you subscribe during the preview you keep the preview price for a defined migration period after it changes, rather than being moved at the next renewal.
Free from localhost and preview origins on the dev plan, like every unmap add-on. A production
origin needs a paid plan and the add-on.
Agent tools
The MCP and A2A route tools use the same Truck Intelligence path as HTTP /route. An entitled
key receives the same validator results, coverage and warnings through all three interfaces. A
tool call remains one request from the same shared allowance.
