Welcome to ROSA P |
Stacks Logo
Advanced Search
Select up to three search categories and corresponding keywords using the fields to the right. Refer to the Help section for more detailed instructions.
Clear All Simple Search
Advanced Search
An overview of Virginia's computerized crash records systems.
  • Published Date:
  • Language:
Filetype[PDF-8.71 MB]

This document cannot be previewed automatically as it exceeds 5 MB
Please click the thumbnail image to view the document.
An overview of Virginia's computerized crash records systems.
  • Publication/ Report Number:
  • Resource Type:
  • Geographical Coverage:
  • OCLC Number:
  • Edition:
    Final report.
  • Abstract:
    This report identifies the various components of Virginia's computerized crash records systems and explains how these components process crash data. Emphasis has been placed on recording information that was previously not documented. Most of the statewide systems were studied in late 1994, and most of the local systems were studied in early 1995. The scope has been limited to systems that capture, store, and report data on traffic crashes. Statewide systems include those of the Department of Motor Vehicles (DMV), the Department of Transportation (VDOT), the Department of State Police (VSP), the Commission on the Virginia Alcohol Safety Action Program (VASAP), the Office of Emergency Medical Services (OEMS), the Department of Education (DOE), and the Department of Corrections (DOC). Local users such as planning district commissions, a traffic engineering department, and certain representative local law enforcement agencies were also included in the study. Representatives from statewide and local agencies were interviewed concerning how their respective systems processed crash data. Computer printouts, data dictionaries, and other agency-generated information were used in conjunction with the interviews to synthesize descriptions of how data are processed. Virginia's computerized crash records are analyzed from several perspectives. These include the diversity of crash data users and providers, the need for access to crash data, existing documentation of database capabilities, coordination among agencies, sources of duplication of effort, the methods used to collect data, and linkage opportunities. In light of this discussion, recommendations are made to improve crash data utility, accessibility, and accuracy.

  • Format:
  • Main Document Checksum:
  • Supporting Files:
    No Additional Files
No Related Documents.
You May Also Like: