The Traffic Dashboard is an interactive data visualization tool for viewing 9-1-1 and non-emergency calls received by Portland Police Bureau (PPB) related to crash and DUII incidents, as well as data related to enforcement actions conducted by the PPB’s Traffic Division including the issuing of warnings and citations. This dashboard presents a detailed look at locations in the city where crash calls and traffic enforcement by PPB Traffic Division staff occurs, and a higher-level look at crash and driving citation statistics. The dashboard also shows information about our Vision Zero traffic missions, a collaborative partnership with PBOT’s citywide initiative to improve traffic safety.
The dashboard is updated by the first business day after the 5th of the month.
Received Traffic Incident Calls
Received traffic incidents, consisting of crash and DUII-related calls for service, are collected by the Bureau of Emergency Communications (BOEC) and sourced from the PPB's record management system, RegJIN. The data is a record of community-generated 9-1-1 and non-emergency public safety calls as well as self-initiated responses by PPB officers.
Six calls types are associated with Portland Police Bureau’s reported traffic incidents:
|Crash - Injury||Crash event resulting in a reported injury|
|Crash - Non-Injury||Crash event with no injury|
|Crash - Unknown Injury||Reported crash with unknown injury condition|
|Driving Under the Influence||Individual suspected of driving under the influence|
|Hit & Run - Active||Hit and run crash that is an active, current event|
|Hit & Run - Past Occurrence||Reported hit and run crash that occurred in the past|
Locations are mapped to the generalized Latitude / Longitude of the reported call. For calls that occurred at a specific address, the point is mapped to the block's midpoint. Calls that occurred at an intersection are mapped to the intersection centroid. Calls without a valid geographical location are not included in the map displays but are counted in the summary numbers and charts. The map display gives a snapshot of locations in the city where crash and DUII events occur within the specified time frame.
Major Crash Team Callouts
PPB tracks incidents where its Major Crash Team (MCT) responded to or was made aware of a serious or fatal crash event. This may not include every fatal or serious injury crash in the city that has occurred. The Major Crash category includes the following types:
|Fatal||A death resulting from the crash per NHTSA standards|
|A serious injury resulting directly from the crash|
|Other||An MCT callout to a crash with other non-NHTSA causes, i.e. a crash resulting from a medical event, suicide, other intentional action or other causes not included in the other categories|
An MCT callout marked as “Vehicle” includes the collision of one or more cars, trucks, or motorcycles. An MCT callout that involved a pedestrian is marked as “Pedestrian”. An MCT callout that involved a bicycle is marked as “Bicycle”.
Occasionally, the MCT will participate in investigations which involve non-traffic related or non-public roadway fatalities. These cases are not applicable to public traffic or roadway associated causes and do not appear on this dashboard.
MCT callouts are mapped to the location of the crash. The map display gives a snapshot of locations in the city where fatal, serious injury or other MCT callout activity occurred within the specified time frame.
Traffic Division Citations
PPB’s Traffic Division keeps digital records of enforcement actions that ended in a written warning or driving citation. The mapped data shows unique locations where a citation or written warning was issued, but each unique incident may result in multiple citations or warnings (e.g. a citation for speeding and a written warning for failure to carry insurance). This data gives an approximate summary of driving infractions citywide (i.e. what people are getting pulled over and ticketed for), and a snapshot of locations in the city where Traffic Division officers are issuing citations and written warnings. The charts and graphs showing citation information count every recorded citation or warning issued during a unique enforcement action.
This is not a full picture of all traffic enforcement that occurs in the city as citation records in hardcopy formats are not reflected in the data. As these additional records move to digital formats, the Strategic Services Division will work on incorporating and making these data available.
Violation Categories consist of the following types:
|Careless/Reckless Driving||Careless or reckless driving with or without accident, etc.|
|Distracted||Use of cell phone while talking or texting, Operation of motor vehicle while using a mobile communication device, etc.|
|Driving on the Right||Crossing center line, Driving wrong way around traffic island, Failure to drive on right or keep trailer in right lane, etc.|
|Driving Uninsured||Driving uninsured or Failure to carry proof of insurance|
|DUII/Substance Related||Driving under the influence of alcohol and/or controlled substances, Refusal to take a test for intoxicants, Unlawful use of marijuana while driving, etc.|
|Equipment||Unreasonable noise with vehicle, Inoperative lighting, obstruction of vehicle windows, Improper brakes, Failure to wear protective headgear (motorcycles/mopeds), etc.|
|Hit and Run||Driver left the scene of the incident|
|Lane Use||Improper use of lanes, Failure to drive within lane, Unlawful/unsignaled lane change, etc.|
|Non-Traffic Violation||Minor in possession of alcohol, Attempt to allude police officer, etc.|
|Other||Carrying passenger on moped, Dragging object on highway, failure to yield for emergency vehicle, Following too closely, Impeding traffic, etc.|
|Other Administrative||Failure to change name or address, Carry registration, Providing vehicle to unlicensed driver, etc.|
|Parking, Standing, and Stopping||Illegal parking, stopping or standing, Blocking access to disabled space, Use of invalid disabled parking permit, etc.|
|Passing||Passing in no passing zone, Unsafe passing, Failure of slower driver to yield to overtaking vehicle, etc.|
|Pedestrian||Failure to use crosswalk or obey traffic control device, Failure to obey bridge or RR signal, Riding bicycle on sidewalk in a prohibited area, etc.|
|Plate Violation||Failure to display plates, Expired tags|
|Prohibited Places||Driving around barricade, Failure to follow rail crossing procedures, Operating motor vehicle on bike path, etc.|
|Right of Way||Failure to yield at uncontrolled intersection, Failure to yield before entering roadway, Obstructing cross traffic, etc.|
|Safety Belt||Failure to use seatbelt, Endangering a child passenger, etc.|
|Signaling||Failure to signal turn, Failure to use appropriate signal, etc.|
|Speed||Violation of speed rules 1-100 mph excess, Speed racing, etc.|
|Traffic Control Devices||Failure to obey traffic control device or one-way designation|
|Turning||Dangerous left turn, Illegal U-turn, Improper turn, etc.|
|Unauthorized Driving||Driving while suspended, Driving while revoked, etc.|
|Vulnerable Road User||Failure to stop and remain stopped for pedestrian, Driving through safety zone, Refusing to obey flagger, etc.|
Vision Zero Mission
Mission areas are digitized from summary information submitted by PPB officers following the completion of a mission. Tracking of missions began October 10, 2017 although earlier Vision Zero missions had been conducted. Counts of citations, warnings, and classes offered (tracking of classes offered began on April 15, 2018) are provided as well as information on the divisions conducting the mission.
|RowID||The unique identifier for the row in the table.|
|Date||The date the incident occurred.|
|Address||Address of the incident at the 100 block level (e.g. 1111 SW 2nd Ave would be 1000 SW 2nd Ave) or intersection|
|Open Data Lat/Lon||Generalized latitude/longitude point of the incident. For incidents that occurred at a specific address, the point is mapped to the block's midpoint. Incidents that occurred at an intersection are mapped to the intersection centroid.|
|Open Data X/Y||Generalized XY point of the incident. For incidents that occurred at a specific address, the point is mapped to the block's midpoint. Incidents that occurred at an intersection are mapped to the intersection centroid. XY points use the Oregon State Plane North (3601), NAD83 HARN, US International Feet coordinate system.|
|PPB Precinct||Portland Police Bureau precinct where the incident occurred.|
|Data Category||Category of data course: traffic incident calls, traffic division enforcement, or Major Crash Team (MCT) callout crashes.|
|Call Description||Applies only to Traffic Incident Calls data. The crash type associated with the call received by PPB. See the Received Traffic Incident Calls section for more detail.|
|Crash Outcome||Applies only to the MCT Callouts data. The outcome of the crash per the data available. This field may be subject to change. See the Major Crash Team Callouts section for more detail.|
|Crash Involved||Applies only the MCT Callouts data. The crash involved either one or more vehicles, pedestrians or bicycles in the collision. See the Major Crash Team Callouts section for more detail.|
|Citation Type||Applies to the Traffic Division data. The citation issued was for either a Crime/Misdemeanor, Standard Traffic Citation, Traffic Citation issued after an accident/crash, Traffic Citation issued due to video evidence (this does not include Photo Radar citations), or warning was recorded in writing.|
|Violation Type||Applies to the Traffic Division data. The Violation Type can be either a violation or misdemeanor offense.|
|Violation Level||Applies to the Traffic Division data. The Violation Level is either major (Class A or B offenses) or minor (Class C, D or other).|
|Violation Class||Applies to the Traffic Division data. The Violation Class refers to the severity of the violation and ranges from Class A (most severe) to Class D (lease severe).|
|Violation Group||Applies to the Traffic Division data. The Violation Group can be either a moving (any violation where the vehicle involved was actively moving) or non-moving (an administrative or clerical-related violation)|
|Violation Category||Applies to the Traffic Division data. The Violation Category refers to broad classes of similarly related violation types. See the Traffic Division Citations section for more information.|
|VZ Citation||Applies to the Traffic Division data. Records marked with a "1" are violations, and corresponding citation or warning, associated with a Vision Zero mission that was conducted by the Traffic Division. This only represents citations issued by Traffic Division officers during a Vision Zero mission, and does not reflect the total citation counts during a mission (e.g. if other non-traffic division officers were part of the mission and issued paper citations).|
|VZ Mission||Applies to the Traffic Division data. A unique identifier for a Vision Zero mission. This unique identifier can be matched with the Vision Zero mission shapes on the Vision Zero tab of the dashboard.|