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.

These offenses correspond to the Police Report Incidents http://data.seattle.gov/dataset/Seattle-Police-Department-Police-Report-Incident/7ais-f98f

The Community Assisted Response and Engagement (CARE) Reference Map consists of five separate map themes, which are selectable from the menu buttons in the map header. The map content will change after selecting a theme from the menu.Summary of the 5 reference map themes:SPD Boundaries: Police operational boundaries - precincts, sectors and beats.Neighborhoods: Informal neighborhood and district boundaries.Public Safety Answering Points (PSAP): County-wide boundary used for routing calls based on the caller's geographic location.Micro-Community Policing Plan (MCPP): Collection of neighborhoods defined for community engagement and public safety.Street Designation and Block Numbering: Streets and geographic boundaries that determine street directionality and block numbering.

View of Channelization data represents roadway paint lines, curbs, and other markings that delineate traffic lanes, bike routes, bus zones, etc. which are critical for public safety.Common Data Layer: Common data layer created from a read only view from this feature layer. It is owned by SDOT Transportation account and will be made available in Open Data.Refresh Cycle: None, Dynamic via AutoCAD updatesChannelization data consists of the following layers:Vertical ElementsLane WidthsPanel MarkingsLongitudinal MarkingsTransverse MarkingsLegend and SymbolsGeneral Background

Each identified street segment is given a prioritization score based on three factors: 1) proximity to high pedestrian trip areas, 2) safety, and 3) equity. Tier 1 segments are the highest priority. This PIN helps identify locations where there may be opportunities to improve conditions for people moving along the street by installing conventional sidewalks, alternative walkways, or traffic calming features that create a safe and comfortable shared street environment.

The Pedestrian Element of the Seattle Transportation Plan (STP) is a blueprint to create a more walkable Seattle and provides a suite of pedestrian improvements across the City. The intent is to focus resources on access to public schools, parks, and light rail, streetcar, and frequent transit networks12, in areas where walking conditions are difficult, and where people most need to be able to walk. It highlights the needs of people walking and rolling and guides future investments to achieve STP goals.The process is based on an analysis of factors related to the STP’s goals of safety, equity, sustainability, mobility & economic vitality, livability, and maintenance & modernization. This data-driven prioritization framework helps the city provide targeted improvements that reflect community priorities, City policy objectives, and current data. Throughout the life of the STP, there will be opportunities to evaluate what has been implemented and what can be prioritized in future funding cycles, within the context of the STP's goals, funding availability and project readiness, and other emergent needs. Decisions made as we craft regular STP Implementation Plans will determine the pace of STP Pedestrian Priority Investment Network implementation. Refresh Cycle: None, Static. Manually as required.Original Publish: 5/23/2024Update Publish: 7/11/2024 per Policy and Planning teamContact: Policy and Planning team

Streets data includes: Arterial Classification, Street Names, Block Number, Direction, One-way, Surface Width, Surface Type, Pavement Condition, Speed Limit, Percent Slope. From the Hansen Asset Management System:The linework is from the SND(Street Network Database) which can be found at our open data site - https://data-seattlecitygis.opendata.arcgis.com/datasets/street-network-database-snd. | Attribute Information: https://www.seattle.gov/Documents/Departments/SDOT/GIS/Seattle_Streets_OD.pdf | Update Cycle: Weekly| Contact Email: DOT_IT_GIS@seattle.gov--- Common SDOT queries and data downloads | Arterial Classification: of Seattle StreetsARTCLASS IN(1,2,3,4)| Transit Classification: of Seattle StreetsTRANCLASS IN(1,2,3,4,5,6)

Urban heat islands are small areas where temperatures are unnaturally high - usually due to dense buildings, expansive hard surfaces, or a lack of tree cover or greenspace. People living in these communities are exposed to more dangerous conditions, especially as daytime high and nighttime low temperatures increase over time. NOAA Climate Program Office and CAPA Strategies have partnered with cities around the United States to map urban heat islands. Using Sentinel-2 satellite thermal data along with on-the-ground sensors, air temperature and heat indexes are calculated for morning, afternoon, and evening time periods. The NOAA Visualization Lab, part of the NOAA Satellite and Information Service, has made the original heat mapping data available as dynamic image services.Dataset SummaryPhenomenon Mapped: Sensing package time step valuesUnits: decimal degrees Cell Size: 30 metersPixel Type: 32 bit floating pointData Coordinate Systems: WGS84 Mosaic Projection: WGS84 Extent: cities within the United StatesSource: NOAA and CAPA StrategiesPublication Date: September 20, 2021What can you do with this layer?This imagery layer supports communities' UHI spatial analysis and mapping capabilities. The symbology can be manually changed, or a processing template applied to the layer will provide a custom rendering. Each city can be queried.Cities IncludedBaltimore, Boise, Boston, Fort Lauderdale, Honolulu, Los Angeles, Nampa, Oakland-Berkeley, Portland, Richmond, Sacramento, San Bernardino, San Juan, Victorville, Washington, West Palm Beach, Worcester, Charleston and YonkersCities may apply to be a part of the Heat Watch program through the CAPA Strategies website. Attribute Table Informationcity_name: Seattle, WAMorning air temperatures in cities