Abstract

This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied.

This dataset defines the boundaries of the 66 groundwater SDL resource units in the Murray-Darling Basin. These include 7 groundwater SDL resource units for deep groundwater that lie beneath the 59 groundwater SDL resource units. 2 of the groundwater SDL resource units have different boundaries in their surface expression and in deep groundwater and therefore are shown with both a Groundwater and Deep Groundwater extent.

In some areas, there are SDL resource units that overlap one another (eg: GS1). This occurs where SDLs have been set for discrete aquifers that overlie one another under the same area of land. These can be differentiated by the GWSDLName field.

There are areas of overlap between the groundwater and deep groundwater SDL resource units which need to be taken into account when viewing the data. These can be differentiated by the GWSDLType field

Purpose

The Basin Plan provides a coordinated approach to water use across the Basin's four States and the ACT. The Basin Plan is a plan for the integrated management of Basin water resources made under the Water Act 2007. It limits water use at environmentally sustainable levels by determining long-term average Sustainable Diversion Limits for both surface water and groundwater resources.

Date of Ceasing: To be ceased 01 Apr 2023

Dataset History

The following data has been used in the development of groundwater SDL resource unit boundaries:

Queensland: - Upper Condamine Basalts (as contained in the data files titled: basalts.dbf, basalts.prj, basalts.sbn, basalts.sbx, basalts.shp, basalts.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Texas beds (as contained in the data files titled: texas beds.dbf, texas beds.prj, texas beds.sbn, texas beds.sbx, texas beds.shp, texas beds.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Griman Creek Formation (as contained in the data files titled: Griman Ck Formation.dbf, Griman Ck Formation.prj, Griman Ck Formation.sbn, Griman Ck Formation.sbx, Griman Ck Formation.shp, Griman Ck Formation.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Great Artesian Basin geology (as contained in the data files titled: Geology.dbf, Geology.prj, Geology.sbn, Geology.sbx, Geology.shp, Geology.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Queensland Murray-Darling Groundwater Management Units (as contained in the data files titled: QLD_MurrayDarling_GMU_GCS_v7.dbf, QLD_MurrayDarling_GMU_GCS_v7.prj, QLD_MurrayDarling_GMU_GCS_v7.sbn, QLD_MurrayDarling_GMU_GCS_v7.sbx, QLD_MurrayDarling_GMU_GCS_v7.shp, QLD_MurrayDarling_GMU_GCS_v7.shx) provided by SKM on 16/12/2009. - Geology sheet sh5502 (as contained in the data files titled: sh5502.dbf, sh5502.prj, sh5502.sbn, sh5502.sbx, sh5502.shp, sh5502.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Geology sheet sh5501 (as contained in the data files titled: sh5501,dbf, sh5501.prj, sh5501.sbn, sh5501.sbx, sh5501.shp, sh5501.shx), provided by the Department of Environment and Resource Management on 18/12/2009. - Geology sheet sh5513 (as contained in the data files titled: sg5513.dbf, sg5513.prj, sg5513.sbn, sg5513.sbx, sg5513.shp, sg5513.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Geology sheet sh5609 (as contained in the data files titled: sg5609.dbf, sg5609.prj, sg5609.sbn, sg5609.sbx, sg5609.shp, sg5609.shx) provided by the Department of Environment and Resource Management, Queensland, on 18/12/2009. - Central Condamine Alluvium boundaries (as contained in the files:Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.dbf, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.prj, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.sbn, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.sbx, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.shp, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.shx) provided by the Department of Environment and Resource Management on 27/5/2011 - DERM Revised Queensland Groundwater SDL Areas (as contained in the files: DERM_Revised_QLD_GW_SDL_AREAS.dbf, DERM_Revised_QLD_GW_SDL_AREAS.prj, DERM_Revised_QLD_GW_SDL_AREAS.sbn, DERM_Revised_QLD_GW_SDL_AREAS.sbx, DERM_Revised_QLD_GW_SDL_AREAS.shp, DERM_Revised_QLD_GW_SDL_AREAS.shp.xml, DERM_Revised_QLD_GW_SDL_AREAS.shx ) provided by the Queensland Department of Environment & Resource Management on 26/9/2011

New South Wales: - Groundwater macro water sharing plan areas (as contained in the data file titled: DraftGWMacroPlanOctober2010.mdb) provided by NSW Office of Water on 14/12/2010. - Groundwater macro water sharing plan areas (as contained in the data file titled: GWMacroPlanFeb2012.gdb) provided by NSW Office of Water on 8/3/2012.

Victoria: - Goulburn-Murray water boundary (as contained in the data files titled: G-MW_Boundary.dbf, G-MW_Boundary.prj, G-MW_Boundary.sbn, G-MW_Boundary.sbx, G-MW_Boundary.shp, G-MW_Boundary.shx) provided by Goulburn-Murray Water on 21/12/2009. - Murray geological basin (as contained in the data files titled: Murray_GB_250K.dbf, Murray_GB_250K.prj, Murray_GB_250K.sbn, Murray_GB_250K.sbx, Murray_GB_250K.shp, Murray_GB_250K.shx) provided by Sinclair Knight Merz on 14/12/2009. - Southern Campaspe Plain (as contained in the data files titled: S_Camp_Plains.dbf, S_Camp_Plains.prj, S_Camp_Plains.sbn, S_Camp_Plains.sbx, S_Camp_Plains.shp, S_Camp_Plains.shx) provided by Department of Sustainability and Environment, Victoria, on 03/03/2010. - West Wimmera and Murrayville water sharing plan area (as contained in the data files titled: West_Wimmera_&_Murrayville_WSPA.dbf, West_Wimmera_&_Murrayville_WSPA.prj, West_Wimmera_&_Murrayville_WSPA.sbn, West_Wimmera_&_Murrayville_WSPA.sbx, West_Wimmera_&_Murrayville_WSPA.shp, West_Wimmera_&_Murrayville_WSPA.shx) provided by Department of Sustainability and Environment, Victoria, on 11/01/2010. - Victorian groundwater management unit (as contained in the data files titled: Vic_GMU_gcs_v02.dbf, Vic_GMU_gcs_v02.prj, Vic_GMU_gcs_v02.sbn, Vic_GMU_gcs_v02.sbx, Vic_GMU_gcs_v02.shp, Vic_GMU_gcs_v02.shx) provided by Sinclair Knight Merz on 30/11/2009. - SA/VIC Border zone agreement area (as contained in the data files titled: Border_Agreement.dbf, Border_Agreement.prj, Border_Agreement.sbn, Border_Agreement.sbx. Border_Agreement.shp, Border_Agreement.shx) provided by Sinclair Knight Merz on 30/11/2009. - AWRC Basins (as contained in the data files titled: AWRC_BASINS.dbf, AWRC_BASINS.prj, AWRC_BASINS.sbn, AWRC_BASINS.sbx, AWRC_BASINS.shp, AWRC_BASINS.shx) provided by MDBA on 19/01/2009.

• Basin water resources exclusions contained in the data files titled westwimmera.dbf, westwimmera.prj, westwimmera.sbn, westwimmera.sbx, westwimmera.shp, westwimmera.shp.xml, westwimmera.shx provided by the Department of Environment on 14/11/2013

South Australia: - South Australian groundwater management unit (as contained in the data files titled: SA_GMU_gcs_v03.dbf, SA_GMU_gcs_v03.prj, SA_GMU_gcs_v03.sbn, SA_GMU_gcs_v03.sbx, SA_GMU_gcs_v03.shp, SA_GMU_gcs_v03.shx) provided by Sincliar Knight Merz on 30/11/2009. - SA/VIC Border zone agreement area (as contained in the data files titled: Border_Agreement.dbf, Border_Agreement.prj, Border_Agreement.sbn, Border_Agreement.sbx. Border_Agreement.shp, Border_Agreement.shx) provided by Sinclair Knight Merz on 30/11/2009. - Murray-Darling Basin Rivers (as contained in the data files titled: MDB_MAIN_RIVERS.dbf, MDB_MAIN_RIVERS.prj, MDB_MAIN_RIVERS.sbn, MDB_MAIN_RIVERS.sbx, MDB_MAIN_RIVERS.shp, MDB_MAIN_RIVERS.shx) provided by the MDBA on 19/01/2009.

• Basin water resources exclusions as contained in the data files titled: Split_poly_MDB_PWRA_Area1_IW.dbf, Split_poly_MDB_PWRA_Area1_IW.prj, Split_poly_MDB_PWRA_Area1_IW..sbn, Split_poly_MDB_PWRA_Area1_IW.sbx, Split_poly_MDB_PWRA_Area1_IW.shp, Split_poly_MDB_PWRA_Area1_IW.shp.xml, Split_poly_MDB_PWRA_Area1_IW.shx, Split_poly_MDB_PWRA_Area2_IW.dbf, Split_poly_MDB_PWRA_Area2_IW.prj, Split_poly_MDB_PWRA_Area2_IW..sbn, Split_poly_MDB_PWRA_Area2_IW.sbx, Split_poly_MDB_PWRA_Area2_IW.shp, Split_poly_MDB_PWRA_Area2_IW.shp.xml, Split_poly_MDB_PWRA_Area2_IW.shx, Split_poly_MDB_PWRA_Area4_IW.dbf, Split_poly_MDB_PWRA_Area4_IW.prj, Split_poly_MDB_PWRA_Area4_IW..sbn, Split_poly_MDB_PWRA_Area4_IW.sbx, Split_poly_MDB_PWRA_Area4_IW.shp, Split_poly_MDB_PWRA_Area4_IW.shp.xml, Split_poly_MDB_PWRA_Area4_IW.shx, Split_poly_MDB_PWRA_Area5_IW.dbf, Split_poly_MDB_PWRA_Area5_IW.prj, Split_poly_MDB_PWRA_Area5_IW..sbn, Split_poly_MDB_PWRA_Area5_IW.sbx, Split_poly_MDB_PWRA_Area5_IW.shp, Split_poly_MDB_PWRA_Area5_IW.shp.xml, Split_poly_MDB_PWRA_Area5_IW.shx, Split_poly_MDB_PWRA_Area6_IW.dbf, Split_poly_MDB_PWRA_Area6_IW.prj, Split_poly_MDB_PWRA_Area6_IW..sbn, Split_poly_MDB_PWRA_Area6_IW.sbx, Split_poly_MDB_PWRA_Area6_IW.shp, Split_poly_MDB_PWRA_Area6_IW.shp.xml, Split_poly_MDB_PWRA_Area6_IW.shx, provided by the Department of Sustainability, Environment, Water, Population and Communities on 27/5/2013 and 28/05/2013.

ACT: - ACT GMU Boundaries (as contained in the data files titled: ACT_GMU_gcs_v01.dbf, ACT_GMU_gcs_v01.prj, ACT_GMU_gcs_v01sbn, ACT_GMU_gcs_v01.sbx, ACT_GMU_gcs_v01.shp, ACT_GMU_gcs_v01.shx) provided by Sinclair Knight Merz on 30/11/2009.

State Borders: - State Borders (as contained in the data files titled: AUS_STATE_BORDER.dbf, AUS_STATE_BORDER.prj, AUS_STATE_BORDER.sbn, AUS_STATE_BORDER.sbx, AUS_STATE_BORDER.shp, AUS_STATE_BORDER.shx) provided by the MDBA on 19/01/2009.

Deep groundwater SDL resource unit boundaries:

• Boundary for the Oaklands Basin (as contained in the files:

This dataset provides shapefile outlines of the 7,150 lakes that had temperature modeled as part of this study. The format is a shapefile for all lakes combined (.shp, .shx, .dbf, and .prj files). A csv file of lake metadata is also included. This dataset is part of a larger data release of lake temperature model inputs and outputs for 7,150 lakes in the U.S. states of Minnesota and Wisconsin (http://dx.doi.org/10.5066/P9CA6XP8).

Google Earth Engine used to compute the NDVI statistics added to Globe-LFMC. The input of the program is a point shapefile (“samplePlotsShapefile”, extensions .cpg, .dbf, .prj, .shp, .shx) representing the location of each Globe-LFMC site. This shapefile is available as additional data in figshare (see Code Availability). To run this GEE code the shapefile needs to be uploaded into the GEE Assets and, then, imported into the Code Editor with the name “plots” (without quotation marks).Google Earth Engine codeChange Notice - GEE_script_for_GlobeLFMC_ndvi_stats_v2.jsThe following acknowledgements have been added at the beginning of the code: “Portions of the following code are modifications based on work created and shared by Google in Earth Engine Data Catalog and Earth Engine Guides under the Apache 2.0 License. https://www.apache.org/licenses/LICENSE-2.0”Change Notice - samplePlotsShapefile_v2The shapefile describing the database sites has been corrected and updated with the correct coordinates.

This dataset provides shapefile of outlines of the 68 lakes where temperature was modeled as part of this study. The format is a shapefile for all lakes combined (.shp, .shx, .dbf, and .prj files). This dataset is part of a larger data release of lake temperature model inputs and outputs for 68 lakes in the U.S. states of Minnesota and Wisconsin (http://dx.doi.org/10.5066/P9AQPIVD).

• DRTO_Grid.dbf 2017-05-12 10:32 2.2M DRTO_Grid.prj 2017-05-12 10:29 424 DRTO_Grid.sbn 2017-05-12 10:29 291K DRTO_Grid.sbx 2017-05-12 10:29 17K DRTO_Grid.shp 2017-05-12 10:29 4.0M DRTO_Grid.shp.xml 2017-12-18 11:07 21K DRTO_Grid.shx 2017-05-12 10:29 243K FlaKeys_Grid.dbf 2017-05-17 09:19 16M FlaKeys_Grid.prj 2017-05-17 09:01 424 FlaKeys_Grid.sbn 2017-05-17 09:01 666K FlaKeys_Grid.sbx 2017-05-17 09:01 10K FlaKeys_Grid.shp 2017-05-17 09:18 8.8M FlaKeys_Grid.shp.xml 2017-12-18 11:07 9.1K FlaKeys_Grid.shx 2017-05-17 09:18 528K SEFCRI_Grid_100m.dbf 2017-05-17 13:08 2.1M SEFCRI_Grid_100m.prj 2017-05-17 13:08 424 SEFCRI_Grid_100m.sbn 2017-05-17 13:08 224K SEFCRI_Grid_100m.sbx 2017-05-17 13:08 5.5K SEFCRI_Grid_100m.shp 2017-05-17 13:08 3.1M SEFCRI_Grid_100m.shp.xml 2017-12-18 11:07 8.4K SEFCRI_Grid_100m.shx 2017-05-17 13:08 188K

4 Analysis SBX DataSets including dbf, xml, shx, sbx, sbn, shp, zip and cpg file types.

The shapefile format is intended for geographic information systems (GIS). It contains all the information related to the geometry of the objects described. It is composed of three files with the same name, with the extensions SHP, DBF (attributes), SHX (geometry index) and PRJ (data projection system).

The file contains the all the lines of the national rail network.

The MNEMO column shows the status of each line: project (PROJECT), operated (OPERATED), neutralized (NEUT), neutralized and preserved (NEUT DEF), transferred to service track (VS), closed not removed (CLOSED ND), closed with the track maintained in place (CLOSED MV), closed and removed (CLOSED D), closed (CLOSED), closed made available to third parties (CLOSED DT ), withdrawn (RETRANCHE), declassified not sold (DEC NV), declassified sold (DEC V).

A line section is a physically continuous part of a line, delimited by two end nodes (origin and end) of line section, and having a coherent identification system. When there is a discontinuity, the line is divided into several sections, with an increasing rank.

The precision of the shapefile of the lines is decametric: use on a medium scale (1/50,000th).

This game publishes the data as of 12/31/2021.

date updated 11/16/2022

GIS Grid Files For The Sampling (NCEI Accession 0208321 and NCEI Accession 0208322)

  -  

DRTO_Grid.dbf 2019-12-20 07:14 2.2M
DRTO_Grid.prj 2019-12-20 07:14 424
DRTO_Grid.sbn 2019-12-20 07:14 291K
DRTO_Grid.sbx 2019-12-20 07:14 17K
DRTO_Grid.shp 2019-12-20 07:14 4.0M
DRTO_Grid.shp.xml 2019-12-20 07:14 21K
DRTO_Grid.shx 2019-12-20 07:14 243K
FlaKeys_Grid.dbf 2019-12-20...

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)

These data are a collection of benthic habitat data from studies conducted in the coastal Long Island Sound, NY region in GIS shapefile (.shp, .dbf, .shx, and .prj files) with associated Federal Geographic Data Committee (FGDC) metadata. Generalized browse graphics were generated by the NODC and are included with the data. Individual subdirectories include data as follows - 2002 Long Island South Shore Estuary Benthic Habitat Polygon Data Set, 1995 benthic grab, sediment grab, and sediment profile image GIS point data files from inland harbor bays (Jamaica Bay), and 1994-1995 benthic grab, sediment grab, and sediment profile image GIS point data files from lower inland harbor bays.

ZIP compressed file containing Shape files (SHP, DBF, SHX and PRJ) Reference system UTM32 - EUREF89

Mule deer home range data collected by GPS collars. Collected from 2015-2017 for the New Mexico Bureau of Land Management Taos Field Office. Each unique entry is one deer during one year, for a total of 23 entries. The point data was used to create minimum convex hulls depicting one deer-year's home range extent. This dataset includes all spatial data - CPG, DBF, XLSX, PRJ, SBN, SBX, SHP, and SHX files.

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)

Global Administrative Areas of Spain

Url with data from any country in the world http://www.gadm.org/country Format file: zip Inside zip files: shp, shx, csv, cpg, dbf, prj

Fields: OBJECTID ID_0 ISO NAME_0 ID_1 NAME_1 ID_2 NAME_2 HASC_2 CCN_2 CCA_2 TYPE_2 ENGTYPE_2 NL_NAME_2 VARNAME_2

URL zip http://biogeo.ucdavis.edu/data/gadm2.8/shp/ESP_adm_shp.zip

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)

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)

The shapefile format is intended for geographic information systems (GIS). It contains all the information related to the geometry of the objects described. It is composed of three files with the same name, with the extensions SHP, DBF (attributes), SHX (geometry index) and PRJ (data projection system).

The file contains the set of tracks of the national rail network.

A line section is a physically continuous part of a line, delimited by two end nodes (origin and end) of line section, and having a system consistent identification. When there is a discontinuity, the line is divided into several sections, with an increasing rank.

The precision of the track shapefile is metric: use at high scales (1/1000 to 1/5000)< /p>

The values ​​of the channel type column are as follows: VPL = Main Lines; VPA = Other Main Lanes; VS = Service route

This game publishes the data as it stands at the end of 2018.

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)

Large-scale_prediction_archiveThis compressed archive includes multiple other files including data files (in .rdata format) GIS shapefiles (in folders with the associated .shp, .shx, .dbf, and .prj files for each map) and an R script that will run all analyses and plot all figures. Specific descriptions of each file are supplied in the README.TXT file.