- API data.seattle.gov | Last Updated 2019-05-13T05:03:54.000Z
<p>The Street Network Database (SND) is a representation of the physical, land based, improved, travel pathway infrastructure and associated theoretical address ranges. The pathway representation consists of Segments and Intersection elements. A Segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A Segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. </p>
- API data.seattle.gov | Last Updated 2019-06-28T16:54:24.000Z
Wage and classification information of City of Seattle Employees as of February 2017. Exclusions may apply for vulnerable populations.
- 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-06-25T21:29:03.000Z
This dataset lists wheelchair accessible taxicab (WAT) owners who received reimbursements from the Wheelchair Accessible Services Fund for maintenance and equipment costs incurred between January 1 and December 30, 2016. Owners were reimbursed for expenses related to ramps, axles, brakes, transmissions and similar items up to $3,500 from the City of Seattle and up to $1,500 from King County.
- API data.seattle.gov | Last Updated 2019-05-15T21:17:09.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 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 2019-04-19T05:06:49.000Z
<p>Seattle is divided into five geographic areas. Within those areas are the 5 precincts or police stations: North, East, South, West and Southwest. Precinct boundaries were determined through consideration of neighborhood boundaries, geographic and other natural boundaries.</p> <p>Each precinct contains smaller geographic areas called Sectors. There are 17 sectors total in the city.</p> <p>Each of these Sectors are divided into between 3 smaller sections called Beats (i.e. Ocean sector has three beats O1, O2, O3) These are the areas that individual patrol officers are assigned responsibility for.</p>
- API data.seattle.gov | Last Updated 2019-07-12T15:51:39.000Z
All code compliance complaints and violations that SDCI is reviewing and processing.
- API data.seattle.gov | Last Updated 2019-07-12T19:29:38.000Z
All trade permits in progress or that have been issued in Seattle.
- API data.seattle.gov | Last Updated 2019-07-15T06:30:13.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.