Completing the Picture of Traffic Injuries: Understanding Data Needs and Opportunities for Road Safety [supporting dataset]
-
2018-07-13
-
Details:
-
Creators:
-
Corporate Creators:
-
Corporate Contributors:United States. Department of Transportation. University Transportation Centers (UTC) Program ; United States. Department of Transportation. Office of the Assistant Secretary for Research and Technology ; Collaborative Sciences Center for Road Safety ; United States. Department of Transportation. Federal Highway Administration
-
Subject/TRT Terms:
-
Publication/ Report Number:
-
DOI:
-
Resource Type:
-
Geographical Coverage:
-
Corporate Publisher:
-
Abstract:Police recorded crash data has improved over time, but still fails to report all aspects of crashes that are important to developing a full understanding of crash mechanism, injury burden, and ultimately total health outcomes. Traditionally, safety and injury analysis have occurred in isolated fields, with road safety researchers relying predominately on police-recorded crash reports, and public health researchers relying on health records (e.g., hospital, emergency department, ambulatory care data). Often, these records do not reflect the same findings, even for the same crash victims. By themselves, injury severity and crash reporting rates are often inconsistent between datasets. A “complete picture” of traffic crashes must be established to address these limitations. This complete picture needs to consider a multi-perspective approach to road safety instead of one point of view by considering multiple sources of data. This complete crash picture can be used to answer inconsistencies in findings and provide a better understanding of the nature of traffic crashes, injury outcome, and eventually direct cost of traffic crashes. The study objectives are: (1) To briefly review data linkage methodology, (2) Review examples of linking databases, (3) Establish a framework for developing a complete picture of traffic crashes, (4) Identify databases that have potential to complete the picture of traffic crashes, and (5) Illustrate linkage potential through case studies. The five case studies are: (1) Evaluating Research on Data Linkage to Assess Underreporting Pedestrian and Bicyclist Injury in Police Crash Data; (2) Pre-Hospital Response Time and Traumatic Injury—A Review; (3) An Approach to Assess Residential Neighborhood Accessibility and Safety: A Case Study of Charlotte, North Carolina; (4) Home-Based Approach: A Complementary Definition of Road Safety; and (5) Neighborhood-Level Factors Affecting Seat Belt Use.
The total size of the described zip file is 13.7MB. The ZIP file for this dataset contains files with the following file extensions: PDFs are used to display text and images and can be opened with any PDF reader or editor. The .csv, Comma Separated Value, file is a simple format that is designed for a database table and supported by many applications. The .csv file is often used for moving tabular data between two different computer programs, due to its open format. Any text editor or spreadsheet program will open .csv files. Files that end in .tab are tab-delimited text files and they are used in GIS programs such as MapInfo. These files can be opened using Notepad or other text file readers, or they can be opened using Microsoft Excel or an open source spreadsheet program.
-
Content Notes:As this dataset is preserved in a repository outside U.S. DOT control, as allowed by the U.S. DOT’s Public Access Plan (https://doi.org/10.21949/1503647) Section 7.4.2 Data, the NTL staff has performed NO additional curation actions on this dataset. The current level of dataset documentation is the responsibility of the dataset creator. NTL staff last accessed this dataset at https://doi.org/10.15139/S3/DLAC9X on 2022-09-29. If, in the future, you have trouble accessing this dataset at the host repository, please email NTLDataCurator@dot.gov describing your problem. NTL staff will do its best to assist you at that time.
-
Format:
-
Funding:
-
Collection(s):
-
Main Document Checksum: