- API data.seattle.gov | Last Updated 2019-07-23T15:24:35.000Z
This data represents records of police reported stops under Terry v. Ohio, 392 U.S. 1 (1968). Each row represents a unique stop. - Each record contains perceived demographics of the subject, as reported by the officer making the stop and officer demographics as reported to the Seattle Police Department, for employment purposes. - Where available, data elements from the associated Computer Aided Dispatch (CAD) event (e.g. Call Type, Initial Call Type, Final Call Type) are included.
- API data.seattle.gov | Last Updated 2019-04-19T05:06:22.000Z
<div><p>No two neighborhoods in Seattle are the same. The Micro Community Policing Plans (MCPP) were designed to address the distinctive needs of each community. The plans take a three prong approach that brings community engagement, crime data and police services together to get direct feedback on perceptions of crime and public safety. MCPP are tailored to meet the individual needs of each community, with a unique approach owned by the community.</p> <strong>Why are Perceptions of Crime Important?</strong> <p>Citizen perceptions of crime and public safety matter. When used in conjunction with crime data, citizen perceptions at the micro-community level provide a more accurate picture of the reality of crime and public safety than can be seen through crime statistics alone. This is what makes the MCPP strategy unique. </p> <strong>How were the Neighborhoods Defined?</strong> The MCPP neighborhoods were defined through police-citizen engagement including community meetings, focus groups, survey data, and the realities of geographic boundaries SPD can use to collect and report on events. The MCPPs and their neighborhoods will be routinely reevaluated with attention to the ways in which citizens who live in Seattle neighborhoods define their communities. <br /></div><div><br /></div><div>https://www.seattle.gov/police/community-policing/mcpp</div>
- API data.seattle.gov | Last Updated 2019-07-24T05:00:25.000Z
Provides Seattle Fire Department 911 dispatches. Updated every 10 minutes.
- API data.seattle.gov | Last Updated 2019-05-13T05:03:59.000Z
Displays citywide address points using TRANSPO.MAFDAP_PV. Differs from TRANSPO.DAP in that it contains address data. Attributes include house number and modifier, directional, street name, and street type. Does not display when zoomed out beyond 1:10,000. Labels are based on the attribute MAF_HSENUMMOD and do not display when zoomed out beyond 1:3,000. ATTRIBUTE INFORMATION: MAILUSECODE ? Identifies suitability of MAF address and associated MAFUNIT record(s) for use as a mailing address. This field serves as an indicator whether the address is being utilized in the City?s Utility Billing System. If so, it is more likely (but still not guaranteed) to be a valid mailing address. DCLUSTAT - Description of address establishment and validation status related to DCLU business process. Valid values: ?INITIAL VALUE? ? SPU-added records are assigned this value upon creation. ?DRAFT? ? only DPD-added records are assigned this value upon creation. ?FIELD VERIFIED? ? only DPD can assign this value. Indicates that DPD at some point conducted a site visit. This value is not reliably assigned and is not necessarily an indicator of a correct address. ?CANCELED? ? only DPD can assign this value. The address was never utilized. ?RETIRED? ? DPD or SPU can assign this value. The address may have been utilized for some period of time but was then replaced by a different address for the location or retired from use completely. DCLUSTATDT - Date of creation or modification of record. SOURCENAME - Descriptive character string identifying agency, department or divisional record source or usage. Valid values: ?DPD_MAF? ? Added or modified by DPD ?CGDB_MAFEDITS? ? Added or modified by SPU ?INIT_MAF? ? The initial record value, likely harvested from King County Assessor data when the MAF/DAP was first implemented.
- API data.seattle.gov | Last Updated 2019-05-15T21:14:23.000Z
**WARNING - THIS DATA IS STATIC** IN MID-2017 KING COUNTY BEGAN A PROCESS TO REFORM THE WAY "POLICE INQUESTS" ARE CONDUCTED. IN OCTOBER OF 2018 AN EXECUTIVE ORDER WAS ISSUED ESTABLISHING THE NEW PROCESS. INQUESTS ARE EXPECTED TO RESUME "BY THE END OF FIRST QUARTER 2019." SEE KING COUNTY FOR MORE INFORMATION: (https://www.kingcounty.gov/elected/executive/constantine/news/release/2018/October/03-inquest-reform.aspx) THESE DATA ARE UPDATED ONLY AFTER THE INQUEST PROCESS HAS BEEN COMPLETED. UPDATES WILL RESUME AS FINDINGS BECOME AVAILABLE. Records of Officer Involved Shootings (OIS) from 2005 to the present. Dataset does not contain records from active investigations.
- API data.seattle.gov | Last Updated 2019-07-23T09:07:17.000Z
This data represents crime reported to the Seattle Police Department (SPD). Each row contains the record of a unique event where at least one criminal offense was reported by a member of the community or detected by an officer in the field. This data is the same data used in meetings such as SeaStat (https://www.seattle.gov/police/information-and-data/seastat) for strategic planning, accountability and performance management. These data contain offenses and offense categorization coded to simulate the standard reported to the FBI under the National Incident Based Reporting System (NIBRS) and used to generate Uniform Crime Report (UCR) summary statistics. As these records evolve, daily and are continually refreshed, they will not match official UCR statistics. They represent a more accurate state of the record. Previous versions of this data set have withheld approximately 40% of crimes. This updated process includes all records of crime reports logged in the Departments Records Management System (RMS) since 2008, which are tracked as part of the SeaStat process. In an effort to safeguard the privacy of our community, offense reports will only be located to the “beat” level. Location specific coordinates will no longer be provided. 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. In addition to the Departments patrol deployment areas, these data contain the “Neighborhood” where the crime occurred, if available. This coding is used to align crime data with the Micro Community Policing Plan (MCPP). For more information see: https://www.seattle.gov/police/community-policing/about-mcpp. As with any data, certain condition and qualifications apply: 1) These data are refreshed, daily and represent the most accurate, evolved state of the record. 2) Due to quality control processes, these data will lag between 2 and 6 weeks. Most changes will occur within that record and reports logged in the last 2 weeks should be treated as volatile. Analysts may wish to remove these records from their analysis. 3) Not all offenses are reported here, only the primary offense as determined by the “Hierarchy Rule.” For more information on NIBRS and UCR, see the FBI (https://ucr.fbi.gov/nibrs-overview). 4) This dataset contains records of offenses that occurred prior to “go-live” of the existing RMS. Records are queried based on the full population of data and are not constrained by “Occurred Date.” We invite you to engage these data, ask questions and explore.
- API data.seattle.gov | Last Updated 2019-05-15T21:18:35.000Z
A closed discrimination case is an investigation that has been completed at the Seattle Office for Civil Rights. This dataset shows closed cases by month and case type in 2017.
- API data.seattle.gov | Last Updated 2019-07-23T14:59:54.000Z
The Asset Inventory Report dataset is automatically updated on daily basis for all assets, their metadata plus total download and pageviews.
- API data.seattle.gov | Last Updated 2019-01-24T17:57:48.000Z
- API data.seattle.gov | Last Updated 2019-05-15T21:13:32.000Z
The Seattle Office for Civil Rights (SOCR) receives calls on the Bias Incident Reporting Line. Calls are received by front desk staff and logged. This dataset shows the amount of calls received each quarter of 2017 by type of report. An “uncategorized” type means the call did not fall into one of the listed categories or SOCR was unable to confirm the type of report. If you have questions about this data or want to learn more about the laws SOCR enforces, call 206-684-4500 or visit http://www.seattle.gov/civilrights. Visit Seattle Police Department’s Bias/Hate Crime Data site for information about bias/hate crimes: https://www.seattle.gov/police/information-and-data/bias-crime-unit/bias-crime-dashboard.