Transcript Crash Data Flow - Past Traffic Records Forums Index

City of Madison, WI
Crash GIS
Short term Crash GIS Goals
• Intended as a 3 year pilot project to develop a
working crash GIS.
• Automate “pin” mapping of crashes
• Automate diagramming of intersection crashes
• Speed transfer of crash data to users
• Enhance crash data query capabilities
• Increase staff efficiency
• Work more directly with other local agencies
(Madison Police, Dane Co. Sheriff)
Old Crash Pin Map
CRASHES PINNED MANUALLY ON A LARGE BOARD
Automated Crash Pin Map
CRASHES PINNED BY COMPUTER
Manual Crash Diagram
Automated Crash Diagram
Westbound
Crashes
prior to test.
BIG SKY/TREE/MINERAL POINT
WAS THE HIGHEST CRASH
FREQUENCY INTERSECTION IN
THE CITY FOR 1998
Westbound
Crashes
after test.
Vehicle
Crash
Four Page MV
4000 filled out
by officer
Crash
Reported
Report delivered to
command central
Crash logged
into 911 Center
Original Data Flow
PD enters additional
data from Paper file
w ith 911 data
Add PDcase
number and
Diranal
Tw o hard copies
made by PD
New
World DB
Diagram
intersection data
One copy for TE
One Copy
for PD desk
Sort Crashes by
month
Hand types
printed data
File completed
interesection
folders
Data
Corrected
WisDOT
DB
Verifies and
corrects location
Additional copies
for special
crashes Bike,
Ped, Fatal,etc.
Diagram crash,
add data and
file report
Scanned by
bubble
reader
Separate out
ammended
reports
Sort by
Intersection or
Midblock
Pull specific
interesection
crash folders
Original for
WisDOT
Files in special
folders
Electronic
crash data
sent to TE
File completed
midblock reports
Data entered added to
crash data base in
four separtate sections
Adds directional
analysis
Crash data
mostly cleaned
TE Data Ready
for use
Enters data in TE
crash database
Pin on Map
Correlates hard copy
to TE database
Four Page MV
4000 filled out
by officer
Vehicle
Crash
Crash
Reported
Potential Savings with
interdepartmental cooperation
Report delivered to
command central
Crash logged
into 911 Center
PD enters additional
data from Paper file
with 911 data
Add PDcase
number and
Diranal
Stakeholders:
New
World DB
Two hard copies
made by PD
Traffic
Engineering,
Diagram
intersection data
One copy for TE
One Copy
for PD desk
Original for
WisDOT
Sort Crashes by
month
Hand type
printed data
Data
Corrected
Sort by
Intersection or
Midblock
Police,
Diagram crash,
add data and
file report
Scanned by
bubble
reader
Separate out
ammended
reports
WisDOT
File completed
interesection
folders
Step Eliminated
WisDOT
DB
Electronic
crash data
sent to TE
Verifies and
corrects location
Additional copies
for special
crashes Bike,
Ped, Fatal,etc.
Pull specific
interesection
crash folders
?
Files in special
folders
File completed
midblock reports
Data entered added to
crash data base in
four separtate sections
Adds directional
analysis
Crash data
mostly cleaned
TE Data Ready
for use
Enters data in TE
crash database
Changed
Pin on Map
Correlates hard copy
to TE database
Vehicle
Crash
Crash
Reported
Four Page MV 4000 filled
out Electronically w ith
correcting templates by
officer
Crash data
mostly cleaned
Report delivered to
command central
Crash logged
into 911 Center
Data on all three
database the
same with only
one entry
instead of four.
New
World DB
WisDOT
DB
TE Data Ready
for use
Possible
New Data
Flow
Pin Map
electronically
1) Officer
2) 911 center
Add diranal
electronically
3) TE
4) WisDOT
Diagram
intersection data
electronically
5) Public via
internet
Traffic Engineering Data Entry
Sheet
Initially created to clean up location data.
A step towards automated data entry by a
police officer.
Automates input of 16 data fields in
current MV-4000
Automated Entry-Select Location by Intersection Name
Automated Entry-Select Location using GPS coordinates
Enhanced Query Capabilities
• Query by fields coded in MV-4000
• Examples of queries include Red Light
Running, Alcohol, crash frequency
Red Light Running Crashes
CRASHES RANKED BY FREQUENCY
FOR A 13 YEAR PERIOD
MADISON 1999 PEDESTRIAN CRASHES
Current Status
• Automate “pin” mapping of crashes-completed
• Automate diagramming of intersection crashespreliminary only
• Speed transfer of crash data to users-turnaround is
improved, but we are not yet to a web based
system
• Enhance crash data query capabilities-completed
• Increase staff efficiency-already substantial
improvement, more yet is possible
• Work more directly with other local agencies
(Madison Police, Dane Co. Sheriff)-yes
Long term Crash GIS Goals
• Web based crash data query
• Automate crash location and reporting by
Police Officers using aerial photos, GIS or
GPS
• Electronic MV-4000 Badger TraCS
Other Data Collection Efforts
Pocket PC-Based Seat belt survey
Coordinated and funded by
WisDOT/BOTS