- API data.seattle.gov | Last Updated 2016-08-29T03:27:28.000Z
- API data.seattle.gov | Last Updated 2016-08-29T05:22:32.000Z
The City of Seattle implements biennial budgeting through the sequential adoption of two one-year budgets. When adopting the budget for the first year of the biennium, the Council endorses a budget for the second year. The Endorsed Budget is the basis for a Proposed Budget for the second year of the biennium, and is reviewed and adopted in the fall of the first year of the biennium. This data reflects all appropriations (by budget control level) included in the 2014 Endorsed Budget.
- API data.seattle.gov | Last Updated 2016-09-09T22:44:33.000Z
Families & Education Levy III Projected Expenditures for seven-year levy (Original Plan) 7-year levy (2nd half of 2005 through 1st half of 2012) Levy programs increase 1 1/2%/year once program is fully ramped up Levy admin is capped at 5%/year Crossing Guard program expires mid-2008
- API data.seattle.gov | Last Updated 2019-12-14T17:10:03.000Z
All code compliance complaints and violations that SDCI is reviewing and processing.
- API data.seattle.gov | Last Updated 2019-08-12T15:35:47.000Z
City of Seattle Business License data current as of January 9, 2017
- API data.seattle.gov | Last Updated 2019-05-15T21:18:34.000Z
Excel version of Attachment A to Ordinance 123177, the Budget Adoption Ordinance for 2010.
- API data.seattle.gov | Last Updated 2019-05-15T21:16:14.000Z
Excel version of the data included in Attachment A to the Budget Adoption Ordinance. This data reflects all appropriations (by budget control level) included in the 2011-2012 Proposed Budget.
- API data.seattle.gov | Last Updated 2019-05-15T21:15:04.000Z
This data comes directly from Attachment A to the 2012 Budget Adoption Ordinance. This data reflects all appropriations (by budget control level) included in the 2012 Proposed Budget.
- API data.seattle.gov | Last Updated 2019-12-11T20:00:03.000Z
A forward facing schedule of City of Seattle datasets that have been identified as target open datasets for publication on data.seattle.gov. We do not guarantee that any datasets identified in this list will ultimately be published.
- API data.seattle.gov | Last Updated 2019-12-14T07:36:24.000Z
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.