Geospatial data about Spokane County, Washington Municipal Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

Municipal boundaries in Spokane County WA

The "Shoreline Jurisdiction" shall refer to the shoreline areas of the Spokane River and Latah Creek within the Spokane City limits where the Shoreline Regulations shall apply, the general boundaries of which are illustrated on the Shoreline Jurisdiction Map, SMC 17E.060.060. In the event that any of the boundaries on the Shoreline Jurisdiction Map conflict with the criteria of WAC 173-22-040 as amended, the criteria shall control. The Shoreline Jurisdiction shall include: 1. All water bodies and land underlying these water bodies within the City of Spokane qualifying as "shorelines of the state," pursuant to the SMA, RCW 90.58.030(2)(c). In the City of Spokane, shorelines of the state are the Spokane River and Latah Creek within the Spokane City limits; 2. All upland areas, also referred to as "shorelands," that extend 200 feet landward in all directions on a horizontal plane from the edge of the ordinary-high-water mark of the Spokane River and Latah Creek within the Spokane City limits; and 3. Any associated wetlands, floodways, and some or all of the 100-year floodplain, including all wetlands within the 100-year floodplain of the Spokane River and Latah Creek within the Spokane City limits.

Spokane county boundary

BAS Submissions Read Me

This shapefile includes the annexation polygons that the Office of Financial Management (OFM) has sent to the Census Bureau since March 2020 as part of the Boundary and Annexation Survey (BAS). The Census Bureau uses these polygons to update Washington State’s city limits. Field names follow Census BAS guidelines, and an outline of relevant field names is below. More information about BAS can be found here: https://www.census.gov/programs-surveys/bas.html

The polygons include the quarterly annexations and other boundary corrections that effect the Census city boundaries, as well as several county boundary adjustments for King, Kittitas, Pierce, Spokane, and Stevens County. The annexation polygons were originally created by Washington’s Department of Transportation, and then edited by OFM to align with the latest BAS city boundary file available. These polygons to not follow the strict legal description of the annexation, as their intent is to make clear delineations between jurisdictions for population allocation. The following are the main differences between BAS annexation polygons and the originals:

<!--· The edges and vertices of polygons are snapped first to contiguous Census city limits and then to county parcels

<!--·
Where an annexation moves a city boundary to be either adjacent or across a right of way, the polygon is drawn to the centerline of the right of way

<!--· Annexations that are only include a right of way are often omitted, as they will not change the Census Bureau boundary

This file is updated quarterly. For questions or for data from earlier years, please contact Nate Chase nate.chase@ofm.wa.gov.

Relevant Field Names:

<!--·
CHNG_TYPE- Type of area update. A is annexation, D is deannexation, and B is a boundary correction which is a newly discovered boundary discrepancy

<!--· Eff_date- the local effective date

<!--· AUTHYPE- O is ordinance or resolution; X is for boundary correction; L signifies a county boundary correction

<!--· DOCU- the legal ordinance or resolution for the annexation. If there is a blank, then the entry is a correction polygon.

<!--· RELATE- Changing from in or out of jurisdiction

<!--· JUSTIFY- OFM’s reason for submitting the change polygon

<!--· A_Date- this is the date that OFM approves the annexation. OFM cannot legally approve annexations until all state requirements are met. The approval date cannot be earlier than the effective date, but it can be on the same day. OFM’s population determinations use the approval date of annexations. BAS submissions are only submitted after this date.

<!--· Source- The file in which the change polygon was originally submitted. Examples:

o
2022_Q1 submitted in December 2021

o 2022_Q2 submitted in March 2022

o
2022_Q3 submitted in June 2022

o
2022_Q4 submitted in September 2022

A precinct is generally the smallest level of geography established for purposes of conducting elections. Each precinct has a specific location where its residents go to vote.

Boundary describes the extent of the Spokane Valley-Rathdrum prairie aquifer from south end of lake Pend Oreille, Idaho - thru Rathdrum Prairie, the Spokane Valley, turning north to discharge at little Spokane River, and Spokane river north and west of the city of Spokane. Source data overview:Spokane Valley aquifer (WA State only) digitized in 1988 by Spokane Co. Engineer Dept from USGS 1977 hydrologic study of the Spokane Aquifer. This layer digitized from 1:24000 quad maps into the County's GDMS GIS. The USGS relied heavily on contour lines that described the valley floor to delineate the Spokane aquifer boundary. The original boundary had the Spokane River as it's west edge, but was revised (by Bea Leckaff Spokane County WQMP-GIS) in June, 1994, under the direction of Stan Miller to include the flood plain terraces on the west side of the river, down to the Little Spokane River confluence. The extent of the aquifer was revised again in March, 1995 to reflect new information from CH2MHill aquifer studies being done for the City of Spokane (to support Wellhead Protection). The revised aquifer extends the influence of impervious basalt outcroppings from the Spokane Falls area to the Trinity Triangle, (Drumheller Springs). The corrections were made by BBL from information provided by Stan Miller.

Idaho Portion of the Aquifer data came from Idaho Panhandle Public Health GIS SCALE: Idaho data digitized originally from 1:24000 USGS maps LAST UPDATED: March 1993- received Idaho data and matched to Spokane county aquifer data.

Neighborhood council boundaries for the City of Spokane

Polygons that represent the boundary or management area for significant facilities in a community

Combined incorporated city limit boundaries and unincorporated Urban Growth Areas (UGA) as defined by the Growth Management Act. Updates were made by collecting city limits and urban growth area boundary information from each of Washington's 39 counties, where available, and the Washington State Department of Transportation.

Fire districts in Spokane County WA

The GIS Commissioner District layer depicts three County Commissioner districts for Spokane County. This layer was developed from Federal Census Blocks rectified to fit Spokane County GIS base layers.

School districts in Spokane County WA

Polygons showing when different land areas were annexed into the City of Spokane

Community Development Neigborhood boundary polygons delineate eligablity for community block grants

BAS Submissions Read Me

This shapefile includes the annexation polygons that the Office of Financial Management (OFM) has sent to the Census Bureau since March 2020 as part of the Boundary and Annexation Survey (BAS). The Census Bureau uses these polygons to update Washington State’s city limits. Field names follow Census BAS guidelines, and an outline of relevant field names is below. More information about BAS can be found here: https://www.census.gov/programs-surveys/bas.html

The polygons include the quarterly annexations and other boundary corrections that effect the Census city boundaries, as well as several county boundary adjustments for King, Kittitas, Pierce, Spokane, and Stevens County. The annexation polygons were originally created by Washington’s Department of Transportation, and then edited by OFM to align with the latest BAS city boundary file available. These polygons to not follow the strict legal description of the annexation, as their intent is to make clear delineations between jurisdictions for population allocation. The following are the main differences between BAS annexation polygons and the originals:

<!--· The edges and vertices of polygons are snapped first to contiguous Census city limits and then to county parcels

<!--·
Where an annexation moves a city boundary to be either adjacent or across a right of way, the polygon is drawn to the centerline of the right of way

<!--· Annexations that are only include a right of way are often omitted, as they will not change the Census Bureau boundary

This file is updated quarterly. For questions or for data from earlier years, please contact Nate Chase nate.chase@ofm.wa.gov.

Relevant Field Names:

<!--·
CHNG_TYPE- Type of area update. A is annexation, D is deannexation, and B is a boundary correction which is a newly discovered boundary discrepancy

<!--· Eff_date- the local effective date

<!--· AUTHYPE- O is ordinance or resolution; X is for boundary correction; L signifies a county boundary correction

<!--· DOCU- the legal ordinance or resolution for the annexation. If there is a blank, then the entry is a correction polygon.

<!--· RELATE- Changing from in or out of jurisdiction

<!--· JUSTIFY- OFM’s reason for submitting the change polygon

<!--· A_Date- this is the date that OFM approves the annexation. OFM cannot legally approve annexations until all state requirements are met. The approval date cannot be earlier than the effective date, but it can be on the same day. OFM’s population determinations use the approval date of annexations. BAS submissions are only submitted after this date.

<!--· Source- The file in which the change polygon was originally submitted. Examples:

o
2022_Q1 submitted in December 2021

o 2022_Q2 submitted in March 2022

o
2022_Q3 submitted in June 2022

o
2022_Q4 submitted in September 2022

BAS Submissions Read Me

This shapefile includes the annexation polygons that the Office of Financial Management (OFM) has sent to the Census Bureau since March 2020 as part of the Boundary and Annexation Survey (BAS). The Census Bureau uses these polygons to update Washington State’s city limits. Field names follow Census BAS guidelines, and an outline of relevant field names is below. More information about BAS can be found here: https://www.census.gov/programs-surveys/bas.html

The polygons include the quarterly annexations and other boundary corrections that effect the Census city boundaries, as well as several county boundary adjustments for King, Kittitas, Pierce, Spokane, and Stevens County. The annexation polygons were originally created by Washington’s Department of Transportation, and then edited by OFM to align with the latest BAS city boundary file available. These polygons to not follow the strict legal description of the annexation, as their intent is to make clear delineations between jurisdictions for population allocation. The following are the main differences between BAS annexation polygons and the originals:

<!--· The edges and vertices of polygons are snapped first to contiguous Census city limits and then to county parcels

<!--·
Where an annexation moves a city boundary to be either adjacent or across a right of way, the polygon is drawn to the centerline of the right of way

<!--· Annexations that are only include a right of way are often omitted, as they will not change the Census Bureau boundary

This file is updated quarterly. For questions or for data from earlier years, please contact Nate Chase nate.chase@ofm.wa.gov.

Relevant Field Names:

<!--·
CHNG_TYPE- Type of area update. A is annexation, D is deannexation, and B is a boundary correction which is a newly discovered boundary discrepancy

<!--· Eff_date- the local effective date

<!--· AUTHYPE- O is ordinance or resolution; X is for boundary correction; L signifies a county boundary correction

<!--· DOCU- the legal ordinance or resolution for the annexation. If there is a blank, then the entry is a correction polygon.

<!--· RELATE- Changing from in or out of jurisdiction

<!--· JUSTIFY- OFM’s reason for submitting the change polygon

<!--· A_Date- this is the date that OFM approves the annexation. OFM cannot legally approve annexations until all state requirements are met. The approval date cannot be earlier than the effective date, but it can be on the same day. OFM’s population determinations use the approval date of annexations. BAS submissions are only submitted after this date.

<!--· Source- The file in which the change polygon was originally submitted. Examples:

o
2022_Q1 submitted in December 2021

o 2022_Q2 submitted in March 2022

o
2022_Q3 submitted in June 2022

o
2022_Q4 submitted in September 2022

Last update: 01/12/2024This data was developed for the Utah Department of Public Safety Bureau of Investigations for use in planning operations throughout the State. It indicates which law enforcement agency has responsibility in a specific area. Identification of local police departments was obtained from the Utah Chiefs of Police Association and from associated 911 dispatch centers. Boundaries for the police departments are the current municipal boundaries in SGID. Periodic boundary boundary changes will be made as municipal boundaries change and responsibilities of city police departments will be updated as they become known. Sheriffs Office boundaries are current county boundaries in SGID minus local police department boundaries.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/society/public-safety/

Rathdrum Comprehensive Aquifer Management Area Plan (CAMP) boundary of the Spokane Valley-Rathdrum Prairie Aquifer clipped at the Idaho border. Original boundary describes the extent of the Spokane Valley-Rathdrum Prairie aquifer from south end of lake Pend Oreille, Idaho - thru Rathdrum Prairie, the Spokane valley, turning north to discharge at little Spokane river, and Spokane river north and west of the city of Spokane. Spokane Valley aquifer (WA State only) was originally digitized in 1988 by Spokane Co. Engineer Dept from USGS 1977 hydrologic study of the Spokane Aquifer. This layer digitized from 1:24000 quad maps into the County's GDMS GIS. It was modified in June 1994 by Spokane County WQMP-GIS and again in March 1995 based on data from additional aquifer studies conducted by CH2Mhill. The Idaho portion of the Aquifer data came from Idaho Panhandle Public Health GIS in March 1993. The Aquifer boundary was redrawn based on new data from a coordinated ground and surface water monitoring program conducted in 2004-2005. The study reassessed the hydrogeology and water budget of the Spokane Valley-Rathdrum Prairie Aquifer (Aquifer). Data was originally digitized at a 1:24000 scale.

Polygons features derived from the Chatham County parcel polygon layer that identify the current zoning classifications for said parcels in Chatham County, NC. This feature class also contains boundaries for the Town of Siler City & Town of Pittsboro ETJ's as well as polygons identifying unzoned areas in Chatham County.

The feature class is maintained by the Chatham County Planning Department.Chatham GIS SOP: "MAPSERV-82"