Layer: Davis (ID: 2)

Name: Davis

Display Field: COUNTY_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><DIV><DIV>We wanted to identify consistent classifications for existing land use across the Wasatch Front Region. Using the Land Information Records (LIR) Parcel data distributed by Utah AGRC, we completed analysis on parcels within the WFRC MPO area. LIR Parcel Data was subject to analyses including comparisons with the Real Estate Market Model (REMM), land ownership, elevation, hydrology, county master development plans, tax exemption and manual editing. The WFRC_LUType field classifies parcels into current land use. Updated December 2018.Land Use Fields added by WFRC described here:WFRC_LUType - Current Land Use TypeAg - AgricultureOS - Parks and Open SpaceC - CommercialSFR - Single Family ResidentialMFR - Multi-Family ResidentialGI - Government and InstitutionI - IndustrialParking - Parking LotsOther ND - Other Non-developable LandPrivate Industrial Reserve - Non-developable Private or Industrial LandRU - Roads and UtilitiesVacant - Vacant Land or No DataAssoc_C - Associated Commercial Land (common space, parking, etc.)Assoc_SF - Associated Single Family (associated undeveloped land, common spaces in PUDs, etc.)Assoc_MF - Associated Multi Family (common spaces, parking and storage in multi-unit developments)LUType_Detail- Breakdown of current land use types Ag, C, Other NDAg_REMM - Land identified as agricultural land by the REMM agriculture analysis, derived from Water-related Land Use (AGRC)Retail - Retail Commercial (available in Salt Lake County Only)Office - Office Commerical (available in Salt Lake County Only)Other SL - Other Non-developable State LandOther NS ND - Other Non-developable Non-State Land*******************************************************************************Original Metadata for LIR Parcel Data from Utah AGRC 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.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.This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer.https://gis.utah.gov/data/sgid-cadastre/Last Update: 2018GIS 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:ftp://ftp.agrc.utah.gov/UtahSGID_Vector/UTM12_NAD83/CADASTRE/LIR_ParcelSchema.zipAt 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)</DIV></DIV></DIV>

Copyright Text:

Default Visibility: true

MaxRecordCount: 12000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 9244648

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

Drawing Info:

Renderer:

Unique Value Renderer:

Field 1:

Field 2:

Field 3:

Field Delimiter:

Default Symbol:

N/A

Default Label:

UniqueValueInfos:

Value: Agriculture
Label: Agriculture
Description: N/A
Symbol:
Value: Associated Commercial
Label: Associated Commercial
Description: N/A
Symbol:
Value: Associated Multi-Family
Label: Associated Multi-Family
Description: N/A
Symbol:
Value: Associated Single-Family
Label: Associated Single-Family
Description: N/A
Symbol:
Value: Commercial
Label: Commercial
Description: N/A
Symbol:
Value: Government and Institution
Label: Government and Institution
Description: N/A
Symbol:
Value: Industrial
Label: Industrial
Description: N/A
Symbol:
Value: Multi-Family Residential
Label: Multi-Family Residential
Description: N/A
Symbol:
Value: Other Non-Developable
Label: Other Non-Developable
Description: N/A
Symbol:
Value: Parking
Label: Parking
Description: N/A
Symbol:
Value: Parks and Open Space
Label: Parks and Open Space
Description: N/A
Symbol:
Value: Private Industrial Reserve
Label: Private Industrial Reserve
Description: N/A
Symbol:
Value: Roads and Utilities
Label: Roads and Utilities
Description: N/A
Symbol:
Value: Single-Family Residential
Label: Single-Family Residential
Description: N/A
Symbol:
Value: Vacant
Label: Vacant
Description: N/A
Symbol:

Transparency:

Labeling Info:

Advanced Query Capabilities:

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
COUNTY_NAME ( type: esriFieldTypeString, alias: County Name, length: 20 )
PARCEL_ADD ( type: esriFieldTypeString, alias: Parcel Address, length: 100 )
PARCEL_CITY ( type: esriFieldTypeString, alias: Parcel City, length: 30 )
PROP_CLASS ( type: esriFieldTypeString, alias: Property Class, length: 100 )
WFRC_LUType ( type: esriFieldTypeString, alias: Land Use Type, length: 30 )

Supported Operations: Query Query Attachments Query Analytic Generate Renderer Return Updates

Iteminfo Thumbnail Metadata