Paul J. Kinzel Amanda R. Whaling 20260326 data compilation Kinzel, P.J., and Whaling, A.R., 2026, ScienceBase river bathymetry surveys in GeoPackage format, U.S. Geological Survey data release, https://doi:10.5066/P144IY7E. https://doi.org/10.5066/P144IY7E At present, 2026, USGS river bathymetry surveys in ScienceBase lack a consistent, standardized organizational structure which impedes discovery and use of these datasets. Standardization of USGS bathymetry surveys allows these data to be more easily identified, queried, and incorporated into any number of science applications across a range of spatial scales. This data release includes river bathymetry data published in ScienceBase that have been subsequently standardized into the GeoPackage format. A GeoPackage is an open-source geospatial format that can store both raster and vector files. The hydrographic address of the data is stored in the GeoPackage to enable queries of position relative to streamgages or upstream or downstream flow directions. Each GeoPackage is organized with a common set of logical relationships or schema. The schema used herein consists of multiple tables. A data table, as the name implies, contains the data itself in X, Y, Z format. The geometry table contains hydrographic addressing information derived from the minimal geospatial format necessary to represent data coverage, such as a coverage polygon or a line representing a cross-section that provides more spatial fidelity than a simple bounding box. Finally, a metadata table contains the column definitions, units, projection, and ellipsoid information required to perform batch projection and datum transformations of the datasets. This dataset is anticipated to be updated and versioned as additional bathymetry datasets are created, discovered, and processed into GeoPackages. The data release includes the following files: 1) The RiverSurvey Data Complier V103. This Microsoft Excel document contains visual Basic for Applications (VBA) macros that facilitate conditioning and formatting river survey data sets discovered on ScienceBase. 2) input_files.zip - this zip archive contains files generated from the RiverSurvey Data Compiler V103. For each of the 50 ScienceBase river bathymetry data sets that were processed with the RiverSurvey Data Compiler, a comma delimited text file and a Microsoft Excel macro worksheet were generated. These file names correspond to the ScienceBase identifier associated with a bathymetry data set. The 50 comma delimited files are used as input to a script that creates the associated GeoPackage. 3) GeoPackages.zip - this zip archive contains the GeoPackages. Each GeoPackage contains the data table, geometry table, and a metadata table. 4) v103_summary_results.csv - this comma delimited text file contains a summary of the 50 ScienceBase river bathymetry data sets that were processed to GeoPackages. Fields in this file include: the title of the ScienceBase data release, the ScienceBase item_id, a file path, the number of partitions, and the type of file partitioning. 5) SB_GeoPackage_Schema.json - this json file defines the schema used in each table in the GeoPackages and provides examples. A standard format for searching, selecting, and retrieving river bathymetry data will enable greater use of these data in various hydrologic application contexts. This work is marked with Creative Commons Zero v1.0 Universal (https://creativecommons.org/publicdomain/zero/1.0/). Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although this information product, for the most part, is in the public domain, it also may contain copyrighted materials as noted in the text. 20040101 20230731 ground condition Complete Annually United States of America -175.0781 -33.7500 71.9654 12.5546 ISO 19115 Topic Category environment None bathymetric cross section cross-sections Inland Waters bathymetry bathymetry measurement channel depth channel width cross-sectional area river systems geomorphology geoscientific information hydraulic geometry monitoring river reaches USGS Metadata Identifier USGS:685ab9cbd4be024a9b286981 None United States of America No access constraints. Please see 'Distribution Information' for details. These data are marked with a Creative Common CC0 1.0 Universal License. These data are in the public domain and do not have any use constraints. Users are advised to read the dataset's metadata thoroughly to understand appropriate use and data limitations. Paul J Kinzel USGS - WATER Hydrologist mailing and physical

4620 Technology Drive

Suite 400

Golden CO 80403 United States 303-278-7941 pjkinzel@usgs.gov All the files included in this data release were processed using standard desktop and laptop computers. The input_files.zip file includes both Microsoft Excel macro-enabled worksheets and comma delimited text files with names corresponding to the ScienceBase item identifier of that bathymetric dataset. The worksheet files can be opened by Microsoft Excel and the csv by text editor programs like Notepad . 5a280c4de4b03852bafe0fa0_v103.csv (132 KB) 5a280c4de4b03852bafe0fa0_v103.xlsm (3859 KB) 5abaad29e4b081f61abb4d81_v103.csv (12 KB) 5abaad29e4b081f61abb4d81_v103.xlsm (1913 KB) 5abe505de4b081f61ac0ee39_v103.csv (12 KB) 5abe505de4b081f61ac0ee39_v103.xlsm (1922 KB) 5ba12393e4b08583a5c428cc_v103.csv (12KB) 5ba12393e4b08583a5c428cc_v103.xlsm (1930 KB) 5bf48171e4b045bfcae24171_v103.csv (12KB) 5bf48171e4b045bfcae24171_v103.xlsm (1931 KB) 5ca69241e4b0c3b0064c28b9_v103.csv (12KB) 5ca69241e4b0c3b0064c28b9_v103.xlsm (1931 KB) 5ccc56fee4b09b8c0b790ead_v103.csv (12KB) 5ccc56fee4b09b8c0b790ead_v103.xlsm (1929 KB) 5da895ade4b09fd3b0c9c5f9_v103.csv (23 KB) 5da895ade4b09fd3b0c9c5f9_v103.xlsm (2107 KB) 5dbc814ce4b06957974edf00_v103.csv (12 KB) 5dbc814ce4b06957974edf00_v103.xlsm (1930 KB) 5ee29cd882ce3bd58d7e169e_v103.csv (122 KB) 5ee29cd882ce3bd58d7e169e_v103.xlsm (3686 KB) 5f29c35282cef313ed9edb0a_v103.csv (12KB) 5f29c35282cef313ed9edb0a_v103.xlsm (1930 KB) 57f1b924e4b0bc0bebfee12b_v103.csv (12KB) 57f1b924e4b0bc0bebfee12b_v103.xlsm (1930 KB) 59f8cff1e4b063d5d309f135_v103.csv (12KB) 59f8cff1e4b063d5d309f135_v103.xlsm (1931 KB) 59f8d308e4b063d5d309f186_v103.csv (12 KB) 59f8d308e4b063d5d309f186_v103.xlsm (1931 KB) 60c24fbad34e86b9389559b8_v103.csv (12KB) 60c24fbad34e86b9389559b8_v103.xlsm (1930 Kb) 62e03799d34e952be90982a8_v103.csv (12KB) 62e03799d34e952be90982a8_v103.xlsm (1931 KB) 64dcac74d34e5f6cd55279c7_v103.csv (22 KB) 64dcac74d34e5f6cd55279c7_v103.xlsm (2104 KB) 64e51063d34e736b81e18a91_v103.csv (12KB) 64e51063d34e736b81e18a91_v103.xlsm (1929 KB) 67d99537d34e5a489eed1a90_v103.csv (12KB) 67d99537d34e5a489eed1a90_v103.xlsm (1930 Kb) 598c6730e4b09fa1cb100dde_v103.csv (12KB) 598c6730e4b09fa1cb100dde_v103.xlsm (1930 KB) 605b7b0dd34e189488343b10_v103.csv (12 KB) 605b7b0dd34e189488343b10_v103.xlsm (1929 KB) 606f6f8dd34ef99870189060_v103.csv (12 KB) 606f6f8dd34ef99870189060_v103.xlsm (1931 KB) 634ea520d34e47431c154396_v103.csv (55 KB) 634ea520d34e47431c154396_v103.xlsm (2633 KB) 638e4f28d34ed907bf7bc830_v103.csv (111 KB) 638e4f28d34ed907bf7bc830_v103.xlsm (3512 KB) 6113eb29d34ed11898f828e5_v103.csv (22 KB) 6113eb29d34ed11898f828e5_v103.xlsm (2106 KB) 6334a06ad34e900e86c6d791_v103.csv (12 KB) 6334a06ad34e900e86c6d791_v103.xlsm (1931 KB) 6446c255d34ee8d4adec6c0f_v103.csv (12 KB) 6446c255d34ee8d4adec6c0f_v103.xlsm (1930 KB) 6564eb25d34e3aa43a43c4e4_v103.csv (12 KB) 6564eb25d34e3aa43a43c4e4_v103.xlsm (1931 KB) 64419ae4d34ee8d4ade7c239_v103.csv (12 KB) 64419ae4d34ee8d4ade7c239_v103.xlsm (1930 KB) 631405ced34e36012efa336e_v103.csv (12 KB) 631405ced34e36012efa336e_v103.xlsm (1929 KB) 631405ced34e36012efa337a_v103.csv (12 KB) 631405ced34e36012efa337a_v103.xlsm (1931 KB) 631405ced34e36012efa337c_v103.csv (12 KB) 631405ced34e36012efa337c_v103.xlsm (1931 KB) 631405ced34e36012efa337e_v103.csv (12 KB) 631405ced34e36012efa337e_v103.xlsm (1929 KB) 631405ced34e36012efa3367_v103.csv (12 KB) 631405ced34e36012efa3367_v103.xlsm (1929 KB) 631405ced34e36012efa3369_v103.csv (12 KB) 631405ced34e36012efa3369_v103.xlsm (1931 KB) 631405ced34e36012efa3370_v103.csv (12 KB) 631405ced34e36012efa3370_v103.xlsm (1931 KB) 631405ced34e36012efa3372_v103.csv (12 KB) 631405ced34e36012efa3372_v103.xlsm (1931 KB) 631405ced34e36012efa3374_v103.csv (12 KB) 631405ced34e36012efa3374_v103.xlsm (1931 KB) 631405ced34e36012efa3376_v103.csv (12 KB) 631405ced34e36012efa3376_v103.xlsm (1931 KB) 631405ced34e36012efa3378_v103.csv (12 KB) 631405ced34e36012efa3378_v103.xlsm (1931 KB) 61376166d34e40dd9c0cda23_v103.csv (12 KB) 61376166d34e40dd9c0cda23_v103.xlsm (1929 KB) 63140560d34e36012efa2b5c_v103.csv (12 KB) 63140560d34e36012efa2b5c_v103.xlsm (1929 KB) 63140560d34e36012efa2b5e_v103.csv (12 KB) 63140560d34e36012efa2b5e_v103.xlsm (1929 KB) 63140560d34e36012efa2b6d_v103.csv (12 KB) 63140560d34e36012efa2b6d_v103.xlsm (1929 KB) 63140560d34e36012efa2b6f_v103.csv (12 KB) 63140560d34e36012efa2b6f_v103.xlsm (1929 KB) 63140560d34e36012efa2b56_v103.csv (12 KB) 63140560d34e36012efa2b56_v103.xlsm (1929 KB) 63140560d34e36012efa2b58_v103.csv (11 KB) 63140560d34e36012efa2b58_v103.xlsm (1931 KB) 63140560d34e36012efa2b62_v103.csv (11 KB) 63140560d34e36012efa2b62_v103.xlsm (1929 KB) 63140560d34e36012efa2b64_v103.csv (11 KB) 63140560d34e36012efa2b64_v103.xlsm (1931 KB) 64419787d34ee8d4ade7c22f_v103.csv (12 KB) 64419787d34ee8d4ade7c22f_v103.xlsm (1931 KB) The GeoPackages.zip file contains the GeoPackages. These files can be opened with the open source QGIS software program. USGS_5a280c4de4b03852bafe0fa0.gpkg (284 KB) USGS_5abaad29e4b081f61abb4d81.gpkg (996 KB) USGS_5abe505de4b081f61ac0ee39.gpkg (108 KB) USGS_5ba12393e4b08583a5c428cc.gpkg (1,468 KB) USGS_5bf48171e4b045bfcae24171.gpkg (40,676 KB) USGS_5ca69241e4b0c3b0064c28b9.gpkg (1,201,156 KB) USGS_5ccc56fee4b09b8c0b790ead.gpkg (108 KB) USGS_5da895ade4b09fd3b0c9c5f9.gpkg (116 KB) USGS_5dbc814ce4b06957974edf00.gpkg (139,368 KB) USGS_5ee29cd882ce3bd58d7e169e.gpkg (750,824 KB) USGS_5f29c35282cef313ed9edb0a.gpkg (268 KB) USGS_57f1b924e4b0bc0bebfee12b.gpkg (556 KB) USGS_59f8cff1e4b063d5d309f135.gpkg (26,268 KB) USGS_59f8d308e4b063d5d309f186.gpkg (340 KB) USGS_60c24fbad34e86b9389559b8.gpkg (42,616 KB) USGS_62e03799d34e952be90982a8.gpkg (156 KB) USGS_64dcac74d34e5f6cd55279c7.gpkg (300 KB) USGS_64e51063d34e736b81e18a91.gpkg (1,220 KB) USGS_67d99537d34e5a489eed1a90.gpkg (16,905,644 KB) USGS_598c6730e4b09fa1cb100dde.gpkg (872 KB) USGS_605b7b0dd34e189488343b10.gpkg (3,224 KB) USGS_606f6f8dd34ef99870189060.gpkg (4,876 KB) USGS_634ea520d34e47431c154396.gpkg (148 KB) USGS_638e4f28d34ed907bf7bc830.gpkg (825,548 KB) USGS_6113eb29d34ed11898f828e5.gpkg (8,676 KB) USGS_6334a06ad34e900e86c6d791.gpkg (234 KB) USGS_6446c255d34ee8d4adec6c0f.gpkg (2,108 KB) USGS_6564eb25d34e3aa43a43c4e4.gpkg (43,044 KB) USGS_64419ae4d34ee8d4ade7c239.gpkg (534,160 KB) USGS_631405ced34e36012efa336e.gpkg (21,444 KB) USGS_631405ced34e36012efa337a.gpkg (1,004 KB) USGS_631405ced34e36012efa337c.gpkg (13,052 KB) USGS_631405ced34e36012efa337e.gpkg (33,216 KB) USGS_631405ced34e36012efa3367.gpkg (12,104 KB) USGS_631405ced34e36012efa3369.gpkg (20,308 KB) USGS_631405ced34e36012efa3370.gpkg (14,344 KB) USGS_631405ced34e36012efa3372.gpkg (18,896 KB) USGS_631405ced34e36012efa3374.gpkg (12,936 KB) USGS_631405ced34e36012efa3376.gpkg (1,868 KB) USGS_631405ced34e36012efa3378.gpkg (2,184 KB) USGS_61376166d34e40dd9c0cda23.gpkg (1,652 KB) USGS_63140560d34e36012efa2b5c.gpkg (3,288 KB) USGS_63140560d34e36012efa2b5e.gpkg (1,688 KB) USGS_63140560d34e36012efa2b6d.gpkg (3,012 KB) USGS_63140560d34e36012efa2b6f.gpkg (3,268 KB) USGS_63140560d34e36012efa2b56.gpkg (752 KB) USGS_63140560d34e36012efa2b58.gpkg (1,452 KB) USGS_63140560d34e36012efa2b62.gpkg (1,044 KB) USGS_63140560d34e36012efa2b64.gpkg (2,784 KB) USGS_64419787d34ee8d4ade7c22f.gpkg (631,820 KB) v103_summary_results.csv (11 KB). This file contains a list of the bathymetry titles on ScienceBase and can be opened with a text editor. RiverSurvey_DataCompiler_V103.xlsm (1.71 MB). This Microsoft Excel document contains visual Basic for Applications (VBA) macros that facilitate conditioning and formatting river survey data sets discovered on ScienceBase. The data release contains the json file, SB_GeoPackage_Schema.json (17.74 KB). This file defines the schema used in each table in the GeoPackages and provides examples. U.S. Geological Survey 20230915 publication https://www.sciencebase.gov/catalog/item/63140560d34e36012efa2b6d U.S. Geological Survey 20230915 publication https://www.sciencebase.gov/catalog/item/63140560d34e36012efa2b56 U.S. Geological Survey 20230915 publication https://www.sciencebase.gov/catalog/item/63140560d34e36012efa2b6f U.S. Geological Survey 20230915 publication https://www.sciencebase.gov/catalog/item/63140560d34e36012efa2b5e U.S. Geological Survey 20230915 publication https://www.sciencebase.gov/catalog/item/63140560d34e36012efa2b5c U.S. Geological Survey 20230915 publication https://www.sciencebase.gov/catalog/item/63140560d34e36012efa2b64 U.S. Geological Survey 20230915 publication https://www.sciencebase.gov/catalog/item/63140560d34e36012efa2b58 U.S. Geological Survey 20230915 publication https://www.sciencebase.gov/catalog/item/63140560d34e36012efa2b62 Alexandra J Pickering Stephen B DeLong 20200513 publication https://www.sciencebase.gov/catalog/item/5ca69241e4b0c3b0064c28b9 Brenda K Densmore Benjamin J Dietsch 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa3367 Brenda K. Densmore Benjamin J Dietsch 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa3369 Brenda K. Densmore Benjamin J Dietsch 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa3370 Brenda K. Densmore Benjamin J Dietsch 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa337e Benjamin J Dietsch Brenda K Densmore 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa3376 Brenda K Densmore Benjamin J Dietsch 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa337c Brenda K. Densmore Benjamin J Dietsch 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa337a Brenda K. Densmore Benjamin J Dietsch 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa3372 Brenda K. Densmore Benjamin J Dietsch 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa336e Jessica Z LeRoy 20210526 publication https://www.sciencebase.gov/catalog/item/606f6f8dd34ef99870189060 Benjamin J Dietsch Brenda K Densmore 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa3374 Justin Krahulik Frank L. Engel 20160528 publication https://www.sciencebase.gov/catalog/item/57f1b924e4b0bc0bebfee12b Carl J Legleiter 20180611 publication https://www.sciencebase.gov/catalog/item/59f8d308e4b063d5d309f186 Brandon T Overstreet Paul J Kinzel Carl J Legleiter 20180611 publication https://www.sciencebase.gov/catalog/item/59f8cff1e4b063d5d309f135 Zachary W Martin 20170919 publication https://www.sciencebase.gov/catalog/item/598c6730e4b09fa1cb100dde Lee R. Harrison Carl J Legleiter 20190417 publication https://www.sciencebase.gov/catalog/item/5abaad29e4b081f61abb4d81 Ryan L Fosness Carl J Legleiter 20190321 publication https://www.sciencebase.gov/catalog/item/5bf48171e4b045bfcae24171 Pamela J Lombard 20180307 publication https://www.sciencebase.gov/catalog/item/5a280c4de4b03852bafe0fa0 Joel A Unema Keith A Kohl Ronald E Griffiths 20220920 publication https://www.sciencebase.gov/catalog/item/62e03799d34e952be90982a8 Cian B Dawson Verlin C Stephens Matthew J Nicotra, Todd A Burton Josip R. Adams Jeremy J Pulli Michael S Kohn Skye C Corbett Jack W. Eggleston John W Lane John W Fulton Frank L Engel 20210128 publication https://www.sciencebase.gov/catalog/item/5abe505de4b081f61ac0ee39 Brandon T Forbes Geoffrey P Debenedetto Carl J Legleiter 20220110 publication https://www.sciencebase.gov/catalog/item/61376166d34e40dd9c0cda23 Nick Elwell Scott W Anderson 20190219 publication https://www.sciencebase.gov/catalog/item/5ba12393e4b08583a5c428cc Paul J Kinzel Carl J Legleiter 20191025 publication https://www.sciencebase.gov/catalog/item/5ccc56fee4b09b8c0b790ead Paul J Kinzel 20210119 publication https://www.sciencebase.gov/catalog/item/5da895ade4b09fd3b0c9c5f9 Amanda R Whaling 20190628 publication https://www.sciencebase.gov/catalog/item/5ee29cd882ce3bd58d7e169e Paul J Kinzel Carl J Legleiter 20210211 publication https://www.sciencebase.gov/catalog/item/5f29c35282cef313ed9edb0a Li Erikson Ann E Gibbs Cordell Johnson Alexander G Snyder 20210719 publication https://www.sciencebase.gov/catalog/item/60c24fbad34e86b9389559b8 Paul J Kinzel 20210119 publication https://www.sciencebase.gov/catalog/item/5dbc814ce4b06957974edf00 Cory L Kavan 20221012 publication https://www.sciencebase.gov/catalog/item/6113eb29d34ed11898f828e5 P. Ryan Jackson Skylar A Smith James J Duncker Jessica Z LeRoy 20200224 publication https://www.sciencebase.gov/catalog/item/5df8fc5fe4b0cdded73b410a Joel A Unema Keith A Kohl Ronald E Griffiths 20230523 publication https://www.sciencebase.gov/catalog/item/6334a06ad34e900e86c6d791 Lee Harrison Carl J Legleiter 20230927 publication https://www.sciencebase.gov/catalog/item/64dcac74d34e5f6cd55279c7 Paul J Kinzel Michael S Kohn 20221214 publication https://www.sciencebase.gov/catalog/item/634ea520d34e47431c154396 Matthew R Acre Robin D Calfee Richard T Kraus Robert Mapes Christine M. Mayer Matthew D. Faust Scott F. Colborne Travis O. Brenden James J Roberts Robert D Hunter Sophia M. Bonjour 20250318 publication https://www.sciencebase.gov/catalog/item/67d99537d34e5a489eed1a90 Dayle J Hoefling Branden L Vonins 20230426 publication https://www.sciencebase.gov/catalog/item/6446c255d34ee8d4adec6c0f Brenda K Densmore Benjamin J Dietsch 20230915 publication https://www.sciencebase.gov/catalog/item/631405ced34e36012efa3378 Benjamin C Rivers Richard J Huizinga 20230711 publication https://www.sciencebase.gov/catalog/item/64419ae4d34ee8d4ade7c239 Jessica Z LeRoy Richard J Huizinga 20230711 publication https://www.sciencebase.gov/catalog/item/64419787d34ee8d4ade7c22f David Fazio Jessica Z LeRoy 20230302 publication https://www.sciencebase.gov/catalog/item/638e4f28d34ed907bf7bc830 Benjamin C Rivers Richard J Huizinga 20240306 publication https://www.sciencebase.gov/catalog/item/6564eb25d34e3aa43a43c4e4 Justin A Boldt 20230906 publication https://www.sciencebase.gov/catalog/item/64e51063d34e736b81e18a91 No formal attribute accuracy tests were conducted on the compiled dataset. Users are encouraged to access the cross referenced ScienceBase records for specific details. No formal logical accuracy tests were conducted on the compiled dataset. Users are advised to access the cross referenced ScienceBase records for specific details. Dataset is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details. No formal positional accuracy tests were conducted on the compiled dataset. Users are encouraged to access the cross referenced ScienceBase records for specific details. No formal positional accuracy tests were conducted on the compiled dataset. Users are encouraged to access the cross referenced ScienceBase records for specific details. Amanda R. Whaling Martin Wernimont Mackenzie K. Marti Paul J. Kinzel Jessica Z. LeRoy 20241001 web site https://water.usgs.gov/themes/river-corridors/ Digital and/or Hardcopy 20241001 publication date Whaling and others, 2024 The River Corridors on ScienceBase web viewer aims to simplify the discovery and exploitation of USGS river corridor data releases. Long, John (Dell) L Roland Viger Kanchana Raja Kyle D Enns John R. Sheflin Drew A Ignizio 20230119 application/service https://code.usgs.gov U.S. Geological Survey https://doi.org/10.5066/p9x4bipr Digital and/or Hardcopy 20230119 publication date sciencebasepy The sciencebasepy package was used to authenticate with ScienceBase and download the relevant files. Jeffrey Whitaker Open Source 20060101 web site with code https://pyproj4.github.io/pyproj/stable/index.html Digital and/or Hardcopy 20250711 publication date pyproj library Processing relied upon helper functions built on the pyproj library Taher Chegini Hong-Yi Li L. Ruby Leung 20211027 web site with code Chegini et al., (2021). HyRiver: Hydroclimate Data Retriever. Journal of Open Source Software, 6(66), 3175, https://doi.org/10.21105/joss.03175 https://github.com/hyriver/hyriver.github.io Digital and/or Hardcopy 20211027 publication date PyNHD package PyNHD is a python package that can be used to navigate and subset NHDPlus mid- and high-res NHD, NHDPlus, and NHDPlus VAA using web services. PyNHD is part of the HyRiver (formerly named hydrodata) suite of Python packages that provides a unified API for retrieving geospatial/temporal data from various web services. River corridor datasets were identified by either querying ScienceBase directly or exploring the USGS River Corridors Mapper (Whaling and others, 2024), which catalogs geospatial data products related to rivers. A dataset was considered potentially suitable for standardization to a custom GeoPackage format using the workflow described in this document if it included one or more downloadable files associated with a valid ScienceBase Item ID and represented surveyed river corridor data, such as streambed or streambank features. These datasets often contained surveyed cross sections, multibeam sonar point clouds, topobathymetric digital elevation models (DEMs), or other spatial products, and were typically provided in a wide range of file formats and coordinate reference systems. Whaling and others, 2024 20241001 Paul J Kinzel USGS - WATER Hydrologist mailing and physical

Kittridge Business Center, Kittridge Business Center

Golden CO 80403 303-278-7941 pjkinzel@usgs.gov Metadata for each dataset was cataloged using a custom macro-enabled Excel workbook named RiverSurvey_DataCompiler_v103.xlsm. This workbook provides a guided interface that assists users in documenting how the files associated with each ScienceBase record should be interpreted. When a ScienceBase landing page URL is entered into the designated cell, the workbook automatically extracts and records the corresponding 24-character ScienceBase Item ID. 20241216 Paul J Kinzel USGS - WATER Hydrologist mailing and physical

Kittridge Business Center, Kittridge Business Center

Golden CO 80403 303-278-7941 pjkinzel@usgs.gov The compiler workbook was completed for 50 ScienceBase IDs, as documented in the accompanying input_files.zip file. Each ScienceBase record was reviewed to determine how many relevant data files were available for spatial processing. Records often included a single file, multiple files, child items with additional files, zipped archives, or combinations of these. Once the number of relevant files was entered, the workbook automatically generated a structured worksheet for each file. These worksheets contain standardized question-and-answer fields that documents information necessary to parse and transform the dataset. This included the file name, its location (main item, child item, or inside a zipped archive), spatial metadata, and whether the file contained a single dataset or multiple subsets requiring attribute-based grouping or spatial clustering. The presence and location of any XML metadata or bibliographic files were also recorded. 20250623 Paul J Kinzel USGS - WATER Hydrologist mailing and physical

Kittridge Business Center, Kittridge Business Center

Golden CO 80403 303-278-7941 pjkinzel@usgs.gov Each worksheet also captured technical metadata related to the spatial structure and coordinate reference system of the dataset. This included the file type and delimiter, the spatial structure (e.g., raster, cross section, or point cloud), and the field mappings for X, Y, and Z coordinates. Additional entries recorded the projection name (e.g., UTM North), zone number, horizontal and vertical datums (e.g., NAD83, NAVD88), coordinate units, and any known geoid model. The data profile (e.g., X-Y-Z), survey method, data type, survey date range, and any supplemental parsing notes were also included. The worksheet framework also supports specifying many additional attributes beyond the core data profile, for example point error estimates. However, this was not applied uniformly and was limited to a few datasets to test the practicality of this utility. A total of 50 CSV files (one from each compiler workbook) were generated and packaged in the accompanying compiler.zip file for use in the next processing step. After all worksheets were completed, the workbook exports a single CSV file containing the full set of processing instructions and metadata for all data files associated with a given ScienceBase ID. A total of 50 CSV files (one from each compiler workbook) were generated and packaged in the accompanying input_files.zip file for use in the next processing step. 20250623 Paul J Kinzel USGS - WATER Hydrologist mailing and physical

Kittridge Business Center, Kittridge Business Center

Golden CO 80403 303-278-7941 pjkinzel@usgs.gov Each compiled CSV served as input to a Python notebook referred to as the parser notebook. A custom function within the notebook read the CSV and converted its contents into a structured Python dictionary. This dictionary included instructions for locating source files, applying geospatial logic, assigning survey classifications, and determining whether grouping or clustering was required. 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov The parser notebook used the sciencebasepy package (https://github.com/usgs/sciencebasepy) to authenticate with ScienceBase and download the relevant files. These included delimited text files, raster surfaces, LAS point clouds, shapefiles, and associated XML and bibliographic metadata. All files were extracted and staged in a temporary working directory. sciencebasepy 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov After download, the notebook attempted to determine the EPSG code for each dataset using the projection name, UTM zone, horizontal datum, and measurement units specified in the compiler output. This step relied on helper functions built on the pyproj library (https://pyproj4.github.io/pyproj/stable/) and often used queries to epsg.io. If a match could not be determined automatically, the notebook prompted the user to manually enter a valid EPSG code. pyproj library 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov Based on the file type, the notebook invoked the appropriate parser to load the data. Delimited text files were processed using pandas, raster data using rasterio, LAS files using laspy, and shapefiles using fiona or geopandas. All data were normalized into a consistent structure as a pandas DataFrame with standardized X, Y, and (optionally) Z coordinates, along with any additional relevant attribute fields recorded in the compiler. Optional additional attributes extracted from the ScienceBase file were appended as attr_1, attr_2, and so on, with the index assigned sequentially based on the order in which the attributes were extracted. 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov Each dataset was processed through two parallel pipelines. In the first pipeline, the original data were preserved in their native projection, coordinate units, and vertical reference. The data were standardized by renaming the X, Y, and Z columns and were organized in preparation for export to a layer referred to as the data layer within the GeoPackage. If a dataset contained more than ten million rows, it was divided into smaller chunks, and each chunk was stored as a separate table prepared for export as an additional data layer. In the second pipeline, the X and Y coordinates were reprojected to the WGS84 coordinate system, corresponding to EPSG code 4326, using the GeoPandas to_crs function. This reprojection was used to generate a simplified spatial representation (typically a point, line, or polygon) suitable for geospatial indexing and querying. The Z coordinate was excluded from the simplified geometry because three-dimensional reprojection, such as transforming from NGVD29 to NAVD88, was not supported within the notebook. However, in addition to preservation of the original vertical values, the associated metadata were retained and staged for export in the final, standardized GeoPackage. In particular, preservation and standardization of this information ensures that the final GeoPackage can be programmatically accessed in the future by external three-dimensional tools like NOAA’s VDatum. This approach facilitates more straightforward 3D transformations across a variety of geospatial assets on ScienceBase, which are otherwise organized in a disparate manner. 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov The parser notebook used the metadata from the compiler CSV to assign a RiverSurveyClass value to each dataset (e.g., cross_section, point_location, or survey_coverage). This classification determined how the geometry was derived from the transformed X-Y data. For instance, survey points organized into swaths were used to create coverage polygons, while cross-sectional profiles may be interpreted as lines. Custom logic is applied to generate these nominal geometries using GeoPandas, based on the spatial distribution and structure of the underlying data. While these geometries generally provide a spatially accurate representation of the dataset’s overall coverage, they are intentionally simplified and may not preserve full point-level fidelity. For example, some original points may fall just outside the derived polygon boundary, or conversely, a polygon may overgeneralize the footprint such as when a convex hull is used to approximate an irregular shape. 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov If an individual data file contained multiple spatial subsets, the notebook supported two methods for partitioning the data. If attribute-based grouping was specified in the compiler, the notebook split the data according to a user-defined column. If spatial clustering was required, the compiler flagged the dataset accordingly, triggering a clustering routine. The notebook then displayed diagnostic plots for user review. The user was prompted to accept or reject the suggested number of clusters, ensuring that each sub-region was valid. 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov Once geometries were finalized, the notebook used the PyNHD package (https://doi.org/10.21105/joss.03175) to intersect each geometry with the NHDPlus flowlines. These intersections returned COMID identifiers, which enabled hydrographic indexing and linkage to specific river reaches. PyNHD package 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov Final metadata for each dataset (including coordinate system details, source filenames, bibliographic citations, and processing notes) was compiled from the compiler CSV and XML files. This information was written to a *_metadata layer in the GeoPackage, while geometry and attribute data were stored in *_geometry and *_data layers, respectively. These three layer types were specifically created to organize and describe the river corridor datasets available on ScienceBase. Detailed descriptions of these layer types, along with their attribute definitions, can be found in the accompanying json file provided with this data release (SB_GeoPackage_Schema.json). 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov The parser notebook utilizes GeoPandas.to_file() in conjunction with a helper function to write all three layer types to a single GeoPackage (.gpkg) for each compiler CSV output. Each GeoPackage includes one *_geometry layer in WGS84 that stored one geometry per feature. Features in the _geometry layer were differentiated using a file number and a file_partition attribute indicating the subset of data they represented (e.g., full_dataset vs. cluster_1). Each _data layer corresponds to a single ScienceBase data file, but a single file may be split across multiple _data layers. No _data layer contains data from more than one file. Importantly, each _data layer includes the file_partition as an attribute along with all fields from the core data profile and any optional additional attributes, allowing both the data and geometry to be cross-referenced consistently. Importantly, each _data layer includes the file_partition as an attribute along with all fields from the core data profile and any optional additional attributes, allowing both the data and geometry to be cross-referenced consistently. If the dataset was split across multiple files or exceeded row count thresholds, separate data layers were created and named using file numbers, chunk identifiers, and partition labels. A single *_metadata layer documented each feature and was linked by a combination of file number, ScienceBase child ID (if applicable), and file_partition. 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov Once processing was complete, the notebook removed temporary files and directories. The final output was a standardized GeoPackage that transformed inconsistently formatted ScienceBase datasets into a spatially indexed and hydrographically linked structure, ready for integration into modern GIS workflows. All 50 GeoPackage files containing standardized river corridor data in the so-called "RiverSurvey" format, version 1.0.3, are included in the provided zip archive (GeoPackages.zip). 20250711 Amanda R Whaling USGS - SOUTHEAST REGION Hydrologist mailing and physical

Fayetteville Field Station, U of AR Res Ctr Blvd - Genesis Technology Incubator

Fayetteville AR 72701 479-442-4888 awhaling@usgs.gov The RiverSurvey Data Complier V103 underwent an Administrative Security Review and was posted to the landing page. 20260209 Paul J Kinzel USGS - WATER Hydrologist mailing and physical

Denver Federal Center, DFC Bldg 53

Lakewood CO 80225 303-278-7941 pjkinzel@usgs.gov Vector Link 50 0.00001 0.00001 Decimal degrees World Geodetic System 1984 (WGS 84) WGS_1984 6378137.0 298.257223563 input_files.zip This zip archive contains files generated from the RiverSurvey Data Compiler V103. For each of the 50 ScienceBase river bathymetry data sets that were processed with the RiverSurvey Data Compiler, a comma delimited text file and a Microsoft Excel macro worksheet were generated. These file names correspond to the ScienceBase identifier associated with a bathymetry data set. The 50 comma delimited files are used as input to a script that creates the associated GeoPackage. The tabs in each Microsoft Excel macro worksheet correspond to the following: a "Main" tab where the ScienceBase data release identifier is entered as well as the total number of files that are being compiled as part of this data release; a "File X", tab where X is a number corresponding to the total number of files compiled as part of that data release; a "Blank" tab that provides the template for each "File X" tab; a "Source" tab that provides the definitions for the macro; and a "Help" tab that describes how to use the macro. Further details describing instructions on how the compiler is used are contained in the Processing Steps section of the metadata. Producer Defined GeoPackages.zip This zip archive contains the GeoPackages. Each GeoPackage contains the data table(s), geometry table, and a metadata table. Producer Defined v103_summary_results.csv This comma delimited text file contains a summary of the 50 ScienceBase river bathymetry data sets that were processed to GeoPackages. Fields in this file include: the title of the ScienceBase data release, the ScienceBase item_id, a file path, the number of partitions, and the type of file partitioning. Producer Defined Title Text that provides the title of the ScienceBase data release Producer Defined Text that provides the title of the ScienceBase data release item_id Alphanumeric string that indicates the ScienceBase item identifier Producer Defined Alphanumeric string that indicates the Sciencebase item identifier file_name Text that provides the file path to the input files used in the script to create the GeoPackage Producer Defined Text that provides the file path to the input files used in the script to create the GeoPackage num_partitions The number of partitions within the ScienceBase data release. A partition is the smallest geospatial entity that the data can be grouped into. Producer Defined 1 29 none 1 file_partitioning Text indicating how the data file was partitioned if there were multiple spatial groupings. Producer Defined none the data did not need to be partitioned as there was only one spatially distinct grouping Producer defined spatial clustering a clustering algorithm was applied to identify the smallest spatial extent to group the data Producer defined chunked_dataset the data were not processed into spatial groups, meaning there will still only be one geometry to represent that file. However, the data file itself was too big to store in one table, so the data table is separated into multiple chunks of 10 million rows each. Producer defined grouped attributes the data was grouped by similar attributes Producer defined SB_GeoPackage_Schema.json This json file defines the schema used in each table in the GeoPackages and provides examples. Producer Defined RiverSurvey_DataCompiler_v103.xlsm This Microsoft Excel document contains visual Basic for Applications (VBA) macros that facilitate conditioning and formatting river survey data sets discovered on ScienceBase. Producer Defined At present, 2026, USGS river bathymetry surveys in ScienceBase lack a consistent, standardized organizational structure which impedes discovery and use of these datasets. Standardization of USGS bathymetry surveys allows these data to be more easily identified, queried, and incorporated into any number of science applications across a range of spatial scales. This data release includes river bathymetry data published in ScienceBase that have been subsequently standardized into the GeoPackage format. A GeoPackage is an open-source geospatial format that can store both raster and vector files. The hydrographic address of the data is stored in the GeoPackage to enable queries of position relative to streamgages or upstream or downstream flow directions. Each GeoPackage is organized with a common set of logical relationships or schema. The schema used herein consists of multiple tables. A data table, as the name implies, contains the data itself in X, Y, Z format. The geometry table contains hydrographic addressing information derived from the minimal geospatial format necessary to represent data coverage, such as a coverage polygon or a line representing a cross-section that provides more spatial fidelity than a simple bounding box. Finally, a metadata table contains the column definitions, units, projection, and ellipsoid information required to perform batch projection and datum transformations of the datasets. This dataset is anticipated to be updated and versioned as additional bathymetry datasets are created, discovered, and processed into GeoPackages. The data release includes the following files: 1) input_files.zip - this zip archive contains files generated from the RiverSurvey Data Compiler V103. For each of the 50 ScienceBase river bathymetry data sets that were processed with the RiverSurvey Data Compiler, a comma delimited text file and a Microsoft Excel macro worksheet were generated. These file names correspond to the ScienceBase identifier associated with a bathymetry data set. The 50 comma delimited files are used as input to a script that creates the associated GeoPackage. 2) GeoPackages.zip - this zip archive contains the GeoPackages. Each GeoPackage contains the data table, geometry table, and a metadata table. 3) v103_summary_results.csv - this comma delimited text file contains a summary of the 50 ScienceBase river bathymetry data sets that were processed to GeoPackages. Fields in this file include: the title of the ScienceBase data release, the ScienceBase item_id, a file path, the number of partitions, and the type of file partitioning. 4) SB_GeoPackage_Schema.json - this json file defines the schema used in each table in the GeoPackages and provides examples. Kinzel, P.J., and Whaling, A.R., 2026, ScienceBase river bathymetry surveys in GeoPackage format, U.S. Geological Survey data release, https://doi:10.5066/P144IY7E. GS ScienceBase U.S. Geological Survye mailing address

Denver Federal Center, Building 810, Mail Stop 302

Denver CO 80225 United States 1-888-275-8747 sciencebase@usgs.gov Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. The data you have secured from the U.S. Geological Survey (USGS) database identified as "ScienceBase river bathymetry surveys in GeoPackage format" have not received USGS approval and as such are provisional and subject to revision. The data are released on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from its authorized or unauthorized use. Although these data have been processed successfully on a computer system at the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and/or contained herein. Digital Data https://doi.org/10.5066/P144IY7E None 20260326 Paul J Kinzel USGS - WATER Hydrologist mailing and physical

4620 Technology Drive, Suite 400

Golden CO 80403 USA 303-278-7941 pjkinzel@usgs.gov FGDC Biological Data Profile of the Content Standard for Digital Geospatial Metadata FGDC-STD-001.1-1999