Dataset: Call Data

About this Dataset

Call Data

Please review this brief video for a better understanding of how these data are created: https://www.youtube.com/watch?v=lvTCjVHxpAU

This data represents police response activity. Each row is a record of a Call for Service (CfS) logged with the Seattle Police Department (SPD) Communications Center. Calls originated from the community and range from in progress or active emergencies to requests for problem solving. Additionally, officers will log calls from their observations of the field.

Previous versions of this data set have withheld approximately 40% of calls. This updated process will release more than 95% of all calls but we will no longer provide latitude and longitude specific location data. In an effort to safeguard the privacy of our community, calls will only be located to the “beat” level. Beats are the most granular unit of management used for patrol deployment. To learn more about patrol deployment, please visit: https://www.seattle.gov/police/about-us/about-policing/precinct-and-patrol-boundaries.

As with any data, certain conditions and qualifications apply:

These data are queried from the Data Analytics Platform (DAP), and updated incrementally on a daily basis. A full refresh will occur twice a year and is intended to reconcile minor changes.
This data set only contains records of police response. If a call is queued in the system but cleared before an officer can respond, it will not be included.
These data contain administrative call types. Use the “Initial” and “Final” call type to identify the calls you wish to include in your analysis.

We invite you to engage these data, ask questions and explore.
Organization: City of Seattle
Last updated: 2024-12-16T22:17:56.245234
Tags: 911, calls-for-service, police

Tables

Table 1

@usgov.city_of_seattle_call_data_eb3f1.table_1

1.37 GB
10267492 rows
44 columns


CREATE TABLE table_1 (
  "cad_event_number" BIGINT,
  "cad_event_clearance_description" VARCHAR,
  "call_type" VARCHAR,
  "priority" DOUBLE,
  "initial_call_type" VARCHAR,
  "final_call_type" VARCHAR,
  "cad_event_original_time_queued" VARCHAR,
  "cad_event_arrived_time" VARCHAR,
  "dispatch_precinct" VARCHAR,
  "dispatch_sector" VARCHAR,
  "dispatch_beat" VARCHAR,
  "dispatch_longitude" VARCHAR,
  "dispatch_latitude" VARCHAR,
  "dispatch_reporting_area" VARCHAR,
  "cad_event_response_category" VARCHAR,
  "call_sign_dispatch_id" VARCHAR,
  "call_sign_dispatch_time" VARCHAR,
  "first_care_call_sign_at_scene_time" VARCHAR,
  "first_care_call_sign_dispatch_time" VARCHAR,
  "first_co_response_call_sign_at_scene_time" VARCHAR,
  "first_co_response_call_sign_dispatch_time" VARCHAR,
  "first_spd_call_sign_at_scene_time" VARCHAR,
  "first_spd_call_sign_dispatch_time" VARCHAR,
  "last_care_call_sign_in_service_time" VARCHAR,
  "last_co_response_call_sign_in_service_time" VARCHAR,
  "last_spd_call_sign_in_service_time" VARCHAR,
  "care_call_sign_total_service_time_s" DOUBLE,
  "co_response_call_sign_total_service_time_s" DOUBLE,
  "spd_call_sign_total_service_time_s" DOUBLE,
  "call_sign_total_service_time_s" DOUBLE,
  "first_care_call_sign_dispatch_delay_time_s" DOUBLE,
  "first_care_call_sign_response_time_s" DOUBLE,
  "first_co_response_call_sign_dispatch_delay_time_s" DOUBLE,
  "first_co_response_call_sign_response_time_s" DOUBLE,
  "first_spd_call_sign_dispatch_delay_time_s" DOUBLE,
  "first_spd_call_sign_response_time_s" DOUBLE,
  "call_sign_dispatch_delay_time_s" BIGINT,
  "call_sign_response_time_s" DOUBLE,
  "call_sign_at_scene_time" VARCHAR,
  "cad_event_first_response_time_s" DOUBLE,
  "call_sign_in_service_time" VARCHAR,
  "call_type_indicator" VARCHAR,
  "dispatch_neighborhood" VARCHAR,
  "call_type_received_classification" VARCHAR
);