Skip to main content

Currently Skimming:


Pages 45-66

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 45...
... 45 The information in this chapter was derived from detailed interviews with individuals from several organizations in nine states selected to serve as case examples (California, Illinois, Iowa, Kentucky, Louisiana, Michigan, Ohio, Vermont, and Washington)
From page 46...
... 46 Integration of Roadway Safety Data from State and Local Sources local agencies along with some tribal, federal, or other state agencies. Caltrans is organized into 12 districts, and some of the MIRE FDEs on local roads are collected by the Research, Innovation and System Information Division, HPMS Branch.
From page 47...
... Case Examples of Data Integration and Maintenance Efforts 47 Interviews with representatives from Orange County, the Kern Council of Governments, and the City of Watsonville indicated that the routine HPMS and pavement condition data (submitted in Excel file format to Caltrans) constituted the MIRE FDE-related data shared.
From page 48...
... 48 Integration of Roadway Safety Data from State and Local Sources also noted that the Iowa DOT has achieved a high level of data integration of its state-level roadway data systems and crash database. Through the use of common services and tools, the integrated roadway information is shared with local transportation agencies.
From page 49...
... Case Examples of Data Integration and Maintenance Efforts 49 annually, while the traffic count data are updated every 4 years. The City of Ankeny does not collect pavement data; rather, the Iowa DOT collects state-level pavement data with a special van equipped with a camera.
From page 50...
... 50 Integration of Roadway Safety Data from State and Local Sources Counties. The Lake Cumberland ADD has been involved in collecting MIRE FDEs since 2000, when the state of Kentucky's 15 ADDs began collecting data for all of the state's 120 counties.
From page 51...
... Case Examples of Data Integration and Maintenance Efforts 51 Data are updated every 2 years, while updates for local road data depend on each LPA's own timing. One of the challenges identified by the Louisiana DOTD was having local agencies update their own data in the future.
From page 52...
... 52 Integration of Roadway Safety Data from State and Local Sources content, use of a data collection software, and an analysis program that helps all of the parties involved in maintaining consistency. City of Baton Rouge and Parish of East Baton Rouge The City of Baton Rouge and Parish of East Baton Rouge have been involved in the collection of MIRE FDEs since 2013.
From page 53...
... Case Examples of Data Integration and Maintenance Efforts 53 the GIS coordinator, while the data are maintained by the Department of Information Services in the city and parish. Although the Louisiana DOTD's collection practices are separate from those of the parishes, the parish offers assistance in providing updated local street information.
From page 54...
... 54 Integration of Roadway Safety Data from State and Local Sources directly to the Louisiana DOTD as they are developed and encourages the LPAs to send all updates to the roadway geodatabase directly to the Louisiana DOTD. Thus far, the New Orleans RPC indicated, the only known direct contact has been the City of New Orleans with the Louisiana DOTD.
From page 55...
... Case Examples of Data Integration and Maintenance Efforts 55 The integration, accessibility, and usability of roadway safety MIRE FDEs to facilitate meaningful crash analysis by all road agencies are the main goals of the implementation of geographic information technologies (GITs)
From page 56...
... 56 Integration of Roadway Safety Data from State and Local Sources A few of the lessons learned mentioned by the Michigan DOT regarding data integration efforts included contextualizing the data element and collection effort for LPAs so that they can better understand the importance and necessity of each data element. This approach will also address the issues associated with LPA relationships with the Michigan DOT in highlighting that the relationship is not just for reporting.
From page 57...
... Case Examples of Data Integration and Maintenance Efforts 57 uses the OGRIP system that collects the county data in various ways. The biggest benefits that MORPC reported from overseeing the data-managing process have been enhanced systemic safety analysis and enhanced hot spot location analysis.
From page 58...
... 58 Integration of Roadway Safety Data from State and Local Sources (DDTI, https://www.ddti.net/) , and at the time of the interview, data editing was done with the LBRS application from DDTI.
From page 59...
... Case Examples of Data Integration and Maintenance Efforts 59 Vermont In the state of Vermont, there are 10 RPCs and one MPO, the Chittenden County Regional Planning Commission (CCRPC)
From page 60...
... 60 Integration of Roadway Safety Data from State and Local Sources data throughout the region. Most traffic counts are for specific projects, and the majority of data collection takes place between May and November.
From page 61...
... Case Examples of Data Integration and Maintenance Efforts 61 MIRE FDEs, which are stored primarily in CRAB's Mobility Dashboard (http://www.crab.wa.gov/ Technology/Mobility/Help40/Overview_1.htm) , a comprehensive road inventory and management system software program.
From page 62...
... 62 Integration of Roadway Safety Data from State and Local Sources Figure 23. Roadway data inventory of horizontal curves (CRAB Mobility software)
From page 63...
... Case Examples of Data Integration and Maintenance Efforts 63 common data elements within the MIRE FDEs and the HPMS was identified as an item of significance for review. In addition, the FHWA Safety Data Business Planning program was mentioned as a potential tool for facilitating the collection and integration of MIRE FDE data.
From page 64...
... 64 Integration of Roadway Safety Data from State and Local Sources those roads where needed. Depending on the technology resources and GIS capabilities available at the various LPAs, this process was reported to allow the opportunity for GIS-knowledgeable or larger local governments to perform their own analysis, conflation, and updates as they are able.
From page 65...
... Case Examples of Data Integration and Maintenance Efforts 65 reporting tool used for extracting roadway inventory and crash and project data according to specific criteria. E-TRIMS is updated daily and is used by consultants, contractors, MPOs, RPOs, and LPAs.
From page 66...
... 66 Integration of Roadway Safety Data from State and Local Sources Agencies Collecting MIRE FDEs MIRE FDE Rank Total Number Interviewed Percent Roadway Segment for Non-Local Paved Roads Route/Street Name 1 10 83.33 Surface Type 2 9 75.00 Type of Governmental Ownership 2 9 75.00 Route Number 4 8 66.67 Segment Identifier 5 7 58.33 Segment Length 5 7 58.33 Intersection for Non-Local Paved Roads Location Identifier for Road 1 Crossing Point 1 4 33.33 Location Identifier for Road 2 Crossing Point 1 4 33.33 Intersection/Junction Geometry 1 4 33.33 Interchange/Ramps for Non-Local Paved Roads Ramp Length 1 5 41.67 Unique Interchange Identifier 2 3 25.00 Location Identifier for Roadway at Beginning Ramp Terminal 2 3 25.00 Location Identifier for Roadway at Ending Ramp Terminal 2 3 25.00 Type of Governmental Ownership 2 3 25.00 Local Paved Road Type of Governmental Ownership 1 9 75.00 Surface Type 2 9 75.00 Segment Identifier 2 7 58.33 Unpaved Road Type of Governmental Ownership 1 8 66.67 Segment Identifier 2 4 33.33 Table 21. Status of MIRE FDE collection summarized from 12 LPA interviews.

Key Terms



This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.