Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Derived from 2010 census blocks to identify urban/rural areas. To qualify as an urban area, the territory identified according to criteria must encompass at least 2,500 people, at least 1,500 of which reside outside institutional group quarters. Urbanized areas area identified as 50,000 or more people, urbanized clusters represent at least 2,500 and less than 50,000 people. Rural areas encompass all population, housing, and territory not included within an urban area.</SPAN></P><P /></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data set represents the extent and approximate location of historic wetland habitats in certain areas of the conterminous United States. The identification of these historic wetlands is limited by the methodology outlined in the associated Historic Wetlands Project Metadata and is not intended to be a comprehensive inventory of all historic wetlands. The U.S. Fish and Wildlife Service (Service) is the principal Federal agency that provides information to the public on the extent and status of the Nation's wetlands and provides stewardship for the wetlands data that comprise the Wetlands Layer of the National Spatial Data Infrastructure. In the formulation of this data layer, historic wetlands are defined as areas where there is evidence that a wetland once existed. This evidence can be from historical map information inventories of past wetland extent or other information collected that relate directly to data on wetland filling, drainage or other modifications. Historic wetlands have been identified using several different techniques depending on the availability and type of information used to locate these areas and user needs. For example, historical maps often provide information about past wetland extent or location and can be useful tools to identify historic wetlands. Historic wetlands have been identified as polygonal data. No linear features have been included. Historic wetland polygons are not classified as wetlands and have no wetland labels or attribution. Since these features no longer exist, boundary delineations are considered approximations based on topography, previously mapped information or indications of historic water levels.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Boundaries.Municipalities is a multi-purpose statewide dataset of municipal boundaries for cartography and approximate boundary identification. Boundaries.Municipalities boundaries are maintained by AGRC with the help of many state, county, and local entities. Changes and updates are through certification by the Lt. Governor’s Office sent in by City and County Recorders offices. Boundary updates are occasionally accepted from local GIS departments when older (pre 2007) relevant boundary change information was not received through required channels. All features are adjusted to the current Geographic Coordinate Database (GCDB) points. Data developed with coordinate geometry (COGO) from legal descriptions were used. When necessary the data was adjusted to conform to known physical features. This dataset does not represent exact legal boundaries, but, rather a set of boundaries used for the administrative purposes that conforms to logical and administrative rules (e.g. no two cities or redevelopment areas may cover the same geographic extent). Data is current thru Dec. 31, 2020. Population Estimates are from July 1,2019.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 1c992cc539a343c188a018ea09be1278
Copyright Text: Cities, Towns and Counties of Utah, AGRC
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>Update information can be found within the layer’s attributes and in a table on the </SPAN><A href="https://gis.utah.gov/data/cadastre/parcels/"><SPAN>Utah Parcel Data webpage</SPAN></A><SPAN> under LIR Parcels.</SPAN></P><P><SPAN>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/ </SPAN></P><DIV><P STYLE="margin:0 0 14 0;"><SPAN>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.</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>GIS Layer Boundary Geometry:</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>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:</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>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.</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>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.</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>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.</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>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).</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>Descriptive Attributes:</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE </SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>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 systems</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>COUNTY_NAME Text 20 - County name including spaces ex. BOX ELDER</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>COUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessor</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>BOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorder</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>DISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>PARCEL_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)</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, Other</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>TAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17A</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>TOTAL_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. 332000</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. Residential</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>PRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. Y</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>HOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor Subdivision</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>BLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>BLDG_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.</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are counted</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>BUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>CONST_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 </SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>Contact: Sean Fernandez, Cadastral Manager (email: [email protected]; office phone: 801-209-9359)</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN /></P></DIV></DIV></DIV>