AndreaBozzo/ceres-open-data-index huggingface dataset:
Opportunity Zones

<span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Investors are able to defer paying taxes on capital gains that are invested in Qualified Opportunity Funds that in turn are invested in distressed communities designated as Opportunity Zones by the governor of each state. Census tracts 86, 87, 90, 91, 92, 93, 94, 110.01, 111.01 and 118 have been designated by the Washington State Department of Commerce as Opportunity Zones. This layer dissolves the aforementioned Census Tracts.</span>

Tags: census, city-of-seattle, community, development, gis, sdci, seattle-gis-open-data
Organization: City of Seattle
Building Outlines 2015

<span style='font-family:&quot;Segoe UI&quot;, Arial, sans-serif; background-color:rgb(255, 255, 255);'><font size='3'>Building roof outlines based on 2015 imagery. Update Areas of Change (AoC) identified from 2015 imagery, AoCs reviewed &amp; accepted by Seattle Public Utilities. Update feature collection done in stereo with 2015 imagery. Original 2012 data removed from identified AoCs, newly collected 2015 data merged back into dataset. All data within 2015 AoCs is given an attribute of &quot;2015&quot; in the &quot;YearUpdated&quot; attribute field. Attribution includes updated building structures apex roof heights.</font></span><div><span style='font-family:&quot;Segoe UI&quot;, Arial, sans-serif; background-color:rgb(255, 255, 255);'><font size='3'><br /></font></span></div><div><span style='background-color:rgb(255, 255, 255);'><font size='3'>Displays data from CGDB.BLDG2015_PLGN. </font></span></div><div><br /><table border='0' cellpadding='0' cellspacing='0' style='border-collapse:collapse; width:183pt;' width='244'><tbody><tr height='20' style='height:15.0pt;'>
  <td height='20' style='height:15.0pt; width:86pt;' width='115'>BP99_TYPE_CODE</td>
  <td style='width:97pt;' width='129'>DESCRIPTION</td>
 </tr>
 <tr height='20' style='height:15.0pt;'>
  <td height='20' style='height:15.0pt;'>BLD</td>
  <td>Building</td>
 </tr>
 <tr height='20' style='height:15.0pt;'>
  <td height='20' style='height:15.0pt;'>DEK</td>
  <td>Deck</td>
 </tr>
 <tr height='20' style='height:15.0pt;'>
  <td height='20' style='height:15.0pt;'>GAR</td>
  <td>Garage</td>
 </tr>
 <tr height='20' style='height:15.0pt;'>
  <td height='20' style='height:15.0pt;'>MSC</td>
  <td>Miscellaneous</td>
 </tr>
 <tr height='20' style='height:15.0pt;'>
  <td height='20' style='height:15.0pt;'>OBS</td>
  <td>Obscured</td>
 </tr>
 <tr height='20' style='height:15.0pt;'>
  <td height='20' style='height:15.0pt;'>PAT</td>
  <td>Patio</td>
 </tr>
 <tr height='20' style='height:15.0pt;'>
  <td height='20' style='height:15.0pt;'>UNK</td>
  <td>Unknown</td>
 </tr>
 <tr height='20' style='height:15.0pt;'>
  <td height='20' style='height:15.0pt;'>U_C</td>
  <td>Under Construction</td>
 </tr></tbody></table></div><div><span style='background-color:rgb(255, 255, 255);'><font size='3'><br /></font></span></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Static data layer, no updates.</span><br /></div>

Tags: apex, building, gis, outlines, roof, seattle-gis-open-data
Organization: City of Seattle
SPU DWW Mainline Points

<span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>SPU DWW Mainline Points is a Group Layer containing all Lifecycles, Ownerships, and other variations of Drainage and Wastewater Mainlines Points.</span><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Proposed Mainline End Points are planned but not yet installed or as-built.</div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>SPU DWW Aba Rem Mainline End Points refers to Abandoned and Removed Mainline End Points.</div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Force Mainline End Points are Mainline End Points under pressure. Detention Lines and Polygons refer to Mainline End Points for Detention Infrastructure.</div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>DWW Mainline Connection Points Wyes refer to side sewer and lateral connection points on mainlines.</div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>The data is refreshed weekly and is maintained by the SPU GIS Data Maintenance Team. </div>

Tags: dww, endpoints, external, mainline, points, seattle-gis-open-data, sewer, spu
Organization: City of Seattle
Bike Plus Network

<div>The Bicycle and E-Mobility Element of the STP will help create a safer, more bikeable Seattle. It provides a foundation for the City of Seattle to grow our investment in bicycling and e-mobility to achieve STP goals. The STP and the Bicycle and E-Mobility Element build on and supersede the 2014 Bicycle Master Plan (BMP). The bicycle and e-mobility network serves not only people riding traditional bicycles, but also people using adaptive bikes, cargo bicycles for both personal use and deliveries, trikes, scooters, skateboards, roller skates, wheelchairs or other wheeled mobility devices, and “e-mobility” devices, which refers to personal and shared electric-powered bicycles, scooters, and other electric-powered devices. It serves people bicycling and taking e-mobility to serve a variety of trip purposes, such as getting to work, school, transit, the gym or doctor's office, recreating, making urban goods deliveries, and more.</div><div><br /></div><div>The Bike+ network consists of bikeways suitable for people of all ages and abilities (AAA), including protected bike lanes, Neighborhood Greenways, Healthy Streets, and bike lanes where vehicle speeds and volumes are sufficiently low.  </div><div><br /></div><div>The Bike+ network is envisioned to seamlessly integrate with the multi-use trail network, which provides connections through or on the edges of parks and opens spaces, where an off-street connection is preferred, or is more feasible than an on-street connection.  </div><div><br /></div><div>Diagram of an umbrella titled &quot;What is Bike+?&quot; Underneath the umbrella, the following are bulleted - protected bike lane, bike lane (if vehicle speed and volumes low. See Table 4), neighborhood greenway, and healthy street.  Many planned projects from the 2014 BMP have been implemented and are shown on the existing bicycle and e-mobility network map. The Bike+ network shows existing and proposed AAA bikeways on Seattle’s arterial and non-arterial (i.e., neighborhood streets) networks.</div><div><br /></div><div>Refresh Cycle: None, Static. Manually as required.</div><div><ul><li>Original Publish: 5/23/2024</li><li>Update Publish: 7/11/2024 per Policy and Planning team</li></ul></div><div>Contact: Policy and Planning team</div>

Tags: aaa-network, bicycle, bicycle-element, bike, e-mobility, gis, sdot, seattle-gis-open-data, seattle-transportation-plan, stp
Organization: City of Seattle
Seattle Police Department Beats 2015 - 2017 (Web Mercator)

The Seattle Police Department has different iterations of police beats as the city's needs evolved.  This layer represents what the beats looked like from 2015 to 2017.  <div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>This layer was published in the WGS 1984 Web Mercator Auxiliary Sphere coordinate system.</span></div>

Tags: beats, police, seattle-gis-open-data, seattle-police, spd, web-mercator, wm
Organization: City of Seattle
2010 Census Block Seattle - Housing Statistics

<i>Data from:  </i><i><a href='http://www.seattle.gov/opcd/population-and-demographics/decennial-census#2010' target='_blank'>2010 Decennial Census</a></i><div><br /></div><div>Decennial housing data for Census Blocks in the City of Seattle.</div>

Tags: blocks, census, dc2010, demographics, gis, housing, planning, seattle-gis-open-data
Organization: City of Seattle
Enhanced Street Crossings

<div><div>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.</div><div><br /></div><div>The process is based on an analysis of factors related to the STP’s goals of safety, equity, sustainability, mobility &amp; economic vitality, livability, and maintenance &amp; modernization. This data-driven prioritization framework helps the city provide targeted improvements that reflect community priorities, City policy objectives, and current data.  </div><div><br /></div><div>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.  </div><div><br /></div><div>Refresh Cycle: None, Static. Manually as required.</div><div><ul><li>Original Publish: 5/23/2024</li><li>Update Publish: 7/11/2024 per Policy and Planning team</li></ul></div><div>Contact: Policy and Planning team</div></div><div><br /></div>

Tags: gis, pedestrian, pedestrian-element, policy-and-planning, sdot, seattle-gis-open-data, seattle-transportation-plan, stp
Organization: City of Seattle
Seattle Tree Canopy 2016 2021 Block Groups

<p>This data layer references data from a high-resolution tree canopy change-detection layer for Seattle, Washington. Tree canopy change was mapped by using remotely sensed data from two time periods (2016 and 2021). Tree canopy was assigned to three classes: 1) no change, 2) gain, and 3) loss. No change represents tree canopy that remained the same from one time period to the next. Gain represents tree canopy that increased or was newly added, from one time period to the next. Loss represents the tree canopy that was removed from one time period to the next. Mapping was carried out using an approach that integrated automated feature extraction with manual edits. Care was taken to ensure that changes to the tree canopy were due to actual change in the land cover as opposed to differences in the remotely sensed data stemming from lighting conditions or image parallax. Direct comparison was possible because land-cover maps from both time periods were created using object-based image analysis (OBIA) and included similar source datasets (LiDAR-derived surface models, multispectral imagery, and thematic GIS inputs). OBIA systems work by grouping pixels into meaningful objects based on their spectral and spatial properties, while taking into account boundaries imposed by existing vector datasets. Within the OBIA environment a rule-based expert system was designed to effectively mimic the process of manual image analysis by incorporating the elements of image interpretation (color/tone, texture, pattern, location, size, and shape) into the classification process. A series of morphological procedures were employed to ensure that the end product is both accurate and cartographically pleasing. No accuracy assessment was conducted, but the dataset was subjected to manual review and correction.</p><p>University of Vermont Spatial Analysis Laboratory in collaboration with City of Seattle.<br /></p><p>This dataset consists of City of Seattle Block Groups areas which cover the following tree canopy categories: </p><p></p><ul><li>Existing tree canopy percent </li><li>Possible tree canopy - vegetation percent </li><li>Relative percent change </li><li>Absolute percent change</li></ul><div style='font-family:inherit;'><div style='font-family:inherit;'>For more information, please see the <a href='https://seattle.gov/documents/Departments/OSE/Urban%20Forestry/2021%20Tree%20Canopy%20Assessment%20Report_FINAL_230227.pdf' style='color:rgb(0, 97, 155); text-decoration-line:none; font-family:inherit;' target='_blank' rel='nofollow ugc noopener noreferrer'>2021 Tree Canopy Assessment</a>.</div></div><div style='font-family:inherit;'><br /></div>

Tags: 2016, 2021, biota, block-groups, environment, land-cover, seattle, seattle-gis-open-data, seattle-office-of-sustainability-environment, tree-canopy
Organization: City of Seattle
Environmentally Critical Area Overlay for Zoned Development Capacity Model Current

Environmentally critical area layer used as an overlay for the City of Seattle Zone Development Capacity Model.  Areas represent the ECAs that would reduce the amount of development on a development site.  This layer is for analytical purposes only and does not represent actual regulatory areas or development regulation, rather an approximation of the potential impact on a development site.<div><br /></div><div>These areas include:</div><div><br /></div><div><u>Steep Slopes (40% or greater)</u></div><div><p style='margin-bottom:0in;'></p><ul><li>Remove all steep slope polygons less than 1,000 square feet in size </li></ul> For remaining steep slope polygons:</div><div><ul><li>Treat areas within steep slope ECAs as if only 30% is developable. For example, on a 10,000 square foot site where half is in a steep slope ECA, we would treat it like at 6,500 square foot site (5,000*100% + 5,000*30%)</li></ul><p></p><p style='margin-bottom:0in;'><u>Riparian Corridors</u></p><p style='margin-bottom:0in;'></p><ul><li>Ignore riparian corridors where the creek is in a culvert</li></ul><p></p><p style='margin-bottom:0in;'>For other riparian corridors:</p><p style='margin-bottom:0in;'></p><ul><li>Assume there will be no development in that riparian corridor and a buffer of 50 feet for streams without salmon and 75 feet for streams with salmon</li><li>Assume 30% of regular development potential in remainder of a 100 feet buffer from the riparian corridor (i.e. the next 50 feet for streams without salmon and the next 25 feet for streams with salmon).</li></ul><p style='margin-bottom:0in;'><u>Wetlands</u></p><p style='margin-bottom:0in;'></p><ul><li>Remove all wetlands polygons less than 1,000 square feet in size</li></ul><p></p><p style='margin-bottom:0in;'>For all other wetland polygons:</p><p style='margin-bottom:0in;'></p><ul><li>For all wetland polygons greater than or equal to an acre, put a 200 foot buffer around them and assume no development will occur in the wetland or the buffer</li><li>For all wetlands less than an acre, put an 80 foot buffer around them and assume no development in wetland or buffer.  Wetlands other than category I have a variety of buffers, but in general we see about half have 50 foot buffers and the other half have 110 foot buffers (with an average of 80 feet)</li></ul></div><div><a href='https://seattlecitygis.maps.arcgis.com/sharing/rest/content/items/0d3d0d928e4c41ff8f1a439ccb2d1b0c/data' target='_blank' rel='nofollow ugc noopener noreferrer'>Supporting Documentation</a></div>

Tags: buildable-lands, capacity-model-current, development-capacity, eca, gis, plannng, seattle-gis-open-data, zoned-capacity
Organization: City of Seattle
SPU DWW Catch Basins, Inlets, Junction Boxes, Sandboxes and Trash Racks

<span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>This layer displays all the catch basins, catch basin grated tops, sandboxes, junction boxes, inlets and trash racks within the City of Seattle (and the former service area north of the City limits) regardless of ownership.</span><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>A catch basin is a connector to the storm drain system that typically includes an inlet where stormwater enters the catch basin and a sump to capture sediment, debris, and associated pollutants prior to the surface water flowing into a storm or sewer pipe. There are two main types of inlets: side inlets and grated inlets.  Side inlets are located adjacent to the curb and rely on the ability of the opening under the curb to capture flow. Grated inlets have gratings or metal grids to prevent large objects and debris from falling into the combined sewer or drainage system.  They collect surface runoff for conveyance in a pipe system. Sandboxes have wooden lids and are filled with sand or gravel and drain directly into the ground or to a culvert as part of the informal drainage system. Sandboxes are no longer being installed. Junction boxes are cement structure with a grated metal lid, shallow in depth, generally connect culverts and are inline as part of the informal ditch and culvert system.  Trash racks are grated structures that collect debris. Trash racks may be on maintenance holes, catch basins, other structures, or streams.</span><br /></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Data source is DWW.catch_basin_pt_pv, and DWW.APPURTENANCE_PT_PV. Maintained by SPU GIS DWW Data Maintenance staff. This layer does not display when zoomed out beyond 1:899.</span></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></span></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Refreshed daily.</span></div>

Tags: appurtenance-point, catch-basin, catch-basin-grated-top, cb, cbl, inl, inlet, jb, jbs, junction-box, junction-box-with-sump, sandbox, sb, seattle-gis-open-data, trash-racks, trr
Organization: City of Seattle
SPU DWW Sub-Basins

<div style='text-align:Left; font-size:12pt;'><p><span><span>The polygons are intended for use by the City of Seattle as planning-level tool for a preliminary understanding of the drainage patterns in particular areas of the City.  The layer is not complete and does not reflect any City determination about how specific locations should be characterized.  The data source is DWW.sub_basin_plgn_pv.  Labels are based on the attribute ID.  Layer does not display when zoomed out beyond 1:50,000.  </span></span></p></div>

Tags: dww, polygon, public-utility, seattle-gis-open-data, sub-basin
Organization: City of Seattle
MIO MPC Zones

<div style='text-align:left;'><p><span style='font-size:12pt;'>These layers are used as part of the City of Seattle Zoned Development Capacity Model </span><span style='font-size:16px;'>2016. Includes all input and output layers.</span><span style='font-size:12pt;'>.</span></p><p style='font-size:12pt;'><span></span></p><p style='font-size:12pt;'><span>To estimate potential development, the City of Seattle maintains a zoned development capacity model that compares existing development to an estimate of what could be built under current zoning. </span></p><p style='font-size:12pt;'><span></span></p><p style='font-size:12pt;'><span>The difference between existing and potential development yields the capacity for new residential and commercial development.</span></p><p style='font-size:12pt;'><span></span></p><p style='font-size:12pt;'><span>There is a </span><a href='https://www.seattle.gov/dpd/cs/groups/pan/@pan/documents/web_informational/p2182731.pdf' target='_blank' rel='nofollow ugc noopener noreferrer'>report</a><span> of summary findings available as part of Seattle 2035 as well as </span><a href='https://www.seattle.gov/opcd/population-and-demographics/zoned-development-capacity' target='_blank' rel='nofollow ugc noopener noreferrer'>resources</a><span> for reports, methodologies and data.</span></p><p style='font-size:12pt;'><span style='font-size:15px;'>When downloading the data, please select a layer and then &quot;GDB Download&quot; under &quot;Additional Resources&quot; to preserve long field names.  The associated file geodatabase contains all the feature classes for the 10 layers represented.<br /></span><span><br /></span></p></div>

Tags: buildable-lands, capacity, capacity-model-2016, devcapapp, development, gis, planning, seattle-gis-open-data, zoned-capacity, zoning
Organization: City of Seattle
Mandatory Housing Affordability (MHA) Fee Areas

<p><span style='font-size:16px;'>Note:  This map is not an official zoning map.  For precise zoning information, please call or visit the Seattle Municipal Tower, </span><a href='https://www.seattle.gov/sdci/about-us' rel='nofollow ugc' style='font-size:12pt;' target='_blank'>Seattle Department of Construction and Inspections</a><br /></p><p>For properties subject to Mandatory Housing Affordability, the fee areas map specifies the locational dimension of the MHA requirement.  </p><p>Mandatory Housing Affordability requires new development to contribute to affordable housing by including affordable housing in the development or making a payment to the City’s Office of Housing to support affordable housing. The amount of the MHA contribution varies based on a property’s location and other factors specified in Seattle Municipal Code Chapters 23.58B and 23.58C.  For properties subject to MHA, the fee areas map specifies the locational dimension of the MHA requirement.  MHA amounts in Downtown and South Lake Union have specific requirement levels for each zone as listed in SMC 23.58B and 23.58C. For other areas, the relative high, medium or low aspect of the MHA requirement corresponds to market strength area of the city.  </p>

Tags: gis, land-use, mha, planning, sdcizoningmap, seattle-gis-open-data, zoning
Organization: City of Seattle