Pavement

Cover of Road Safety Engineering Risk Assessment Part 3: Review of Best Practice in Road Crash Database and Analysis System Design
Road Safety Engineering Risk Assessment Part 3: Review of Best Practice in Road Crash Database and Analysis System Design
  • Publication no: AP-T148-10
  • ISBN: 978-1-921709-13-5
  • Published: 11 March 2010
Crash databases are an essential tool in analysing crash risk. Databases allow identification of high crash locations, and provide information on crash causation, allowing these crashes to be effectively targeted. The information contained in crash databases also allows analysis of trends and so assists greatly in strategic safety related decisions. All Australasian jurisdictions have crash database systems, but many provide only basic analysis tools for the data collected. In order to add value to this data, and better inform decision makers, additional tools should be available. This project identified good practice in database design, including features that may be of high interest to Australasian jurisdictions. This project involved a detailed review of Australasian and international crash databases to assess best practice features. Contact was made with each Australasian jurisdiction, and information was gathered on available features. Visits were made to a sample of jurisdictions to view these features, as often a live demonstration is the only way to appreciate system capabilities. A literature review was undertaken of international practice on this issue. Contact was also made with key international experts to determine current best practice.
  • AP-T148/10 Road Safety Engineering Risk Assessment Part 3: Review of Best Practice in Road Crash Database and Analysis System Design
  • Austroads profile
  • CONTENTS
  • TABLES
  • FIGURES
  • SUMMARY
  • ACKNOWLEDGEMENTS
  • 1. INTRODUCTION
    • 1.1. Objectives and Principal Tasks
  • 2. METHOD
    • 2.1. Literature Review
    • 2.2. Contact with International Experts
    • 2.3. Contact with Australasian Jurisdictions
  • 3. RESULTS FROM LITERATURE REVIEW
    • 3.1. What Makes a Good Database?
    • 3.2. Data Entry
    • 3.3. Data Items Included
    • 3.4. Database Navigation
    • 3.5. Analysis of Crashes – Sites of Interest
    • 3.6. Analysis of Crashes – Policy Level
    • 3.7. Mapping
    • 3.8. Integration with Other Data
    • 3.9. Quality
    • 3.10. Monitoring Sites
    • 3.11. Dissemination
  • 4. CONTACT WITH INTERNATIONAL EXPERTS
    • 4.1. Data Entry
    • 4.2. Data Items Included
    • 4.3. Database Navigation
    • 4.4. Analysis of Crashes – Sites of Interest
    • 4.5. Analysis of Crashes – Policy Level
    • 4.6. Mapping Ability
    • 4.7. Integration with Other Data
    • 4.8. Quality of Data
    • 4.9. Monitoring Sites of Interest
    • 4.10. Dissemination
  • 5. CONTACT WITH AUSTRALASIAN JURISDICTIONS
    • 5.1. Data Entry
    • 5.2. Data Items Included
    • 5.3. Database Navigation
    • 5.4. Analysis of Crashes – Sites of Interest
    • 5.5. Sites of Interest – Policy Level
    • 5.6. Mapping
    • 5.7. Integration with Other Data
    • 5.8. Quality of the Data
    • 5.9. Monitoring Site of Interest
    • 5.10. Dissemination
  • 6. SUMMARY OF KEY FEATURES AND DISCUSSION
    • 6.1. Key Features
    • 6.2. Discussion
  • REFERENCES
  • APPENDIX A AUSTROADS ROAD SAFETY ENGINEERING RISK ASSESSMENT PROJECT
  • A.1 Background to Risk Assessment Research
  • A.2 Parts to Risk Assessment Series
  • APPENDIX B QUESTIONNAIRE
  • INFORMATION RETRIEVAL