If you have ever searched for a reliable source of low clearance bridge data, you have probably ended up in the same place everyone does: the National Bridge Inventory. And if you tried to use that data for actual route planning, you probably ran into problems immediately.
The truth is that low clearance bridge data in the United States and globally is in bad shape. The sources that exist are incomplete, outdated, inconsistent, and in many cases explicitly disclaim their own accuracy. This is the core problem that Low Clearance Map was built to solve.
The National Bridge Inventory: What It Is and What It Is Not
The National Bridge Inventory (NBI) is maintained by the Federal Highway Administration (FHWA). It contains records for over 600,000 bridges across the United States. On the surface, it looks like exactly what you would want for clearance routing: a federal database of every bridge in the country with structural data.
In practice, it falls short of being useful for clearance-based navigation for several reasons.
Clearance Data Is Not Reliable for Routing
The FHWA itself states that NBI data should not be used for route clearance purposes. Bridges are inspected on a two-year cycle at best, so clearance values in the database may not reflect current conditions. Construction, repaving, seasonal ground shifts, and structural modifications can all change the actual clearance of a bridge between inspection cycles.
Missing and Inconsistent Records
Academic research into NBI data quality has found widespread issues including missing fields, erroneous entries, and logical inconsistencies. One study found that approximately 1% of bridge records were not located within 100 meters of any actual road: meaning their GPS coordinates were wrong. Other records show structural condition improvements over time with no corresponding maintenance activity recorded, suggesting data entry errors or retroactive corrections without documentation.
No Directional Data
The NBI records a single clearance value per bridge. It does not indicate which direction of travel the restriction applies to. A bridge that is 11 feet on the northbound side and 14 feet on the southbound side is recorded as a single value. This means any system that uses raw NBI data will either generate false warnings for drivers approaching from the safe direction, or miss hazards entirely if it picks the wrong value.
Not All Low Clearances Are Bridges
The NBI tracks bridges. It does not track other low clearance structures like parking garage entrances, private overpasses, railroad underpasses on private roads, canopies, or overhead utility infrastructure. These structures are not in any federal database but are very real hazards for tall vehicles.
Google Maps, Waze, and Apple Maps: Zero Clearance Awareness
The navigation apps used by hundreds of millions of people have no bridge clearance data in their routing engines. This is not an oversight or a feature they are working on: it is a fundamental design choice. Google Maps, Waze, and Apple Maps are built for passenger vehicles. They optimize for travel time, traffic conditions, and turn efficiency. Vehicle height is not a variable in their routing algorithms.
Google has added some limited low bridge markers as map annotations in certain regions, but these are display-only points of interest: they do not influence the route the app calculates. If a 10-foot bridge is directly on your route, Google Maps will still send you straight into it.
Waze has a community-based reporting system that occasionally surfaces low clearance warnings, but these are user-submitted, unverified, and not integrated into routing logic. They appear as passive alerts, not route modifications.
Apple Maps has no bridge clearance features at all.
The Truck GPS Gap
Dedicated truck GPS apps like SmartTruckRoute, CoPilot, and Trucker Path do account for vehicle dimensions in their routing. But the quality and coverage of their bridge clearance databases are not publicly documented. Most rely on combinations of NBI data, commercial data providers like HERE and TomTom, and proprietary additions. None of them disclose how many bridges they track, how often their data is verified, or how they handle the directional problem.
This creates a trust gap. Drivers are asked to rely on bridge clearance routing without being able to evaluate whether the underlying data is actually good enough to keep them safe.
How Low Clearance Map Approaches the Problem Differently
Low Clearance Map was built specifically because the existing data sources are inadequate. Instead of scraping NBI records and shipping them as-is, we built a curation pipeline that treats bridge clearance data as a safety-critical dataset that requires active verification and maintenance.
23,000+ Verified Records
The Low Clearance Map database contains over 23,000 verified bridge clearance records across the United States, Canada, and the United Kingdom. Every record goes through a multi-step verification process before it enters the database.
Six-Stage Data Pipeline
Our curation process has six stages:
Source Identification. We pull from government databases (NBI, provincial/state DOT records, UK Highways England data), satellite imagery, street-level data, and community submissions. No single source is treated as authoritative.
Data Extraction. Raw clearance values, coordinates, and structural metadata are extracted and normalized into a common format.
Data Standardization. Units are converted, coordinate systems are aligned, and duplicate or near-duplicate records are resolved. This step catches a surprising number of issues: feet vs. meters confusion, transposed coordinates, and records that reference demolished or replaced structures.
Accuracy Verification. Clearance values are cross-referenced against multiple sources. Where discrepancies exist, the most conservative (lowest) value is used until verification can resolve the conflict.
Hazard Direction Annotation. This is the step that no other provider does. Every bridge in the database gets a Hazard Heading. This directional data indicates which direction of travel the clearance restriction applies to. It is calculated using road geometry, bridge orientation, and approach angles. It eliminates false positives for drivers approaching from the unaffected side.
Maintenance. The database is continuously updated as new data comes in. Community submissions from drivers, DOT notifications, and periodic re-verification cycles keep the data current. This is not a static dataset. It is a living system.
Why This Matters for Drivers
The practical impact of better data is fewer false warnings and fewer missed hazards. If your navigation app warns you about a bridge that is actually safe in your direction of travel, you learn to ignore the warnings. If it misses a bridge entirely because it was not in the database, you learn the hard way.
Low Clearance Map's combination of database size (23,000+), directional accuracy (Hazard Headings), and active curation means drivers get alerts that are both reliable and relevant. When HeadRoom tells you a bridge ahead will not fit your vehicle, you can trust it. And when it does not warn you, you can trust that too.
The Data Problem Will Not Fix Itself
The NBI is not going to become a real-time clearance database. Google is not going to add bridge heights to Maps. Waze is not going to verify community-submitted clearance reports. These are structural limitations of how those systems are designed and funded.
The only way to get reliable bridge clearance data is to build and maintain it as a dedicated, purpose-built dataset: which is exactly what Low Clearance Map does. Our database is the largest verified bridge clearance dataset in North America, and it is the foundation that HeadRoom's SafeRoute navigation runs on.
If you are a driver who has been burned by bad data: whether it was a false warning that made you take an unnecessary 30-mile detour, or a missed bridge that nearly took your roof off: you already understand why this matters.
Try HeadRoom free for 7 days and see the difference verified, directional bridge data makes on a route you know well.
