AndreaBozzo/ceres-open-data-index huggingface dataset:
Bus Stop Ridership Table

Utah Transit Authority Bus stop boardings and alightings Table. The average daily number for boardings and alightings are calculated by the average of monthly samples at each stop. The dataset also includes Stop Abbreviation, Month, Year, City, County, XY, Service Type (Weekday, Saturday, Sunday) and Routes served at each stop. For spatial stop data, see UTA's feature layer called [UTA Stops & Most Recent Ridership.]
UTA Stops and Most Recent Ridership

Feature Layer includes all stops for bus, Light Rail (TRAX) and Commuter Rail (FrontRunner). Includes: Stop Name, City, Zip Code, County, Routes served, Stop Number (Integer), Stop Abbreviation (Text), Mode (Bus or Rail), Average Weekday Boarding and Alightings, and the Latitude/Longitude of the stop. * Stop locations are updated 3 times a year (typically April, August, and December). * Weekday ridership values (AVGBoard, AVGAlight) are updated monthly. AVG Boarding (Detail) and AVG Alighting (Detail) show ridership numbers in decimal format. * Stop Number (UTA_StopID) represents the numeric stop numbers. * Stop Abbreviation (StopAbbr_J) describes the type of stop: Numeric Values: Regular Bus Stop; Beginning with BB: Bus Bay; Beginning with FR: FrontRunner Station; Beginning with TX: TRAX Station; Beginning with S: Ski Stop; Beginning with MT: Microtransit; Beginning with F: Flex Route Stop Average weekday boardings and alightings are updated monthly after the 10th of the following month. Boarding and Alightings are not currently available for Flex (F) Routes.
UTA Routes and Most Recent Ridership

Feature Layer includes all routes for bus, Light Rail (TRAX), Streetcar (S Line) and Commuter Rail (Frontrunner). Includes: Route Number, route name, frequency in minutes, route type, average weekday ridership, and all cities and counties the route services. Routes are updated 3 times a year (typically April, August, and December). Weekday ridership values (AvgBrd) are updated monthly after the 10th of the following month.
Utah Oil and Gas Fields

This layer is updated on a yearly basis as a response to R649-2-7 - Naming of Oil and Gas Fields or Pools. The division shall name oil and gas fields or pools within the state in cooperation with a Fields Names Advisory Committee and with due regard and consideration for any recommendation from the owners or operators of such fields or pools. The Field Names Advisory Committee shall be composed of a representative of the United States Bureau of Land Management and representatives of appropriate state agencies and the oil and gas industry.For information, including PROD_FORM codes, please see the [SGID datapage] for this item.
UTA FrontRunner Commuter Rail Route Centerline

Centerline of UTA's FrontRunner Commuter Rail from Ogden in the north to Provo in the south. This centerline is the Main (M1) track. Siding Track (S) is not included. Includes FrontRunner North and South lines. Each line begins at MP 0.0 at Salt Lake Central Station. Milepost ascending on FrontRunner North from SL Central station to Ogden. Milepost ascending for FrontRunner South from SL Central Station to Provo.
Utah Broadband Service Areas

These service area polygons are derived from the FCC's [National Broadband Map]. Data are downloaded monthly from the BDC API, aggregated to the H3 level 8 polygons identified in the data, and then spatially dissolved to create individual polygons for each provider's technologies and max advertised speeds. Thus, each polygon represents the area a particular provider claims served by a given technology and up/down speeds. Because the data are aggregated by H3 ID and max speeds advertised by the provider for the given tech, each hexagon in the service area has at least one location where the provider advertises those speeds and technology. It does not guarantee all locations in that hexagon have that advertised service. The FCC data are updated on a [twice-yearly schedule]. We update monthly to catch any mid-cycle updates that may be released. Individual availability records are based on the “[Location Fabric],” which is a collection of Broadband Serviceable Locations (BSLs) that identify individual locations that are served by mass-market broadband service or could conceivably order mass-market broadband service. This fabric is created and owned by a third-party consultant and licensed to the FCC and participating entities. This license prevents sharing the locations of the BSL to non-licensees but does allow aggregated data to be shared; hence why we aggregate the data to H3 level 8 polygons.
Utah Stream Alteration Points

Section 73-3-29 of the Utah Code requires any person, governmental agency, or other organization wishing to alter the bed or banks of a natural stream to obtain written authorization from the State Engineer prior to beginning work.

The Stream Alteration Program was implemented in 1972 in order to protect the natural resource value of the state’s streams and protect the water rights and recreational opportunities associated with them. The U.S. Army Corps of Engineers issued Programmatic General Permit 10 (PGP-10) which allows an applicant to obtain both state approval and authorization under Section 404 of the Clean Water Act though a single application process. Although not all stream alteration activities qualify for approval under PGP-10, many minimal impact projects can be approved under this joint permit agreement.
Measurement Stations

Add to Favorites
 Edit
The Utah Division of Water Rights (DWRi) maintains records of water diversion from surface and underground sources included in water distribution systems within the state. There are 44 active river distribution systems across the state, each of which is managed by a River Commissioner. Some have automated systems to measure water diversion/use and/or operate controls. Distribution systems are organized either through a court order or by the State Engineer. The scope of DWRi’s measurement data includes approximately 1,1200 active surface water diversion stations with approximately 500 of those having automated data telemetry and data loggers. These monitoring sites are operated by DWRi or by many partner organizations to provide Utah’s water use data infrastructure, and the data produced serve as the basis on which water rights and water distribution accounting decisions are made daily. The dataset includes 79 stream gages (out of the 1,200 stations) operated by the United States Geological Survey (USGS) in various parts of the state
Utah DDW Source Water Assessment Zones for TNC Systems

The source water assessment zones (TransientNCZones) have been developed by the Utah Division of Drinking Water for "existing groundwater" sources (as defined by the UAC R309-600 Rule) for transient non-community systems. "Existing ground-water source" of drinking water means a public supply ground-water source for which plans and specifications were submitted to the Utah Division of Drinking Water on or before July 26, 1993 [Utah Administrative Code, R309-600-6(1)(k)].
Utah DDW Surface Water Source Protection Zones

These data represent the Drinking Water Source Protection (DWSP) zones for surface water sources operated by Public Water Systems (PWS) in Utah. These zones have been delineated by PWS to comply with the requirements of Utah Administrative Code (UAC) Rule R309-605. Zone 1: (A) Streams, rivers and canals: zone 1 encompasses the area on both sides of the source, 1/2 mile on each side measured laterally from the high water mark of the source (bank full), and from 100 feet downstream of the POD to 15 miles upstream, or to the limits of the watershed or to the state line, whichever comes first. If a natural stream or river is diverted into an uncovered canal or aqueduct for the purpose of delivering water to a system or a water treatment facility, that entire canal will be considered to be part of zone 1, and the 15 mile measurement upstream will apply to the stream or river contributing water to the system from the diversion. (B) Reservoirs or lakes: zone 1 is considered to be the area 1/2 mile from the high water mark of the source. Any stream or river contributing to the lake/reservoir will be included in zone 1 for a distance of 15 miles upstream, and 1/2 mile laterally on both sides of the source. If a reservoir is diverted into an uncovered canal or aqueduct for the purpose of delivering water to a system or a water treatment facility, that entire canal will be considered to be part of zone 1, and the 15 mile measurement upstream will apply to the reservoir and tributaries contributing water to the system. Zone 2: Zone 2 is defined as the area from the end of zone 1, and an additional 50 miles upstream (or to the limits of the watershed or to the state line, whichever comes first), and 1000 feet on each side measured from the high water mark of the source. Zone 3: Zone 3 is defined as the area from the end of zone 2 to the limits of the watershed or to the state line, whichever comes first, and 500 feet on each side measured from the high water mark of the source. Zone 4: Zone 4 is defined as the remainder of the area of the watershed (up to the state line, if applicable) contributing to the source that does not fall within the boundaries of zones 1 through 3.
Utah_Distribution_Systems

Site Type- The purpose of this database field is to categorize the hydrologic feature being observed and measured. * Conveyance - flow in a human-constructed conveyance work such as a canal or pipeline * Stream - flow in a natural channel * Reservoir - the elevation, contents, or surface area of a reservoir or pond * Dry Dam Release - flow past a diversion dam constructed across the streambed * Reservoir Release - flow from a reservoir into the natural stream; note that a site measuring flow in a conveyance work coming directly from a reservoir should be categorized as a conveyance * Well - flow from a well measured before any conveyance splitting; flow from a well measured after a conveyance split should be categorized as a conveyance * Hydropower - flow that transfers water energy to a rotating shaft to produce power * Unknown - indicates the person evaluating the observation station could not determine the site type * N/A - for all stations that are not observations * Unevaluated (default) - indicates this field has not yet been evaluated
Generalized Future Land Use (MAG 2024, WFRC 2020)

This data presents a generalized view of local land use plans along Utah's Wasatch Front. Each city's most recent general plan was interpreted in 2020 to provide a best match to a set of common, simplified land use codes. Where general plan information was not available, current zoning designations were used as a proxy. Data sources for this map are described in this table. For the most current, detailed land use plans, please consult the city-specific dataset links and city planning offices. This data was developed to provide general context for transportation and other regional planning applications. WFRC and MAG use generalized land use information as an input for its Real Estate Market Model (REMM). REMM is used to project the location of future development intensity, including household and job growth, in future years and decades.
Generalized Future Land Use (MAG and WFRC 2025)

This map presents a generalized view of local land use plans along Utah's Wasatch Front. Each city's most recent general plan was collected in late 2024 or early 2025 and interpreted to provide a best match to a set of common, simplified land use codes Where general plan information was not available, current zoning designations were used as a proxy. Data sources for this map can be found using the Data Source Link in the map pop-ups. For the most current, detailed land use plans, please consult the city-specific dataset links and city planning offices. This map was developed to provide general context for transportation and other regional planning applications. WFRC and MAG use generalized land use information as an input for its Real Estate Market Model (REMM). REMM is used to project the location of future development intensity, including household and job growth, in future years and decades.
Utah Water Diversion Monitoring Stations

Overview This feature service provides detailed spatial data on water diversion stations managed within the state of Utah. It includes information essential for monitoring water diversion from natural streams, constructed conveyance systems, and reservoirs, supporting water rights administration and distribution accounting. Feature Layers * Diversion Stations: This layer represents active water diversion stations across Utah. It includes station identification, names, associated water systems, current operational status, and recent measurement readings. These stations are vital points for real-time water diversion monitoring and management. * Inactive Diversion Stations: This layer captures diversion stations that are no longer active. It provides essential historical data including station identifiers, names, and system associations, which are important for legacy water resource records and analysis. Geographic Coverage The dataset covers water diversion stations throughout Utah, encompassing a range of water systems from surface water diversions to conveyance works across various regions within the state. Use Cases * Supports water resource management and regulation by the Utah Division of Water Rights. * Enables tracking and reporting of water diversion activities for legal and environmental compliance. * Assists water system operators and hydrologists in monitoring water usage and infrastructure status. Additional Information The data is licensed by the Utah Division of Water Rights and comes with no warranty. The information is intended to aid water rights enforcement and water system oversight rather than serve as a legal land survey record.
Utah Petroleum Storage Tanks Facilities

This dataset is updated nightly from the DERR Salesforce database which is continually updated. This data layer contains coordinates of Facility PST sites. There can be multiple tanks for each facility. Each storage tank is associated with a facility via the DERRID (Alt Facility ID) (the number that uniquely identifies a facility). The coordinate data have been created and utilized by the Utah Division of Environmental Response and Remediation (DERR) for the plotting of Facility PST sites on maps depicting the state and several counties. The data used to produce these maps have been reviewed by DERR staff and found to be adequate for DERR’s purposes which require the depiction of general site locations. The accuracy of these locations may not be sufficient for other purposes. Persons relaying upon these maps do so at their own risk. The DERR assumes no responsibility or liability oft he accuracy of these points. Additional tank information can be found in these related tables: [Tanks], [Compartments], and [Releases].
Utah Quaternary Faults

The Utah Geological Survey Quaternary Fault and Fold Database and Map of Utah is a compilation of existing information on faults and fault-related folds considered to be potential earthquake sources (i.e., “active” faults and folds). The faults and folds contained in the database are those considered to have been sources of large earthquakes (about magnitude 6.5 or greater) during the Quaternary Period (past 2.6 million years); these geologic structures are the most likely sources of large earthquakes in the future. The database is intended to be a comprehensive source of the most current information available for characterizing active faults and folds in Utah for seismic-hazard analysis. This version of the database incorporates fault data from geologic maps and other documents formally published through 2020, along with several additional faults. More information on faults and earthquake hazards in Utah is available at http://geology.utah.gov/hazards/earthquakes-faults/utah-faults.The database was compiled and attributed using ESRI ArcGIS geographic information system software. In general, the database attribute conventions follow those of the Quaternary Fault and Fold Database of the United States maintained by the U.S. Geological Survey (USGS).
Utah Inland Port Authority Project Areas

This polygon layer contains the project area name, county (or counties), acreage, and an approximate date the area was last updated. The layer name includes the date July 17, 2025: this is the date the layer was initially compiled. Updates to this layer are carried out as new data is made available. Boundaries included in this dataset are approximate only and are not for legal boundary delineation. You can learn more about the Utah Inland Port Authority on https://inlandportauthority.utah.gov/.
Utah Agricultural Protection Areas

Last Updated: 3/31/2026 This layer compiles Utah property parcels that have been included in an Agriculture Protection Area (APA) resolution. APAs are approved by the county in which they are located, and catalogued by Utah Department of Agriculture and Food. APAs provide legal protection for agricultural land uses and activities, it also provides notice to neighboring landowners that they border an APA and should expect normal agricultural activities to take place. Not every county has created APAs; Sanpete and Sevier Counties have created APAs, but they are currently not included in this dataset. APA's are covered under Utah state code (17-41) [https://le.utah.gov/xcode/Title17/Chapter41/17-41-S101.html].
Utah Dam Safety and River Cross-Section Data

Overview This feature service provides comprehensive geospatial data related to dam safety, flood risk, and river hydrology within the State of Utah. It integrates multiple layers capturing critical information about dam locations, potential inundation zones from dam breaches, river cross sections, and inspection status of dams to support water resource management and emergency planning efforts. Feature Layers * Dam Inventory: This point feature layer details dam locations statewide, sourced from the Utah Division of Water Rights Dam Safety Regulatory Database. It includes information such as dam identification, condition ratings, and inspection records, offering essential data for monitoring dam safety and regulatory compliance. * Dam Inundation Zones: Represented as polygons, this layer models potential flood extents resulting from catastrophic dam failures. These worst-case scenarios are derived from Emergency Action Plans and provide critical insights for emergency management, evacuation planning, and risk assessment concerning downstream flood hazards. * River Cross Sections Data: This polyline layer depicts detailed river cross sections across various segments, containing hydrological measurements like flow depth, discharge rates, and water surface elevation under different conditions. These data support hydrologic analyses, environmental studies, and flood modeling to inform infrastructure design and environmental impact assessments. * Uninspected Dams Overview: This point layer identifies dams within Utah that have not undergone recent inspections. It highlights dams requiring attention for safety assessments and prioritization, aiding government agencies and engineers in resource allocation for inspection scheduling and risk mitigation. Geographic Coverage The data collectively cover the entire State of Utah, providing vital information specific to regional dam safety, flood risks, and river characteristics within this geography. Use Cases * Supports water resource managers and engineers in evaluating dam integrity and river dynamics. * Assists emergency planners and public safety officials in flood risk visualization and evacuation planning. * Facilitates environmental scientists with detailed hydrologic profiles for habitat and impact studies. * Aids regulatory agencies in prioritizing dam inspections and maintaining updated safety records.
AADT Rounded

This layer contains traffic statistics collected or obtained by the Transportation Monitoring Unit and developed and analyzed by the [Traffic Analysis section ]of the Technology & Innovation Division at the Utah Department of Transportation. These statistics are intended for transportation management, private businesses, and public use. The traffic information is used in planning, programming, highway design, maintenance, traffic control, and general administration of highway systems. The traffic information contained represents the Annual Average Daily Traffic (AADT) on road sections of State Highway and Federal-Aided roads. These statistics are developed by the Traffic Analysis section through the use of the following count site types: 1. Continuous Count Stations (CCS) provided by the Utah Department of Transportation. A statewide system of permanent vehicle count stations that collect volume, vehicle classification (length), and speed, 24 hours per day, 365 days per year. 2. Short-term counts administered by the Utah Department of Transportation, each traffic section is generally counted about every 3 years for a duration of 48 hours, and seasonally factored using factors created by CCS stations. AADT represents traffic for both directions of travel. The routes are sectioned according to: a. Major intersections b. Sections where traffic volumes show a significant difference in AADT. Generally 20% under 5,000 AADT to 5% for over 50,000 AADT. Truck Statistics are available for State routes only. Single-Unit Truck (FHWA Vehicle Axle Classifications 4-7), and Combination Unit Trucks (FHWA Vehicle Axle Classifications 8-13). The values are represented by a percentage of the AADT reported for the same year. Example: A roadway with 1000 AADT has 0.1500 SUTRK reported, is 15% of the AADT are Single-Unit Trucks (or 150 SUTRK AADT). For AADT reported as Rounded, reports and maps use the AASHTO recommendation as follows: AADT = 0 - 999: Round to the nearest 10th AADT = 1,000 - 9,999: Round to the nearest 100th AADT >= 10,000: Round to the nearest 1000th NOTE: If a statistical calculation is needed to be applied to the AADT, (such as when calculating Vehicle Miles Traveled), it is not recommended to use rounded AADT’s. Unrounded AADT’s and truck percentages for are available at [UDOT's Open Data Portal] for download. This service is specially configured for use with [UDOT's Open Data Portal]. Please see the [Data Assessment Form] for more information. To download either the Rounded or Unrounded AADT for this data please visit the UDOT Open Data Portal and download the available Shapefile and CSV's.