A Development Site (DV), referenced using a Development Site Number, is a property boundary that the Seattle Department of Construction and Inspections (SDCI) uses to apply code standards. A Development Site may overlap with one or more King County tax parcels.Source Data: DPD.DevsitesDefinition Query: Where DEVSITE STATUS IN ('ACTIVE', 'PRESUMED', 'UPDATE') And DEVSITE ID does not begin with 'UN' And DEVSITE ID does not begin with 'WB' And SEATTLE is not equal to 0Symbology Category Expression: var disp_txt = $feature["PRCLID"]; if (Find("RW", disp_txt, 0)>-1) { return "Right-of-Way"; } else { return "Non-Right-of-Way"; }Refresh: Daily
Displacement risk indicator showing the number of new residential units through building construction permits filed with the Seattle Department of Construction and Inspections (SDCI). Summarized at the census tract level; summarized based on the year the permit was issued.
Displacement risk indicator showing the number of Early Design Guidance building permits filed with the Seattle Department of Construction and Inspections (SDCI) summarized at the census tract level; available for every year from 2006 through the most recent year of available data.
How were URMs in this database identified? SDCI compiled an inventory of URM buildings from various visual and permit research surveys performed over the years. This inventory was validated by reviewing photographs of the buildings, visiting selected buildings to view the exterior construction details, and reviewing permit records and other documents, to verify each building should be included. The 2016 Report to Policy Committee on URM List Validation provides a detailed description of the data validation process. Are all of Seattle’s URMs included in this database? This URM database is intended to be a comprehensive inventory of URM buildings in Seattle. There may be URM buildings that were not identified during the City’s inventory process; if a building is found to contain URM load bearing walls and is not included in the inventory, it will be classified as a URM and subject to future mandatory retrofit requirements. How often is this database updated? The URM database is maintained regularly by staff, and updates are pushed to this dataset weekly. How does the City recognize URM buildings as retrofitted? A URM building owner must provide the required documentation and follow submittal procedures to demonstrate compliance with Seattle Existing Building Code section 304.5.1. This code section establishes a minimum standard for a URM to be recognized as retrofitted. Once SDCI approves this documentation, the building’s status in the “Confirmed Compliant Retrofit” column will be updated to “Yes”. An adjacent column, “Retrofit Method per SEBC 304.5.1”, will be updated to reflect the appropriate level of completed retrofit. See page 3 for further description of columns and field values. When will URM retrofits be required? Owners can undertake a voluntary retrofit at any time. Owners must retrofit URM building parapets (any wall that continues vertically past the roofline) when they are doing other permitted construction work in the building. (Per Seattle Existing Building Code 302.9 and A113.6.) The SEBC currently requires that buildings be seismically retrofitted if owners are conducting a major renovation, occupying a vacant building, or changing the use or occupancy of the building. Future mandatory requirements: The City will not require a mandatory retrofit until financial and supportive resources have been clearly identified. The City passed Resolution 32033 in 2021 guiding the development of a Seattle mandatory URM retrofit program. The resolution recommends a variety of potential funding opportunities and f
The updated FTN has two primary components: it establishes aspirational frequency targets alongside a transit corridor map illustrating how frequency targets are proposed to be distributed throughout the city. Transit corridors that are part of the updated FTN are classified into three categories: Frequent: Better than 10 minutes. 6-minute to 10-minute service from 6 AM–7 PM, 10-minute to 15-minute service from 7PM to midnight, and 30-minute service from midnight to 6AM, every day. This category captures a vision that the best transit service is even more frequent than 10-minutes and that SDOT is willing to invest in certain Metro RapidRide lines and other very high frequency routes. Frequent 10 minutes. 10-minute service from 6 AM–7 PM, 15-minute service from 7PM to midnight, and 30-minute to 60-minute service from midnight to 6AM, every day. This is a high frequency category for main transit corridors, including some RapidRide corridors. Frequent 15 minutes. 15-minute service from 6 AM–9 PM, 30-minute service from 9PM to midnight, and service as needed between midnight and 6AM, every day. This designation aligns with parking flexibility areas monitored by the Seattle Department of Construction and Inspections (SDCI), in which parking minimums for new housing development are reduced or removed near frequent transit operating at least every 15 minutes.
In Section 11 of the legislation, the Council directed the Seattle Department of Construction and Inspections (SDCI) and Office of Planning and Community Development (OPCD) to report annually for five years on citywide ADU permit activity.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
A Development Site (DV), referenced using a Development Site Number, is a property boundary that the Seattle Department of Construction and Inspections (SDCI) uses to apply code standards. A Development Site may overlap with one or more King County tax parcels.Source Data: DPD.DevsitesDefinition Query: Where DEVSITE STATUS IN ('ACTIVE', 'PRESUMED', 'UPDATE') And DEVSITE ID does not begin with 'UN' And DEVSITE ID does not begin with 'WB' And SEATTLE is not equal to 0Symbology Category Expression: var disp_txt = $feature["PRCLID"]; if (Find("RW", disp_txt, 0)>-1) { return "Right-of-Way"; } else { return "Non-Right-of-Way"; }Refresh: Daily