Purpose:To provide detailed 2-foot elevation contours across Wood County, supporting topographic analysis, land use planning, environmental assessments, and infrastructure development.Supplemental Information:This dataset offers precise elevation data based on LiDAR, valuable for environmental planning, flood risk assessment, and site development.Keywords:Elevation, Contours, Topography, LiDAR, Wood County, Environmental PlanningLineage:Source(s): Derived from LiDAR data collected by Wood County GIS. The data was processed to generate 2-foot interval contours, ensuring high accuracy and consistency.Process Steps:LiDAR data was processed to create contour lines at a 2-foot interval, using digital elevation models and specialized software to ensure accuracy in elevation representation.Accuracy and Consistency:Vertical Accuracy: Consistent with LiDAR standards, suitable for detailed elevation and landform analysis.Positional Accuracy: Verified against ground control points to align with Wood County’s high-accuracy mapping standards.Logical Consistency: Complete, continuous contour lines with no overlaps or breaks, ensuring seamless integration in topographic maps.Data Type:Vector (Polyline)Composition:Polyline features representing 2-foot contour intervals across Wood County.Spatial Reference:Coordinate System: Web Mercator (WGS 84)WKID: 3857Time Period of Content:Reflects conditions at the time of the most recent LiDAR acquisition and processing.Currentness Reference:Updated in line with new LiDAR acquisitions or significant topographical changes, supporting infrastructure and environmental projects.Contacts:Primary Contact:David L. Price, GIS Coordinator, Wood County GIS DepartmentPhone: (419) 373-3984Email: dprice@woodcountyohio.govDistributor:Available upon request through Wood County GIS or accessible via the Wood County Public Geolibrary.Distribution Liability:Wood County disclaims responsibility for misuse or incorrect application of this dataset. Provided "as-is" without warranty.Metadata Date:October 21, 2024Metadata Review Date:October 21, 2025Metadata Contact:David L. Price, (419) 373-3984, dprice@woodcountyohio.gov

Geospatial data about Wood County, West Virginia Parcels. Export to CAD, GIS, PDF, CSV and access via API.

Purpose:To provide a spatially accurate representation of the Wood County boundary in Ohio, supporting county-level mapping, jurisdictional delineation, public service delivery, and regional planning.Supplemental Information:This dataset is intended for general mapping and administrative use within Wood County, assisting with public safety, land management, and jurisdictional clarity.Keywords:County Boundary, Administrative Boundary, Jurisdiction, Wood County, Ohio, Mapping, Regional Planning.Lineage:Source(s): Derived from authoritative state and county records, maintained by Wood County GIS for accuracy and alignment with Ohio jurisdictional standards.Process Steps:Boundaries were digitized based on official county records and validated to ensure consistency with Ohio Department of Transportation and state standards.Accuracy and Consistency:Positional Accuracy: Conforms to county records and official state boundary definitions.Attribute Accuracy: Boundary attributes have been verified against county and state records.Logical Consistency: Ensures complete and closed boundary with no overlaps or gaps.Data Type:Vector (Polygon)Composition:Polygon feature representing the boundary of Wood County, Ohio.Spatial Reference:Coordinate System: NAD 1983 NSRS2007 StatePlane Ohio North FIPS 3401 (US Feet)Projection: Lambert Conformal ConicDatum: NAD 1983 NSRS2007Time Period of Content:Reflects conditions as of the latest boundary confirmation from Wood County GIS.Currentness Reference:Updated as needed to reflect any jurisdictional changes, in alignment with county and state standards.This dataset was created and last updated prior to the current GIS Manager.Contacts:Primary Contact:David L. Price, GIS Coordinator, Wood County GIS DepartmentPhone: (419) 373-3984Email: dprice@woodcountyohio.govDistributor:Available upon request through Wood County GIS or via the Wood County GIS Public Data Site.Distribution Liability:Wood County disclaims responsibility for improper or incorrect use of this dataset. Provided "as-is" without warranty for completeness or accuracy for any specific use.Metadata Date:October 21, 2024Metadata Review Date:October 21, 2025Metadata Contact:David L. Price, (419) 373-3984, dprice@woodcountyohio.gov

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

Geospatial data about Wood County, West Virginia Zoning. Export to CAD, GIS, PDF, CSV and access via API.

Purpose:To provide spatial information on school district boundaries within Wood County, supporting educational planning, public access, and jurisdictional management.Supplemental Information:This dataset includes detailed boundaries of school districts within Wood County, serving as a resource for school zoning, jurisdictional assessment, and planning efforts across educational institutions.Keywords:School Districts, Education, Boundaries, Wood County, OhioLineage:Source(s): Compiled and maintained by Wood County GIS based on records from state and local educational authorities.Process Steps: Digitized from official school district records and validated against authoritative local and state maps to ensure accurate boundary representation.Accuracy and Consistency:Positional Accuracy: Aligned with official school district boundaries provided by Wood County and local educational authorities.Attribute Accuracy: School district names and classifications verified for accuracy with local and state records.Logical Consistency: Ensures complete polygon boundaries for each district without overlaps or gaps.Data Type:Vector (Polygon)Composition:Polygons representing school district boundaries with attributes such as district name, type, and area.Spatial Reference:Coordinate System: NAD 1983 NSRS2007 StatePlane Ohio North FIPS 3401 (US Feet)Projection: Lambert Conformal ConicDatum: NAD 1983 NSRS2007Time Period of Content:Reflects current school district boundaries as last updated by Wood County GIS.Currentness Reference:Updated periodically to reflect changes in school district boundaries within Wood County.Contacts:Primary Contact:David L. Price, GIS Coordinator, Wood County GIS DepartmentPhone: (419) 373-3984Email: dprice@woodcountyohio.govDistributor:Available through Wood County GIS or via the Wood County Public Geolibrary.Distribution Liability:Wood County disclaims responsibility for misuse or misapplication. Dataset provided "as-is" without warranty.Metadata Date:October 21, 2024Metadata Review Date:October 21, 2025Metadata Contact:David L. Price, (419) 373-3984, dprice@woodcountyohio.gov

Download .zipThis ground-water resources theme shows an estimate of sustainable yield available from the aquifers in the area. Individual well yields may vary.

Original coverage data was converted from the .e00 file to a more standard ESRI shapefile(s) in November 2014.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesReal Estate & Land ManagementReal Estate and Lands Management2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Parcels and Land Ownership dataset current as of 2011. Parcel ID can be linked to taxroll.

Purpose:To provide a spatially accurate, topologically correct representation of the road network within Wood, Lucas, Ottawa, Seneca, Hancock, Henry, and Fulton Counties, supporting general mapping, transportation planning, geocoding, and roadway inventory.Supplemental Information:This dataset is part of the Ohio Location Based Response System (LBRS) and adheres to its standards for accuracy and topological correctness. It is designed to assist with public safety, transportation planning, and roadway management across multiple counties.Keywords:Road Centerline, LBRS, Transportation, General Mapping, Geocoding, Roadway Inventory, Multi-County, Ohio.Lineage:Source(s): Data collected through the Ohio LBRS with contributions from local authorities across Wood, Lucas, Ottawa, Seneca, Hancock, Henry, and Fulton Counties.Process Steps: Includes GPS field data collection, digitization, topology enforcement, validation, and periodic updates across all represented counties.Accuracy and Consistency:Positional Accuracy: Consistent with LBRS standards, verified through GPS and county-level records.Attribute Accuracy: Street names, classifications, and jurisdiction verified against official records for each county.Logical Consistency: Maintains topological integrity, providing a continuous, non-overlapping road network.Data Type:Vector (Polyline)Composition:Polylines representing road centerlines with attributes like street names, jurisdiction, surface type, and classification.Spatial Reference:Coordinate System: NAD 1983 NSRS2007 StatePlane Ohio North FIPS 3401 (US Feet)Projection: Lambert Conformal ConicDatum: NAD 1983 NSRS2007Time Period of Content:Reflects conditions as of the LBRS and county GIS updates at the time this was produced. This is a preexisting dataset created before the current GIS Manager.Currentness Reference:Updated as needed for new developments, closures, or reclassifications across all included counties, in alignment with LBRS standards.Contacts:Primary Contact:David L. Price, GIS Coordinator, Wood County GIS DepartmentPhone: (419) 373-3984Email: dprice@woodcountyohio.govDistributor:Available upon request through Wood County GIS or the LBRS data distribution network.Distribution Liability:Wood County, LBRS, and ODOT disclaim responsibility for improper or incorrect dataset use, provided "as-is" without warranty.Metadata Date:October 21, 2024Metadata Review Date:October 21, 2025Metadata Contact:David L. Price, (419) 373-3984, dprice@woodcountyohio.gov

Download .zipThis coverage was extracted from the 1994 statewide land cover inventory of Ohio produced by Bruce R. Motsch and Gary M. Schaal of the Ohio Department of Natural Resources.

The land cover inventory for the State of Ohio was produced by the digital image processing of Landsat Thematic Mapper Data. The Thematic Mapper is a multi-spectral scanner that collects electromagnetic radiation reflected from the earth's surface in the visible, near infrared and mid-infrared wavelength bands. The resolution of the Thematic Mapper data is a 30 meter by 30 meter cell. The computer analysis of the data isolates unique spectral classes that relate to land cover characteristics.

The land cover inventory was produced from Thematic Mapper data acquired in September and October 1994. The data was classified into the general land cover categories of urban, agriculture/open urban areas, shrub/scrub, wooded, open water, non-forested wetlands and barren.

The land cover information reflects the conditions of the satellite data during the specific year and season the data was acquired. The Thematic Mapper data was processed using ERDAS image processing software. The data was originally created in raster format and georeferenced to Universal Transverse Mercator (UTM) zone 17 coordinates NAD27. The data can be combined with other georeferenced digital data layers.

The data is also available in its original ERDAS image format.

Original coverage data was converted from the .e00 file to a more standard ESRI shapefile(s) in November 2014.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesReal Estate & Land ManagementReal Estate and Lands Management2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Geospatial data about Wood County, West Virginia Roads. Export to CAD, GIS, PDF, CSV and access via API.

Geospatial data about Ohio Urban Areas. Export to CAD, GIS, PDF, CSV and access via API.

Purpose:To provide a detailed spatial representation of drainage paths derived from LiDAR data within Wood County. This dataset supports hydrological analysis, resource management, and environmental planning.Supplemental Information:This dataset was created using high-resolution LiDAR data to identify and map drainage paths, ensuring accuracy in representing hydrological flow patterns and their attributes.Keywords:LiDAR, Drainage Paths, Hydrology, Environmental Planning, Resource Management, Wood CountyLineage:Source(s):Derived from high-resolution LiDAR data collected for Wood County.Process Step(s):The dataset was generated by Intern Kingsley Kanjin using advanced LiDAR processing techniques to delineate drainage paths. Steps included point cloud processing, flow accumulation analysis, and vectorization to create a line layer of drainage paths.Positional Accuracy:Consistent with the original LiDAR data, ensuring a high degree of spatial accuracy for hydrological modeling and analysis.Attribute Accuracy:Attributes have been verified for consistency with the LiDAR-derived flow accumulation and drainage path modeling.Logical Consistency:The dataset is logically consistent, with continuous drainage lines validated for hydrological network integrity.Type of Data:Vector (Polyline)Composition:The dataset consists of polyline features representing drainage paths. Attributes may include flow direction, stream order, and accumulation values.Coordinate System:NAD 1983 NSRS2007 StatePlane Ohio North FIPS 3401 (US Feet)Projection:Lambert Conformal ConicDatum:NAD 1983 NSRS2007Time Period of Content:Data represents conditions as captured during the LiDAR survey for Wood County.Currentness Reference:The dataset is updated based on new LiDAR surveys or significant changes in land use and hydrological features.ContactsPrimary Contact:Name: David L. PriceOrganization: Wood County GIS DepartmentPosition: GIS CoordinatorAddress: 1 Court House Sq., Bowling Green, OH 43402Phone: (419) 373-3984Email: dprice@woodcountyohio.govDistributor:Name: Wood County GIS DepartmentResource Description: Available upon request through the Wood County GIS Public Data Site.Distribution Liability:Wood County is not responsible for improper or incorrect use of this dataset. The dataset is provided "as-is" without warranty for completeness or accuracy for any specific use.Metadata Date:January 9, 2025Metadata Review Date:January 9, 2026Metadata Contact:Name: David L. PricePhone: (419) 373-3984Email: dprice@woodcountyohio.gov

A polygon data-set that represents the jurisdictional boundaries of public school districts throughout Wood County, Wisconsin.

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 dataset contains model-based census tract level estimates in GIS-friendly format. PLACES covers the entire United States—50 states and the District of Columbia—at county, place, census tract, and ZIP Code Tabulation Area levels. It provides information uniformly on this large scale for local areas at four geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. PLACES was funded by the Robert Wood Johnson Foundation in conjunction with the CDC Foundation. Data sources used to generate these model-based estimates are Behavioral Risk Factor Surveillance System (BRFSS) 2022 or 2021 data, Census Bureau 2010 population estimates, and American Community Survey (ACS) 2015–2019 estimates. The 2024 release uses 2022 BRFSS data for 36 measures and 2021 BRFSS data for 4 measures (high blood pressure, high cholesterol, cholesterol screening, and taking medicine for high blood pressure control among those with high blood pressure) that the survey collects data on every other year. These data can be joined with the Census tract 2022 boundary file in a GIS system to produce maps for 40 measures at the census tract level. An ArcGIS Online feature service is also available for users to make maps online or to add data to desktop GIS software. https://cdcarcgis.maps.arcgis.com/home/item.html?id=3b7221d4e47740cab9235b839fa55cd7

Download .zipGroundwater Vulnerability is an evaluatation of an area’s vulnerability to groundwater contamination based upon its hydrogeologic, topographic, and soil media characteristics.Contact Information:Geological Survey, Customer ServiceOhio Department of Natural ResourcesDivision of Geological SurveyGeologic Records2045 Morse RoadColumbus, OH, 43229-6693Telephone: 614-265-6576Email: geo.survey@dnr.ohio.gov

The Wood County Highway Department imposes seasonal weight restrictions on most county trunk highways during the spring thaw. The seasonal weight restrictions TYPICALLY occur from mid-March to around the end of April. The weight restrictions are 6 tons gross load for single axle vehicles and 10 tons gross load for tandem axle vehicles (any two axles under 8 feet apart). The maximum gross weight is 24 tons. Weight restrictions always remain in place until posted signs are removed.

Public Land Survey System (PLSS) control that have established survey grade GPS coordinates. Wisconsin County Surveyor’s Association survey grade standard: Coordinates collected under the direction of a Professional Land Surveyor, in a coordinate system allowed by s. 236.18(2), and obtained by means, methods and equipment capable of repeatable 2 centimeter or better precision.Statutory Standards for PLSS Corner Remonumentation:s. 59.74, Wis. Stats. Perpetuation of section corners, landmarks.s. 60.84, Wis. Stats. Monuments.ch. A-E 7.08, Wis. Admin. Code, U.S. public land survey monument record.ch. A-E 7.06, Wis. Admin. Code, Measurements.s. 236.15, Wis. Stats. Surveying requirements.

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)