Skip to main content

madis-data

madis-data produces analysis-ready full-hour MADIS Mesonet datasets for arbitrary date ranges and operationally meaningful U.S. regions or individual stations as netCDF files.

It downloads, processes, extracts, and interpolates to the full hour Meteorological Assimilation Data Ingest System (MADIS) data. Currently, madis-data operates with the following publicly available MADIS Mesonet data:

  • 2 m temperature
  • 2 m dewpoint temperature
  • 10 m west-east and south-north wind speed
  • solar radiation

MADIS data are provided by the National Centers for Environmental Prediction.

Installation

pip

pip install madis-data

conda / mamba

mamba install -c jan.kazil -c conda-forge madis-data

Overview

The package provides a command-line tool that:

  • selects stations by geography (an individual MADIS station, a U.S. state, a Regional Transmission Organization/Independent System Operator regions, and the special region CONUS representing the contiguous United States),
  • downloads Mesonet observation files for a specified date range,
  • extracts, preprocesses, and saves in netCDF files the observables,
    • 2 m temperature
    • 2 m dewpoint temperature
    • 10 m west-east and south-north wind speed
    • solar radiation
  • optionally removes the original Mesonet observation files after successful preprocessing to reduce storage requirements,
  • constructs full-hourly time series for the supported observables,
  • and saves the spatially filtered observations and hourly time series in netCDF files.

It also generates a map showing the selected station locations.

Once preprocessed files with the above variables have been generated for a given date range, constructing full-hourly time series for that date range for individual stations, U.S. states, or the CONUS region no loner requires downloading the original Mesonet observations again.

Geospatial region selection is based on U.S. Energy Information Administration definitions of Regional Transmission Organization/Independent System Operator footprints and U.S. Census Bureau state and territory boundaries included with the package.

Command-line interface (CLI)

The CLI is exposed as "build-mesonet-dataset" when installed.

Usage:

build-mesonet-dataset START_YEAR START_MONTH START_DAY END_YEAR END_MONTH END_DAY REGION DATA_DIR \
    [-n N_JOBS] [--remove-original] [-r] [-v]

Positional arguments

  • START_YEAR, START_MONTH, and START_DAY: Components of the first requested timestamp at 00:00 UTC
  • END_YEAR, END_MONTH, and END_DAY: Components of the last requested timestamp at 00:00 UTC
  • REGION: Region or station selector. Use a two-letter U.S. state or territory code, CONUS, an RTO/ISO code, or a MADIS Mesonet station identifier
  • DATA_DIR: Directory where downloaded data and generated outputs will be stored

Options

  • -n, --n N_JOBS: Number of parallel workers used for downloading, spatial extraction, and interpolation. Values greater than 1 can accelerate processing but may increase memory use or the risk of network errors.
  • --remove-original: Remove downloaded original MADIS files after successful preprocessing.
  • -r, --refresh: Download files even when corresponding local files already exist.
  • -v, --verbose: Print detailed progress information.

The command downloads one additional day before and after the requested interval so observations can bracket its boundary hours during interpolation. It creates a NetCDF file containing the selected record-oriented observations, a map of the selected station locations, and a NetCDF file containing the merged full-hourly UTC time series.

Examples:

# Show usage information:
build-mesonet-dataset --help

# Download and process MADIS Mesonet data for station SMPC2 from 00:00 UTC on January 1, 2026,
# through 00:00 UTC on January 31, 2026, and save the results in /path/to/data:
build-mesonet-dataset -v 2026 1 1 2026 1 31 SMPC2 /path/to/data

# Build datasets for Colorado using 16 parallel workers and remove source files after preprocessing:
build-mesonet-dataset -v 2026 1 1 2026 2 1 CO /path/to/data -n 16 --remove-original

Workflow (using API)

The detailed workflow is documented in the HowTo Jupyter notebook. The notebook performs the following tasks:

  1. download MESONET surface observations data files for January 2026 from the MADIS archive,
  2. extract January 2026 data for stations in the state of Colorado of the following observables:
    • 2 m temperature,
    • 2 m dewpoint temperature,
    • 10 m west-east and south-north wind speed,
    • solar radiation
  3. save the extracted data in a s netCDF file,
  4. interpolate the data to full-hourly time series,
  5. save the full-hourly time series in a netCDF file,
  6. plot the original and the full-hourly interpolated time series at an individual station over select time intervals,
  7. plot the stations in the state of Colorado on a US map.

Requirements

This notebook requires the Jupyter kernel madis-data, which is automaticaly installed as part of the madis-data conda development environment. The conda development environment can be installed from the root directory of the madis-data distribution with

make setup-dev-env

Development

Code Quality and Testing Commands

  • make fmt - Runs ruff format, which reformats Python files according to the style rules in pyproject.toml.
  • make lint - Runs ruff check --fix, which lints the code and auto-fixes what it can.
  • make check - Runs formatting and linting.
  • make type - Currently disabled. Intended to run mypy using the settings in pyproject.toml.
  • make test - Runs pytest with the test settings configured in pyproject.toml.

Disclaimers

The data accessed by this software are publicly available from NOAA's National Centers for Environmental Prediction (NCEP) and are subject to their terms of use. This project is not affiliated with or endorsed by NOAA.

This software uses U.S. Census Bureau and U.S. Energy Information Administration data, but is neither endorsed nor certified by the U.S. Census Bureau or the U.S. Energy Information Administration.

Author

Jan Kazil - jan.kazil.dev@gmail.com - github.com/jankazil/madis-data

License

BSD-3-Clause

Metadata

Release files for madis-data 0.1.3

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

Source distribution (sdist)

Source distribution for madis-data 0.1.3
File Size Uploaded Provenance Actions
madis_data-0.1.3.tar.gz 22.1 MB Without provenance Details for madis_data-0.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for madis-data 0.1.3
File Interpreter ABI Platform Actions
madis_data-0.1.3-py3-none-any.whl Python 3 none any Details for madis_data-0.1.3-py3-none-any.whl

Total release size: 44.4 MB

Release files / madis_data-0.1.3.tar.gz

Download URL madis_data-0.1.3.tar.gz
Size 22.1 MB
Tags Source
SHA-256 checksum
How to use checksums
73ce1f9f35e3c4b211a57b08045a7869e1d365ea3bef700e1e767b13edbae92d
BLAKE2b-256 checksum
How to use checksums
2e74fa72a1b9dec10262623aa80806cccf20d939017e0ff4a5fda6e14d7b02e2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.13

Release files / madis_data-0.1.3-py3-none-any.whl

Download URL madis_data-0.1.3-py3-none-any.whl
Size 22.3 MB
Tags Python 3
SHA-256 checksum
How to use checksums
c8142b4ff180cf67406571546ad42c29be99ccab90694dcc0475d3a4389d13fa
BLAKE2b-256 checksum
How to use checksums
ad5f9e48d81b0b98c0cfca78e78bb45e656f3a56ff3bb7474fce1a1e3a8ad545
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.13

Security for madis-data 0.1.3

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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.

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