For platforms and partners
The highway intelligence layer — licensable, integrable, already in production.
Most milepost data products stop at the static layer: “where is MP 142?” MileCheck delivers both — that milepost lookup plus live conditions at MP 142 right now, normalized from 50 state DOT feeds across 19 distinct upstream platform formats. One schema. One API response. No state contracts on your side.
Open a conversation →Live on the Geotab Marketplace — the fleet add-in runs in MyGeotab today · data API by license.
Why the layer matters
The mile marker is the location format institutions actually run on.
GPS didn’t retire the mile marker — it exposed how much emergency response, dispatch, and the entire highway data system still depend on it. The evidence is primary-sourced:
It’s what dispatch asks for
“When calling #77 or 911 for emergency assistance, providing the information on a mile marker sign will help responders reach you quickly.”
— Virginia DOT, official guidance
Cell-phone 911 location is often wrong
The FCC requires carriers to deliver an accurate location for only 80% of wireless 911 calls — and highways are the worst case, where cell towers line up in a row and triangulation fails.
— FCC E911 location-accuracy rules
The maps in your pocket won’t show it
Google and Apple Maps deliberately omit mileposts — Google’s own support threads tell users there’s no setting, and to use a dedicated app. The one number a responder needs is the one consumer maps won’t display.
— Google Maps support
The whole system is milepost-referenced
DOTs locate nearly everything — crashes, work zones, signs, 511 alerts — by route + milepost. Since 2014, FHWA’s ARNOLD mandate requires every state to maintain milepost-referenced inventories of all public roads.
— FHWA ARNOLD / Linear Referencing
The infrastructure
Five layers, one stack.
Milepost corpus
Every interstate, US highway, and most state routes across all 50 states — sourced from official state DOT and government GIS records, never crowd-sourced. Quality-checked, normalized across state-by-state inconsistencies, and interpolated to one-tenth-of-a-mile precision between markers. Continuously updated as states add, reclassify, and re-route highways — a living dataset, not a one-time export. Bundled offline in the app; available as a structured dataset for integration.
DOT integration corpus
50 state DOTs integrated and growing, each a different upstream platform format. A serverless dispatcher normalizes every source into a single consistent road-conditions and incident schema, with caching tuned per source and resilient fallbacks for agencies with restrictive access.
Navigate-to-milepost primitive
The first consumer nav stack where a mile marker is a destination, not a display element. Tapping a milepost in the map hands off to Google Maps, Apple Maps, or Waze with the milepost coordinate as the routing target. Direct workflow value for dispatch-to-driver handoffs in fleet, roadside, and emergency-response use cases.
CarPlay & Android Auto
Live on CarPlay and Android Auto. Apple’s Driving Task entitlement requires a separate navigational utility review — it’s not a standard developer-portal option, and most transportation apps don’t qualify. MileCheck passed that review. The same data layer that powers the phone experience ships to the vehicle screen.
Real-time infrastructure status
Beyond DOT alerts: live commercial border-crossing wait times for all 82 US land crossings (commercial and FAST lanes, direct from CBP), plus live movable-bridge open/closed status — hyper-local, time-critical signals no consumer map surfaces. Live drawbridge status runs in Seattle and Florida (state DOT sensors) with Louisiana road/marine status behind it — and the federal opening rules for 800+ regulated US drawbridges are already normalized in the corpus, published as state-by-state web maps.
Who we talk to
Seven segments where mile-marker precision is the missing layer.
Fleet management
That’s how drivers report location. Telematics logs GPS coordinates — so dispatch can’t plot the one format drivers actually use without a manual lookup. We’re the translation layer.
Mapping & navigation
Adding a milepost layer yourself means fifty state negotiations and a pipeline to keep it current. Most platforms skip it. The corpus is licensable today.
511 / traveler information
Cross-state alerts live in 50 incompatible DOT systems; aggregating them yourself means bilateral agreements with every agency on the route. We already normalized all 50.
Digital freight & logistics
No native equivalent in consumer nav — drivers send approximate pins, dispatchers guess. Plus live commercial waits at all 82 land borders, an input no fleet platform surfaces today.
Roadside & incident response
Stranded drivers report a mile marker; most dispatch systems demand a street address. The workaround is literally asking a stressed driver to go find a sign. We turn the marker into a routable point.
Towing & dispatch platforms
Your board already receives that call. Plot it automatically — and flag whether that stretch is closed or under chain control right now. One API call, zero state-DOT contracts on your side.
State DOTs & agencies
Watching conditions across a border means separate logins, schemas, and feeds per neighbor — the perennial unsolved consortium problem. One feed, every neighboring agency, one schema.
Run on road + mile? It plugs in.
If your operation speaks “route and milepost,” the layer drops into your stack — live conditions included, production-proven in a five-star app.
Open a conversation →Build vs. license
Building the data is harder than building the app.
MileCheck runs alongside your routing or weather stack: direct-from-state-DOT road events — closures, construction, crashes, chain controls — tied to the exact mile marker. It’s privacy-light by design — no driver accounts, and the vehicle’s location stays in your platform, not on our servers. A coordinate-to-milepost lookup is available elsewhere — the live conditions at that milepost, normalized across 50 agencies and proven in a five-star app, are the part that’s hard to copy.
Proven in production through the MileCheck iOS, Android, CarPlay, and Android Auto applications.
Validated continuously by a nationwide tester network — real drivers across the country who flag issues in the field, so a data problem surfaces before someone hits it in an emergency. Automated per-source monitoring catches the feeds; the testers catch the road.
↗ Live API status · DOT feed uptime monitored 24/7
Why it’s hard to build in-house
- Every agency is different — 50 integrations, each with its own auth method, rate limits, schema, and reliability characteristics. One upstream change breaks your feed until someone catches it.
- No common standard — ibi511, COtrip, ArcGIS FeatureServer, GeoJSON / WZDx, CARS FEU-g, EVBG XML, and more. No two states publish the same data the same way.
- State-by-state access — some feeds require registration, API keys, terms agreements, and back-and-forth with agency IT. Multiply that by 50.
- Continuous normalization — route names, mile marker formats, and direction codes vary by state and change without notice. Keeping them aligned is an ongoing maintenance burden, not a one-time project.
- Feed monitoring — DOT feeds go stale, change endpoints, and return unexpected errors. Without active per-source monitoring, your app silently serves outdated data.
MileCheck solved this once, in production, for a consumer app with five-star ratings on both stores. The platform is available to license today — no agency negotiations required on your side.
Ways to work together
Pick the model that fits — we're flexible.
API access
The unified DOT alerts feed — direct from 50 state agencies: closures, construction, crashes, and chain controls — plus live commercial border-crossing waits from all 82 US land crossings (CBP), served through one normalized endpoint.
Data licensing
The 50-state milepost corpus as a static dataset or continuous sync, shaped to your schema.
White-label SDK
Mile-marker display and DOT alert integration embedded directly into your existing driver app.
Joint development
Co-engineering a vertical use case on top of the highway intelligence layer.
Corridor boards
Live road conditions on a screen in your venue.
A MileCheck corridor board turns any TV in a truck stop, travel center, diner, or gas station into a live dashboard for the highway outside your door — closures, crashes, chain controls, and weather for your stretch of interstate, updating around the clock from the same direct-from-DOT layer that powers the app.
For venues
The board is free. We configure it for your corridor and your location — drivers walk in, see exactly what's ahead on their route, and your venue becomes the place that knows the road.
For sponsors
One sponsor slot per screen — your brand alongside the one piece of information every driver in the building actually came in wondering about.
How it runs
Any screen with a browser — no hardware to buy, nothing to install or maintain. The board is a live web page that keeps itself current.
To put a board in your venue — or your brand on one — email info@milecheckapp.com.
Open a conversation
Get in touch.
For partnership and platform inquiries, contact info@milecheckapp.com.
Already run a fleet platform? MileCheck drops in as an Add-In.
It installs inside MyGeotab and Geotab Drive as an Add-In — the driver’s live mile marker and direct-from-DOT alerts, right in the dashboard. Same normalized data layer, no rebuild on your side.