Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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)
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under Basic Parcels."Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.
Demographic Data dataset current as of 2005. demo_muni- Demographics of Iron County municipalities.
A 1:24,000 scale, full color geologic map of the Rice Mountain quadrangle, Lincoln County, Nevada and Iron County, Utah, with 2 cross sections and description of 23 units. Detailed geologic mapping by Jeffrey D. Keith, David G. Tingey, and Myron G. Best of Bringham Young University in 1994. Location of the Rice Mountain Quadrangle in relation to nearby geologic maps published by the U.S. Geological Survey and the Indian Peak caldera complex consisting of the Indian Peak White Rock and Mt. Wilson calderas that collapsed as the Wah Wah Springs, Lund, and Ripgut tuffs, were erupted (Best and others, 1989a). Paritial financial support for field work provided by the Geological Society of Nevada. The GIS work was in support of the U.S. Geological Survey COGEOMAP program. The Geodatabase specifies feature datasets and feature classes, together with feature attributes, subtypes and domains, suitable for a variety of geologic maps. In addition to basic geology, the maps may include metamorphic overprints, cross sections, and explanatory legend graphics such as correlation charts, used to supplement columnar legends. To download this GIS zipped data-set resource, please see the link provided.
1:24,000 scale Geologic Map of the Iron Point Quadrangle, Humboldt County, Nevada, USGS, GQ-1175. Detailed geologic mapping by R. L. Erickson and S. P. Marsh in 1974. geology of the Iron Point 7.5' Quadrangle, Humboldt County, Nevada, with description of 26 geologic units. The GIS work was in support of the U. S. Geological Survey COGEOMAP program. The Geodatabase specifies feature datasets and feature classes, together with feature attributes, subtypes and domains, suitable for the printed geologic map. In addition to basic geology (lithology, contacts and faults, etc.), the maps may include metamorphic overprints, cross-sections, and explanatory legend-graphics such as correlation charts, used to supplement columnar legends. For more information about this PDF map resource or to download the map and associated GIS zipped data-set, please see the links provided.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
This data set contains historical average tax rates by Counties in Utah from 2004-2013. Average tax rates are computed by dividing total locally and centrally assessed taxes charged by total taxable value, excluding motor vehicle fee-in-lieu value.
These vector contour lines are derived from the 3D Elevation Program using automated and semi-automated processes. They were created to support 1:24,000-scale topographic map products, but are also published in this GIS vector format. Contour intervals are assigned by 7.5-minute quadrangle, so this vector dataset is not visually seamless across quadrangle boundaries. The vector lines have elevation attributes (in feet above mean sea level on NAVD88), but this dataset does not carry line symbols or annotation.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Last update: April 4, 2023Added the Mammoth address system in Juab county. Additional minor edits to account for annexations in Utah (Springville, Lehi) and Box Elder (Willard, Garland) counties, April 2023.Added several address grids in Beaver county (Elk Meadows, Ponderosa, Greenville, Adamsville, Sulphurdale). Made major updates to grids in Utah, Cache, Tooele, and Box Elder Counties. Renamed 'NSL' to 'North Salt Lake' and 'East Carbon City' to 'East Carbon', December 2022. Minor adjustment to quadrants in Bluff.Added Rocky Ridge address grid in northern Juab county, August 2022.Updates were made near Elsinore/Central Valley/Monroe corners due to recent Elsinore annexation and inputs from Sevier County, September 2021.Improvements were made to Brigham City, Millville, Logan, and Providence, February 2016.Improvements were made to the Heber, Hyde Park, Logan, and Woodland address system boundaries; updated the American Fork, Fielding, Payson, and Saratoga Springs address system boundaries to reflect recent annexations, January 2016Improvements were made to the Hyde Park and Logan address system boundary, November 2015Improvements were made to the Hyrum and Logan address system boundary, November 2015Updated the American Fork address system boundary to reflect recent annexations, October 2015Improvements were made to the Brigham City, Fishlake, Fremont, Garland, Loa, Lyman, Mantua, Tremonton, and Willard address system boundaries; updated the Lehi and Santa Clara address system boundaries to reflect recent annexations, August 2015Improvements were made to the Price and Wellington address system boundaries; updated the Lehi and Provo address system boundaries to reflect recent annexations, July 2015Improvements were made to the Layton and HAFB address system boundaries; updated the Provo and Spanish Fork address system boundaries to reflect recent annexations, June 2015Updated address system boundaries to reflect annexations in Lehi, Lewiston, and Snowville, May 2015Improvements were made to the Orderville address system boundary to match the municipal boundary, February 2015Updated address system boundaries to match annexations in American Fork, Farmington, Elk Ridge, Grantsville, Lehi, Mendon, Mount Pleasant, Payson, Provo, Spanish Fork, and Washington, January 2015 Improvements were made to the Elmo and Cleveland address system boundaries, December 2014Improvements were made to the Wellington address system boundaries, July 2014Improvements were made to the NSL (North Salt Lake) and Bountiful address system boundaries, June 2014.Changed address system name East Carbon-Sunnyside to East Carbon City, May 2014Updated address system boundaries to match annexations in northern Utah County; misc improvements in Davis County; adjusted Laketown/Garden City boundary, April 2014Merged East Carbon and Sunnyside to create the East Carbon-Sunnyside address system, February 2014.Improvements were made to the Iron County address system quadrant boundaries and topological errors were corrected statewide, January 2014. Improvements were made to Garfield County and Washington County address system quadrant boundaries, August 2013.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/location/address-data/
The data is available in two formats: a ZIP file containing GIS shapefiles connected to an Access datafile containing information pertaining to excavation area, finds, object types along with other metadata regarding the archaeological investigation. The second ZIP file consists of corresponding .gml and .xlsx files.
Soil Survey PublicationsON 00 - Preliminary Soil Survey of Southwestern Ontario (1923)ON 02 - Soil Survey Report Elgin County (1929)ON 03 - Soil Survey Report Kent County (1930)ON 05 - Soil Survey Report Welland County (1935)ON 06 - Soil Survey Report Middlesex County (1931)ON 07 - Soil Survey Report Carleton County (1944)ON 08 - Reconnaissance Soil Survey of Parts of Northwestern Ontario (1944)ON 09 - Soil Survey Report Durham County (1946)ON 10 - Soil Survey Report Prince Edward County (1948)ON 11 - Soil Survey Report Essex County (1949)ON 12 - Soil Survey Report Grenville County (1949)ON 13 - Soil Survey Report Huron County (1952)ON 14 - Soil Survey Report Dundas County (1952)ON 15 - Soil Survey Report Perth County (1952)ON 16 - Soil Survey Report Bruce County (1954)ON 17 - Soil Survey Report Grey County (1954)ON 18 - Soil Survey Report Peel County (1953)ON 19 - Soil Survey Report York County (1955)ON 20 - Soil Survey Report Stormont County (1954)ON 21 - Soil Survey Report New Liskeard - Englehart Area (1952)ON 22 - Soil Survey Report Lambton County (1957)ON 23 - Soil Survey Report Ontario County (1956)ON 24 - Soil Survey Report Glengarry County (1957)ON 25 - Soil Survey Report Victoria County (1957)ON 26 - Soil Survey Report Manitoulin Island (1959)ON 27 - Soil Survey Report Hastings County (1962)ON 28 - Soil Survey Report Oxford County (1961)ON 28a - Soil Survey Report Oxford County Upgrade (1996)ON 29 - Soil Survey Report Simcoe County (1962)ON 30 - Soil Associations of Southern Ontario (1964)ON 31 - Soil Survey Report Parry Sound County (1962)ON 32 - Soil Survey Report Wentworth County (1965)ON 33 - Soil Survey Report Prescott Russell County (1962)ON 34 - Soil Survey Report Lincoln County (1963)ON 35 - Soil Survey Report Wellington County (1963)ON 36 - Soil Survey Report Lennox Addington County (1963)ON 37 - Soil Survey Report Renfrew County (1964)ON 38 - Soil Survey Report Dufferin County (1964)ON 39 - Soil Survey Report Frontenac County (1966)ON 40 - Soil Survey Report Lanark County (1967)ON 41 - Soil Survey Report Leeds County (1968)ON 42 - Soil Survey Report Northumberland County (1974)ON 43 - Soil Survey Report Halton County (1971)ON 44 - Soil Survey Report Waterloo County (1971)ON 44a - Soil Survey Report Waterloo County Upgrade (1996)ON 45 - Soil Survey Report Peterborough County (1981)ON 46 - Soils of Timmins-Noranda-Rouyn (1978) - MathesonON 46 - Soils of Timmins-Noranda-Rouyn (1978) - PamourON 46 - Soils of Timmins-Noranda-Rouyn (1978) - TimminsON 46 - Soils of Timmins-Noranda-Rouyn (1978) - Iroquois FallsON 46 - Soils of Timmins-Noranda-Rouyn (1978) - Kirkland LakeON 46 - Soils of Timmins-Noranda-Rouyn (1978) - Porquis JunctionON 46 - Soils of Timmins-Noranda-Rouyn (1978) - Timmins / Noranda / Rouyn AreaON 48 - Soils of Thunder Bay Area (1981) - Jarvis RiverON 48 - Soils of Thunder Bay Area (1981) - LoonON 48 - Soils of Thunder Bay Area (1981) - ParthON 48 - Soils of Thunder Bay Area (1981) - SunshineON 48 - Soils of Thunder Bay Area (1981) - Thunder BayON 48 - Soils of Thunder Bay Area (1981) - Thunder Bay AreaON 48 - Soils of Thunder Bay Area (1981) - Kakabeka FallsON 48 - Soils of Thunder Bay Area (1981) - Onion LakeON 48 - Soils of Thunder Bay Area (1981) - Pigeon RiverON 49 - Soils of Sudbury Area (1983) - CapreolON 49 - Soils of Sudbury Area (1983) - ChelmsfordON 49 - Soils of Sudbury Area (1983) - ConistonON 49 - Soils of Sudbury Area (1983) - Copper CliffON 49 - Soils of Sudbury Area (1983) - EspanolaON 49 - Soils of Sudbury Area (1983) - Lake TemagamiON 49 - Soils of Sudbury Area (1983) - MilnetON 49 - Soils of Sudbury Area (1983) - NoelvilleON 49 - Soils of Sudbury Area (1983) - SudburyON 49 - Soils of Sudbury Area (1983) - VernerON 49 - Soils of Sudbury Area (1983) - Whitefish FallsON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - AlgomaON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - Blind River - Sault Ste Marie AreaON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - Bruce MinesON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - Dean LakeON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - Ile ParisienneON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - Iron BridgeON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - MadawansonON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - Pancake BayON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - Sault Ste MarieON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - SearchmountON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - SpanishON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - St. Joseph IslandON 50 - Soils of Blind River - Sault Ste Marie Area (1983) - Whisky LakeON 51 - Soils of Fort Frances - Rainy River Area (1984) - Arbor VitaeON 51 - Soils of Fort Frances - Rainy River Area (1984) - EmoON 51 - Soils of Fort Frances - Rainy River Area (1984) - Fort FrancesON 51 - Soils of Fort Frances - Rainy River Area (1984) - Fort Frances - Rainy River AreaON 51 - Soils of Fort Frances - Rainy River Area (1984) - Northwest BayON 51 - Soils of Fort Frances - Rainy River Area (1984) - Rainy RiverON 52 - Soils of Kenora-Dryden-Pointe Du Bois Area (1987) - Crowduck LakeON 52 - Soils of Kenora-Dryden-Pointe Du Bois Area (1987) - DrydenON 52 - Soils of Kenora-Dryden-Pointe Du Bois Area (1987) - KeewatinON 52 - Soils of Kenora-Dryden-Pointe Du Bois Area (1987) - Vermilion BayON 53 - Soils of Pukaskwa National Park (1985) - PukaskwaON 54 - Soils of North Bay Area (1986) - KioskON 54 - Soils of North Bay Area (1986) - Marten LakeON 54 - Soils of North Bay Area (1986) - MattawaON 54 - Soils of North Bay Area (1986) - North BayON 54 - Soils of North Bay Area (1986) - PowassonON 54 - Soils of North Bay Area (1986) - Sturgeon FallsON 54 - Soils of North Bay Area (1986) - TemiscamingON 55 - Soil Survey Report Brant County (1989)ON 56 - Soil Survey Report Middlesex County (1992)ON 57 - Soil Survey Report Regional Municipality Haldimand Norfolk (1984)ON 58 - Soil Survey Report Regional Municipality Ottawa Carleton (1987)ON 59 - Soils of Gogama Area (1986) - CharltonON 59 - Soils of Gogama Area (1986) - ElkON 59 - Soils of Gogama Area (1986) - GogamaON 60 - Soil Survey Report Regional Municipality Niagara (1989)ON 61 - Soil Survey Report Chapleau Foleyet (1984)ON 63 - Soil Survey Report Elgin County (1992)ON 64 - Soil Survey Report Kent County Upgrade (1994)ON 90 - Soil Survey Report Ville Marie (1990)ON 98 - Location and Extent of the Soils of Southern Ontario (1998)
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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)