The data contained in this web map is the Final Land Use for the update of Horizon 2045. It contains all Land Use categories for both the 2019 base year and the 2045 horizon year by Transportation Analysis Zones (TAZ). The Land Use categories are as follows:LU1 - Single Family Housing UnitsLU2 - Multi-Family Housing UnitsLU3 - Hotels/MotelsLU4 - IndustrialLU5 - Non CBD-Retail (Non Central Business District)LU6 - Services and OfficesLU7 - Finance, Insurance, Real Estate (FIRES)LU8 - MedicalLU9 - CBD-Retail (Central Business District)LU10 - Students UniversityLU11 - Education Employees (K-12)LU12 - University Employees

Donation sent to the University of Idaho Library Government Documents Librarian a CD containing General Land Office maps on it. A readme file on the CD contains this information:"I obtained the attached GLO maps from Mitch Price at River Design Group who obtained them from another source. These maps apparently do not have a date, I assume it was stripped off when they were rectified. These maps show the Great Northern Rail line, it arrived in Bonners Ferry in 1892. The Spokane International Railroad (Union Pacific purchased this line) built a bridge across the Kootenai R. in 1906." "I am a bit puzzled on the map dates, the Kootenai River Master Plan indicated these maps are 1862-65 but they also show the Great Northern Rail line but not the Spokane International Railroad which seems to place them somewhere between 1892 - 1906 unless perhaps they were revised at a later date."Gary Barton USGS Tacoma, WA 253-552-1613 officegbarton@usgs.gov

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.

Municipal boundaries in Spokane County WA

Property ID, name(s), document type, and description: WL0466; Spokane Tunnel; map: Metsker's Atlas of Shoshone County.

Spokane county boundary

The Town has numerous zoning designations that dictate development for properties. Each zoning designation has a special set of rules and regulations that planners use for organization of parcels amongst other things.The designations created by the Town are listed in our Community Development Code (CDC).Current Zoning Districts: - Single-Family - Multi-Family - Industrial - Village Center - Civic - Single Family Common Interest Community - Full Use, Ski Resort Active Open Space - Resource Conservation Active Open Space - Active Open Space * - Right-of-Way Active Open Space - Site Specific PUD - Village Center Open Space - No Zone District – Rezoning Required Prior to New Use* Active Open Space to be rezoned consistent with the future land use plan found in the Mountain Village Comprehensive Plan.Future Zoning Districts: - Limited Use, Ski Resort Active Open Space - Limited Use, Golf Course Active Open Space - Planned Unit Development Zoning District

This interactive map shows the Spokane Regional Transportation Council’s (SRTC) 2022–2050 land use forecast by Transportation Analysis Zone (TAZ). Select a TAZ to view projected growth in population, households, and employment, as well as totals for the base year (2022) and forecast year (2050).Learn more about SRTC’s land use forecasting at: https://srtc.org/maps-and-data/land-use-forecasts/.

Ownership, Values, Amounts, and Billing information of all unpaid bills for Buncombe County for 2014

The taxlot layer contains all parcels in Deschutes County, as found on the county Assessor's Maps. The taxlot layer is the basis for many other layers; that is, other layers were built using the taxlot layer as the location control.

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

This layer is intended for archival purposes only. It has been superseded by the future land use adopted under Ordinance 2011-04. This layer depicts future land use districts for Walton County, Florida. The basis for this layer is the Future Land Use Map and Map Series adopted by Ordinance 1996-25 on 19961107. Edits have been made to incorporate changes to land use districts since the adoption of the 1996 map. Land use map changes are noted in the attributes by ordinance number and date. Otherwise, the information can be assumed to come from the original adopted map and map series. Land use districts depicted in this layer are approximate and not suitable for parcel-specific decision making. Further research may be required to draw accurate conclusions.

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)

Tax entities include all incorporated bodies that have the power to levy a local property tax such as school districts, counties, cities, special service districts, redevelopment districts, etc. This dataset was first created through a cooperative effort of the Governor's Office of Planning and Budget, the Utah Department of Transportation, the Utah State Tax Commission, and AGRC. All incorporated tax entities in the state through dates varying from 1984 to 1992 were initially represented. Updates for further annexations and de-annexations were completed with the cooperative efforts of the State Tax Commission, Property Tax Division, and AGRC, and currentness is through the end of the 2021 calendar year. Data developed with coordinate geometry (COGO) from legal descriptions were used. When necessary the data were adjusted to conform to known physical features. Due to adjustments to resolve conflicting or ambiguous data, the result was more a physical cadastre than a legal one. In other words, this dataset does not represent exact legal boundaries as per surveyed description, but, rather a set of boundaries used for the administrative purposes that conforms to logical & administrative rules (e.g. no two cities or redevelopment areas may cover the same geographic extent).This data is for 2021. Rates will be available in Sept.

This dataset represents Taxing Districts/Areas in the State of Utah as maintained by the Utah State Tax Commission (USTC). Each taxing district polygon represents a unique combination of overlapping taxing entities. The property tax within a taxing district should be the same for all residential properties. This dataset is derived from a spatial analysis process utilizing the USTC Tax Entities dataset. This data is for 2023. Updates are only done at the beginning of each calendar year for the previous year. The 2024 rates have not been done yet and won't be ready until September.