cityofchicago/traffic-crashes-vision-zero-chicago-traffic-gzaz-isa6
Icon for Socrata external plugin
 
Readme
Updated 4 days ago
Indexed 2 hours ago

Traffic Crashes - Vision Zero Chicago Traffic Fatalities

Traffic fatalities within the City of Chicago that are included in Vision Zero Chicago (VZC) statistics. Vision Zero is Chicago’s commitment to eliminating fatalities and serious injuries from traffic crashes. The VZC Traffic Fatality List is compiled by the City’s multi-departmental Fatal Crash Response Coordination Committee (FCRCC) that reviews fatal traffic crashes provided by Chicago Police Department’s Major Accident Investigation Unit (MAIU). The dataset is updated after the FCRCC meetings in the 4th week of the month. Thus, the fatality list for a particular month will be available in the dataset after the 4th week of the following month.

This committee uses a standardized process – sometimes differing from other sources and everyday use of the term -- to determine whether a death is a “traffic fatality” for VZC purposes. Therefore, the traffic fatalities included in this list may differ from the fatal crashes reported in the full Traffic Crashes dataset (https://data.cityofchicago.org/d/85ca-t3if).

Official traffic crash data are published by the Illinois Department of Transportation (IDOT) on a yearly basis. The traffic fatality list determined on an ongoing basis through the year may differ from IDOT’s official crash data for Chicago as IDOT may define the cause and location differently from the FCRCC. Once IDOT publishes its data for a year, crashes in this dataset for that year are edited to match IDOT’s determinations, unless the FCRCC disagrees with the IDOT determination – which happens only rarely and usually due to an interpretation of one of the criteria below.

VZC Traffic Fatalities can be linked with other traffic crash datasets using the “RD_NO” or “Person_ID” fields.

The FCRCC defines a “traffic fatality” for the purpose of VZC statistics as "any death caused by a traffic crash, within 30 days of the crash” and “involves a motor vehicle.” Fatalities that meet the VZC definition of a traffic fatality are included in this dataset unless excluded by the criteria below. There may be records in this dataset that do not appear as fatalities in the other datasets.

The following criteria exclude a death from being considered a "traffic fatality" for VZC purposes:

  1. The Medical Examiner determined that the primary cause of the fatality was not the traffic crash, including:

a. The fatality was reported as a suicide based on a police investigation.

b. The fatality was reported as a homicide in which the "party at fault" intentionally inflicted serious bodily harm that caused the victim's death.

c. The fatality was caused directly and exclusively by a medical condition or where the fatality was not attributable to road user movement on a public roadway. (Note: If a person driving suffers a medical emergency and consequently hit and kills another road user, the other road user is included although the driver suffering a medical emergency is excluded.)

  1. The crash did not occur within the public right-of-way.
  1. The crash involved a train or such mode of transport within their dedicated right-of-way.
  1. The fatality was on a roadway not under Chicago Police Department jurisdiction, including:

a. The fatality was occurred on an expressway. The City of Chicago does not have oversight on the expressway system. However, a fatality on expressway ramps occurring within the City jurisdiction will be counted in Vision Zero Chicago Traffic Fatalities.

b. The fatality occurred outside City limits. Crashes on streets along the City boundary may be assigned to another jurisdiction after the investigation if it is determined that the crash started or substantially occurred on the side of the street that is outside the City limits. Jurisdiction of streets along the City boundary are split between City and neighboring jurisdictions along the street center line.

  1. The fatality is not for a person (e.g., an animal).

Columns

NameSocrata field nameColumn name in sgr mountData typeDescription
Locationgeocoded_columngeocoded_columnPointThe crash location in a format that allows for mapping and other geographic analysis.
LongitudelongitudelongitudeNumberLongitude
VictimvictimvictimTextActivity classification of victim: CYCLIST / DRIVER / MOTORCYCLIST / PASSENGER / PEDESTRIAN
Census Tracts:@computed_region_bdys_3d7i:@computed_region_bdys_3d7iNumberThis column was automatically created in order to record in what polygon from the dataset 'Census Tracts' (bdys-3d7i) the point in column 'geocoded_column' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
Crash_Datecrash_datecrash_dateCalendar dateDate and time of crash on police report
Zip Codes:@computed_region_6mkv_f3dw:@computed_region_6mkv_f3dwNumberThis column was automatically created in order to record in what polygon from the dataset 'Zip Codes' (6mkv-f3dw) the point in column 'geocoded_column' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
RD_Nord_nord_noTextUnique ID for eCrash / SR-1050 reports
LatitudelatitudelatitudeNumberLatitude
Crash_Locationcrash_locationcrash_locationTextEstimated address of crash based on crash report
Community Areas:@computed_region_vrxf_vc4k:@computed_region_vrxf_vc4kNumberThis column was automatically created in order to record in what polygon from the dataset 'Community Areas' (vrxf-vc4k) the point in column 'geocoded_column' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
Boundaries - ZIP Codes:@computed_region_rpca_8um6:@computed_region_rpca_8um6NumberThis column was automatically created in order to record in what polygon from the dataset 'Boundaries - ZIP Codes' (rpca-8um6) the point in column 'geocoded_column' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
Person_IDperson_idperson_idTextUnique ID linking this record to the PERSON table in eCrash
Wards:@computed_region_43wa_7qmu:@computed_region_43wa_7qmuNumberThis column was automatically created in order to record in what polygon from the dataset 'Wards' (43wa-7qmu) the point in column 'geocoded_column' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
 
Preview
  • traffic_crashes_vision_zero_chicago_traffic
     
Upstream Metadata