100+ datasets found
  1. T

    Utah Municipal Boundaries Cartography

    • opendata.utah.gov
    • opendata.gis.utah.gov
    • +3more
    application/rdfxml +5
    Updated Mar 20, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2020). Utah Municipal Boundaries Cartography [Dataset]. https://opendata.utah.gov/dataset/Utah-Municipal-Boundaries-Cartography/h4hr-3dht
    Explore at:
    csv, json, xml, application/rdfxml, tsv, application/rssxmlAvailable download formats
    Dataset updated
    Mar 20, 2020
    Area covered
    Utah
    Description

    These data were created for mapping usage, areas have been trimmed to the high water mark of Great Salt Lake and Utah Lake. Creates a clearer visual picture of the municipalities.

    Current thru June 30, 2017

  2. T

    Utah HUC Boundaries

    • opendata.utah.gov
    • opendata.gis.utah.gov
    • +3more
    application/rdfxml +5
    Updated Mar 20, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2020). Utah HUC Boundaries [Dataset]. https://opendata.utah.gov/dataset/Utah-HUC-Boundaries/6f24-ncdx
    Explore at:
    application/rssxml, xml, tsv, json, csv, application/rdfxmlAvailable download formats
    Dataset updated
    Mar 20, 2020
    Area covered
    Utah
    Description

    This data set is a subset of the complete digital hydrologic unit boundary layer to the Subwatershed (12-digit) 6th level for the State of Utah. The State Watershed Boundary (WBD) was dissolved to the 8 digit, 4th level sub-basin. The State WBD consists of geo-referenced digital data and associated attributes created in accordance with the "FGDC Proposal, Version 1.0 - Federal Standards For Delineation of Hydrologic Unit Boundaries 3/01/02"(http://www.ftw.nrcs.usda.gov/huc_data.html). Polygons are attributed with hydrologic unit codes for 4th level sub-basins, 5th level watersheds, 6th level subwatersheds, name, size, downstream hydrologic unit, type of watershed, non-contributing areas and flow modification. Arcs are attributed with the highest hydrologic unit code for each watershed, linesource and a metadata reference file.

  3. a

    LOA Hunt Boundaries

    • dwr-data-utahdnr.hub.arcgis.com
    • utahdnr.hub.arcgis.com
    Updated Jul 27, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah DNR Online Maps (2024). LOA Hunt Boundaries [Dataset]. https://dwr-data-utahdnr.hub.arcgis.com/datasets/loa-hunt-boundaries
    Explore at:
    Dataset updated
    Jul 27, 2024
    Dataset authored and provided by
    Utah DNR Online Maps
    Area covered
    Description

    Utah Landowner Association (LOA) Boundaries 2024

  4. TIGER/Line Shapefile, Current, State, Utah, County Subdivision

    • catalog.data.gov
    Updated Dec 15, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geospatial Products Branch (Point of Contact) (2023). TIGER/Line Shapefile, Current, State, Utah, County Subdivision [Dataset]. https://catalog.data.gov/dataset/tiger-line-shapefile-current-state-utah-county-subdivision
    Explore at:
    Dataset updated
    Dec 15, 2023
    Dataset provided by
    United States Census Bureauhttp://census.gov/
    Area covered
    Utah County, Utah
    Description

    This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

  5. 2022 Cartographic Boundary File (SHP), Current Census Tract for Utah,...

    • catalog.data.gov
    Updated Dec 14, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Customer Engagement Branch (Point of Contact) (2023). 2022 Cartographic Boundary File (SHP), Current Census Tract for Utah, 1:500,000 [Dataset]. https://catalog.data.gov/dataset/2022-cartographic-boundary-file-shp-current-census-tract-for-utah-1-500000
    Explore at:
    Dataset updated
    Dec 14, 2023
    Dataset provided by
    United States Census Bureauhttp://census.gov/
    Area covered
    Utah
    Description

    The 2022 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some states and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

  6. T

    Municipal Boundaries

    • opendata.utah.gov
    • hub.arcgis.com
    • +1more
    application/rdfxml +5
    Updated Aug 20, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2022). Municipal Boundaries [Dataset]. https://opendata.utah.gov/dataset/Municipal-Boundaries/e8k6-zy9k
    Explore at:
    xml, json, application/rdfxml, application/rssxml, csv, tsvAvailable download formats
    Dataset updated
    Aug 20, 2022
    Description

    Salt Lake County Municipal Boundaries, including Cities, Metro Townships and Unincorporated areas.


    Source:
    Salt Lake County Surveyor's Office

  7. TIGER/Line Shapefile, Current, State, Utah, Place

    • catalog.data.gov
    Updated Dec 15, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geospatial Products Branch (Point of Contact) (2023). TIGER/Line Shapefile, Current, State, Utah, Place [Dataset]. https://catalog.data.gov/dataset/tiger-line-shapefile-current-state-utah-place
    Explore at:
    Dataset updated
    Dec 15, 2023
    Dataset provided by
    United States Census Bureauhttp://census.gov/
    Area covered
    Utah
    Description

    This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census, but some CDPs were added or updated through the 2023 BAS as well.

  8. TIGER/Line Shapefile, Current, State, Utah, Census Tract

    • catalog.data.gov
    Updated Dec 14, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geospatial Products Branch (Point of Contact) (2023). TIGER/Line Shapefile, Current, State, Utah, Census Tract [Dataset]. https://catalog.data.gov/dataset/tiger-line-shapefile-current-state-utah-census-tract
    Explore at:
    Dataset updated
    Dec 14, 2023
    Dataset provided by
    United States Census Bureauhttp://census.gov/
    Area covered
    Utah
    Description

    This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

  9. a

    Utah Address Points Base map (WMTS)

    • hub.arcgis.com
    • opendata.gis.utah.gov
    • +1more
    Updated Feb 1, 2017
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah Automated Geographic Reference Center (AGRC) (2017). Utah Address Points Base map (WMTS) [Dataset]. https://hub.arcgis.com/maps/5b92021338f64f5ba77765d6fc47cbc9
    Explore at:
    Dataset updated
    Feb 1, 2017
    Dataset authored and provided by
    Utah Automated Geographic Reference Center (AGRC)
    Area covered
    Description

    AddressPoints is a statewide dataset that contains address point data from all 29 Utah Counties. This dataset is a work in progress and some counties are more complete than others. One person in each county has been identified as the Master Address List (MAL) Authority to eliminate duplication of address point data and clarify the main person of contact. AGRC is working with each MAL Authority to continually improve this data and work toward quarterly updates.

  10. d

    Utah County Data

    • search.dataone.org
    • beta.hydroshare.org
    • +1more
    Updated Dec 5, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Dan Ames (2021). Utah County Data [Dataset]. https://search.dataone.org/view/sha256%3Ad52e65d674118c9badf4ff7500d8a859ea14a186c1327639c74f05ca8ae9584b
    Explore at:
    Dataset updated
    Dec 5, 2021
    Dataset provided by
    Hydroshare
    Authors
    Dan Ames
    Area covered
    Description

    This dataset reflects the most current GCDB version of Utah county boundaries plus modifications made to correct known issues along the Davis-Weber and Duchesne-Uintah county boundaries. (20111108) and boundary agreement (certified 20120612) between Juab and Millard Counties.

  11. Digital Geohazard-GIS Map of the Zion National Park Study Area, Utah (NPS,...

    • catalog.data.gov
    Updated Nov 2, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Park Service (2024). Digital Geohazard-GIS Map of the Zion National Park Study Area, Utah (NPS, GRD, GRI, ZION, ZION_geohazards digital map) adapted from a Utah Geological Survey Special Study Map by Lund, Knudsen, and Sharrow (2010) [Dataset]. https://catalog.data.gov/dataset/digital-geohazard-gis-map-of-the-zion-national-park-study-area-utah-nps-grd-gri-zion-zion-
    Explore at:
    Dataset updated
    Nov 2, 2024
    Dataset provided by
    National Park Servicehttp://www.nps.gov/
    Area covered
    Utah
    Description

    The Digital Geohazard-GIS Map of the Zion National Park Study Area, Utah is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (zion_geohazards.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (zion_geohazards.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (zion_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (zion_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (zion_geohazards_metadata_faq.pdf). Please read the zion_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Utah Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (zion_geohazards_metadata.txt or zion_geohazards_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

  12. u

    Utah Terrain Base map

    • opendata.gis.utah.gov
    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    Updated Feb 1, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah Automated Geographic Reference Center (AGRC) (2017). Utah Terrain Base map [Dataset]. https://opendata.gis.utah.gov/maps/38a765a1306e4ba3804c0faaeede95e0
    Explore at:
    Dataset updated
    Feb 1, 2017
    Dataset authored and provided by
    Utah Automated Geographic Reference Center (AGRC)
    License

    http://www.utah.gov/disclaimer.htmlhttp://www.utah.gov/disclaimer.html

    Area covered
    Description

    Saved as a web map to be included in the basemap selector.

  13. K

    Utah Tribal Boundaries

    • koordinates.com
    csv, dwg, geodatabase +6
    Updated Jan 16, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    State of Utah (2023). Utah Tribal Boundaries [Dataset]. https://koordinates.com/layer/112180-utah-tribal-boundaries/
    Explore at:
    geodatabase, mapinfo tab, kml, pdf, mapinfo mif, geopackage / sqlite, csv, dwg, shapefileAvailable download formats
    Dataset updated
    Jan 16, 2023
    Dataset authored and provided by
    State of Utah
    Area covered
    Description

    Geospatial data about Utah Tribal Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

  14. d

    Utah Federal and Public Lands

    • datadiscoverystudio.org
    Updated Jul 25, 2012
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    The State of Utah School and Institutional Trust Lands Administration (2012). Utah Federal and Public Lands [Dataset]. http://datadiscoverystudio.org/geoportal/rest/metadata/item/11033c63659a4895b4c5ae1572ed6da6/html
    Explore at:
    Dataset updated
    Jul 25, 2012
    Dataset provided by
    The State of Utah School and Institutional Trust Lands Administration
    Area covered
    Description

    This dataset depicts the cooperative interagency 1:24,000 scale land ownership status for the State of Utah. Administrative ownership polygons are updated by The State of Utah School and Institutional Trust Lands Administration (SITLA) and the United States Bureau of Land Management (BLM) Salt Lake City office on a regular basis. Revisions are posted monthly. This data was originally digitized for the 1993 U. S. Fish and Wildlife Utah GAP Analysis project by the Remote Sensing and GIS Laboratories, Department of Geography and Earth Resources, Utah State University (RSGIS/USU). Maintenance of this data layer is performed by a cooperative federal and state effort. The Utah School and Institutional Trust Lands Administration (SITLA) revises this data regularly to reflect changes in State Trust Lands, other State Land and Private Land as needed. The BLM revises this data regularly to reflect changes in Federal Land as needed. Other information is edited and updated as needed but not on a regular schedule.

  15. d

    Utah Historical Boundaries

    • datadiscoverystudio.org
    Updated Jan 1, 1900
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Wetlands Reserve Program (1900). Utah Historical Boundaries [Dataset]. http://datadiscoverystudio.org/geoportal/rest/metadata/item/466e95c11dfc4bc7a1707b97e24aa381/html
    Explore at:
    Dataset updated
    Jan 1, 1900
    Authors
    Wetlands Reserve Program
    Area covered
    Description

    This document serves as the metadata for the Utah Historical Counties Dataset shapefile for use in a geographic information system (GIS).That file may be downloaded without charge from this Web site (www.newberry.org/ahcbp); see also Distribution_Information, below.

  16. T

    Roosevelt Hot Springs, Utah FORGE Geology Map and GIS Data

    • opendata.utah.gov
    • data.openei.org
    • +3more
    application/rdfxml +5
    Updated Feb 6, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2020). Roosevelt Hot Springs, Utah FORGE Geology Map and GIS Data [Dataset]. https://opendata.utah.gov/dataset/Roosevelt-Hot-Springs-Utah-FORGE-Geology-Map-and-G/j2i4-npmc
    Explore at:
    json, xml, csv, tsv, application/rssxml, application/rdfxmlAvailable download formats
    Dataset updated
    Feb 6, 2020
    Area covered
    Roosevelt
    Description

    This archive contains a geology map of the general Roosevelt Hot Springs region, both in PDF and ArcGIS geodatabase formats, that was created as part of the Utah FORGE project.

  17. a

    Utah Big Game Hunt Boundaries 2024

    • dwr-data-utahdnr.hub.arcgis.com
    • hub.arcgis.com
    Updated Jun 12, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah DNR Online Maps (2024). Utah Big Game Hunt Boundaries 2024 [Dataset]. https://dwr-data-utahdnr.hub.arcgis.com/maps/2e8d3f5a26d846bf9c3b4ad6010f82ba
    Explore at:
    Dataset updated
    Jun 12, 2024
    Dataset authored and provided by
    Utah DNR Online Maps
    Area covered
    Description

    2024 Big Game hunts (boundaries and corresponding hunts per boundary) as described in the Utah Big Game Guidebook. For general reference only. For more information on boundaries and hunts visit the Utah Hunt Planner and wildlife.utah.gov/hunting

  18. d

    TIGER/Line Shapefile, 2016, state, Utah, Current County Subdivision...

    • catalog.data.gov
    Updated Jan 15, 2021
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2021). TIGER/Line Shapefile, 2016, state, Utah, Current County Subdivision State-based [Dataset]. https://catalog.data.gov/dataset/tiger-line-shapefile-2016-state-utah-current-county-subdivision-state-based
    Explore at:
    Dataset updated
    Jan 15, 2021
    Area covered
    Utah
    Description

    The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2015, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs, delineated in 20 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

  19. S

    State of Utah Acquired Lidar Data - Wasatch Front

    • portal.opentopography.org
    • otportal.sdsc.edu
    • +4more
    raster
    Updated Mar 25, 2015
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    OpenTopography (2015). State of Utah Acquired Lidar Data - Wasatch Front [Dataset]. http://doi.org/10.5069/G9TH8JNQ
    Explore at:
    rasterAvailable download formats
    Dataset updated
    Mar 25, 2015
    Dataset provided by
    OpenTopography
    Time period covered
    Oct 18, 2013 - May 31, 2014
    Area covered
    Variables measured
    Area, Unit, RasterResolution
    Dataset funded by
    Utah Division of Emergency Management
    Federal Emergency Management Agency
    U.S. Geological Survey
    Salt Lake County Surveyors Office and partner cities
    Utah Geological Survey
    Description

    The State of Utah, including the Utah Automated Geographic Reference Center, Utah Geological Survey, and the Utah Division of Emergency Management, along with local and federal partners, including Salt Lake County and local cities, the Federal Emergency Management Agency, the U.S. Geological Survey, and the U.S. Environmental Protection Agency, have funded and collected over 8380 km2 (3236 mi2) of high-resolution (0.5 or 1 meter) Lidar data across the state since 2011, in support of a diverse set of flood mapping, geologic, transportation, infrastructure, solar energy, and vegetation projects. The datasets include point cloud, first return digital surface model (DSM), and bare-earth digital terrain/elevation model (DEM) data, along with appropriate metadata (XML, project tile indexes, and area completion reports).

    This 0.5-meter 2013-2014 Wasatch Front dataset includes most of the Salt Lake and Utah Valleys (Utah), and the Wasatch (Utah and Idaho), and West Valley fault zones (Utah).

    Other recently acquired State of Utah data include the 2011 Utah Geological Survey Lidar dataset covering Cedar and Parowan Valleys, the east shore/wetlands of Great Salt Lake, the Hurricane fault zone, the west half of Ogden Valley, North Ogden, and part of the Wasatch Plateau in Utah.

  20. K

    Utah Law Enforcement Boundaries

    • koordinates.com
    csv, dwg, geodatabase +6
    Updated Jan 16, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    State of Utah (2023). Utah Law Enforcement Boundaries [Dataset]. https://koordinates.com/layer/112189-utah-law-enforcement-boundaries/
    Explore at:
    dwg, mapinfo mif, geodatabase, geopackage / sqlite, shapefile, csv, kml, pdf, mapinfo tabAvailable download formats
    Dataset updated
    Jan 16, 2023
    Dataset authored and provided by
    State of Utah
    Area covered
    Description

    Geospatial data about Utah Law Enforcement Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
(2020). Utah Municipal Boundaries Cartography [Dataset]. https://opendata.utah.gov/dataset/Utah-Municipal-Boundaries-Cartography/h4hr-3dht

Utah Municipal Boundaries Cartography

Explore at:
csv, json, xml, application/rdfxml, tsv, application/rssxmlAvailable download formats
Dataset updated
Mar 20, 2020
Area covered
Utah
Description

These data were created for mapping usage, areas have been trimmed to the high water mark of Great Salt Lake and Utah Lake. Creates a clearer visual picture of the municipalities.

Current thru June 30, 2017

Search
Clear search
Close search
Google apps
Main menu