What Is MIRE? | Roadway Safety Data Explained

Starting With The Basic Idea Of MIRE

If you have ever heard classmates ask “what is mire?” during a transportation lesson, they usually mean the Model Inventory of Roadway Elements created by the Federal Highway Administration in the United States. MIRE is a recommended catalog of roadway and traffic characteristics that agencies can collect so they can study crash patterns in a careful, data driven way.

In simple terms, MIRE does not tell engineers how to design a road. Instead, it spells out which details to record about each road, intersection, and interchange so that safety statisticians can compare locations on fair terms. The list covers items such as how many lanes a segment has, what type of median separates traffic, whether there are turn lanes, and how signals operate.

The goal is simple: when everyone keeps similar records, it becomes much easier to link crash files, roadway inventories, and traffic volume data. That shared structure saves time, reduces confusion, and gives analysts more confidence that they are drawing the right lessons from the numbers.

Core Categories In The Model Inventory Of Roadway Elements

MIRE organizes its elements into logical groups, which makes the list easier to understand and manage. The table below gives a broad look at several major categories and the type of details that fall under each one.

Element Category	Typical Data Items	Reason The Data Helps Safety Work
Roadway Segment	Segment ID, length, number of lanes, shoulder presence, median type	Links crash counts to the physical layout of the road so analysts can compare similar segments.
Alignment And Grade	Horizontal curves, vertical grade, superelevation	Shows where sharp curves or steep slopes might add risk for drivers, riders, and pedestrians.
Roadside Features	Clear zone width, barriers, fixed objects	Helps engineers judge how likely a run off road crash will lead to severe outcomes.
Intersection Geometry	Number of legs, control type, presence of turn lanes, skew angle	Helps with fair comparison of different intersection layouts and control strategies.
Traffic Control Devices	Signal presence, phasing type, stop signs, speed limits	Shows how drivers receive instructions, which matters when agencies change signs or signal timing.
Traffic Volume	Average annual daily traffic, truck percentage, peak hour volume	Lets analysts convert raw crash counts into rates that reflect how much traffic a location carries.
Nonmotorized Facilities	Sidewalks, bike lanes, crossings, trail connections	Gives insight into exposure and risk for people walking or cycling along or across the road.
Interchange Elements	Ramp types, merge and diverge lengths, ramp control	Captures how high speed traffic enters and leaves freeways, where conflict points can cluster.

When students study the high level structure of MIRE, this spread of categories helps them see that the model is not just a long list of codes. Instead, it represents a complete picture of how road segments, junctions, and traffic conditions fit together in a safety database.

Meaning Of MIRE In Roadway Safety Data

The phrase “Model Inventory of Roadway Elements” captures three ideas at once. “Model” shows that MIRE is a template that states can copy or adapt. “Inventory” reminds readers that the focus lies on what exists along the road network. “Elements” points to the individual data fields, such as lane width or shoulder type, that together build a full record.

MIRE grew out of efforts to improve safety data quality across states. Earlier crash databases often used local codes and text descriptions that were hard to compare from one region to another. With MIRE, agencies have a shared reference that describes each data field, lists allowed values, and explains how to code special cases. That shared language makes it easier to combine datasets, run studies across state lines, and apply national tools such as the Highway Safety Manual.

The Federal Highway Administration keeps the official description of MIRE and updates it over time so that new design practices and safety methods can appear in the data model. Students who want to read the formal definition can visit the agency’s Model Inventory of Roadway Elements page, which also links to the current version of the guideline.

What Is MIRE? Deeper Look For Students

When a textbook or instructor asks “what is mire?” in a roadway data context, the answer stretches beyond a simple one line definition. For a learning audience, MIRE is a way to connect theory about crash risk with real world data that comes from road networks. Each coded field in the model corresponds to something that students can picture on a map or at a site visit.

For instance, a record might say that a segment has two lanes in each direction, a raised median, a posted speed of 80 kilometers per hour, and an adjacent sidewalk on one side. At an intersection, a record might flag protected left turn phases, pedestrian signals, or roundabout control. By working with coded data and then looking at photographs or field notes, learners see how abstract entries in a table reflect pavement markings, signs, and physical layout.

MIRE also shows the link between careful data collection and fair evaluation of safety projects. If two regions code the same type of curve or intersection in different ways, then any comparison between those regions may mislead decision makers. The model gives agencies a shared baseline, which improves trust in the results of crash modification studies and network screening work.

Why MIRE Matters For Safety Analysis

Crash counts by themselves do not tell the full story of risk on a network. A short downtown street with thousands of vehicles and pedestrians each day might show more reported crashes than a quiet rural lane, yet still offer lower risk per person using it. To judge such tradeoffs, analysts need both crash records and solid roadway inventory data. MIRE describes which inventory details to store so that these comparisons stay fair.

MIRE also encourages consistent terminology between roadway records, traffic volume files, and crash databases. When a segment ID or intersection ID appears in all three datasets, agencies can link them without complicated matching steps. That linkage lets safety teams study patterns such as crash rate by curve radius, or injury severity by presence of turn lanes, with far less manual cleaning.

Better data also shapes long range planning. State and regional agencies use MIRE inspired inventories to spot corridors with recurring patterns, such as frequent run off road crashes or rear end crashes at similar types of signals. With that insight, they can prepare project lists for Highway Safety Improvement Program funding and explain, in clear terms, why a certain corridor deserves attention ahead of others.

How Agencies Put MIRE Into Practice

States do not need to adopt every single field in MIRE. The guideline outlines more than two hundred possible elements, and each agency chooses which ones to include based on local goals, budget, and data systems. Many agencies start with the subset known as the Fundamental Data Elements, a smaller group that federal rules call out as especially helpful for safety analysis.

Collecting these fields often starts with existing roadway inventory files, traffic volume maps, aerial imagery, and field visits. Staff may load records into a geographic information system so that each segment, intersection, and ramp includes the required details. Over time, maintenance staff, project designers, and traffic engineers add updates when they change striping, install signals, or rebuild a corridor.

Agencies then connect these inventories with crash records. When staff can quickly map crashes onto segments and intersections that already carry MIRE style attributes, they can spot trends such as higher crash rates on undivided segments with high speeds or at intersections with complex signal timing. Those patterns then guide low cost treatments, systemic safety projects, and larger reconstruction plans.

MIRE Versions And Fundamental Data Elements

MIRE has evolved over time. The first formal report, version 1.0, laid out a detailed list of roadway and traffic elements for agencies that wanted to move toward more consistent data. MIRE 2.0 refined that list, lined it up with other federal data sets, and responded to feedback from early adopters. The latest update, called MIRE 2.1, continues that process and reflects two decades of safety data practice and policy.

The Federal Highway Administration describes MIRE as a recommended listing of roadway characteristics and traffic inventory elements that help form a complete safety data system. The agency also defines the Fundamental Data Elements subset, which states are expected to collect for all public roads as part of Highway Safety Improvement Program requirements. The MIRE 2.1 technical report explains this in more detail and is available through the National Transportation Library record for MIRE 2.1.

The table below gives a simple summary of how the Fundamental Data Elements vary by road type, based on guidance that many transportation departments share when they explain their MIRE plans to staff.

Road Type	Number Of Fundamental Data Elements	Short Description
Non Local Paved Roads	About 37 elements	These roads carry heavy traffic, so agencies collect many details on geometry, control, and volumes.
Local Paved Roads	About 9 elements	These streets serve neighborhoods, so a smaller set of MIRE fields can still give a useful safety picture.
Unpaved Roads	About 5 elements	On these facilities, a basic inventory of alignment, width, and traffic volume can still reveal patterns.

In class, this summary shows students why MIRE scales by road function. A freeway or major arterial has many more features to describe than a low speed local street.

Linking MIRE To Broader Safety Programs

MIRE does not stand alone. Agencies use the model as one piece of a wider data picture that also includes crash records, traffic counts, and information on land use around the road. These inputs feed tools such as the Highway Safety Manual and AASHTOWare Safety, which estimate expected crashes under different design choices and help staff compare treatment options.

Federal transportation laws, such as the Moving Ahead for Progress in the 21st Century Act and the Fixing America’s Surface Transportation Act, pushed states to improve safety data on all public roads. MIRE and the Fundamental Data Elements respond to that push by giving a clear description of what to collect. When states follow these recommendations, it becomes easier to track progress toward strategic safety goals, share findings with partners, and report results to federal agencies.

For students, this link between a data model and high level policy is a helpful lesson. It shows how a carefully defined set of fields on a spreadsheet can influence real decisions about guardrails, rumble strips, signal retiming, and other treatments that people notice on the street.

Main Points About MIRE For Learners

MIRE often appears in road safety courses as a short acronym, but behind that short label sits a detailed description of how roadway and traffic details can be stored in a common format. By walking through MIRE categories, example fields, and the idea of Fundamental Data Elements, students gain a clearer sense of how data turns into insight.

For exam review, many students recall that MIRE is not a law or a mandatory checklist for design. Instead, it is a shared reference for data fields that describe road segments, intersections, interchanges, and nearby facilities for walking and cycling. When agencies base their inventories on this reference, they can compare sites in a fair way, run network screening across large regions, and explain why certain corridors stand out as priorities.

Most of all, MIRE reminds learners that safety analysis begins with clear, consistent facts about the roads people use each day. With that base in place, crash numbers and traffic counts start to tell clearer stories, and engineers can respond with projects that match the risks they see in the data. That habit of careful data work carries over into many fields later.