Link to King County GIS Center Open Data site. Provides access to browse and download from hundreds of enterprise data sets. Includes links to other data sources including legacy FTP Download Portal

A parcel based layer providing an address based on spatial overlay where available, and a range of other property related attributes. To produce PARCEL_ADDRESS_AREA , PARCEL_AREA is spatially joined to ADDRESS_POINT to obtain address attributes, KROLLIDX_AREA to obtain a Kroll page reference, INTRMPAA_AREA to obtain potential annexation area attributes, and PLSS_AREA to obtain section-township-range. It is also joined on PIN to RPACCT_EXTR, PARCEL_EXTR, CONDOCOMPLEX_EXTR, and CONDOUNIT_EXTR to obtain property and assessment related attributes from the KC Assessor office. In many cases multiple addresses are spatially coincident with one parcel, and in those cases only one arbitrarily selected address is used to populate the address attribute information.

Parcel Viewer makes searching for King County parcel information easy. You can search by address, search by parcel number, or you can just zoom in on the map and click on a parcel. Once a parcel is selected, you will get direct links to the King County Assessor’s eReal Property report and the Districts and Development Conditions report.

Countywide datasets are available as zipped Esri geodatabases. Sets of the 5-foot-interval contours at township-level extents are available as zipped shapefiles in addition to geodatabases. (None of the data are available in GeoJSON or KML format.) Note that the zipped files are exceptionally large.All files are compressed in the open-source 7-Zip format (external link to 7-zip.org). Other utilities which can extract zipped files will work in most cases, but some of these data files might extract with 7-Zip only.

King County GIS data is at: https://gis-kingcounty.opendata.arcgis.com/ (new KCGIS Open Data site) OR http://www5.kingcounty.gov/gisdataportal/ (legacy KCGIS data FTP download portal)

This dataset covers bridge structures in unincorporated King County, contract cites, and King County parks.

Analysis of ‘King County Tax Parcel Centroids with select City of Seattle geographic overlays’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/360b2b98-85f4-4a30-ae63-1b047824ef61 on 13 February 2022.

--- Dataset description provided by original source is as follows ---

--- Original source retains full ownership of the source dataset ---

This feature class consists of points describing well locations and is an excerpt from King County GIS data for Group A and Group B community water supply wells downloaded from the King County GIS Data Portal on July 15, 2016, within and in the immediate vicinity of the City of Bellevue. Group B wells were cross-referenced with state Department of Health Office of Drinking Water Sentry Internet data which provides summary information pertaining to public Water Systems. AESI removed one water system that was listed as inactive (water system ID 13107). This feature class is part of Appendix C, GIS Files and Documentation, of the Infiltration Infeasibility Analysis and Technical Report, prepared for the City of Bellevue Utilities Department by Associated Earth Sciences, Inc, April 4, 2016.

The 1991 Kings County land use survey data set was developed by DWR through its Division of Planning and Local Assistance (DPLA). The data was gathered using aerial photography and extensive field visits, the land use boundaries and attributes were digitized, and the resultant data went through standard quality control procedures before finalizing. The land uses that were gathered were detailed agricultural land uses, and lesser detailed urban and native vegetation land uses. The data was gathered and digitized by staff of DWR’s San Joaquin District. Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and San Joaquin District. The finalized data is a countywide shapefile (land use vector data). Important Points about Using this Data Set: 1. The land use boundaries were hand drawn directly on USGS quad maps and then digitized. They were drawn to depict observable areas of the same land use. They were not drawn to represent legal parcel (ownership) boundaries, or meant to be used as parcel boundaries. 2. This survey was a "snapshot" in time. The indicated land use attributes of each delineated area (polygon) were based upon what the surveyor saw in the field at that time, and, to an extent possible, whatever additional information the aerial photography might provide. For example, the surveyor might have seen a cropped field in the photograph, and the field visit showed a field of corn, so the field was given a corn attribute. In another field, the photograph might have shown a crop that was golden in color (indicating grain prior to harvest), and the field visit showed newly planted corn. This field would be given an attribute showing a double crop, grain followed by corn. The DWR land use attribute structure allows for up to three crops per delineated area (polygon). In the cases where there were crops grown before the survey took place, the surveyor may or may not have been able to detect them from the field or the photographs. For crops planted after the survey date, the surveyor could not account for these crops. Thus, although the data is very accurate for that point in time, it may not be an accurate determination of what was grown in the fields for the whole year. If the area being surveyed does have double or multicropping systems, it is likely that there are more crops grown than could be surveyed with a "snapshot". 3. If the data is to be brought into a GIS for analysis of cropped (or planted) acreage, two things must be understood: a. The acreage of each field delineated is the gross area of the field. The amount of actual planted and irrigated acreage will always be less than the gross acreage, because of ditches, farm roads, other roads, farmsteads, etc. Thus, a delineated corn field may have a GIS calculated acreage of 40 acres but will have a smaller cropped (or net) acreage, maybe 38 acres. b. Double and multicropping must be taken into account. A delineated field of 40 acres might have been cropped first with grain, then with corn, and coded as such. To estimate actual cropped acres, the two crops are added together (38 acres of grain and 38 acres of corn) which results in a total of 76 acres of net crop (or planted) acres. 4. Water source and irrigation method information was not collected for this survey. 5. During the transfer of data from the INTERGRAPH system to the AUTOCAD system, some attributes were lost. For those polygons that were attributed with either “D” (double cropped), “I” (intercropped), or "M" (mixed), the second crop has either an asterisk, blank, or zero in the two fields “IRR_TYP2PA” (irrigated or non-irrigated) and “IRR_TYP2PB” (type of irrigation system). There should have been either and “i” or “n” in the “IRR_TYP2PA” field, and a “U” or “*” in the “IRR_TYP2PB” field. 6. Not all land use codes will be represented in the survey.The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.3, dated April 13, 2022. DWR makes no warranties or guarantees - either expressed or implied - as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. See the CADWR Land User Viewer (gis.water.ca.gov/app/CADWRLandUseViewer) for the most current contact information. Comments, problems, improvements, updates, or suggestions should be forwarded to gis@water.ca.gov.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Ranges Feature Shapefile (ADDRFEAT.dbf) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. The ADDRFEAT shapefile contains a record for each address range to street name combination. Address range associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that the ADDRFEAT shapefile includes all unsuppressed address ranges compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefile contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

This shapefile contains tax rate area (TRA) boundaries in Kings County for the specified assessment roll year. Boundary alignment is based on the 2016 county parcel map. A tax rate area (TRA) is a geographic area within the jurisdiction of a unique combination of cities, schools, and revenue districts that utilize the regular city or county assessment roll, per Government Code 54900. Each TRA is assigned a six-digit numeric identifier, referred to as a TRA number. TRA = tax rate area number

Neighborhood boundaries within King County

Transportation features including rail, trails and pedestrian walkways with address ranges & names derived from digital orthophotography and GPS.

The King County Sheriff’s Office (KCSO) is providing offense report data captured in it's Records Management System (RMS) from 2020 to present. KCSO replaced its RMS in late 2018 and at the same time transitioned to the FBI’s National Incident-Based Reporting System (NIBRS). The NIBRS standardization of crime classifications allows for comparison over time and between agencies. For official KCSO NIBRS reporting, please visit the WASPC Crime in Washington Report: https://www.waspc.org/cjis-statistics---reports. Disclaimer: Only finalized (supervisor approved) reports are released. Those in draft, awaiting supervisor approval, or completed after the daily update of data, will not appear until the subsequent day(s). Data updates once every twenty-four hours. Records and classification changes will occur as a report makes its way through the approval and investigative process, thus reports might appear in the data set one day, but be removed the next day if there is a change in the approval status. This mirrors the fluidity of an investigation. Once a report is re-approved, it will show back up in the data set. Other than approval status, the report case status is factored into what can be released in the daily data set. As soon as a report case status matches the criteria for release, it will be included in the data set. For a list of offenses that are included in the data set, please see the attached pdf. Resources: - KCSO's 2019 crime data: https://data.kingcounty.gov/Law-Enforcement-Safety/King-County-Sheriff-s-Office-Incident-Dataset/rzfs-wyvy - Police District GIS shapefile: https://gis-kingcounty.opendata.arcgis.com/datasets/king-county-sheriff-patrol-districts-patrol-districts-area/explore - Police District key: https://data.kingcounty.gov/Law-Enforcement-Safety/KCSO-Patrol-Districts/ptrt-hdax/data - For more information on definitions and classifications, please visit https://www.fbi.gov/services/cjis/ucr/nibrs - SPD's Crime Data: https://data.seattle.gov/Public-Safety/SPD-Crime-Data-2008-Present/tazs-3rd5

This data layer describes the boundaries of combined water & sewer utility districts. This data does not describe water service or sewer service areas of the districts.

Transit routes

King County Real Property. Parcels owned by King County for the multiple category types, and the following use codes: County Used, Financial Investment, Interim Holdings, Social Investment, Surplus. Includes assessed value and acquisition dates.

KC streets derived from the cadastral database where lines represent the mid-point of the parcel right-of-way. Because it's parcel based, lines will not always align with the ortho photos. A feature in ST_ADDRESS should exist if there is a property with a valid address. A property such as an apartment or condo complex may have many streets within the property but only one street will be shown in ST_ADDRESS, containing the site address. Use TRANS_NETWORK when the lines should more closely match the ortho photos.