State Planner
Sign inSign Up

TOAST Corridor Scores

The Ohio Department of Transportation's yearly scan of how well traffic flows on every corridor of the State Priority System, each direction scored on its own: recurring bottlenecks, how often traffic moves near free-flow speed, how reliable travel times are at each time of day, rear-end and severe crashes, how long incidents take to clear, traffic per lane and truck share, rolled into one score and statewide and district ranks. ODOT uses it to find the corridors most likely to benefit from Transportation Systems Management and Operations (TSMO) work such as signal retiming, ramp metering, incident management or traveler information, and the low scorers are where its districts study and fund that work.

Published by
Ohio Department of Transportation, Office of Traffic Management
Source
ODOT Traffic Operations Assessment Systems Tool (TOAST)
Original data
odotgis.dot.state.oh.us
On the map
Lines

From the publisher

"TOAST is a scanning tool which scores and ranks corridors based on multiple data sets and metrics in order to help transportation professionals make data-driven decisions and determine operationally sensitive corridors throughout the state. Routes are segmented into the State Priority System with breaks at the urban area boundaries, interchange center points, and road functional class changes. Where possible, data is provided directionally." "In general, the higher the percent, the better the route is performing, whereas the lower the percent, the more likely a route is to benefit from application of TSMO strategies." (Ohio Department of Transportation)

Ask your own question about Ohio

Send takes you to sign up (every feature free for 7 days, no card needed), or to sign in if you have an account. Your question will be waiting in your new chat.

Fields

What each record holds, as the publisher describes it: 57 fields.

FieldDescription
year
TOAST year (2025, which scores 2024 data)
corridor_id
ODOT's corridor id: NLFID, begin and end log point, and direction (SHAMIR00071**C_06.977_08.058_F)
nlfid
ODOT's route id: jurisdiction, county, route type, route number and extension (SHAMIR00071**C)
direction
Cardinal (northbound or eastbound) or Non-cardinal (southbound or westbound)
direction_code
F cardinal, R non-cardinal
district
ODOT district, 1–12
county
County name
county_code
ODOT's three-letter county code (HAM)
county_geoid
County FIPS code (39061)
route_type
Interstate, US route or State route
route_type_code
IR, US or SR
route
Route number
begin_log
Log point where the corridor begins, in miles along the route in the county
end_log
Log point where it ends
length_mi
Corridor length, miles
functional_class
FHWA functional class: Interstate, Other freeway or expressway, Principal arterial, Minor arterial, Major collector, Minor collector, Local
functional_class_code
1–7, in that order
urban_rural
Urban or Rural
urban_rural_code
U or R
roadway_category
Urban freeway, Urban non-freeway, Rural freeway or Rural non-freeway
roadway_category_code
UrbFwy, UrbNonFwy, RurFwy or RurNonFwy
score
Overall TOAST score, 0–1; lower is worse
rank_statewide
Rank among all corridors, 1 the worst
rank_statewide_category
Rank among the state's corridors of its roadway category
rank_district
Rank among its district's corridors
rank_district_category
Rank among its district's corridors of its roadway category
current_projects
Construction projects active on the corridor
current_projects_max_days
Active days of the longest current project
future_projects
Planned projects
future_projects_large
Planned large or TSMO projects
bottleneck_passthrough_impact
Summed impact of the bottlenecks reaching the corridor; null for none
bottleneck_passthrough_score
0–10, 10 the best
bottleneck_origin_impact
Summed impact of the bottlenecks starting in the corridor; null for none
bottleneck_origin_score
0–10, 10 the best
ttp_share
Travel time performance: share of the time at 90% or more of reference speed, 0–1
ttp_score
0–10, 10 the best
ttr_weekday_am
Travel time reliability, weekday morning: 80th-percentile ÷ median travel time
ttr_weekday_midday
Travel time reliability, weekday midday
ttr_weekday_pm
Travel time reliability, weekday afternoon
ttr_weekend
Travel time reliability, weekends
ttr_score
0–10 for the worst period, 10 the best
crashes_3yr
Crashes in three years
rear_end_share
Rear-end share of those crashes, 0–1
rear_end_score
0–10, 10 the best
ksi_crashes_3yr
Fatal and serious-injury crashes in three years
ksi_share
Fatal and serious-injury share of the crashes, 0–1
vc_ratio
Volume to capacity ratio
safety_eligible
ODOT's safety-eligible flag
crash_severity_impact
Crashes × V/C ratio × fatal and serious-injury share ÷ length
crash_severity_score
0–10, 10 the best
incident_clearance_minutes
Summed crash clearance time, minutes, weighted by clustering
incident_clearance_score
0–10, 10 the best
vehicles_per_lane
Daily vehicles per lane
vehicles_per_lane_score
0–10, 10 the best
trucks
Daily truck volume
truck_share
Trucks ÷ total daily volume, 0–1
truck_score
0–10, 10 the best

More Ohio data

Every Ohio data set

HomePricingAboutTerms of ServicePrivacy Policy