Genesee County (Flint, Michigan) Uses usRAP to Develop Safety Improvement Plan for County Roads

Original publication: 2013 National Roadway Safety Awards Noteworthy Practices Guide Publication FHWA-SA-14-002; 2013

Description of Practice

In 2012, the Genesee County Road Commission (GCRC) in Flint, Michigan, signed an agreement for a U.S. Road Assessment Program (usRAP) Safety Improvement evaluation of the county road system. Initiated in 2004 as a pilot by the AAA Foundation, the usRAP program was designed to assess and benchmark the relative safety of roads using historical crash data and roadway inventory data. The program includes a Road Protection Score (RPS), which can identify road segments with higher crash potential through analyses of road inventory data relative to design features that are strongly correlated with the risk of serious crashes.

GCRC developed the safety improvement plan based on a comprehensive review of the existing physical infrastructure of the county road system. Project staff obtained and assembled data on over 40 existing safety-related infrastructure elements for more than 8,600 300-ft roadway segments. The project database was uploaded to the usRAP Tools software and processed to develop a safety improvement plan.

Key Accomplishments and Results

Assessing and benchmarking the relative safety of roads using historical crash data and roadway inventory data. The development of the plan was completed in early 2013 and is now proceeding to the programming and implementation stage.

Contact

John H. Daly III, Ph.D.
Genesee County Road Commission
810-767-4920
jdaly@gcrc.org

Wisconsin's Information System for Local Roads Expands Local Access to Data while Integrating State and Local Safety Data Systems

Summary from: Wisconsin Information System Local Roads State and Local Data Integration Case Study FHWA-SA-14-037

Background

This case study, available as part of the Federal Highway Administration's (FHWA) Integration of State and Local Safety Data project, describes Wisconsin's efforts to integrate local roadway data into their State data system.

This case study is part of a series of four. Each case study identifies a State's experience collecting local data, the challenges and obstacles faced and how they were overcome, benefits of the practices, reasons for success, lessons learned, and applicability of the practices to other agencies.

The Wisconsin Information System for Local Roads (WISLR) is an example of successful development of a safety and asset management system designed specifically to meet local stakeholder's needs. For Wisconsin, that included developing the new system in a spatial framework that differed from what was already in place for State-maintained roads, and then integrating the State roadway data with the new local roads system to create an all-public-roads database.

Before migrating to the WISLR system, Wisconsin managed the centerline mileage certification process for over 90,000 miles of local roads with more than 1,900 separate paper maps. The Wisconsin Department of Transportation (WisDOT) entered roadway attribute information into a mainframe database accessible only to select State staff, and local agencies received paper copies of local road mileage certification data. There was enormous duplication of effort—local agencies often had their own systems for managing data on roadway miles, assets, and attributes that were not compatible with the existing WisDOT system.

WisDOT launched WISLR in the mid-1990s. It integrates spatial location, asset, inventory, and crash information for local roads using an “on/at/towards” LRS (Linear Referencing System). Users identify the road name (“on”), plus the distance and direction to the nearest intersecting street (“at” or “towards”). This location coding method gains precision by incorporating measured distances along each roadway. WISLR records Intersections at measured distances along that roadway and termini (the ends of the roadways) as the starting (zero) or final distance measurement within a jurisdiction. When a location is specified, WISLR represents that location as the unique combination of the street name and the distance and direction from the nearest intersecting road or terminus. This allows the data for each event or feature to be associated spatially with all other data from the same location. WISLR also includes a translation of State-maintained roadway location, crash, and inventory data into the “on-at-towards” LRS so that WISLR serves as an all-public-roads safety data resource. In Wisconsin, local agencies collect and own the data for roadways under their jurisdiction; the centralized system is available to all authorized users.

Key Accomplishments:

The following are key accomplishments of the Wisconsin Information System for Local Roads:

• Consistent statewide local roadway data.
• Cost savings through reduced redundancy.
• Expanded use by local agencies as new modules and capabilities are added.
• Efficient tool for safety analysis.
• All-public-roads LRS and basemap.

Results:

The original purpose of WISLR was to serve as an aid to mandatory recertification of centerline mileage by the local agencies. While State law requires the recertification of centerline mileage, agencies can use any method or software to accomplish the recertification. Even so, compliance is above 90 percent and the vast majority of local agencies use WISLR for data mining and decision-making. The online WISLR user numbers continue to increase each year.

The State is considering upgrades to make the WISLR network representation as high resolution as the state trunk network (STN). This could include turn lanes, medians, dual carriageways and other features not currently captured at the same resolution in the WISLR for the STN making the system even more useful.

Contacts

Susie Forde
Data Management Section Chief
Wisconsin Department of Transportation
608-266-7140
Susie.Forde@dot.wi.gov

Kelly Schieldt
Statewide Local Road Coordinator
Wisconsin Department of Transportation
608-267-9748
Kelly.Schieldt@dot.wi.gov

Stuart Thompson
Federal Highway Administration
202-366-8090
Stuart.Thompson@dot.gov

Tennessee Updates Roadway Information Management System (TRIMS) State Roads Database to Include Local Road Data

Summary from: Tennessee Roadway Information System State and Local Data Integration Case Study FHWA-SA-14-038

Background

This case study, available as part of the Federal Highway Administration's (FHWA) Integration of State and Local Safety Data project, describes Tennessee's efforts to integrate local roadway data into their State data system.

This case study is part of a series of four. Each case study will identify a State's experience collecting local data, the challenges and obstacles faced and how they were overcome, benefits of the practices, reasons for success, lessons learned, and applicability of the practices to other agencies.

Historically, the majority of Tennessee's fatal and incapacitating crashes occurred on local/rural roads; however, local agencies within Tennessee collected very little roadway inventory data and the data collected was largely unavailable to the State. In 2007, the Tennessee Department of Transportation (TDOT) hired a contractor to collect location description and inventory data on all local roads and integrate the information into the Tennessee Roadway Information Management System (TRIMS) database that had been in place for State roads since the 1970s. TDOT's contractor collected data over a five-year period and met TDOT's rigorous data quality standards.

TRIMS is a single integrated linear referencing system database for State and local roadway structures, pavement, traffic, photo log, and crash data. In 2007, TDOT began developing eTRIMS, a map-centric, web-based version of TRIMS with the purpose of encouraging wider use of the TRIMS database. Additionally, the online application supports easier maintenance as users no longer need to install the TRIMS software locally in order to use the system. While TDOT expects that eTRIMS will eventually replace TRIMS, TDOT, local agencies and contractors in all 95 counties in Tennessee have access to both systems.

Key Accomplishments:

The following are key accomplishments of the Tennessee Roadway Information Management System:

• Improved data accuracy (for both roadway and crash data).
• One-stop access to all safety information.
• Data analytic support for State and local agencies.
• Support for project selection and funding justification.

Results:

Local agencies, by working with the State, use TRIMS/eTRIMS to identify safety needs, select projects, and obtain funding from the State to address safety issues. The integrated system also helps resolve crash data quality issues related to location coding accuracy, completeness, and timeliness.

TDOT is developing a long-term data maintenance method. They have not yet established procedures, but plan to include local agencies in reporting roadway updates in accordance with TDOT's data quality requirements. For now, the State will update data using an overlay on aerial photography as a way to identify major changes.

Contacts

Brian Hurst
Safety Manager
Project Safety Office
Tennessee Department of Transportation
615-253-2433
Brian.Hurst@tn.gov

Jeff Murphy
Information Systems Manager
GIS Mapping & Facilities Data Office TRIMS/E-TRIMS
Tennessee Department of Transportation
615-741-3429
Jeff.Murphy@tn.gov

Bryan Semore
Information Resource Specialist
GIS Mapping & Facilities Data Office TRIMS/E-TRIMS
Tennessee Department of Transportation
202-366-8090
Bryan.Semore@tn.gov

Tom Eldridge
Software Consultant
Intergraph Corporation
Tennessee Department of Transportation
Federal Highway Administration
202-366-8090
Tom.Eldridge@tn.gov

Stuart Thompson
Federal Highway Administration
202-366-8090
Stuart.Thompson@dot.gov

Ohio, with Stakeholder Input, Develops Consistent Mapping and Data Standards for State and Local Roads

Summary from: Ohio Location Based Response System State and Local Data Integration Case Study FHWA-SA-14-036

Background

This case study, available as part of the Federal Highway Administration's (FHWA) Integration of State and Local Safety Data project, describes Ohio's efforts to integrate local roadway data into their State data system.

This case study is part of a series of four. Each case study identifies a State's experience collecting local data, the challenges and obstacles faced and how they were overcome, benefits of the practices, reasons for success, lessons learned, and applicability of the practices to other agencies.

With the majority of public road mileage in Ohio owned and maintained by local agencies such as counties, cities and villages, ODOT (Ohio Department of Transportation) faced challenges with consistency in creating and storing local road maps: there was no single standard and locating crashes on local roads was a “hit or miss” process. For the most part, local road jurisdictions did not have a consistent linear referencing system—many local roadway crash reports referenced approximate street addresses, alias street names, or intersections that no longer existed. Using street addresses as a location reference was problematic because the State road database did not contain address ranges, and the State's list of local street names was often inaccurate. Given that roughly two-thirds of crashes in Ohio happened on non-State roads, this was a significant concern.

To remedy the issue, Ohio integrated the local road system into the State Linear Referencing System (LRS) by assigning consistent route numbers and mileposts to the local roads and then brought the local roadway data into a centralized data system: the Location Based Response System (LBRS). With data standards set by ODOT, each local agency collects, inputs, and field verifies the data in LBRS. LBRS is web-based and the information is available for all stakeholders as soon as agencies enter it. Mapping and analytic tools are available through the website.

Key Accomplishments:

The following are key accomplishments of the Ohio Location Based Response System:

• Improved location references for crashes on local roads.
• Consistent mapping and data standards.
• Easy integration of compliant local data into the State roadway database.
• More efficient process for conducting safety analyses.
• Routine updates of State road miles and addressing.
• Improved data access for the State and local agencies.

Results:

The integration of local and State data via the LBRS proved beneficial for a number of State agencies, as well as the local agencies themselves. At the State level, the improved road centerline and mileposting data has enhanced crash reporting and safety analysis. Ohio now places local road crashes more accurately allowing for better analysis of road safety issues in the counties. The State also now has consistent mapping and data standards for all counties allowing easy integration and improved data access. Finally, this program helps save taxpayer dollars by reducing redundant, and sometimes conflicting, data collection activities. At the local level, one of the most important uses of the LBRS data is for better routing for 911 services by providing more accurate location information for 911 calls and support for next generation 911 implementation.

Ohio plans to improve integration by providing more guidance to local agencies on data maintenance and increasing coordinated communication among the State and local agencies. However, Ohio's experience so far with developing and implementing LBRS shows that there can be successful integration of the local road addressing and mileposting into a State system.

Contacts

Stuart Davis
State CIO/Assistant Director
Ohio Office of Information Technology
614-644-3923
Stu.Davis@oit.ohio.gov

Jeff Smith
GIS Administrator
Ohio Office of Information Technology
614-466-8862
Jeff.Smith@das.ohio.gov

Dave Blackstone
GIS Manager
Ohio Department of Transportation
614-466-2594
Dave.Blackstone@dot.State.oh.us

Stuart Thompson
Federal Highway Administration
202-366-8090
Stuart.Thompson@dot.gov

Michigan's Roadsoft Program Enables Local Agencies to Collect and Maintain Data, while Preserving Local Ownership and Control

Summary from Michigan Roadsoft Integration of State And Local Safety Data

Background

This case study, available as part of the Federal Highway Administration's (FHWA) Integration of State and Local Safety Data project, describes Michigan's efforts to integrate local roadway data into their State data system.

This case study is part of a series of four. Each case study identifies a State's experience collecting local data, the challenges and obstacles faced and how they were overcome, benefits of the practices, reasons for success, lessons learned, and applicability of the practices to other agencies.

One way some States are enabling local agencies to collect and maintain data, while still preserving local ownership and control, is through centrally supported data models like Michigan's Roadsoft program. With Roadsoft, there is no centralized database of local data; local agencies receive a copy of the Roadsoft software to download and maintain locally. However, since Michigan applied a consistent linear referencing system to the local roads, and since most local agencies use the Roadsoft system, the similar structure and data definitions make it easier to share data when needed.

Michigan Technological University's Center for Technology and Training (CTT) developed Roadsoft for the Michigan Department of Transportation (MDOT) as a standardized suite of data management and analysis tools in the early 1990s for local centerline mileage certification and pavement management. Before Roadsoft, local agencies had widely varied levels of access to IT support, software tools and analytic capability. Over time, MDOT and the CTT enhanced Roadsoft to cover a broader range of assets and planning and budgeting support, and to include features such as traffic and crash data for use in safety analysis.

The Roadsoft system meets most analysis needs at the local agency level, but more advanced analyses are not included in Roadsoft. To do such analyses, the local agency must create a data extract to import into any other analysis package. With funding from MDOT, the CTT also supports local agencies with training and analytic assistance. Local agencies are not required to use Roadsoft, though approximately two-thirds of local agencies do.

While MDOT provides Roadsoft to local agencies at no charge, it does not eliminate the costs of data collection. Still, Roadsoft does improve data quality by defining data collection standards, where applicable, within each module. Local agencies are only required to report standard roadway asset and pavement condition data to MDOT for the Federal aid-eligible portions of their network; however, the same standards apply to all data entered into the system. Additionally, Roadsoft has modules for managing a large number of assets and each module was created based on input from local agencies. To help with data collection, Roadsoft has an integrated, GPS-enabled, mobile data collection utility which links Google Maps and Street View, thus creating an inexpensive photo log.

Key Accomplishments:

The following are key accomplishments of Michigan's Roadsoft system:

• Improved location references for crashes on local roads.
• Consistent mapping and data standards for all local jurisdictions.
• Data sharing among local, regional, and State agencies.
• Efficient process for conducting safety analyses.
• Comprehensive asset management capabilities.

Results:

The lessons learned from the Roadsoft effort are that long-term support, local agency control, and frequent, gradual, incremental updates, are the keys to Roadsoft's success. The CTT supports the incremental nature of Roadsoft development using a rapid prototyping model with frequent user testing to be sure that the final product meets local users' needs. Local users have a great deal of control over decisions regarding Roadsoft's enhancements—the Roadsoft Users' Group selects and approves each project. MDOT supports Roadsoft by funding the CTT's efforts and by supplying data.

Contacts

Tim Colling, Director
Center for Technology & Training (CTT)
Michigan Technological University
906-487-2102
TKCollin@mtu.edu

Stuart Thompson
Federal Highway Administration
202-366-8090
Stuart.Thompson@dot.gov

Thurston County, Washington, Public Works Department Applies Systemic Safety Project Selection Tool

Original publication: FHWA Safety Program | Systemic In Practice | Washington

Overview of Practice

The Thurston County Public Works Department used the Systemic Safety Project Selection Tool to explore the potential benefits of proactive safety planning. Although Thurston County staff had experience conducting strategic safety planning in partnership with the Washington State Department of Transportation (WSDOT), those efforts focused on site-specific safety improvements such as turn lanes, guardrail enhancement, and shoulder paving and widening.

Results

The Tool provided Thurston County a proactive, data driven and defensible approach to identifying curves for improvement prior to a severe crash occurring, rather than reacting after an incident has occurred. Upon conclusion of the systemic analysis, Thurston County applied for Highway Safety Improvement Program (HSIP) grant funding using the results as documentation for the request. The WSDOT approved the grant and the County is moving forward with implementing the systemic countermeasures identified through this systemic analysis. The Tool also proved to present a process that is flexible and implementable by a local agency with limited funding and staffing resources. A benefit of working with the WSDOT to apply the systemic safety planning process is that the experience provided County staff an opportunity for greater involvement in Strategic Highway Safety Planning (SHSP) activities.

Contact

Scott Davis, P.E.
Traffic Engineering and Operations Manager
Thurston County Public Works
davissa@co.thurston.wa.us

New York State Department of Transportation Applies Systemic Planning Process to Lane Departure Crashes on State Highway System

Original publication: FHWA Safety Program | Systemic Safety Project Selection Tool | New York Case Study(PDF, 186kB)

Overview of Practice

The New York State Department of Transportation (NYSDOT) used the Systemic Safety Project Selection Tool to identify sites where safety could be improved by deploying low-cost countermeasures on roadways with a high crash risk rather than just focusing on specific sites with a history of severe crashes.

Results

The Tool is beneficial because it provides a process to identify locations that would benefit from safety-related improvements that would not otherwise be identified through the traditional site-specific analysis process. The Tool also is flexible enough to be applied by NYSDOT staff in a central location and disseminated to region staff or to be applied by region staff at the local level. The countermeasures identified during the pilot along with the documentation of segment mileages with risk factors present will be useful tools in future systemic safety program development.

Contact

Regina Doyle
Office of Traffic Safety and Mobility
New York State Department of Transportation
RDoyle@dot.ny.gov

Missouri Department of Transportation Evaluation of Project Proves Systemic Planning Process is Beneficial

Original publication: FHWA Safety Program | Missouri Case Study(PDF, 202kB)

Overview of Practice

The Missouri Department of Transportation (MoDOT) used the concepts discussed in the Systemic Safety Project Selection Tool to evaluate a project that was developed using a systemic planning process. MoDOT evaluated the effects of adding edge line pavement markings to 570 miles of rural, two-lane State highways with average daily traffic volumes between 400 and 1000 vehicles.

Results

Crash data collected after the project provided proof that implementing low-cost countermeasures on low-volume roads with low-crash frequency and density yields a reduction in crashes. While evidence was stronger for total crashes, there was still a net reduction in fatal and severe injury crashes on improved corridors. Evaluation results can be used by decision-makers to decide whether to continue or discontinue funding or to implement a particular countermeasure for a focus crash type on a focus facility. In this manner, limited safety funding can be appropriately directed to the projects and locations that will produce the most benefit in terms of reduced crashes for the least investment.

Contact

John P. Miller, P.E.
Traffic Safety Engineer
Missouri Department of Transportation
573-526-1759
John.P.Miller@modot.mo.gov

Missouri's Blueprint to Arrive Alive Implements System-Wide Safety Improvements

Original publication: FHWA Safety Program | Systemic In Practice | Missouri(PDF, 279kB)

Overview of Practice

Missouri is one state that has been successful in identifying and implementing system-wide improvements. Missouri's Blueprint to Arrive Alive, which is the State's SHSP, identifies their “Targeted 10” strategies in education, enforcement, engineering, and public policy areas. The state uses Highway Safety Improvement Program (HSIP) funding for many of these strategies, proactively incorporating the installation of rumble strips/stripes, improved signing and delineation, wider pavement markings, and improved shoulders into pavement resurfacing projects.

Results

Since 2007, almost two-thirds of Missouri's HSIP funds have been allocated to system-wide improvements. While overall results cannot be attributed to specific safety improvements, the evidence is compelling. Between 2005 and 2011, Missouri has seen a 37.5 percent drop in overall fatalities and a 46 percent reduction in lane departure fatalities. In addition, since the installation of cable median barriers on the Interstate system throughout the State, there has been an 80 percent reduction in cross-median crash fatalities on Missouri freeways.

Contact

John P. Miller, P.E.
Traffic Safety Engineer
Missouri Department of Transportation
573-526-1759
John.P.Miller@modot.mo.gov

Minnesota Makes Systemic Safety Improvements Based on Risk Assessments at County Level

Original publication: FHWA Safety Program | Practice - Minnesota(PDF, 426kB)

Overview of Practice

Minnesota DOT (Mn/DOT) is another example of a state implementing a systemic approach. While Missouri's approach is focused on state-maintained roadways, Minnesota has taken a different approach through the development of safety plans for each of state's 87 counties. The safety plans disaggregate the severe crash types by each of the AASHTO SHSP emphasis areas to identify emphasis and target crash types at the regional level. Mn/DOT has selected crash surrogates for various facility types to use in the risk assessment. Locations identified and included in the plans can be submitted for project funding through the HSIP.

Results

One example is a risk assessment based on curve radius. Evaluating the data against surrogate risk factors helped Minnesota identify curves with 500-1,200 foot radii to consider for systemic improvements.

Contact

Bradley Estochen
State Safety Engineer
Minnesota Department of Transportation
651-234-7011
Bradley.Estochen@state.mn.us

Publication Year: 2011