AndreaBozzo/ceres-open-data-index huggingface dataset:
Utah EMS Response Areas

Last update: 06/29/2026 Overview This polygon data was created to represent Emergency Medical Service (EMS) response areas in Utah for the Next-Generation 911 system (NG911). It depicts the primary EMS response agency for a given location in Utah and was compiled from a variety of data sources. The response areas represent a variety of service levels (paramedic, advanced EMT, with or without transport capability, etc.), but generally include 911 scene response. The data was compiled using written descriptions from the licensing database of the Bureau of Emergency Medical Services and Preparedness ([BEMSP]), which is part of the Utah Department of Health and Human Services (DHHS). In some instances, the BEMSP data was incomplete or the written descriptions were inaccurate, contradictory, ambiguous, or failed to close. To make the data more complete, computer-aided dispatch (CAD) data from within the state was used to resolve conflicts, fill in gaps, and improve completeness. Field Descriptions Most of the fields are based on the National Emergency Number Association's (NENA) [Standard for NG911 GIS Data Model]. More information can be found on the UGRC data page for this layer: [https://gis.utah.gov/data/society/public-safety/]
Utah Law Enforcement Locations

The US Bureau of Justice Statistics describes law enforcement agencies as "publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This dataset includes point locations for federal, state, local, and special jurisdiction law enforcement agency facilities. This dataset was created to provide a general purpose database of law enforcement facility locations. Law enforcement facility data can been used to asses whether the total police capability of a given area is adequate and to help local governments identify areas of greatest concern. The data are also a helpful resource for situational awareness planning, emergency response, and route analysis. A version of this data is also used to map [Firearm Safe Harbor Storage Locations]. The points in this dataset indicate the locations of law enforcement facilities (police stations, sheriff's offices, etc.) throughout the state of Utah. Each point includes attributes such as the facility name, street address, contact information, city, zip, county, and coordinates. Points have been placed on or near the main structure of the facility. UGRC originally derived this dataset from the Homeland Infrastructure Foundation-Level Data (HIFLD) database maintained by the [US Bureau of Justice Statistics]. The primary source for this database was the 2008 Census of State and Local Law Enforcement Agencies. The data are currently maintained by UGRC in collaboration with the Department of [Public Safety's Bureau of Criminal Identification (BCI)].
Utah Bikeways

The Utah Bikeways dataset provides a detailed representation of on-street and pathway bikeway features in the state and serves as a comprehensive resource for understanding the state's cycling infrastructure. The data includes various attributes such as the name of the bikeway, the city and county it traverses, and specific details about the facility type (e.g., dedicated bike lanes, shared-use paths). It also includes an estimated Level of Traffic Stress (LTS) score and the source of the data. The Utah Bikeways data is intended for planning, analysis, and visualization of planned cycling routes and infrastructure at various scales within Utah. Users should be aware that while efforts are made to keep the data current, recent changes in infrastructure are not immediately reflected. Data updates are sourced through periodic coordination between transportation agencies (UDOT and Utah's four MPOs), local government GIS and active transportation contacts, and through user submissions with the [Utah Bikeways] app. The Bikeways data is maintained within two separate statewide editing layers stewarded by UGRC -- [Roads] and [Trails and Pathways]. This more user-friendly dataset is derived by UGRC using a [python script] that combines bike facilities in the two editing layers. It merges and formats the data into a single schema, determines the best bike feature, and which side of the road the best feature is on. The script also calculates a [Level of Traffic Stress ]metric that represents the amount of discomfort people feel when they ride their bicycles near traffic. Finally, the data is split into existing and planned features, for use in the [Utah Bikeways] app.
Utah Planned Bikeways

The Utah Bikeways dataset provides a detailed representation of planned on-street and pathway bikeway features in the state and serves as a comprehensive resource for understanding the state's cycling infrastructure. The data includes various attributes such as the name of the bikeway, the city and county it traverses, and specific details about the facility type (e.g., dedicated bike lanes, shared-use paths). It also includes an estimated Level of Traffic Stress (LTS) score and the source of the data. The Utah Planned Bikeways data is intended for planning, analysis, and visualization of planned cycling routes and infrastructure at various scales within Utah. Users should be aware that while efforts are made to keep the data current, recent changes in infrastructure are not immediately reflected. Data updates are sourced through periodic coordination between transportation agencies (UDOT and Utah's four MPOs), local government GIS and active transportation contacts, and through user submissions with the [Utah Bikeways] app. For current/existing features, users should use the Utah Bikeways dataset. The Planned Bikeways data is maintained within two separate statewide editing layers stewarded by UGRC -- [Roads] and [Trails and Pathways]. This more user-friendly dataset is derived by UGRC using a [python script] that combines bike facilities in the two editing layers. It merges and formats the data into a single schema, determines the best bike feature, and which side of the road the best feature is on. The script also calculates a [Level of Traffic Stress ]metric that represents the amount of discomfort people feel when they ride their bicycles near traffic. Finally, the data is split into existing and planned features, for use in the [Utah Bikeways] app.
{Deprecated} Utah Lake Monitoring (Mature Support)

NOTE: This dataset is an older dataset that we have removed from the SGID and 'shelved' in ArcGIS Online. There may (or may not) be a newer vintage of this dataset in the SGID. NOTE: This dataset has been replaced by `SGID.ENVIRONMENT.DWQMonitoringLocations` and will be deleted on or after April 2, 2024. See here for more info: https://github.com/agrc/porter/issues/299. Contains locations of 729 lakes in Utah monitored for water quality by the Division of Water Quality (Department of Environmental Quality). Each location is a point, which is located within the lake's high water level shoreline.
{Deprecated} Utah Lake Monitor Sites (Mature Support)

NOTE: This dataset is an older dataset that we have removed from the SGID and 'shelved' in ArcGIS Online. There may (or may not) be a newer vintage of this dataset in the SGID. This data set represents lake water qality monitoring sites based on the generation of points from latitude, longitude coordinates furnished by the Utah Department of Environmental Quality, Division of Water Quality (DWQ).
{Deprecated} Utah Unique House Senate 2002

NOTE: This dataset is an older dataset that we have removed from the SGID and 'shelved' in ArcGIS Online. There may (or may not) be a newer vintage of this dataset in the SGID. Updated to include legislative districts modifications made in state code to accomodate the 2006 change in the Salt Lake - Utah County boundary in the Traverse Ridge area. Polygons that approximate the boundaries of districts where constituents have the same Utah House of Representatives legislator, the same Utah Senate legislator, and the same US House congressperson. For district scheme beginning with the 2002 elections. This dataset is based, where possible, on high accuracy representations of the street centerlines used to delimit these boundaries. The initial release of this data was based on US Census TIGER 2000 centerlines that had a lower level of positional accuracy.
Utah Senate Districts 2012 to 2022

NOTE: This dataset is an older dataset that we have removed from the SGID and 'shelved' in ArcGIS Online. There may (or may not) be a newer vintage of this dataset in the SGID. This dataset includes the political districts used for the Utah State Legislature. Utah’s 2012 State Senate Districts have been used for election purposes beginning January 1, 2012. Elected officials began representing these districts in January 2013. These boundaries supersede the State Senate Districts that were used in 2002-2011. Boundaries were initially created using Census Block Assignment files. Boundaries were moved around residences as per SB 3005 (2011 Third Special Session). Changes were made as per SB 125 (2012 general session) wherein county clerks requested changes be made to political boundaries to align with local boundaries or to prevent small voting precincts. This bill also allowed political boundaries to be moved to accurately represent municipal boundaries.
Utah Soils Deprecated

NOTE: This dataset is an older dataset that we have removed from the SGID and 'shelved' in ArcGIS Online. There may (or may not) be a newer vintage of this dataset in the SGID. NOTE: This dataset holds 'static' data that we don't expect to change. We have removed it from the SDE database and placed it in ArcGIS Online, but it is still considered part of the SGID and shared on opendata.gis.utah.gov.
Utah Natural Gas Service Areas Approx

This dataset is a work in progress. AGRC will work with Division of Public Utilities staff to expand the content to include all natural gas supplying utilities within Utah. The purpose is to show where Natural Gas is currently available or potentially available. Existing natural gas service lines were buffered to depict approximate service areas, additional service areas to be added in the future. Current August 2013 Added non-Questar areas in December 2015.
Utah HUC Boundaries

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. Data downloaded from USDA on 8/14/2017.
Utah Streams NHD

This dataset has be derived from the National Hydrologic Dataset (NHD). The derivation and modification process has been performed by AGRC to provide a general purpose feature class of water bodies for cartographic purposes. Four fields have been added to this feature class (FType_Text, FCode_Text, InUtah, IsMajor, and Submerged) and features have been split at the state boundary.The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.
Utah Lakes NHD

This dataset has be derived from the National Hydrologic Dataset (NHD). The derivation and modification process has been performed by AGRC to provide a general purpose feature class of water bodies for cartographic purposes. Four fields have been added to this feature class (FType_Text, FCode_Text, InUtah and IsMajor) and features have been split at the state boundary.The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.
Utah Major Lakes

These data were extracted from the NHD in order to better represent the 1:24,000 major lakes of Utah. The below abstract is from the High Resolution NHD metadata. The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.
Utah Major Rivers Polygons

These data were extracted from the NHD in order to better represent the major rivers wider than 10 feet in Utah The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.
Utah Great Salt Lake Flooding

This dataset represents the Flood Plain Management Services Study (FPMS) ares, 100-Year Flood for the Great Salt Lake. The area included Salt Lake City, Davis, Weber, tooele and box elder County The information was collected by digitzing the quad maps (Salt Lake, Tooele, boxelder county) and plat maps (weber and Davis county). The digital data contain the zone boundary and shoreline boundary. The FPMS study was limited to the general area along the Salt Lake County shoreline of the Great Salt Lake Only the 100-year flood elevation was evaluated and included wind and wave action for the Great Salt Lake. This dataset is the most current digital information available.
Utah Great Salt Lake Shoreline Flooding

This dataset represents the Flood Plain Management Services Study (FPMS) ares, 100-Year Flood for the Great Salt Lake. The area included Salt Lake City, Davis, Weber, tooele and box elder County The information was collected by digitzing the quad maps (Salt Lake, Tooele, boxelder county) and plate maps (weber and Davis county). The digital data contain the zone boundary and shoreline boundary. The FPMS study was limited to the general area along the Salt Lake County shoreline of the Great Salt Lake Only the 100-year flood elevation was evaluated and included wind and wave action for the Great Salt Lake. This dataset is the most current digital information available.
Utah NHD Points All

This dataset has be derived from the National Hydrologic Dataset (NHD). The derivation and modification process has been performed by AGRC to provide a general purpose feature class of water bodies for cartographic purposes. Three fields have been added to this feature class (FType_Text, FCode_Text, and InUtah) and features have been split at the state boundary.The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.
Utah Springs NHD

This dataset has be derived from the National Hydrologic Dataset (NHD). The derivation and modification process has been performed by AGRC to provide a general purpose feature class of water bodies for cartographic purposes. Three fields have been added to this feature class (FType_Text, FCode_Text, and InUtah) and features have been split at the state boundary.The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.
Utah Stream Gauges NHD

This dataset of stream gauges has be derived from the National Hydrologic Dataset (NHD) NHDPointaEventFC. The derivation and modification process has been performed by AGRC to provide a general purpose feature class of water bodies for cartographic purposes. The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.
Utah Great Salt Lake Water Level 2016

Last updated: May 3, 2022 This dataset was derived from the breakline features associated with the [2016 Great Salt Lake LiDAR project]. To create this dataset the Lake Pond features were extracted from the GreatSaltLake_Breaklines shapefile and converted into polygons. All polygons outside of the main north and south arms of the lake were removed. The Elevation_m (elev_m) & Elevation_ft (elev_ft) values represent the elevation of the water when the LiDAR was acquired. More information can be found on the UGRC data page for this layer: [https://gis.utah.gov/data/water/gsl-resources/]
Utah PLSS Quarter Sections GCDB

PLSSQuarterSections_GCDB is the third level of a hierarchical breakdown of the Public Land Survey System Rectangular surveys. This data is Version 2.3 2020 of the Utah PLSS Fabric. This data set represents the GIS Version of the Public Land Survey System. Updates are expected annually as horizontal control positions from published sources and global positioning system (GPS) observations are added. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. This data was originally published on 1/3/2017. This is no longer a standard and is now published as a Reference layer. This data is derived from the Second Division of the PLSS which includes quarter, quarter-quarter, sixteenth or government lot division of the PLSS. Updates were made to Quarter Sections in Utah County to add quarter sections to areas that were not broken down less than the Section level. They were added using information from points collected by county surveyors, that is in the data and extrapolating information from adjoining sections wherever possible. They are still areas that could not be interpreted well enough and they were left empty, beyond the section level. Quarter Sections were consolidated from the Quarter Quarter Sections to better represent the four quarters in all Aliquot Part areas. Areas with Lots or Special Surveys remain as is. Updated 4/8/2022