noaabathymetry 0.8.2

NOAA National Bathymetric Source data download, mosaic, and status tools

National Bathymetric Source

---

Background • Requirements • Installation • Quickstart • CLI • Data Sources • Contact

Overview

Point this package at your area of interest and get the latest and best public bathymetric data from NOAA.

For most use cases, the quickstart below is all you need.

For more detailed guides, API reference, and troubleshooting, see the full documentation.

For a browser-based user interface to this repository, please consider trying this.

Background

NOAA's National Bathymetric Source builds and publishes the best available high-resolution bathymetric data of U.S. waters. The program's workflow is designed for continuous throughput, ensuring the best bathymetric data is always available to professionals and the public. This data provides depth measurements nationwide, along with vertical uncertainty estimates and information on the originating survey source. It is available in multiple formats (GeoTIFF compilations like BlueTopo and Modeling, BAG, and IHO S-102) hosted on a public S3 bucket.

This package simplifies downloading bathymetric data from NOAA and optionally assembling it into per-UTM-zone GDAL Virtual Rasters for use in GIS applications. It supports six data sources (BlueTopo, Modeling, BAG, S-102 v2.1/v2.2/v3.0).

Requirements

This package requires Python and the following dependencies, which are handled by the installation guide below:

• GDAL
• boto3
• tqdm

Installation

Install conda (If you have not already): conda installation

In the command line, create an environment with the required packages:

conda create -n noaabathymetry_env -c conda-forge 'gdal>=3.9'  # add libgdal-hdf5 for BAG/S-102 support

conda activate noaabathymetry_env

pip install noaabathymetry   # installs boto3 and tqdm automatically

Quickstart

After installation, the package provides a Python API and a CLI. You can use fetch for downloading tiles and mosaic for assembling them together.

See the Python API and CLI sections below to get started. You can also use the Quickstart Helper to draw your area of interest on a map and generate usage examples.

Python API

Define your area of interest using any of the geometry formats listed below. You can then use the following in a Python shell or script.

To download files in your area of interest (default data source is BlueTopo):

from nbs.noaabathymetry import fetch_tiles
result = fetch_tiles('/path/to/project', geometry='area_of_interest.gpkg')

To mosaic the downloaded files:

from nbs.noaabathymetry import mosaic_tiles 
result = mosaic_tiles('/path/to/project')

CLI

You can also use the command line. Confirm the environment we created during installation is activated.

To fetch the latest data (default data source is BlueTopo), pass a directory path and a geometry input of your area of interest:

nbs fetch -d /path/to/project -g area_of_interest.gpkg

Pass the same directory path to nbs mosaic to mosaic the fetched data:

nbs mosaic -d /path/to/project

Use -h for help and to see additional arguments.

For most use cases, reusing the commands above to stay up to date in your area of interest is adequate.

Geometry formats

The geometry parameter accepts four formats. File inputs use the CRS defined in the file. All other formats assume EPSG:4326 (WGS 84).

File — any GDAL-compatible vector file (shapefile, geopackage, GeoJSON file, etc.):

result = fetch_tiles('/path/to/project', geometry='/path/to/area_of_interest.gpkg')

Bounding box — xmin,ymin,xmax,ymax as longitude/latitude:

result = fetch_tiles('/path/to/project', geometry='-76.1,36.9,-75.9,37.1')

WKT — Well-Known Text geometry:

result = fetch_tiles('/path/to/project', geometry='POLYGON((-76.1 36.9, -75.9 36.9, -75.9 37.1, -76.1 37.1, -76.1 36.9))')

GeoJSON — geometry or Feature object:

result = fetch_tiles('/path/to/project', geometry='{"type":"Polygon","coordinates":[[[-76.1,36.9],[-75.9,36.9],[-75.9,37.1],[-76.1,37.1],[-76.1,36.9]]]}')

Data Sources

BlueTopo, Modeling, and various S-102 versioned data are available as data sources. You can work with these using the data_source argument (e.g. data_source='modeling'). When not specified, data_source defaults to BlueTopo.

The primary difference between BlueTopo and Modeling data is the vertical datum. Modeling data is on a low water datum.

Please note that these S-102 data are for test and evaluation and should not be used for navigation. For official S-102 please see the data available from Precision Marine Navigation.

Authors

• Glen Rice (NOAA), [e-mail]

• Tashi Geleg (Lynker / NOAA), [e-mail]

License

This work, as a whole, falls under Creative Commons Zero (see LICENSE).

Disclaimer

This repository is a scientific product and is not official communication of the National Oceanic and Atmospheric Administration, or the United States Department of Commerce. All NOAA GitHub project code is provided on an 'as is' basis and the user assumes responsibility for its use. Any claims against the Department of Commerce or Department of Commerce bureaus stemming from the use of this GitHub project will be governed by all applicable Federal law. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation or favoring by the Department of Commerce. The Department of Commerce seal and logo, or the seal and logo of a DOC bureau, shall not be used in any manner to imply endorsement of any commercial product or activity by DOC or the United States Government.