Why Google Maps can't tell you a lane is closed at MP 142

Washington's DOT can tell you the right lane is closed at mile marker 142 on I-90. It posted that alert twelve minutes ago. Google Maps can't tell you any of it.

It's not because the data doesn't exist. Every state's Department of Transportation publishes road-condition alerts in real time. It's because nobody connected those feeds to the apps people actually drive with.

I wanted to understand why. The answer became MileCheck.

The data exists, and almost nobody sees it

Every state runs a real-time road-alert feed. WSDOT in Washington, TripCheck in Oregon, AZ511 in Arizona, 511GA in Georgia, FL511 in Florida — all live, public-facing, updated continuously. All of that information is public.

But the data shows up on each state's own map and basically nowhere else. It never gets aggregated into the apps people use to drive. So a closure the Montana DOT posted an hour ago sits in public view — and the trucker driving toward it on I-90 has no way to see it without knowing to open Montana's specific 511 site, on the specific day, in the specific browser tab.

Why the big nav apps don't bother

Two reasons, both rational from where those companies sit.

First, every state's feed is shaped differently. One state serves its data as a raw JavaScript variable — var static_api = {...}; — not clean JSON, because it was built for a hardcoded webpage years ago and nobody migrated it. Another hides mile markers inside map-line geometry. Texas runs its own custom platform. There's no single standard to integrate against; there are fifty.

Second, DOT alerts aren't the kind of data most consumer navigation products optimize around. GPS traffic comes from millions of phones. DOT alerts come from the agencies managing the road. Cross-state normalization is a lot of engineering for a relatively small consumer feature, so most platforms don't prioritize it. Reasonable for them — but it leaves a real gap.

Who actually loses when nav apps skip this data

The people who drive for a living.

The trucker running cross-country who hits a closure with no posted detour. The DOT crew that can't see what other crews are reporting on the same corridor. The EMT trying to route around an incident they don't yet know is there. The dispatcher who gets a call that says "I'm on I-95 somewhere in Connecticut" and has no way to verify or refine it.

These aren't edge cases. They're the daily reality of the freight and first-responder world, where "where exactly are you?" is a question with real money and real safety riding on the answer — and the consumer nav apps don't speak that language.

What I built

A backend that pulls from 50 different state DOT systems, normalizes them into a single format, and serves them through a real-time API — to an app that also shows you exactly where you are on the road, down to a tenth of a mile.

I think of it as the highway intelligence layer: a normalized view of state DOT road data that actually works across state lines. Today it's live with road alerts in 42 states and mile markers in all 50, and the app holds 5.0 stars on both the App Store and Google Play. It's used by truck drivers, DOT crews, EMTs, and everyday commuters.

The app on the surface is simple — a big mile marker, your speed, the alerts ahead of you. The hard part is underneath. One state's feed arrives as a JavaScript variable instead of JSON. Another buries mile markers in map geometry. Another runs on a platform completely different from its neighbors. The hard part isn't finding the data — it's keeping fifty different systems behaving like one as endpoints move, keys expire, and agencies reorganize. That maintenance discipline is the product. The result is one consistent layer that works the same whether you're driving in Washington, Texas, Florida, or North Dakota.

The piece no one else has shipped: navigate to a mile marker

Here's the feature that surprised even me with how obvious-in-hindsight it is.

You can't type "I-90 MP 200" into Google Maps. No consumer navigation app I've found treats a mile marker as a place you can go. You can navigate to an address, a business, a dropped pin — but not to the one coordinate system the entire highway world actually runs on.

MileCheck does. Enter a mile marker on any route and the app routes you to it, the same way you'd enter a street address. As far as I've been able to find, it's the first consumer app to treat a mile marker as a navigation destination.

That sounds small until you think about who needs it. A dispatcher tells a driver "meet the load swap at I-80 MP 184." A DOT supervisor sends a crew to "the guardrail damage at US-2 MP 47." A tow operator is told "the breakdown is at I-5 MP 204 southbound." Today every one of those handoffs ends with someone fumbling to convert a mile marker into something their nav app understands. It shouldn't.

The bigger thesis

GPS-derived traffic is great at one thing: telling you a highway is slow right now. It's structurally incapable of telling you why a bridge is closed, where a lane closure begins, or which detour a DOT just posted. That information doesn't emerge from the movement of phones — it comes from the people managing the road itself. The closure data is the part the algorithms can't infer. Somebody has to go get it from the source.

The future of highway data isn't choosing between algorithms and agency data. It's combining both.

That's the bet behind MileCheck's highway intelligence layer.