Skip to main content
Vyperdatum

PyPI version DOI Read the Docs

Vyperdatum

Vyperdatum is a NOAA OCS/NBS toolkit for performing high-accuracy vertical datum transformations using NOAA’s separation grids within the modern PROJ/GDAL ecosystem. It provides a high-level Transformer interface that builds PROJ pipelines from a source CRS (crs_from) to a target CRS (crs_to), and applies them consistently to point cloud and raster formats (e.g. GeoTIFF, BAG, VRBAG, LAZ, NPZ, and GeoParquet).

The goal of Vyperdatum is to make it easy to transform coastal and hydrographic data between tidal, orthometric, and ellipsoidal vertical datums (for example, NAD83(2011) ellipsoid heights to MLLW or NAVD88) while preserving full coordinate reference system metadata so that transformations are transparent and reproducible.

Typical use cases include:

  • Normalizing hydrographic surveys to charting datums for ENC/RNC and bathymetric products
  • Preparing inputs for coastal flood, storm surge, and inundation models that require a specific vertical datum
  • Converting between ellipsoidal, orthometric, and tidal datums for coastal GNSS/GNSS-tide workflows

Under the hood, Vyperdatum uses a PROJ database augmented with NOAA grids and metadata. Transformation steps can be inferred automatically from crs_from/crs_to, or prescribed explicitly when fine-grained control over the pipeline is required. NOAA’s grid files and the updated proj.db are not bundled with the package; instead, they are downloaded separately and the VYPER_GRIDS environment variable is pointed at their location.

Installation

Vyperdatum requires GDAL, which is most reliably installed from the conda-forge channel. In the steps below, a conda environment is created first, then GDAL and Vyperdatum are installed into it.

conda create -n vd python=3.11
conda activate vd
conda install -c conda-forge proj=9.6 gdal python-pdal
pip install vyperdatum

Before vyperdatum is run, NOAA's datum files and the updated proj.db must be downloaded DOI. Once downloaded, a persistent environment variable VYPER_GRIDS is set to the directory that holds the downloaded grids and proj.db.

Usage

Vyperdatum offers a Transformer class to handle the transformation of point and raster data. The Transformer class applies transformation from crs_from to crs_to coordinate reference system. By default the transformation steps will be determined automatically:

from vyperdatum.transformer import Transformer

crs_from = "EPSG:6346"            # NAD83(2011) 17N (vertical: Ellipsoid)
crs_to = "EPSG:6346+NOAA:98"      # NAD83(2011) 17N + MLLW
tf = Transformer(crs_from=crs_from,
                 crs_to=crs_to,
                 )

Alternatively, the transformation steps may be prescribed manually:

from vyperdatum.transformer import Transformer

crs_from = "EPSG:6346"            # NAD83(2011) 17N
crs_to = "EPSG:6346+NOAA:98"      # NAD83(2011) 17N + MLLW
steps = [{"crs_from": "EPSG:6346", "crs_to": "EPSG:6318", "v_shift": False},
         {"crs_from": "EPSG:6319", "crs_to": "EPSG:6318+NOAA:98", "v_shift": True},
         {"crs_from": "EPSG:6318", "crs_to": "EPSG:6346", "v_shift": False}
         ]
tf = Transformer(crs_from=crs_from,
                 crs_to=crs_to,
                 steps=steps
                 )

Once an instance of the Transformer class is created, the transform() method can be called. The input format is detected automatically. GDAL-supported raster drivers, variable-resolution BAG, LAZ, NPZ, XYZ, and GeoParquet inputs are supported, with a PDAL fallback for additional point-cloud formats.

transform

tf.transform(input_file=<PATH_TO_INPUT_RASTER_FILE>,
             output_file=<PATH_TO_OUTPUT_RASTER_FILE>
             )

The file-specific transform methods may also be called directly instead of the generic Transformer.transform() method:

Click to see pseudo-code examples
# Direct point transformation. The input x, y, z can be lists or numpy arrays.
# transform_points returns a tuple in the order (success, x, y, z).
import numpy as np
xi, yi, zi = np.array([278881.198]), np.array([2719890.433]), np.array([0])
success, xt, yt, zt = tf.transform_points(x=xi, y=yi, z=zi, always_xy=True)

# GDAL-supported raster transform  
tf.transform_raster(input_file=<PATH_TO_INPUT_RASTER_FILE>,
                    output_file=<PATH_TO_OUTPUT_RASTER_FILE>
                    )

# VRBAG transform
tf.transform_vrbag(input_file=<PATH_TO_INPUT_VRBAG_FILE>,
                   output_file=<PATH_TO_OUTPUT_VRBAG_FILE>
                   )

# LAZ transform
tf.transform_laz(input_file=<PATH_TO_INPUT_LAZ_FILE>,
                 output_file=<PATH_TO_OUTPUT_LAZ_FILE>
                 )

# NPZ transform
tf.transform_npz(input_file=<PATH_TO_INPUT_NPZ_FILE>,
                 output_file=<PATH_TO_OUTPUT_NPZ_FILE>
                 )

# XYZ transform
tf.transform_xyz(input_file=<PATH_TO_INPUT_XYZ_FILE>,
                 output_file=<PATH_TO_OUTPUT_XYZ_FILE>
                 )

# GeoParquet transform
tf.transform_geoparquet(input_file=<PATH_TO_INPUT_PARQUET_FILE>,
                        output_file=<PATH_TO_OUTPUT_PARQUET_FILE>
                        )

Documentation

For a quick start, more detailed descriptions or search through the API, see Vyperdatum's documentation at: https://vyperdatum.readthedocs.io.

Metadata

Release files for vyperdatum 0.3.60

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vyperdatum 0.3.60
File Size Uploaded Provenance Actions
vyperdatum-0.3.60.tar.gz 224.5 kB With provenance Details for vyperdatum-0.3.60.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for vyperdatum 0.3.60
File Interpreter ABI Platform Actions
vyperdatum-0.3.60-py3-none-any.whl Python 3 none any Details for vyperdatum-0.3.60-py3-none-any.whl

Total release size: 486.7 kB

Release files / vyperdatum-0.3.60.tar.gz

Download URL vyperdatum-0.3.60.tar.gz
Size 224.5 kB
Tags Source
SHA-256 checksum
How to use checksums
f0142b1e067abaa2a408d95ef497cdb1a44064f6daf532c7ae119c530cd3fd1a
BLAKE2b-256 checksum
How to use checksums
5fd5150703d8c65b4b47978001ecc4013edaeb32674df49905861cbef18b6a41
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 10, 2026.

Transparency log

Release files / vyperdatum-0.3.60-py3-none-any.whl

Download URL vyperdatum-0.3.60-py3-none-any.whl
Size 262.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bf0a04bfa41192c86f7c0a427974b9fc593a93af3bf72b2b7428f3a093c20d22
BLAKE2b-256 checksum
How to use checksums
18196e69ccf4ef1db3fdf60a693ef1c5db02cecff82a22cd249f76b585fe0a6a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 10, 2026.

Transparency log

Security for vyperdatum 0.3.60

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for vyperdatum-0.3.60.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 10, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.3.60 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page