10 datasets found
  1. u

    Utah Morgan County Parcels LIR

    • opendata.gis.utah.gov
    • hub.arcgis.com
    • +1more
    Updated Nov 20, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah Automated Geographic Reference Center (AGRC) (2019). Utah Morgan County Parcels LIR [Dataset]. https://opendata.gis.utah.gov/datasets/utah-morgan-county-parcels-lir
    Explore at:
    Dataset updated
    Nov 20, 2019
    Dataset authored and provided by
    Utah Automated Geographic Reference Center (AGRC)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    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)

  2. a

    B Law Coal Permit Maps - Morgan County

    • gis-odnr.opendata.arcgis.com
    • hub.arcgis.com
    Updated Nov 6, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Ohio Department of Natural Resources (2024). B Law Coal Permit Maps - Morgan County [Dataset]. https://gis-odnr.opendata.arcgis.com/datasets/b-law-coal-permit-maps-morgan-county
    Explore at:
    Dataset updated
    Nov 6, 2024
    Dataset authored and provided by
    Ohio Department of Natural Resources
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Description

    Download .zipThe B Law Coal Permit Maps county coverage sets were developed using the original mine maps for coal mining and reclamation permits issued under Ohio law from 1973 through 1976. Approximately 1285 B-Permits were issued during this time period, however, only approximately 414 records could be located and captured at this time. The Division of Mineral Resources Management will continue to search for missing B permit archival records as resources allow; additional B permit data may be added to this existing coverage in the future.

    Ohio started issuing coal mining licenses in the 1940s. The earliest license and permit requirements were minimal and sometimes did not include submittal of a map or other delineation of the mined area. Significant changes to legal requirements are reflected by the alphabetical designation of each subsequent law revision, i.e., earlier A-law permits (circa 1966) through contemporary D-law permits. The ODNR-Division of Mineral Resources Management (DMRM) has attempted to create as complete a database as possible from available archive records, however, research has identified missing permit files. Thus, this GIS data is known to be incomplete due to the loss of archival records.

    The B law permit maps were scanned at a density of 200 dots per inch (dpi). The scanned image was then heads-up digitized using Microstation computer aided design software (CAD) to create design files grouped by county location. Data captured within the design file includes permit boundary, affected boundary, test hole locations, and associated attributes. The design file was then "placed-to-ground" using ODNR Division of Geological Survey's "ODNR Land Subdivision Background Design Files" NAD83 State Plane coverages and DOQQ aerial images obtained through the Ohio Geographically Referenced Information Program (OGRIP)/Ohio Department of Administrative Services. The design file was then converted to ARC/INFO coverage and projected to State Plane Ohio Coordinates, NAD83:

    Projected coordinate system name: NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet

    Geographic coordinate system name: GCS_North_American_1983

    A complete county coverage set consists of three data files for the permit area, affected area, and test hole locations. For example, the coverage for Belmont County includes:

    belmont_b_permitted (Belmont County, B-permit area polygons) belmont_b _affected (Belmont County, B-permit affected area polygons) belmont_testholes_b (Belmont County, Test Hole points)

    In addition to the ArcView shape files in the county data sets, the scanned TIF images for source documents are available at DMRM. The scanned mine map depicts information about the operations conducted, environmental resources, and extracted coal resources. If more detailed information is desired, the available archival record for each captured permit can be accessed at either the State Archives at the Ohio Historical Society or the ODNR-DMRM central office.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Mineral Resources ManagementAbandoned Mine Land Program2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

  3. a

    Utah Morgan County Parcels

    • hub.arcgis.com
    • opendata.gis.utah.gov
    Updated Nov 20, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah Automated Geographic Reference Center (AGRC) (2019). Utah Morgan County Parcels [Dataset]. https://hub.arcgis.com/maps/utah::utah-morgan-county-parcels
    Explore at:
    Dataset updated
    Nov 20, 2019
    Dataset authored and provided by
    Utah Automated Geographic Reference Center (AGRC)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    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.

  4. b

    Berks County Tax Map Index Map: New Morgan

    • opendata.berkspa.gov
    Updated Feb 7, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    County of Berks (2023). Berks County Tax Map Index Map: New Morgan [Dataset]. https://opendata.berkspa.gov/documents/2489b29749114d62b1d8cb57ad860d77
    Explore at:
    Dataset updated
    Feb 7, 2023
    Dataset authored and provided by
    County of Berks
    Description

    An official index map of tax maps by municipality for the County of Berks Assessment Department.

  5. a

    Flood Hazard Areas - Morgan County

    • gis-odnr.opendata.arcgis.com
    Updated Nov 6, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Ohio Department of Natural Resources (2024). Flood Hazard Areas - Morgan County [Dataset]. https://gis-odnr.opendata.arcgis.com/documents/54a511e382fb4b6480b06722f4e7324f
    Explore at:
    Dataset updated
    Nov 6, 2024
    Dataset authored and provided by
    Ohio Department of Natural Resources
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Description

    Download .zipThe flood hazard areas coverage is a representation of the 100 year floodplain as contained in the Federal Emergency Management Agency's (FEMA) most recent NFIP maps at the time of digitizing (2000). These maps were transferred to USGS 7.5 minute quadrangle maps and digitized in a vector mode.

    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

  6. U

    GIS Data for the Geologic Map of the Arlington Quadrangle, Carbon County,...

    • data.usgs.gov
    • catalog.data.gov
    Updated Apr 30, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Karen Morgan; John Horton (2024). GIS Data for the Geologic Map of the Arlington Quadrangle, Carbon County, Wyoming [Dataset]. http://doi.org/10.5066/P9HG38IQ
    Explore at:
    Dataset updated
    Apr 30, 2024
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Authors
    Karen Morgan; John Horton
    License

    U.S. Government Workshttps://www.usa.gov/government-works
    License information was derived automatically

    Time period covered
    Jun 5, 2023
    Area covered
    Wyoming, Carbon County
    Description

    This U.S. Geological Survey (USGS) data release for the geologic map of the Arlington quadrangle, Carbon County, Wyoming, is a Geologic Map Schema (GeMS, 2020)-compliant version of the printed geologic map published in USGS Geologic Map Quadrangle GQ-643 (Hyden and others, 1967). The database represents the geology for the 35,776-acre map plate at a publication scale of 1:24,000. References: Hyden, H.J., King, J.S., and Houston, R.S., 1967, Geologic map of the Arlington quadrangle, Carbon County, Wyoming: U.S. Geological Survey, Geologic Quadrangle Map GQ-643, scale 1:24,000; https://doi.org/10.3133/gq643. 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. B10, 74 p., https://doi.org//10.3133/tm11B10.

  7. a

    A Law Coal Permit Maps - Morgan County

    • gis-odnr.opendata.arcgis.com
    Updated Nov 6, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Ohio Department of Natural Resources (2024). A Law Coal Permit Maps - Morgan County [Dataset]. https://gis-odnr.opendata.arcgis.com/datasets/a-law-coal-permit-maps-morgan-county
    Explore at:
    Dataset updated
    Nov 6, 2024
    Dataset authored and provided by
    Ohio Department of Natural Resources
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Description

    Download .zipThe A Law Coal Permit Maps county coverage sets were developed using the original mine maps for coal mining and reclamation permits issued under Ohio law from approximately 1966 through 1973. Approximately 1111 A-Permits were issued during this time period, however, only 350 records could be located and captured at this time. The Division of Mineral Resources Management will continue to search for missing A permit archival records as resources allow; additional A permit data may be added to this existing coverage in the future.

    Ohio started issuing coal mining licenses in the 1940s. The earliest license and permit requirements were minimal and sometimes did not include submittal of a map or other delineation of the mined area. Significant changes to legal requirements are reflected by the alphabetical designation of each subsequent law revision, i.e., earlier A-law permits (circa 1966) through contemporary D-law permits. The ODNR-Division of Mineral Resources Management (DMRM) has attempted to create as complete a database as possible from available archive records, however, research has identified missing permit files. Thus, this GIS data is known to be incomplete due to the loss of archival records.

    The A law permit maps were scanned at a density of 200 dots per inch (dpi). The scanned image was then heads-up digitized using Microstation computer aided design software (CAD) to create design files grouped by county location. Data captured within the design file includes permit boundary and affected boundary and associated attributes. When available, test hole locations and associated attributes were also captured. The design file was then "placed-to-ground" using ODNR Division of Geological Survey's "ODNR Land Subdivision Background Design Files" NAD83 State Plane coverages and DOQQ aerial images obtained through the Ohio Geographically Referenced Information Program (OGRIP)/Ohio Department of Administrative Services. The design file was then converted to ARC/INFO coverage and projected to State Plane Ohio Coordinates, NAD83:

    Projected coordinate system name: NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet or NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet

    Geographic coordinate system name: GCS_North_American_1983

    A complete county coverage set consists of three data files for the permit area, affected area, and test hole locations. For example, the coverage for Harrison County includes:

    harrison_a_permitted (Harrison County, A-permit area polygons) harrison_a _affected (Harrison County, A-permit affected area polygons) harrison_testholes_a (Harrison County, Test Hole points)

    In addition to the ArcView shape files in the county data sets, the scanned TIF images for source documents are available at DMRM. The scanned mine map depicts information about the operations conducted, environmental resources, and extracted coal resources. If more detailed information is desired, the available archival record for each captured permit can be accessed at either the State Archives at the Ohio Historical Society or the ODNR-DMRM central office.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Mineral Resources ManagementAbandoned Mine Land Program2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

  8. a

    Tax Parcels

    • hub.arcgis.com
    Updated Nov 23, 2015
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Morgan County, Illinois Maps & Applications Portal (2015). Tax Parcels [Dataset]. https://hub.arcgis.com/maps/Morganmaps::tax-parcels
    Explore at:
    Dataset updated
    Nov 23, 2015
    Dataset authored and provided by
    Morgan County, Illinois Maps & Applications Portal
    Area covered
    Description

    Land boundaries for taxing purposes in Morgan County Illinois. Updated on 5/2/2025

  9. a

    15 13 GIS Map Morgan Property Aerial

    • chatham-county-planning-subdivisions-and-rezonings-chathamncgis.hub.arcgis.com
    Updated May 3, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Chatham County GIS Portal (2025). 15 13 GIS Map Morgan Property Aerial [Dataset]. https://chatham-county-planning-subdivisions-and-rezonings-chathamncgis.hub.arcgis.com/items/e9415b77dffc4dc8b26e6ccf49738754
    Explore at:
    Dataset updated
    May 3, 2025
    Dataset authored and provided by
    Chatham County GIS Portal
    Description

    Attachment regarding 1. A rezoning request by Morgan Property Group on Parcels 2719, 2720, 2721, 69884, 60612, 2508, from R-1 Residential to CD-CB Conditional District Community Business for a retail shopping center with specific uses prohibited. The total accumulative parcel totals is approximately 27.53 acres.

  10. a

    Voting Precincts

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • portal-morganmaps.opendata.arcgis.com
    • +1more
    Updated Jan 25, 2022
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Morgan County, Illinois Maps & Applications Portal (2022). Voting Precincts [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/maps/Morganmaps::voting-precincts
    Explore at:
    Dataset updated
    Jan 25, 2022
    Dataset authored and provided by
    Morgan County, Illinois Maps & Applications Portal
    Area covered
    Description

    Voting Precincts for Morgan County Illinois. Updated on 3/30/2023

  11. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Utah Automated Geographic Reference Center (AGRC) (2019). Utah Morgan County Parcels LIR [Dataset]. https://opendata.gis.utah.gov/datasets/utah-morgan-county-parcels-lir

Utah Morgan County Parcels LIR

Explore at:
Dataset updated
Nov 20, 2019
Dataset authored and provided by
Utah Automated Geographic Reference Center (AGRC)
License

Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically

Area covered
Description

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)

Search
Clear search
Close search
Google apps
Main menu