Safety Data

About Safety Data at DDOT

DDOT's primary repository of GIS safety data is based upon the MIRE safety data (more info below). While the MIRE data provide a substantial portion of the repository, there are a number of other related data which could potentially be utilized for safety analysis. Check this page in the future for additional updates on MIRE and other safety data which may be used for your projects and analyses.

Traffic Records Assessment

The most recent Traffic Records Assessment (2017) provides a comprehensive evaluation of DC's traffic safety program. A significant part of this assessment covers how 'healthy' the roadway data program is for supporting traffic safety analysis. This wiki was created as a result of some of the recommendations presented within this assessment. The DDOT GIS team hopes that this will better enable us to provide more comprehensive documentation of our activities, data maintenance and analysis responsibilities - especially as they relate to supporting the safety program here at DDOT.

Take a look at the TRA and see how we scored (the 'Roadway' section focuses on roadway data systems).

Model Inventory of Roadway Elements (MIRE)

If you'd like to check out general info about MIRE, FHWA has a few helpful online resources:

MIRE 2.0 Report: Revision to the original report. NEW!
MIRE 1.0 Report: The original report that contains background information as well as a comprehensive overview of all required elements.
Data Collection Guidebook: Guide highlighting practical approaches to MIRE data collection, highlighting techniques and technologies as well as providing additional guidance.
MIRE FDE Cost Benefit Estimation: Required reading. This document goes into good detail and highlights what some states have already done.

MIRE FDE Data Collection

The MIRE Fundamental Data Elements (FDE) is a subset of 33 safety data items required by FHWA. Below, the main table of required FDE are listed, with some additional items required by DDOT:

Note

The actual list of FDEs is 37 - but if you remove duplicates of AADT, AADT Year, Governmental Ownership and Functional Class, the actual number is 33. Each of these four items appear twice.

In the summer of 2018, DDOT contractors completed a project which involved collecting roadway section data in support of FHWA's MIRE safety data specification. The data will be collected using DDOT's linear referencing system (LRS): Roads and Highways Roadway Characteristics Editor. For a detailed review of the project, check out the blog article describing the data and proposed extraction process

Roadway Sections (Lanes) Centerline Project: visit our summary page.
Automated Extraction - from LRS to MIRE data elements using Python. COMING SOON

Click Here to View Current Status of the MIRE FDE Data Collection

Green = Items either in HPMS or already extractable via DDOT scripting

Orange = DDOT will capture Summer 2017

Red = Contractor will capture Summer 2017

Roadway Segment	Intersection
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Interchange/Ramp
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Additional Elements Captured by DDOT
Sidewalk Type + L/R (DDOT Type)
Sidewalk Width (the generalized width in feet of the sidewalk)
Lane Type (DDOT Type) (through lane, bike lane, right turn only, etc)
Dividers (includes medians (54), centerline striping type, etc)
Street Buffers (protections that do not divide opposing traffic, e.g. continuous painted, curbed protections)
Lane Directionality (DDOT Type) (direction of traffic as the centerline geometry ascends)
Lane Width (DDOT Type) (width in feet of a given travel lane)