How tall is your rig?
At 13' 6" there are … verified bridges, tunnels and overpasses you will not clear. Every one of them is on the map, with the direction it applies to.
28,232 verified structures across the United States, Canada and the United Kingdom. About three times the coverage of the next largest dataset. The demo runs a sample vehicle on routes within Ohio.FHWA, Case Study: Response to Bridge Impacts, an overview of state practices (HIF-20-087), 2020. Annual totals ran between 13,000 and 18,000 from 2013 through 2018. Read the report.
A strike is never just a repair bill
Indiana DOT billed one carrier $107,462 for a single hit on the Virginia Avenue bridge in Indianapolis. That bridge has been inspected for damage more than 70 times since 2006.
Behind the claim comes the road closure, the citation on your CSA record, the insurance renewal, and the days the truck sits. Apple Maps, Google Maps and Waze do not know how tall you are. We do.
Damage claim reported by NBC News, "In Indianapolis, there's a really smashing bridge" (2013). Read the article.
Check a route in four steps
Enter your route
Start, destination and any stops along the way.
Set your height
Truck, RV or trailer, in feet and inches. Save it once and it sticks.
We check every structure
Your path is checked against 28,232 verified clearances. Alerts only fire for the direction you are travelling.
Drive it
Send the cleared route to Apple Maps or Google Maps, or follow voice guidance in HeadRoom.
$4.99 a month, or $45 a year with a 7 day free trial. Unlimited routes, the full dataset and HeadRoom included. Cancel anytime.
HeadRoom: voice guidance that knows your height
The in-cab navigation app built on the Low Clearance Map dataset, on iOS and Android, with Apple CarPlay and Android Auto.
- SafeRoute
- Set your height once. Every route is built to fit it.
- Auto reroute
- A low clearance ahead triggers a new route on the spot.
- Sentry mode
- Hazard alerts keep running even when you are not navigating.
- Hazard headings
- Alerts only on the approaches that can hit you, never when you cross over the top.
A real walkthrough of HeadRoom on iOS. More about HeadRoom.
Built for anything taller than a sedan
Typical heights, and how many verified structures in our data sit below each one.
| Vehicle | Typical height | Structures you will not clear |
|---|
Why this data is different
Every low-bridge app is only as good as its list of bridges. Ours is bigger, checked, and knows which way you're facing.
- Verified, not crowdsourced
- Every structure is checked against public DOT records, computer vision on street-level imagery, and driver reports. Each record carries the date of the imagery it was last confirmed against.
- Three times the coverage
- 28,232 verified structures: 24,140 in the United States, 1,147 in Canada and 2,945 in the United Kingdom, all on one subscription. The next largest dataset we know of holds roughly a third of that.
- Hazard headings, which nobody else has
- A low bridge only threatens traffic passing under it, usually from one or two directions. Each record stores those compass headings, so routing detours you only when your direction is affected, and alerts fire only on those approaches. The result is fewer needless detours and far fewer false alarms.
Traffic coming in on the two red headings passes under the deck, so the router keeps tall vehicles off that stretch and HeadRoom warns on those approaches only. Traffic crossing on top is never rerouted or alerted.
The same routing, in your own stack
The API is self-serve: pick a plan, add a card, and your key is issued in about a minute. Every plan starts with a 14 day free trial.
- Safe Route and Clearance Check on every plan, the same clearance-aware routing behind the app and HeadRoom
- Send any route geometry (Google or HERE polyline, GeoJSON, coordinates) and get back whether it's safe and what's in the way
- Hazard headings and the imagery date on every record returned
- Full database access, scheduled CSV deliveries and the Database Portal on an annual licence
POST /api/check_route
X-Api-Secret: your-key
{ "route": "o~s~Fdj|uO...", // Google or HERE polyline, or GeoJSON
"clearance_feet": 13, "clearance_inches": 6 }
{ "safe": false,
"hazard_count": 1,
"hazards": [
{ "structure_id": "5318",
"name": "FRONTAGE RD Under I70 EB",
"clearance": 12.58, "distance_m": 4.2 } ] }
Illustrative request and response, trimmed. Field names follow the API reference.
Questions drivers ask
How accurate is the data?
Every entry is checked against public DOT records, computer vision on street-level imagery, and driver reports. Each point carries hazard headings so you only get alerts for your direction of travel.
How often is it updated?
Whenever new information arrives: new structures, changed clearances, better metadata. Commercial customers get scheduled CSV updates or live API access.
Is there a free version?
No. The annual plan starts with a 7 day free trial, and the monthly plan has no commitment. Both include unlimited routing and HeadRoom. A free demo with a sample vehicle is available for routes within Ohio.
Which regions do you cover?
The United States, Canada and the United Kingdom. UK drivers have their own page with heights in metres and feet.
What are hazard headings?
The compass directions a clearance applies to. Most low structures only threaten traffic approaching from one or two directions, so the router only detours you when your direction is affected, and alerts fire on those approaches and stay quiet on the others. Crossing over the top of a bridge never triggers a warning.