Data for Infrastructure & Movement

Infrastructure you
can plan around

Upload a corridor and get a PDF risk report back in minutes — bridge condition, pavement condition, and funded capital work, all within your buffer. Then get the data behind it, pre-scoped to your exact route.

Try Route Risk Manager Get the data
Instant, automated generationNationwide coverageNo account, no sales call

Before & after

Nobody should have to read this

A real row from Pennsylvania's bridge file, exactly as FHWA published it. Below: the raw record, and what we turn it into.

RAW · PA DOT, 2025
4230000000000000221310000000800174680US 15; SR 0015 T-530; WOODSIDE RDNE OF GETTYSBURG 999900000200 0039544105077095593014301010919670208000510202450055024000115N000000000A11502000004000008500213000655005005008501029999H0442H999999756NN1925…
DECODED
Location
39.9114, −77.1655
Validated
Vertical clearance
14.50 ft 4.42 m
Highway beneath structure
Operating rating
102.0 ton 92.5 t
Inspected 06/23

Real record · PA structure 000000000000022 · 2025 vintage

Get started

Start wherever makes sense

Get a report, get the data, or both — there's no required order, and no account needed for either.

Route Risk Manager

Get a corridor report

Upload a route (GPX, KML, or zipped Shapefile) and get a PDF risk report back in minutes — bridge condition, pavement condition, and funded capital work within your buffer.

Try Route Risk Manager →
The Data Stack

Get the data

Pick a state, county, or route, then any combination of layers — bridges, pavement, capital programs. If you've already run a report, it's pre-scoped to that same corridor.

Go to the Data Stack →

Who it's for

From route surveys to data pipelines

One needs an answer on a corridor today. The other needs a foundation to build on.

Superload & OS/OW route teams

Screen a corridor in minutes, not weeks

  • Manual route surveys take weeks per corridor — upload yours, get a risk report back today
  • Clearances and weight ratings in feet and tons, not raw federal codes
  • Permit-ready PDF — hand it straight to your application
  • Re-run instantly whenever a route changes

Engineering, GIS & planning teams

Get the data, build your own tooling

  • Bridges, pavement, and capital programs in one order, one checkout — not three separate purchases
  • Feet and metric, side by side, versioned and reproducible
  • Priced by scope — a county, a route, or the whole stack
  • API-first — pull it straight into your own systems

The Data Stack

One connected stack, pick your layers

One schema, one checkout. Pick a state, a county, or a route, then any combination of layers below.

Bridge Inventory (2025)

624,193 structures nationwide. Clearance, load rating, posting, condition, geometry, and 190+ decoded fields.

Available

Historical Panel (2015–2025)

One row per structure per year across 11 years — condition trend, age, and reconstruction history.

Available

Element Condition (2025)

Component-level detail for 233,970 structures that moves before the headline rating does.

Available

Capital Pipeline — Declared Work

183,675 structures nationwide with owner-stated planned work, cost estimate, and year — fact, not a heuristic.

Available

Road & Pavement Condition

Every public road segment, decoded functional class/ownership/surface type, and an FHWA (23 CFR 490.313) Good/Fair/Poor rating per segment — not raw HPMS codes.

Available

State Capital Program (STIP/TIP)

What each state has actually funded and scheduled — project, cost, status, and letting date where reported. No free federal equivalent exists for this data at all.

Available

We're adding more layers over time — rail crossings and tunnels are next — all on this same schema, so a new layer never means learning a new file format. See current pricing →

Provenance

Know where every number came from

Every layer traces back to a named government source — so you can check it, not just take our word for it.

  • Every product names its source agency and publication — FHWA's NBI, FHWA's HPMS, or a specific state DOT's own STIP/TIP
  • Confidence scored wherever a value is joined or estimated, not asserted as fact
  • Decoded and derived values are named and kept separate from what the agency actually reported
FieldUnit & scaleNoteConfidence
vertical_underclearance m × 0.01 the primary clearance field · bridges Verified
pavement_condition_rating Good / Fair / Poor 23 CFR 490.313 threshold logic · pavement Verified
terrain_type raw HPMS code codes not yet confirmed against the current field manual · pavement Under review

Integration

A live API behind every layer

# every county in Pennsylvania, with names curl "https://www.panomapic.com/api/v1/states/42/counties" # the full product catalog and current pricing curl "https://www.panomapic.com/api/v1/products"

Start with a corridor you know well

Upload a route and see your own report in minutes — no form required. Want a sample first, or a bulk quote for a large order? Send us your county or corridor below. Ready to buy data directly instead? Go to the Data Stack.

Or reach Greg directly — greg.alliger@panomapic.com · 832.561.6105