For platforms and partners

Milepost data and road conditions for your platform.

Add milepost lookup and state DOT feeds to your dispatch software or driver app — normalized from 50 state DOT feeds across 19 upstream formats into one schema, one API.

Explore the data Discuss an integration →

Live on the Geotab Marketplace — the fleet add-in runs in MyGeotab today · data API by license.

50 states + 3 Canadian provinces · 50 live DOT integrations  ·  CarPlay & Android Auto  ·  AWS Partner Network member

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 — referenced by highway and milepost. No driver accounts; the vehicle’s location stays in your platform, not ours.

50
state milepost corpus — official GIS, never crowdsourced
50
live agency integrations — production-proven
19
DOT platform formats — one schema
24/7
monitored feeds — per state

Proven in production on iOS, Android, CarPlay, and Android Auto — and live today inside MyGeotab as a fleet Add-In.

See the Geotab Add-In ↓  ·  Live API status ↗

Why it’s hard to build in-house
  • Every agency is different — 50 integrations, each its own auth, rate limits, and schema.
  • No common standard — no two states publish road data the same way.
  • State-by-state access — registration, API keys, and agency IT, times 50.
  • Continuous normalization — route names and mile formats change without notice.
  • Feed monitoring — without it, your app silently serves stale data.

Three products, each usable on its own.

Milepost dataset

Every interstate, US highway, and most state routes in all 50 states. Sourced from official DOT and GIS records, never crowdsourced, interpolated to one-tenth of a mile between markers.

  • Coverage — 50 states, updated when routes are added or reclassified.
  • Fields — route ID, mile, latitude, longitude.
  • Delivery — structured dataset export, or continuous sync.
  • Also includes — a navigate-to-milepost primitive (a marker as a routing target, handed off to Google Maps, Apple Maps, or Waze) and the same data on CarPlay and Android Auto.
  • Limitation — positions are interpolated between physical signs, not individually GPS-surveyed.

Live conditions API

50 state DOTs and 3 Canadian provinces, each on a different upstream platform, normalized into one schema. Closures, construction, crashes, chain controls, and weather — referenced by highway and milepost.

  • Coverage — 50 states + 3 provinces, 19 upstream formats, one schema.
  • Also normalized — live CBP commercial border-crossing waits, and movable-bridge open/closed status (Seattle, Florida).
  • Refresh — matches each source's own posting cadence; every feed is monitored, not polled blind.
  • Unavailable-source behavior — ten states' live feeds don't carry crash data at all (Alaska, Arkansas, Hawaii, Kentucky, Maine, North Dakota, New Mexico, Oklahoma, South Dakota, West Virginia); the API says so rather than returning a silent zero.

Real response, pulled live

{
  "event-type-id": "CL",
  "headline": "Bridge demolition work on 101-LOOP Southbound from W Indian School Rd (MP 4) to I-10 Eastbound (MP 2). All lanes closed.",
  "location": {
    "route-id": "SR-101",
    "direction": "South",
    "start-location": { "start-mile-marker": "4", "start-lat": 33.4939, "start-long": -112.2641 },
    "end-location":   { "end-mile-marker": "2",   "end-lat": 33.4655,   "end-long": -112.2688 }
  },
  "is-full-closure": true,
  "severity": "Minor",
  "start-time": 1790395200,
  "end-time": 1790596800
}

Arizona DOT, live on /v1, pulled September 25, 2026.

Historical archive

Every state DOT and Canadian provincial feed (DriveBC, Alberta, Manitoba), saved on a schedule — a growing record of road-feed snapshots.

  • Collection interval — every two hours since September 2026, daily before that, back to mid-August.
  • Gaps — a jurisdiction's history starts the day its live integration went in, not before.
  • What it's produced — real crash-clearance times, bridge-raise duration histograms, and border-wait curves by hour and day, measured rather than estimated.
  • Delivery — a dated export, or a continuous sync, separate from the live API.

MileCheck solved this once, in production, for a consumer app live on both stores. Available to license today.

Which one fits?

APIData licenseWhite-label SDKWebsite sponsorship
What you getLive mile-marker lookups, road alerts and border waitsThe whole milepost dataset, with updatesMile markers and alerts inside your appYour logo atop the pages you pick
Your app doesRequests live data when neededStores the dataset and draws its own map layerDisplays our componentNo integration needed
Best forLive lookups and dispatch toolsMap layers, offline use and analyticsApps without a map teamLocal businesses that serve drivers
How you payDev $0. Business $499/month for 100,000 calls/day. Enterprise quoted. API pageYearly quote based on use and update frequencyQuoted$50/page/month for three months, then month to month. Sponsor page
ExampleA dispatch screen showing “I-80 mile 184”A wildfire app’s mile-marker map layerA trucking app’s driver screenA ski shop on the Stevens Pass page

Only requests that reach our server count toward your plan. For the whole dataset in your own map, choose a data license.

Building something bigger? We also take on joint development, quoted case by case. Get in touch

Seven segments that already work in mile markers.

Fleet management — “I’m at MP 184 on I-80.” That’s how drivers report location; telematics only logs coordinates. We’re the translation layer. See the fleets page →
Mapping & navigation — 19 source formats, one schema, one license. The corpus is licensable today.
511 / traveler information — one corridor, five agency logins. We already normalized all 50.
Digital freight & logistics — “Meet the driver at I-80 MP 184.”
Roadside & incident response — “Can you find a sign and read it back?” We turn the marker into a routable point.
Towing & dispatch platforms — “Disabled vehicle, I-5 NB MP 164.” One API call, zero state-DOT contracts on your side.
State DOTs & agencies — the corridor doesn’t stop at the state line. One feed, every neighboring agency.

Request a sample →

Not a data buyer? Two more doors.

Corridor boards

A free live-conditions screen for your truck stop, travel center, or diner — one sponsor slot included.

See how it works →

Website sponsorships

One sponsor slot on camera, corridor, pass, and drawbridge pages that already rank. Website only; the app has no ads.

API Pricing and traffic →

See it before you commit to it.

Tell us your intended use and geography — a state, a corridor, or nationwide — and which product: milepost dataset, live conditions API, or historical archive. We'll send a real sample back.

See the API, endpoints and pricing → Request a sample →

Developer keys are free. Business is $499 a month for 100,000 calls a day. Fleet and enterprise licences are quoted.

Now on the Geotab Marketplace

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 live state DOT feeds, right in the dashboard. Same normalized data layer, no rebuild on your side.

The Monthly Highway Report

Which highways had the most closures and crashes this month

The month's numbers from DOT feeds in all 50 states and BC. See the September report. No spam.