wetterdienst

repository·main·Indexed 19 days ago

https://github.com/earthobservations/wetterdienst

Open weather data library providing access to meteorological data, including radar products from the Deutscher Wetterdienst (DWD). Version 0.132.0 features a backend API with a Model Context Protocol (MCP) server, a frontend with Meteogram and Climate Stripes visualizations, and a DuckDB query component for direct SQL access to datasets.

Tokens
126.2K
Snippets
240
Records
419
Agent score
66%

What's inside wetterdienst

  1. Overview of DWD Derived Data Products

    main

    The DWD (Deutscher Wetterdienst) provides various data products derived from raw weather data. These products are categorized by their temporal resolution and the quality control status of the data.

    Supported Resolutions

    • hourly: Data measured once per hour.
    • daily: Data measured or summarized once per day.
    • monthly: Data measured or summarized once per month.

    Data Periods

    • historical: Values based on data that has completed full quality control.
    • recent: Newer values based on data that has not yet passed full quality control.
  2. Overview of Mosmix forecast products

    main

    Mosmix is a DWD forecast product based on global weather models that uses statistical downscaling for land-based climate stations to provide precise, local forecasts. It is available for over 5,000 stations worldwide.

    There are two versions of Mosmix available:

    • Mosmix-S: Includes a set of 40 parameters and is updated every hour.
    • Mosmix-L: Includes approximately 115 parameters and is updated every 6 hours (at 3am, 9am, 3pm, and 9pm).

    Both versions provide a forecast horizon of up to 240 hours.

  3. Overview of GHCN (Global Historical Climatology Network) data

    main

    The NOAA Global Historical Climatology Network (GHCN) provides a collection of hourly and daily weather data aggregated from various weather services worldwide.

    Key characteristics:

    • Resolution: While both hourly and daily data are available, the resolution is often fixed to daily in many implementations as it is the most common and maintainable format for global observations.
    • GHCN-Hourly: This dataset represents the data previously known as the ISD (Integrated Surface Database).
    • Scope: Includes data from regions where public weather data might otherwise be difficult to access.
  4. Overview of DWD Radar products

    main

    The DWD (Deutscher Wetterdienst) provides various radar data products for different radar sites.

    Key products include:

    • Radolan: Advanced radar products providing calibrated areal precipitation. It is available in two versions:
      • Hourly version: Provides hourly sums of precipitation.
      • Daily version: Provides gliding sums of the last 24 hours.
      • Note: Precipitation amounts are provided in units of 1/10 mm.
    • Radvor: A precipitation forecast based on radar data.
    • Standard Site Products: Various products (like echo top and reflectivity) available for specific radar sites.
  5. Overview of Météo-France open data products

    main

    Météo-France provides two main open data products via meteo.data.gouv.fr that can be accessed through this project:

    1. synop: Surface synoptic observation data from approximately 190 stations across metropolitan France and overseas territories. Data is provided at a 3-hourly reporting interval, covering the period from 1996 to the present.
    2. observation: Known as "Données climatologiques de base", these are daily and monthly climatological summaries from a network of several thousand stations. This dataset is sharded by French department.

    All data is published under the Etalab Open License 2.0.

  6. Overview of Hubeau hydrometry data in Wetterdienst

    main

    Wetterdienst integrates the Hubeau API (the open API platform of Eaufrance) to provide real-time river observations for the French river network. The data covers approximately the last 30 days of observations.

    Key characteristics:

    • Data types: Water level (stage) and discharge (flow).
    • Endpoints: Real-time observations are served via hydrometrie/observations_tr (JSON format), and station metadata is available via hydrometrie/referentiel/stations.
    • Authentication: The API is key-less; no authentication is required.
    • Resolution: Because the data is strictly real-time, it uses a single "dynamic" resolution rather than the fixed temporal resolutions used by other observation providers.
  7. Overview of NOAA NWS Observation data

    main

    The NOAA NWS Observation provider provides hourly weather data collected from US weather stations.

    Key Characteristics:

    • Resolution: Fixed at hourly intervals.
    • Temporal Coverage: Data is provided for the last week.
    • Limitation: The current station list may contain inaccuracies; some stations requested may not exist in the NWS Observation network and will return no data.
  8. Overview of MeteoFrance Observation datasets

    main

    The MeteoFrance observation provider provides "Données climatologiques de base" covering thousands of stations across metropolitan France and overseas territories. Data is sharded by French department.

    Important Note on Station Metadata: Station identity, coordinates, and start/end dates are sourced from Météo-France's canonical station metadata registry. Because of this, a small fraction of listed stations may not have downloadable daily or monthly records available.

  9. Overview of supported weather data sources

    main

    The wetterdienst service provides access to meteorological and hydrological data from various national agencies across Europe and globally. Data types include historical observations, recent/real-time observations, statistical forecasts (MOSMIX), and radar products.

    Key Data Providers and Capabilities:

    • DWD (Germany): Extensive coverage including historical observations (~300 years), MOSMIX statistical forecasts (5400 stations worldwide), DMO model-extracted timeseries, road weather observations, SWSMOS road forecasts, and Radar products (Composite, Radolan, Radvor, etc.).
    • AEMET (Spain): Climatological observations (hourly to annual).
    • CHMI (Czechia): Station observations (10-minute to annual).
    • DMI (Denmark/Greenland/Faroe Islands): Quality-controlled climate data.
    • EA (UK): Hydrology data (river flow and groundwater stage).
    • Eaufrance (France): River network data (flow and stage).
    • ECCC (Canada): Historical weather observations (~180 years).
    • FMI (Finland): Station observations via WFS.
    • Geosphere (Austria): Historical meteorological data.
    • IMGW (Poland): Meteorology and Hydrology (daily/monthly summaries).
    • IPMA (Portugal): Near-real-time hourly observations.
    • KNMI (Netherlands): Station observations (10-minute to daily).
    • LHMT (Lithuania): Hourly observations via REST API.
    • Météo-France (France): SYNOP observations and climatological summaries.
    • MeteoSwiss (Switzerland): SwissMetNet automatic weather station network data.
    • MET Norway (Norway): Frost historical and recent observations.
    • Met Office (UK): MIDAS Open archive historical land surface observations.
    • NOAA (USA/Global): GHCN global hourly and daily observations; NWS recent US observations.
    • RMI (Belgium): AWS network observations.
    • SMHI (Sweden): Station observations (1-minute to monthly).
    • WSV (Germany): Pegelonline river network data (stage, runoff).
  10. Overview of DMI Observation data provider

    main

    The DMI (Danish Meteorological Institute) observation provider provides quality-controlled, aggregated station values for stations in Denmark, Greenland, and the Faroe Islands.

    Key characteristics:

    • Resolutions: Available at hourly, daily, monthly, and annual resolutions.
    • Access: Data is served via DMI's key-less OGC API Features endpoint (climateData). No authentication or API keys are required.
    • Data Model: The provider queries the stationValue collection, which returns all available parameters for a specific station, resolution, and date range in a single request.
    • Time Alignment:
      • Hourly: Aligned to UTC and labeled by the start of the hour.
      • Daily, Monthly, Annual: Uses local civil period boundaries (e.g., a Danish day runs from local midnight to local midnight). These aggregates are labeled by their civil calendar date at UTC midnight. The provider automatically widens requested date ranges by one day on each side to ensure local/UTC offsets do not cause boundary periods to be missed.