Vector polygon map data of property parcels from Canyon County, Idaho containing 101,782 features.

​

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

​

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

​

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

This U.S. Geological Survey (USGS) data release provides a digital geospatial database for the geologic map of the Bayhorse area, central Custer County, Idaho (Hobbs and others, 1991). Attribute tables and geospatial features (points, lines, and polygons) conform to the Geologic Map Schema (GeMS, 2020) and represent the geologic map as published in the USGS Miscellaneous Investigations Series Map I-1882 (Hobbs and others, 1991). The 357,167-acre map area represents the geology at a publication scale of 1:62,000. References: Hobbs, S.W., Hays, W.H., and McIntyre, D.H., 1991, Geologic map of the Bayhorse area, central Custer County, Idaho: U.S. Geological Survey, Miscellaneous Investigations Series Map I-1882, scale 1:62,500, https://doi.org/10.3133/i1882. U.S. Geological Survey National Cooperative Geologic Mapping Program, 2020, GeMS (Geologic Map Schema) - A standard format for the digital publication of geologic maps: U.S. Geological Survey Techniques and Methods, book 11, chap ...

This layer is for the statewide standardized parcels polygons. This follows the standards that were approved by the Idaho Geospatial Council Executive Committee (IGC-EC). The data comes directly from the counties within Idaho that have a data sharing agreement with the Office of Information Technology Services (ITS). Each county within Idaho who chose to participate in the statewide effort are the owners of the data. Parcel data in constantly updated in the county office, this feature layer will be updated when ITS receives updates from the counties.A statewide Parcel Framework is a critical source of information for resource land management, community and economic development needs, infrastructure maintenance, research and analysis, homeland security, business development, public safety, and more. Many private sector and local, state, and federal government agencies have business needs for Parcel data.Standard:S4232 - Idaho Parcel Data Exchange Standard

More MetadataData updated daily.A parcel is a tract or plot of land surveyed and defined by legal ownership. Data were compiled from plats and deeds recorded at the Clerk of the Court and from historic tax maps. Source material was digitized or the coordinates were entered into the database via ARC/INFO Coordinate Geometry (COGO). Digital data from engineering companies has also been incorporated for newer subdivisions. A MCPI number is used to identify each parcel, which is a unique ID number further explained below. Purpose: Parcels are used to support a variety of services including assessment, permitting, subdivision review, planning, zoning, and economic development. Parcel data were initially developed to replace existing tax maps. As a result, there are parcel polygons digitized from tax maps that do not represent land parcels but are taxable entities such as leaseholds or easements. Supplemental Information: Data are stored in the corporate ArcSDE Geodatabase as a feature class. The coordinate system is Virginia State Plane (North), Zone 4501, datum NAD83 HARN. Maintenance and Update Frequency: Parcels are updated on an hourly basis from recorded deeds and plats. Depending on volume and date of receipt of recordation information, data may be updated 2-3 weeks following recordation. Completeness Report: Features may have been eliminated or generalized due to scale and intended use. To assist Loudoun County, Virginia in the maintenance of the data, please provide any information concerning discovered errors, omissions, or other discrepancies found in the data. MCPI: 9 digit unique parcel ID that is a combination of: MAP, CELL, and PARCEL. MAP: 3 digit map number (001-701) corresponding with map tile index. CELL: 2 digit map grid location of parcel center; the grid is comprised of 1000 by 1000 ft grid cells numbered as rows and columns (Columns numbered > 5 6 7 8 9 0; Rows numbered > 1 2 3 4). PARCEL: 4 digit location of polygon center based on the 1927 Virginia State Plane coordinate grid where an easting and northing measurement is taken. example: 6654 from: E 2229668 N475545. The MAP, CELL, and PARCEL values of a parcel do not change when a parcel is altered by a boundary line adjustment or becomes residue from a subdivision. The MAP, CELL, and PARCEL values may therefore be inconsistent with the location of polygon center. MAP, CELL, and PARCEL values have been manually altered for some parcels to agree with other databases; as a result, not all parcels can be located by the MAP, CELL, and PARCEL values. Data Owner: Office of Mapping and Geographic Information

This web map contains the Bing Maps aerial imagery with labels web mapping service, which provides worldwide orthographic aerial and satellite imagery with roads and labels overlaid. Coverage varies by region, with the most detailed coverage in the USA and United Kingdom. Coverage in different areas within a country also varies in detail based on the availability of imagery for that region. Bing Maps is continuously adding imagery in new areas and updating coverage in areas of existing coverage. This map does not include bird's eye imagery. Information regarding monthly updates of imagery coverage are available on the Bing Community blog. Post a comment to the Bing Community blog to request imagery vintage information for a specific area.Tip: The Bing Maps Hybrid service is one of the basemaps used in the ArcGIS.com map viewer and ArcGIS Explorer Online. Simply click one of those links to launch the interactive application of your choice, and then choose Bing Maps Hybrid from the Basemap control to start browsing! You'll also find this service in the Basemap gallery in ArcGIS Explorer Desktop and ArcGIS Desktop 10.If you need information on how to access Bing Maps, information is available in the ArcGIS Online Content Resource Center.See Bing Maps (http://www.bing.com/maps) for more information about the Bing Maps mapping system, terms of use, and a complete list of data suppliers.

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 distributedGIS 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 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)

This map provides assorted zoning, service areas, and municipal information to support property research for Boise, Idaho.

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

The Digital Geologic-GIS Map of Craters of the Moon National Monument and Preserve and Vicinity, Idaho is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (crmo_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (crmo_geology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (crmo_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (crmo_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (crmo_geology_metadata_faq.pdf). Please read the crmo_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey and Idaho Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (crmo_geology_metadata.txt or crmo_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

The County parcels dataset contains polygons representing individual taxed parcels or individual tax-exempt parcels tracked for taxing purposes. It also contains polygons representing the locations of multiple tax properties (multi-PID parcels). It is the combination of the parcel base dataset and the multiple parcel base dataset with attributes from a monthly extract of the property tax information system. The PID field contains the property ID number for each parcel.In the case of multiple tax properties, several parcel polygons may be stacked on top of one another. These are multiple tax parcels that cannot be delineated on a two-dimensional map, including both taxed and tax-exempt parcels. The parcels are represented with identical geometries but have different parcel IDs and associated tax attributes.For more information about this dataset, please view metadata.

This U.S. Geological Survey (USGS) data release provides an updated digital geospatial database for the geologic map of the Salmon National Forest and vicinity, east-central Idaho (Evans and Green, 2003). Attribute tables and geospatial features (points, lines and polygons) conform to the Geologic Map Schema (USGS NCGMP, 2020) and represent the geologic map as published in USGS Investigations Series Map I-2765. Minor errors, such as mistakes in line decoration or differences between the digital data and the map image, are corrected in this version.

The database represents the geology for the 11,265 square kilometer, geologically complex Salmon National Forest in two plates, at a publication scale of 1:100,000. The map covers primarily Lemhi County, but also includes minor parts of Beaverhead, Custer, Idaho, Ravalli and Valley Counties. New geologic mapping was undertaken between 1990 and 2002 and synthesized with older published maps, providing significant stratigraphic and struc ...

This layer is for the statewide standardized parcels polygons. This follows the standards that were approved by the Idaho Geospatial Council Executive Committee (IGC-EC). The data comes directly from the counties within Idaho that have a data sharing agreement with the Office of Information Technology Services (ITS). Each county within Idaho who chose to participate in the statewide effort are the owners of the data. Parcel data in constantly updated in the county office, this feature layer will be updated when ITS receives updates from the counties.A statewide Parcel Framework is a critical source of information for resource land management, community and economic development needs, infrastructure maintenance, research and analysis, homeland security, business development, public safety, and more. Many private sector and local, state, and federal government agencies have business needs for Parcel data.Standard:S4232 - Idaho Parcel Data Exchange Standard

The Florida Department of Revenue’s Property Tax Oversight(PTO) program collects parcel level Geographic Information System (GIS) data files every April from all of Florida’s 67 county property appraisers’ offices. This GIS data was exported from these file submissions in August 2025. The GIS parcel polygon features have been joined with thereal property roll (Name – Address – Legal, or NAL)file. No line work was adjusted between county boundaries.The polygon data set represents the information property appraisers gathered from the legal description on deeds, lot layout of recorded plats, declaration of condominium documents, recorded and unrecorded surveys.Individual parcel data is updated continually by each county property appraiser as needed. The GIS linework and related attributions for the statewide parcel map are updated annually by the Department every August. The dataset extends countywide and is attribute by Federal Information Processing Standards (FIPS) code.DOR reference with FIPS county codes and attribution definitions - https://fgio.maps.arcgis.com/home/item.html?id=55e830fd6c8948baae1601fbfc33a3b2If you discover the inadvertent release of a confidential record exempt from disclosure pursuant to Chapter 119, Florida Statutes, public records laws, immediately notify the Department of Revenue at 850-717-6570 and your local Florida Property Appraisers’ Office. Please contact the county property appraiser with any parcel specific questions: Florida Property Appraisers’ Offices:Alachua County Property Appraiser – https://www.acpafl.org/Baker County Property Appraiser – https://www.bakerpa.com/Bay County Property Appraiser – https://baypa.net/Bradford County Property Appraiser – https://www.bradfordappraiser.com/Brevard County Property Appraiser – https://www.bcpao.us/Broward County Property Appraiser – https://bcpa.net/Calhoun County Property Appraiser – https://calhounpa.net/Charlotte County Property Appraiser – https://www.ccappraiser.com/Citrus County Property Appraiser – https://www.citruspa.org/Clay County Property Appraiser – https://ccpao.com/Collier County Property Appraiser – https://www.collierappraiser.com/Columbia County Property Appraiser – https://columbia.floridapa.com/DeSoto County Property Appraiser – https://www.desotopa.com/Dixie County Property Appraiser – https://www.qpublic.net/fl/dixie/Duval County Property Appraiser – https://www.coj.net/departments/property-appraiser.aspxEscambia County Property Appraiser – https://www.escpa.org/Flagler County Property Appraiser – https://flaglerpa.com/Franklin County Property Appraiser – https://franklincountypa.net/Gadsden County Property Appraiser – https://gadsdenpa.com/Gilchrist County Property Appraiser – https://www.qpublic.net/fl/gilchrist/Glades County Property Appraiser – https://qpublic.net/fl/glades/Gulf County Property Appraiser – https://gulfpa.com/Hamilton County Property Appraiser – https://hamiltonpa.com/Hardee County Property Appraiser – https://hardeepa.com/Hendry County Property Appraiser – https://hendryprop.com/Hernando County Property Appraiser – https://hernandocountypa-florida.us/Highlands County Property Appraiser – https://www.hcpao.org/Hillsborough County Property Appraiser – https://www.hcpafl.org/Holmes County Property Appraiser – https://www.qpublic.net/fl/holmes/Indian River County Property Appraiser – https://www.ircpa.org/Jackson County Property Appraiser – https://www.qpublic.net/fl/jackson/Jefferson County Property Appraiser – https://jeffersonpa.net/Lafayette County Property Appraiser – https://www.lafayettepa.com/Lake County Property Appraiser – https://www.lakecopropappr.com/Lee County Property Appraiser – https://www.leepa.org/Leon County Property Appraiser – https://www.leonpa.gov/Levy County Property Appraiser – https://www.qpublic.net/fl/levy/Liberty County Property Appraiser – https://libertypa.org/Madison County Property Appraiser – https://madisonpa.com/Manatee County Property Appraiser – https://www.manateepao.gov/Marion County Property Appraiser – https://www.pa.marion.fl.us/Martin County Property Appraiser – https://www.pa.martin.fl.us/Miami-Dade County Property Appraiser – https://www.miamidade.gov/pa/Monroe County Property Appraiser – https://mcpafl.org/Nassau County Property Appraiser – https://ncpafl.com/Okaloosa County Property Appraiser – https://okaloosapa.com/Okeechobee County Property Appraiser – https://www.okeechobeepa.com/Orange County Property Appraiser – https://ocpaweb.ocpafl.org/Osceola County Property Appraiser – https://www.property-appraiser.org/Palm Beach County Property Appraiser – https://www.pbcgov.org/papa/index.htmPasco County Property Appraiser – https://pascopa.com/Pinellas County Property Appraiser – https://www.pcpao.org/Polk County Property Appraiser – https://www.polkpa.org/Putnam County Property Appraiser – https://pa.putnam-fl.com/Santa Rosa County Property Appraiser – https://srcpa.gov/Sarasota County Property Appraiser – https://www.sc-pa.com/Seminole County Property Appraiser – https://www.scpafl.org/St. Johns County Property Appraiser – https://www.sjcpa.gov/St. Lucie County Property Appraiser – https://www.paslc.gov/Sumter County Property Appraiser – https://www.sumterpa.com/Suwannee County Property Appraiser – https://suwannee.floridapa.com/Taylor County Property Appraiser – https://qpublic.net/fl/taylor/Union County Property Appraiser – https://union.floridapa.com/Volusia County Property Appraiser – https://vcpa.vcgov.org/Wakulla County Property Appraiser – https://mywakullapa.com/Walton County Property Appraiser – https://waltonpa.com/Washington County Property Appraiser – https://www.qpublic.net/fl/washington/Florida Department of Revenue Property Tax Oversight https://floridarevenue.com/property/Pages/Home.aspx

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)

The data release for geologic maps of Ravalli Group and other Mesoproterozoic Belt Supergroup strata in northern Idaho and northwestern Montana is a digital, Geologic Map Schema (GeMS)-compliant version of maps published in U.S. Geological Survey (USGS) Open-File Report 2001-438 (Boleneus and others, 2001). The new digital data include attribute tables and geospatial features (points, lines, and polygons) in the format that meets GeMS requirements. This data release presents the geologic maps as shown on the plates and captured in geospatial data for the published maps. The database represents the geology for the 2.7 million acre, geologically complex study area in eleven plates at a publication scale of 1:48,000, and two plates at a publication scale of 1:12,000. The maps cover primarily Sanders, Shoshone, Kootenai, and Lincoln Counties, but also include minor parts of Benewah and Bonner Counties. Geologic mapping was undertaken between 1979 and 1984 by ASARCO Inc. as part of their program to explore for sediment-hosted stratiform copper deposits in northern Idaho and western Montana. Geologic mapping was primarily focused on formations of the Ravalli Group, which resulted in large unmapped areas within the map boundary. In 2001 maps were scanned, georeferenced, and published by USGS (Boleneus and others, 2001). Boleneus, D.E., Applegate, L.M., Joseph, N.L., and Brandt, T.R., 2001, Raster Images of Geologic Maps of Middle Proterozoic Belt strata in parts of Benewah, Bonner, Kootenai and Shoshone Counties, Idaho and Lincoln, Mineral and Sanders Counties, Montana: U.S. Geological Survey Open-File Report OF-2001-438, scales 1:48,000 and 1:12,000, https://doi.org/10.3133/ofr2001438.

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)

The Digital Geologic-GIS Map of City of Rocks National Reserve and Vicinity, Idaho is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (ciro_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (ciro_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (ciro_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (ciro_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (ciro_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (ciro_geology_metadata_faq.pdf). Please read the ciro_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (ciro_geology_metadata.txt or ciro_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

The data release for the geologic map of the Dillon 1 x 2 degrees quadrangle, Idaho and Montana, is a Geologic Map Schema (GeMS)-compliant version that updates the GIS files for the geologic map published in U.S. Geological Survey (USGS) Miscellaneous Investigations Series Map I-1803-H (Ruppel and others, 1993). The updated digital data present the attribute tables and geospatial features (lines and polygons) in the format that meets GeMS requirements. This data release presents the geospatial data for the geologic map that is published as one plate. Minor errors, such as mistakes in line decoration or differences between the digital data and the map image, are corrected in this version. The database represents the geology for the 4.3 million acre, geologically complex Dillon 1 x 2 degrees quadrangle, at a publication scale of 1:250,000. The map covers primarily Beaverhead, Madison, Silver Bow, Deer Lodge, and Lemhi Counties, but also includes minor parts of Ravalli, Granite, and ...

These parcel boundaries represent legal descriptions of property ownership, as recorded in various public documents in the local jurisdiction. The boundaries are intended for cartographic use and spatial analysis only, and not for use as legal descriptions or property surveys. Tax parcel boundaries have not been edge-matched across municipal boundaries.