Best practice features in crash data systems – some examples
Discover best features in crash data systems through a research project funded by Austroads. Focus on analysis tools, data entry, crash analysis, mapping, integration, and dissemination. Learn how a small investment in tools can save time and money. Explore mapping, trend identification, and data export. Find out how to select and treat sites of interest effectively.
Best practice features in crash data systems – some examples
E N D
Presentation Transcript
Best practice features in crash data systems – some examples Blair Turner, Principal Research Scientist, Australian Road Research Board
Background • Research project funded in Australia by Austroads (www.austroads.com.au) • Aim to identify good features from crash data systems • Focus on analysis tools • Literature review, surveys, demonstrations - 20 data systems
Areas of interest • Data entry • Types of data collected • Analysis of crashes – sites of interest • Analysis of crashes – policy level • Mapping • Integration with other data • Quality control issues • Monitoring sites of interest • Dissemination of data
Concluding comments • It costs a lot to collect crash data • A small additional investment can produce some tools that will save a lot of time and money in the future • Mapping is a key feature – ensure data can be exported to a GIS system if this is not already built in to the database system • Many other tools available, but check with the end user to see what is of greatest value • Check the Austroads report for what others are doing.
Questions? blair.turner@arrb.com.au