Skip to main content
U.S. flag

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Skip to content

Colorado River milage system and ancillary attribute data for connecting to hydrodynamic model output in Glen Canyon, AZ

Metadata Updated: October 29, 2025

These data were compiled to support stranding risk modeling of young-of-year rainbow trout in Glen Canyon resulting from fluctuating flows from Glen Canyon Dam, called Trout Management Flows (TMFs). The objective of our study was to evaluate the stranding risk associated with different TMFs. We used the results of a 2-dimensional hydrodynamic model (Wright and others, 2024) as input to a rainbow trout stranding model and described in the associated Larger Work Citation. This data table was developed to link the data output tables of Wright and others (2024) and the trout stranding model to a commonly used and standardized measure of distance along the Colorado River between Glen Canyon Dam and Lees Ferry, AZ (Gushue 2019). The data are organized based on the spatial coordinates of the center point of cells in the hydrodynamic model (Wright and others 2024). The data table represents spatial grid coordinates and locations to the nearest hundredth mile for each row and column of a bathymetry grid that are closest to the Colorado River centerline. The data table includes additional data values that represent bed elevations and distances of the center point for each selected bathymetry grid cell to the nearest Colorado River mile point location. Distances in miles follow a standard referencing system where miles are measured as negative values upstream from Lees Ferry (river mile 0) to Glen Canyon Dam (river mile -15.85). The 2-dimensional hydrodynamic model and trout stranding model described in the associated Larger Work Citation extend from river mile -0.02 to river mile -15.71. This data table provides a way to assign a Colorado River mile to each computational grid cell of Wright and others (2024) and the trout stranding risk model in the associated Larger Work Citation that we used to evaluate how flow influences depth, velocity, and stranding risk of Trout Management Flows. This table can be used by other studies to link the hydrodynamic model to the standard Colorado River reference system on the Colorado River in Glen Canyon.

Access & Use Information

Public: This dataset is intended for public access and use. License: No license information was provided. If this work was prepared by an officer or employee of the United States government as part of that person's official duties it is considered a U.S. Government Work.

Downloads & Resources

Dates

Metadata Created Date September 12, 2025
Metadata Updated Date October 29, 2025

Metadata Source

Harvested from DOI USGS DCAT-US

Additional Metadata

Resource Type Dataset
Metadata Created Date September 12, 2025
Metadata Updated Date October 29, 2025
Publisher U.S. Geological Survey
Maintainer
Identifier http://datainventory.doi.gov/id/dataset/usgs-64504179d34eefd5da8070a1
Data Last Modified 2024-07-16T00:00:00Z
Category geospatial
Public Access Level public
Bureau Code 010:12
Metadata Context https://project-open-data.cio.gov/v1.1/schema/catalog.jsonld
Metadata Catalog ID https://ddi.doi.gov/usgs-data.json
Schema Version https://project-open-data.cio.gov/v1.1/schema
Catalog Describedby https://project-open-data.cio.gov/v1.1/schema/catalog.json
Harvest Object Id 643df156-71e5-4106-84c9-863b3b331b6b
Harvest Source Id 2b80d118-ab3a-48ba-bd93-996bbacefac2
Harvest Source Title DOI USGS DCAT-US
Metadata Type geospatial
Old Spatial -111.6060823, 36.8400632, -111.4771889, 36.9401487
Source Datajson Identifier True
Source Hash be17a5395e6ea24315bab11964a6d636d8233d61060d09c57ebe99f46164327b
Source Schema Version 1.1
Spatial {"type": "Polygon", "coordinates": -111.6060823, 36.8400632, -111.6060823, 36.9401487, -111.4771889, 36.9401487, -111.4771889, 36.8400632, -111.6060823, 36.8400632}

Didn't find what you're looking for? Suggest a dataset here.