AndreaBozzo/ceres-open-data-index huggingface dataset:
SDOT Drawbridge Status

SDOT manages several drawbridges/movable bridges in the City. Their status is monitored automatically and recorded in this table. Please note this data is not checked before publishing and may contain errors or omissions. For example, sometimes a bridge must be moved a few times to get it fully settled and that may show in the data as multiple openings/closings, when in reality it was one bridge event. The sensors may fail and a bridge will still open/close and not be recorded in this dataset.
Office of Police Accountability Complaints

This dataset represents complaints against employees of the Seattle Police Department (SPD). The data is pulled from dynamic, live databases and is subject to change. Each row represents an individual allegation of misconduct from a Complainant against an individual SPD employee. A single OPA case may contain one or more Complainant(s), Named Employee(s), and Allegation(s) against each Named Employee. Data is denormalized to represent the one-to-many relationship between the Complaint and all the associated allegations. **USE CAUTION WHEN COUNTING**
Landsburg Fish Ladder Annual Salmon Counts

The Landsburg Fish Ladder was constructed in 2003 at the Landsburg Diversion Dam at River Mile 23 on the Cedar River. Data includes annual (Return Year) salmon counts by species as well as by sex and adipose fin status, where known. Fish counts are obtained either through manual sorting (Sorted) or by analyzing fish camera videos (Fish Camera). Data are collected as part of the Habitat Conservation Plan and Landsburg Mitigation Agreement. Methods and data summaries are available in the Fish Ladder Annual Reports (SPU). Most recent Annual Report can be found here: https://archives.seattle.gov/digital-collections/index.php/Detail/objects/278289 Past Annual Reports: https://archives.seattle.gov/digital-collections/index.php/Detail/collections/2593 For more information visit: https://www.seattle.gov/utilities/protecting-our-environment/our-water-sources/habitat-conservation-plan/fish/landsburg-fish-passage
Integrated Library System (ILS) Data Dictionary

Lookup table of Horizon item and borrower codes. The source of this data are the code definition tables in Horizon, such as bstat, btype, collection, and itype. This dataset is useful for understanding the codes used in some of Seattle Public Library's other open datasets. These codes (namely "ItemType" and "ItemCollection") are systematically used in the cataloging of items within Integrated Library System (ILS), Horizon (Sirsidynix).
Fremont Bridge - Combined Bicycle and Scooter Counter

The Fremont Bridge Bicycle Counter began operation in October 2012 and records the number of bikes that cross the bridge using the pedestrian/bicycle pathways. Inductive loops on the east and west pathways count the passing of bicycles regardless of travel direction. The data consists of a date/time field: Date, east pathway count field: Fremont Bridge NB, and west pathway count field: Fremont Bridge SB. The count fields represent the total bicycles detected during the specified one hour period. Direction of travel is not specified, but in general most traffic in the Fremont Bridge NB field is travelling northbound and most traffic in the Fremont Bridge SB field is travelling southbound.
Elliott Bay Trail - Combined Pedestrian Bicycle and Scooter Counter

Counting hardware was replaced summer 2024. These sensors counts both people riding bikes and pedestrians. Separate volumes are tallied for each travel mode. Wires in a diamond formation in the concrete detect bikes and an infrared sensor mounted on a wooden post detects pedestrians. The counters also capture the direction of travel for both bikes and pedestrians. The temporary counter data from 5/10/2013 to 12/11/2013 have been combined to this data set which counted only bikes and not pedestrians.
SPU Solid Waste Tons and Trips Data

SPU Solid Waste Tons and Trips provides daily collection tonnages from the residential sector that are collected by contracted haulers. The data provides a full accounting of residential garbage, recycling, organics curbside collections. Commercial, self-haul and C&D are not included. Data from private transfer stations is not included. For more information see [https://www.seattle.gov/utilities/about/plans/solid-waste/about-solid-waste].
COBAN Logs

Note: The dataset is no longer being updated as the COBAN video system is no longer in use, and it will be removed from data.seattle.gov on 12/31/2023. This dataset includes Police In-Car video activities. Data shows activity of In-Car recorded video including, Officer Serial Number, Start (Date & Time) of video, post recording activity code and description. Data is refreshed on a weekly basis. Data is records of video and does not imply that there is actual playable video associated.
Chief Sealth Trail North of Thistle Bicycle Counter (Out of Service)

Due to hardware issues, this counter is no longer in service. Counts are conducted using tubes on a quarterly basis. Previous counter counted both people riding bikes and pedestrians. Separate volumes are tallied for each travel mode. Wires in a diamond formation in the concrete detect bikes and an infrared sensor mounted on a wooden post detects pedestrians. The counters also capture the direction of travel for both bikes and pedestrians.
Checkouts By Title (Physical Items)

This dataset includes a log of all physical item checkouts from Seattle Public Library. The dataset begins with checkouts that occurring in April 2005. Data from 2005 to 2016 in this dataset is from digital artwork "Making Visible the Invisible" by studios of George Legrady. [Learn more] about this contribution. Renewals are not included. Have a question about this data? Ask us! Data Notes: There is a machine-readable data dictionary available to help you understand the collection and item codes. Access from here: https://data.seattle.gov/Community/Integrated-Library-System-ILS-Data-Dictionary/pbt3-ytbc Also: 1. "CheckoutDateTime" (the timestamp field) is rounded to the nearest minute. 2. "itemType" is a code from the catalog record that describes the type of item. Some of the more common codes are: acbk (adult book), acdvd (adult DVD), jcbk (children's book), accd (adult CD) 3. "Collection" is a collection code from the catalog record which describes the item. Here are some common examples: nanf (adult non-fiction), nafic(adult fiction), ncpic(children's picture book), nycomic (Young adult comic books). 4. "Subjects" includes the subjects and subject subdivisions from the item record.
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: 1) 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. 2) 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. 3) 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.
Building Energy Benchmarking Data, 2015-Present

Seattle’s Building Energy Benchmarking Program (SMC 22.920) requires owners of non-residential and multifamily buildings (Greater than 20,000 square feet) to track energy performance and annually report to the City of Seattle. Annual benchmarking, reporting, and disclosing of building performance are foundational elements of creating more market value for energy efficiency. Per Ordinance (125000), starting with 2015 energy use performance reporting, the City of Seattle is making the data for all buildings greater than 20,000 SF available annually. This dataset contains benchmarking records for all buildings required to report for years 2015-2024. If you have questions or comments on the data, email us at energybenchmarking@seattle.gov and include Open Data in the subject line.
Bridging The Gap Accomplishments 2007 to 2011

In 2006, Seattle voters passed a nine-year, $365 million levy for transportation maintenance and improvements known as Bridging the Gap. The levy is complemented by a commercial parking tax. The levy funds programs to address the maintenance backlog for paving; sidewalk development and repairs; bridge repair, rehabilitation and seismic upgrades; tree pruning and planting; transit enhancements; and other much needed maintenance work. Funding also supports projects that implement the Bicycle and Pedestrian Master plans, create a Safe Routes to School Program, improve transit connections and help neighborhoods get larger projects built through the Neighborhood Street Fund large project program.
Annual Parking Study Data

Manual parking study details from citywide paid parking study, presented by blockface and date/hour of study. Most data is from spring of each year, with some data sets including summer studies. Study time periods: • 2014 • 2015 • 2016 • 2017 • 2018 • 2019 Purpose: To determine hourly parking occupancy for most paid blockfaces in Seattle Note: In the column descriptions below, a street segment is typically defined as a drivable public street, or as a public walkway or trail, within Seattle city limits. A blockface is defined as one side of a block between road intersections, and often features a sidewalk.
2013 Technology Access and Adoption Survey

Before using this data set, refer to instructions below! Since 2000, the City's Information Technology Indicators project has been collecting extensive and statistically valid data on residential use of cable tv, broadband adoption and uses (including health, work, education, finance and civic engagement), barriers to broadband adoption, and customer service needs. This project is managed by our Community Technology Program with technical advice from our Citizens Telecommunications and Technology Advisory Board (CTTAB). INSTRUCTIONS FOR USING DATA SET Do not pull down the data set and use it without using the code book. When you run the data set, be sure to refer to the Code Book for invalid or missing values for each question item (variables). You must recognize that the data here is unweighted; to replicate the figures in the City’s Information Technology Access and Adoption Report and get values that are representative of Seattle population, you should use the weights. There are 2 weighting variables, one that allows you to use the phone and online survey together (labeled "weightfin") and one that is for only the phone survey (labeled "wgtphoneonly", which excludes or zeros out everyone in the online survey).
Sockeye Fry Condition

The size and condition of Cedar River sockeye fry has been collected most years since 2006 as part of the Cedar River Sockeye Program. Fry from both the Cedar River Hatchery operations and fry produced from adults spawning naturally in the Cedar River are measured by Washington Department of Fish and Wildlife. Data are collected as part of the Habitat Conservation Plan and Landsburg Mitigation Agreement. Methods and data summaries are available in the Hatchery Annual Reports (WDFW) and Fry Production Annual Reports (WDFW).
Sockeye Broodstock Weir Operations - Cedar River

Since 2008 adult Cedar River sockeye have been collected at a broodstock collection weir that is temporarily installed each fall in the lower Cedar River (Renton, WA). Adult sockeye collected at the weir are trucked to the Cedar River Sockeye Hatchery as part of the Landsburg Mitigation Agreement. The weir is operated by the Washington Department of Fish and Wildlife. This operations dataset includes the daily number of hours the weir was fishing, and tip-gate and/or panel configuration hours. Methods and data summaries are available in the Hatchery Annual Reports (WDFW). A metadata file includes links to reports, protocols, and attribute information.
Short Term Rental License

Short-term rentals are a type of lodging sometimes called vacation rentals. A house, condo, or apartment (or a part of one) that is rented for a fee for fewer than 30 consecutive nights is a short-term rental. Short-term rental operators are required to obtain an operator license & register each rental unit on that license. This dataset lists all Short-Term Rental operator licenses & their associated units. To learn more about short-term rental regulations in Seattle, please visit: [https://www.seattle.gov/business-regulations/short-term-rentals]
SPD 9-11 Customer Satisfaction Survey Data

Background: “In 2006, the Seattle Police Department began surveying members of the public (customers) who had personal contact with an officer after calling 9-1-1. The surveys have been conducted two to four times a year, and a total of 44 surveys have been conducted to date. These surveys have been designed to assess customers’ experiences and satisfaction with the service provided by the Seattle Police Department, and the results of the surveys have been used to assess service delivery; examine differences between precincts; identify strategies and tactics to achieve specific service objectives; and provide feedback to officers, precinct captains, and watch lieutenants. This report presents the results of the September 2019 customer survey and compares the September 2019 survey results to results from the 13 other surveys conducted since March 2016.” Research Methods. “Similar to the previous surveys, 200 customers who called 9-1-1 and had an officer dispatched to provide assistance were interviewed by telephone for this survey. All of the customers interviewed had called 9-1-1 between August 21 and August 29, 2019, and were randomly selected from lists of 9-1-1 callers who had an officer dispatched to provide assistance, excluding sensitive cases such as domestic violence calls. The interviews were completed between September 3 and September 10, 2019. The interviews were approximately 10 to 12 minutes long. The questionnaire used in the interviews was developed with Department input and approval. During the course of this research, some questions have been added to or deleted from the survey questionnaire to reflect the changing information needs of the Department. However, questions about customers’ overall satisfaction with their experience with the Department after calling 9-1-1, experiences with and opinions of the officer who first visited after the call to 9-1-1, opinions of the Seattle Police Department overall, and satisfaction with the service provided by the 9-1-1 operator have been included in every survey. Since late 2006 and early 2007, the surveys also included questions about customers’ feelings of safety in Seattle.”
SPD Arrest Data

Under the current business process, every seizure (4th Amendment of the US Constitution) conducted under the evidentiary standard of Probable Cause (PC) is documented in the RMS (Mark43). In addition to physical arrests made by officers, the system is configured to capture warrants, and summons arrests (where the officer is affecting a PC seizure on the authority of someone else (the court) and administrative arrest types that document updates to the identity of the subject who was arrested and additional charges. In total, 12 types of arrest are captured in the source. Note: This data set includes counts of arrest reports written which are distinct from physical, in-custody events. All counts herein reflect either total counts of arrest reports by the selected filter parameters, and/or the total number of reports written per subject.
Terry Stops

Note! Subject Data is temporarily unavailable, while we chase down a bug. Please excuse the inconvenience (DGAL-8). 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.
Public Life Data - Study

Provides details on the different studies that have been conducted, including project information. ------------------------------------------ The City of Seattle Department of Transportation (SDOT) is providing data from the public life studies it has conducted since 2017. These studies consist of measuring the number of people using public space and the types of activities present on select sidewalks across the city, as well as several parks and plazas. The data set is continually updated as SDOT and other parties conduct public life studies using Gehl Institute’s Public Life Data Protocol. This dataset consists of four component spreadsheets and a GeoJSON file, which provide public life data as well as information about the study design and study locations: 1 Public Life Study: provides details on the different studies that have been conducted, including project information. 2 Public Life Location: provides details on the sites selected for each study, including various attributes to allow for comparison across sites. https://data.seattle.gov/Transportation/Public-Life-Data-Locations/fg6z-cn3y 3 Public Life People Moving: provides data on people moving through space, including total number observed, gender breakdown, group size, and age groups. https://data.seattle.gov/Transportation/Public-Life-Data-People-Moving/7rx6-5pgd 4 Public Life People Staying: provides data on people staying still in the space, including total number observed, demographic data, group size, postures, and activities. https://data.seattle.gov/Transportation/Public-Life-Data-People-Staying/5mzj-4rtf 5 Public Life Geography: A GeoJSON file with polygons of every location studied. https://data.seattle.gov/Transportation/Public-Life-Data-Geography/v4q3-5hvp Please download and refer to the Public Life metadata document - in the attachment section below - for comprehensive information about all of the Public Life datasets.
Public Life Data - People Staying

Provides data on people staying still in the space, including total number observed, demographic data, group size, postures, and activities. ------------------------------------------ The City of Seattle Department of Transportation (SDOT) is providing data from the public life studies it has conducted since 2017. These studies consist of measuring the number of people using public space and the types of activities present on select sidewalks across the city, as well as several parks and plazas. The data set is continually updated as SDOT and other parties conduct public life studies using Gehl Institute’s Public Life Data Protocol. This dataset consists of four component spreadsheets and a GeoJSON file, which provide public life data as well as information about the study design and study locations: 1 Public Life Study: provides details on the different studies that have been conducted, including project information. https://data.seattle.gov/Transportation/Public-Life-Data-Study/7qru-sdcp 2 Public Life Location: provides details on the sites selected for each study, including various attributes to allow for comparison across sites. https://data.seattle.gov/Transportation/Public-Life-Data-Locations/fg6z-cn3y 3 Public Life People Moving: provides data on people moving through space, including total number observed, gender breakdown, group size, and age groups. https://data.seattle.gov/Transportation/Public-Life-Data-People-Moving/7rx6-5pgd 4 Public Life People Staying: provides data on people staying still in the space, including total number observed, demographic data, group size, postures, and activities. 5 Public Life Geography: A GeoJSON file with polygons of every location studied. https://data.seattle.gov/Transportation/Public-Life-Data-Geography/v4q3-5hvp Please download and refer to the Public Life metadata document - in the attachment section below - for comprehensive information about all of the Public Life datasets.
Public Life Data - People Moving

Provides data on people moving through space, including total number observed, gender breakdown, group size, and age groups. ------------------------------------------ The City of Seattle Department of Transportation (SDOT) is providing data from the public life studies it has conducted since 2017. These studies consist of measuring the number of people using public space and the types of activities present on select sidewalks across the city, as well as several parks and plazas. The data set is continually updated as SDOT and other parties conduct public life studies using Gehl Institute’s Public Life Data Protocol. This dataset consists of four component spreadsheets and a GeoJSON file, which provide public life data as well as information about the study design and study locations: 1 Public Life Study: provides details on the different studies that have been conducted, including project information. https://data.seattle.gov/Transportation/Public-Life-Data-Study/7qru-sdcp 2 Public Life Location: provides details on the sites selected for each study, including various attributes to allow for comparison across sites. https://data.seattle.gov/Transportation/Public-Life-Data-Locations/fg6z-cn3y 3 Public Life People Moving: provides data on people moving through space, including total number observed, gender breakdown, group size, and age groups. 4 Public Life People Staying: provides data on people staying still in the space, including total number observed, demographic data, group size, postures, and activities. https://data.seattle.gov/Transportation/Public-Life-Data-People-Staying/5mzj-4rtf 5 Public Life Geography: A GeoJSON file with polygons of every location studied. https://data.seattle.gov/Transportation/Public-Life-Data-Geography/v4q3-5hvp Please download and refer to the Public Life metadata document - in the attachment section below - for comprehensive information about all of the Public Life datasets.