Geospatial data about Spokane County, Washington Quarter Sections. 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. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

description: The geology of Spokane County and vicinity, Washington and Idaho was compiled from Carrara and others (1995), Joseph (1990), Kiver and others (1979), Miller (written communication, 1995), and Waggoner (1990a, b) for input into an Arc/Info geographic information system (GIS). The digital geologic map database can be queried in many ways to produce a variety of derivative geologic maps.; abstract: The geology of Spokane County and vicinity, Washington and Idaho was compiled from Carrara and others (1995), Joseph (1990), Kiver and others (1979), Miller (written communication, 1995), and Waggoner (1990a, b) for input into an Arc/Info geographic information system (GIS). The digital geologic map database can be queried in many ways to produce a variety of derivative geologic maps.

Real Estate sales reviewed by Spokane County Assessors Office.

Real Estate sales reviewed by Spokane County Assessors Office.

Tax parcel polygons developed and maintained by the Spokane County Assessor office.

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

These data depict geographic features on the surface of the earth. They were created primarily as a visual aid for urban and county planning. Standards-based geospatial metadata did not accompany the source files for the collection. There is however a standards-based metadata record for the collection that was provided by Aerials Express. That collection-level metadata record indicates a time period of content of 20050510. Additionally, flight reports indicate dates in late May. This is inconsistent with the metadata table available on EarthExplorer.The source data for this service are available for download from USGS EarthExplorer. Individual image tiles can be downloaded using the Idaho Aerial Imagery Explorer.These data can be bulk downloaded from a web accessible folder.Source Metadata From USGS EarthExplorer:Beginning Date: 2009/07/23Ending Date: 2009/07/23EPSG: 26911Map Projection Description: NAD83 / UTM zone 11NState/Province/Country: ID/WADatum: NAD83Dataset: 200907_spokane_wa_0x3000_utm_clrProjection Zone: 11Sensor: UNKNOWNSensor Type: ColorNumber of Bands: 3Vendor: AERIALS_EXPRESSResolution: 0.3Units of Resolution: METERAgency: USGSUsers should be aware that temporal changes may have occurred since these data were collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of the limitations of these data as described in the lineage or elsewhere.

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

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.

Geospatial data about Spokane County, Washington Urban Growth Areas. Export to CAD, GIS, PDF, CSV and access via API.

This GIS data set was derived from a variety of source documents, including plats of survey, subdivision plats, certified survey maps, records of deed and row plats. These documents were of varying scales and from dates ranging from the late 1940's to present. These maps provide a useful representation of the geometry of the tax parcels and is suitable for its intended purpose.This GIS data set was derived from a variety of source documents, including plats of survey, subdivision plats, certified survey maps, records of deed and row plats. These documents were of varying scales and from dates ranging from the late 1940's to present. These maps provide a useful representation of the geometry of the tax parcels and is suitable for its intended purpose. This data was created to serve as an inventory of property owners for use by various county departments to determine septic and building permitting, voter and tax information, planning, social services, and use for the general public.This data was created to serve as an inventory of property owners for use by various county departments to determine septic and building permitting, voter and tax information, planning, social services, and use for the general public.For more information https://gisdownload.buncombecounty.org/parcels.htm

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

Spokane county boundary

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under Basic Parcels."Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.

Parcel map web service containing complementary feature classes to help supplement parcel navigation. This dataset contains nightly refreshed appraisal data and ownership information joined to the actual parcel layer..We also have the parcel layer available via our Open Data Portal where you can view, filter and download the tabular data.

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

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.

USGS Quad Map Boundary File for Deschutes County.