Metadata for Dispatched Calls Open Data
Metadata for Dispatched Calls Open Data Download
Calls deemed sensitive due to the nature of the incident, potential suspect or offender, potential victim/offender relationship, or investigation status may contain data that cannot be shared openly at this time. Specific location information for sensitive cases are not included in the open data.
| Call Number | Call identification number (randomly generated and assigned to anonymize call data). |
| Report Month Year | The Month and Year the call was placed in the police dispatch queue. |
| Report Date Time | The date and time the call was placed in the police dispatch queue. To protect the identity of victims and other privacy concerns, the date/time of certain call types are not released. |
| Time in Queue | Total seconds the call waited in the police dispatch queue before an officer was dispatched to the scene. |
| Travel Time | Total seconds for an an officer to arrive on-scene after being dispatched. |
| Response Time | Total seconds between a call being placed in the police dispatch queue and the first officer arriving on-scene. Time in Queue + Travel Time. |
| Priority | The priority level that is based on the severity of the incident and used to prioritize the police response. |
| Final Call Group | The classification of the call based on nine call groupings that broadly define the final nature of the call for service. A description of the call groupings are included in the Introduction to Calls for Service guide. |
| Final Call Category | A more-specific categorization of the final grouping used to define the final nature of the call for service. A description of the call categories are included in the Introduction to Calls for Service guide. |
| Neighborhood | Neighborhood where incident occurred. If the neighborhood name is missing, the incident occurred outside of the boundaries of the Portland neighborhoods or at a location that could not be assigned to a specific address in the system (e.g., Portland, near Washington Park, on the streetcar, etc.). Note: Neighborhood boundaries and designations vary slightly from those found on the Office of Community & Civic Life website. |
| Address | Address of reported call at the 100 block level (e.g.: 1111 SW 2nd Ave would be 1100 Block SW 2nd Ave). To protect the identity of victims and other privacy concerns, the points of certain call types are not released. |
| Open Data X / Y |
Generalized XY point of the reported call. For calls that occurred at a specific address, the point is mapped to the block's midpoint. Offenses that occurred at an intersection are mapped to the intersection centroid. To protect the identity of victims and other privacy concerns, the points of certain call types are not released. XY points use the Oregon State Plane North (3601), NAD83 HARN, US International Feet coordinate system. |
| Open Data Lat / Lon |
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. To protect the identity of victims and other privacy concerns, the points of certain call types are not released. |