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

Spokane county boundary

Municipal boundaries in Spokane County WA

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 Relationship File (ADDR.dbf) contains the attributes of each address range. Each address range applies to a single edge and has a unique address range identifier (ARID) value. The edge to which an address range applies can be determined by linking the address range to the All Lines Shapefile (EDGES.shp) using the permanent topological edge identifier (TLID) attribute. Multiple address ranges can apply to the same edge since an edge can have multiple address ranges. Note that the most inclusive address range associated with each side of a street edge already appears in the All Lines Shapefile (EDGES.shp). The TIGER/Line Files contain potential address ranges, not individual addresses. 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. 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.

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. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

Deschutes County boundary.

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

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.

This dataset reflects the most current version of Utah county boundaries plus modifications made to correct known issues along the Davis-Weber and Duchesne-Uintah county boundaries. (20111108) and boundary agreement (certified 20120612) between Juab and Millard Counties. And an adjustment between Morgan and Summit Counties (4/3/2013). Minor adjustments were made to align with the Newest PLSS-GCDB layers from BLM (CadNSDIv2), any where from 10 to 50 feet all in non-populated areas (7/18/2014). Minor adjustment between Davis and Weber County (20201105)Data is current through Nov. 15, 2021; Population Figures from 2020 Census. Population Estimates are Null until we get a 2021 update.

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

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. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

School districts in Spokane County WA

Fire districts in Spokane County WA

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.

The geographic extent of a CountyData current as of the last business day.

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

The Washington State Department of Ecology has four regions covering the state: Eastern, Central, Northwest, and Southwest. Boundaries between the regions follow county boundaries. Regional offices are located in Spokane (Eastern), Yakima (Central), Bellevue (Northwest), and Olympia (Southwest).

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 Feature Names Relationship File (FEATNAMES.dbf) contains a record for each feature name and any attributes associated with it. Each feature name can be linked to the corresponding edges that make up that feature in the All Lines Shapefile (EDGES.shp), where applicable to the corresponding address range or ranges in the Address Ranges Relationship File (ADDR.dbf), or to both files. Although this file includes feature names for all linear features, not just road features, the primary purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute, which can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature is identified by the linear feature identifier (LINEARID) attribute, which can be used to relate the address range back to the name attributes of the feature in the Feature Names Relationship File or to the feature record in the Primary Roads, Primary and Secondary Roads, or All Roads Shapefiles. The edge to which a feature name applies can be determined by linking the feature name record to the All Lines Shapefile (EDGES.shp) using the permanent edge identifier (TLID) attribute. The address range identifier(s) (ARID) for a specific linear feature can be found by using the linear feature identifier (LINEARID) from the Feature Names Relationship File (FEATNAMES.dbf) through the Address Range / Feature Name Relationship File (ADDRFN.dbf).

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/