anemoi-datasets 0.5.28__tar.gz → 0.5.29__tar.gz

{anemoi_datasets-0.5.28 → anemoi_datasets-0.5.29}/.github/workflows/downstream-ci-hpc.yml

@@ -48,6 +48,8 @@ jobs:
         gnu@rocky-8.6
         clang@rocky-8.6
         gnu@ubuntu-22.04
+      python_versions: |+
+        - '3.11'
     secrets: inherit
 
   # # Build downstream packages on HPC

{anemoi_datasets-0.5.28 → anemoi_datasets-0.5.29}/.github/workflows/python-pull-request.yml

@@ -19,7 +19,7 @@ jobs:
   checks:
     strategy:
       matrix:
-        python-version: ["3.10", "3.11", "3.12"]
+        python-version: ["3.11", "3.12"]
     uses: ecmwf/reusable-workflows/.github/workflows/qa-pytest-pyproject.yml@v2
     with:
       python-version: ${{ matrix.python-version }}

{anemoi_datasets-0.5.28 → anemoi_datasets-0.5.29}/.gitignore

@@ -141,11 +141,6 @@ _version.py
 *.to_upload
 tempCodeRunnerFile.python
 Untitled-*.py
-*.zip
-*.json
-*.db
-*.tgz
-_api/
 trace.txt
 ?/
 *.prof

{anemoi_datasets-0.5.28 → anemoi_datasets-0.5.29}/.pre-commit-config.yaml

@@ -20,19 +20,19 @@ repos:
   - id: no-commit-to-branch # Prevent committing to main / master
   - id: check-added-large-files # Check for large files added to git
   - id: check-merge-conflict # Check for files that contain merge conflict
--   repo: https://github.com/pre-commit/pygrep-hooks
-    rev: v1.10.0  # Use the ref you want to point at
-    hooks:
-    -   id: python-use-type-annotations # Check for missing type annotations
-    -   id: python-check-blanket-noqa # Check for # noqa: all
-    -   id: python-no-log-warn # Check for log.warn
+- repo: https://github.com/pre-commit/pygrep-hooks
+  rev: v1.10.0  # Use the ref you want to point at
+  hooks:
+  - id: python-use-type-annotations # Check for missing type annotations
+  - id: python-check-blanket-noqa # Check for # noqa: all
+  - id: python-no-log-warn # Check for log.warn
 - repo: https://github.com/psf/black-pre-commit-mirror
-  rev: 25.9.0
+  rev: 25.12.0
   hooks:
   - id: black
     args: [--line-length=120]
 - repo: https://github.com/pycqa/isort
-  rev: 6.1.0
+  rev: 7.0.0
   hooks:
   - id: isort
     args:
@@ -41,7 +41,7 @@ repos:
     - --profile black
     - --project anemoi
 - repo: https://github.com/astral-sh/ruff-pre-commit
-  rev: v0.13.3
+  rev: v0.14.10
   hooks:
   - id: ruff
     args:
@@ -50,36 +50,30 @@ repos:
     - --exit-non-zero-on-fix
     - --exclude=docs/**/*_.py
 - repo: https://github.com/sphinx-contrib/sphinx-lint
-  rev: v1.0.0
+  rev: v1.0.2
   hooks:
   - id: sphinx-lint
-# For now, we use it. But it does not support a lot of sphinx features
-- repo: https://github.com/dzhu/rstfmt
-  rev: v0.0.14
-  hooks:
-  - id: rstfmt
-    exclude: '(cli|schemas)/.*' # Because we use argparse and pydantic sphinx directives
 - repo: https://github.com/b8raoult/pre-commit-docconvert
   rev: "0.1.5"
   hooks:
   - id: docconvert
     args: ["numpy"]
 - repo: https://github.com/tox-dev/pyproject-fmt
-  rev: "v2.7.0"
+  rev: "v2.11.1"
   hooks:
   - id: pyproject-fmt
--   repo: https://github.com/jshwi/docsig # Check docstrings against function sig
-    rev: v0.71.0
-    hooks:
-    -   id: docsig
-        args:
-        - --ignore-no-params # Allow docstrings without parameters
-        - --check-dunders    # Check dunder methods
-        - --check-overridden # Check overridden methods
-        - --check-protected  # Check protected methods
-        - --check-class      # Check class docstrings
-        - --disable=SIG101,SIG102     # Disable empty docstrings
-
+    args: ["--max-supported-python", "3.12"]
+- repo: https://github.com/jshwi/docsig # Check docstrings against function sig
+  rev: v0.74.0
+  hooks:
+  - id: docsig
+    args:
+    - --ignore-no-params # Allow docstrings without parameters
+    - --check-dunders    # Check dunder methods
+    - --check-overridden # Check overridden methods
+    - --check-protected  # Check protected methods
+    - --check-class      # Check class docstrings
+    - --disable=SIG101,SIG102,SIG305     # Disable empty docstrings
 ci:
   autoupdate_schedule: monthly
   autoupdate_commit_msg: "chore(deps): pre-commit.ci autoupdate"

anemoi_datasets-0.5.29/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+    ".": "0.5.29"
+}

{anemoi_datasets-0.5.28 → anemoi_datasets-0.5.29}/CHANGELOG.md

@@ -8,6 +8,33 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 Please add your functional changes to the appropriate section in the PR.
 Keep it human-readable, your future self will thank you!
 
+## [0.5.29](https://github.com/ecmwf/anemoi-datasets/compare/0.5.28...0.5.29) (2026-01-28)
+
+
+### Features
+
+* Abstracting accumulation ([#326](https://github.com/ecmwf/anemoi-datasets/issues/326)) ([57a2895](https://github.com/ecmwf/anemoi-datasets/commit/57a2895c30a7752c96dc2bf7d93de0262693dab6))
+* Add id and location for point data ([#500](https://github.com/ecmwf/anemoi-datasets/issues/500)) ([8cf8a10](https://github.com/ecmwf/anemoi-datasets/commit/8cf8a10a8986d89d115fe87bcb9600f18c682d5e))
+* Add xarray patches for changing time dimension and summing variables ([#494](https://github.com/ecmwf/anemoi-datasets/issues/494)) ([7c44d99](https://github.com/ecmwf/anemoi-datasets/commit/7c44d99329aba869022504d15e746f5ef25abd31))
+* **apply mask:** Apply a boolean mask when opening a dataset ([#496](https://github.com/ecmwf/anemoi-datasets/issues/496)) ([820eb39](https://github.com/ecmwf/anemoi-datasets/commit/820eb39ce48124d274b5fe60c2c12235790fc456))
+
+
+### Bug Fixes
+
+* '--test' changes grid/number  ([#386](https://github.com/ecmwf/anemoi-datasets/issues/386)) ([71238c6](https://github.com/ecmwf/anemoi-datasets/commit/71238c69d307f2266e495f5c39f60d36fe9dcc76))
+* Complement with max distance ([#469](https://github.com/ecmwf/anemoi-datasets/issues/469)) ([a8666fa](https://github.com/ecmwf/anemoi-datasets/commit/a8666fa26f97d32ccc43eb0a729c4773f5369523))
+* Coordinate (multiple) indexing - check indices before comparison ([#506](https://github.com/ecmwf/anemoi-datasets/issues/506)) ([859ed19](https://github.com/ecmwf/anemoi-datasets/commit/859ed194a9a9e0171bd1260e9c6b45d304f9ca5b))
+* Grids for masked datasets, field_shape thinning ([#504](https://github.com/ecmwf/anemoi-datasets/issues/504)) ([e7b8d58](https://github.com/ecmwf/anemoi-datasets/commit/e7b8d58adb83f9764b2df96280ab41e3facb6147))
+* Issue [#477](https://github.com/ecmwf/anemoi-datasets/issues/477) ([#478](https://github.com/ecmwf/anemoi-datasets/issues/478)) ([42b9e27](https://github.com/ecmwf/anemoi-datasets/commit/42b9e27c621be292cea77358c738a6c90590a2a9))
+* Pin min version of ruamel-yaml ([#514](https://github.com/ecmwf/anemoi-datasets/issues/514)) ([e6037b0](https://github.com/ecmwf/anemoi-datasets/commit/e6037b0fa759fb75dc28be79f419e1977010d222))
+* Update README to reflect project maturity status ([#465](https://github.com/ecmwf/anemoi-datasets/issues/465)) ([ec8a15e](https://github.com/ecmwf/anemoi-datasets/commit/ec8a15eac36743502d8850070ce8f1d892a40ef0))
+
+
+### Documentation
+
+* Document the option to specify types when selecting a GRIB message ([#466](https://github.com/ecmwf/anemoi-datasets/issues/466)) ([8940839](https://github.com/ecmwf/anemoi-datasets/commit/8940839ed6f2b7f606e20465f45dbad0c68e2096))
+* Fix interpolate to interpolation key in combining page ([#461](https://github.com/ecmwf/anemoi-datasets/issues/461)) ([990a5c3](https://github.com/ecmwf/anemoi-datasets/commit/990a5c3f54706aacd8252b832ad45b598c7252b2))
+
 ## [0.5.28](https://github.com/ecmwf/anemoi-datasets/compare/0.5.27...0.5.28) (2025-10-30)
 
 

{anemoi_datasets-0.5.28 → anemoi_datasets-0.5.29}/CONTRIBUTORS.md

@@ -1,6 +1,6 @@
 ## How to Contribute
 
-Please see the [read the docs](https://anemoi.readthedocs.io/en/latest/dev/contributing.html).
+Please see the [read the docs](https://anemoi.readthedocs.io/en/latest/contributing/contributing.html).
 
 
 ## Contributors
@@ -10,4 +10,4 @@ Thank you to all the wonderful people who have contributed to Anemoi. Contributi
 
 ## Contributing Organisations
 
-Significant contributions have been made by the following organisations: [DWD](https://www.dwd.de/), [FMI](https://www.ilmatieteenlaitos.fi/), [KNMI](https://www.knmi.nl), [MET Norway](https://www.met.no/), [MeteoSwiss](https://www.meteoswiss.admin.ch/), [RMI](https://www.meteo.be/) & [ECMWF](https://www.ecmwf.int/)
+Significant contributions have been made by the following organisations: [DMI](https://www.dmi.dk/), [DWD](https://www.dwd.de/), [FMI](https://www.ilmatieteenlaitos.fi/), [KNMI](https://www.knmi.nl), [MET Norway](https://www.met.no/), [MeteoSwiss](https://www.meteoswiss.admin.ch/), [RMI](https://www.meteo.be/), [Met Office](https://www.metoffice.gov.uk/), [Météo-France](https://meteofrance.com/) & [ECMWF](https://www.ecmwf.int/)

{anemoi_datasets-0.5.28/src/anemoi_datasets.egg-info → anemoi_datasets-0.5.29}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: anemoi-datasets
-Version: 0.5.28
+Version: 0.5.29
 Summary: A package to hold various functions to support training of ML models on ECMWF data.
 Author-email: "European Centre for Medium-Range Weather Forecasts (ECMWF)" <software.support@ecmwf.int>
 License:                                  Apache License
@@ -216,23 +216,23 @@ Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: Apache Software License
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3 :: Only
-Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Programming Language :: Python :: Implementation :: PyPy
-Requires-Python: >=3.10
+Requires-Python: >=3.11
 License-File: LICENSE
-Requires-Dist: anemoi-transform>=0.1.10
-Requires-Dist: anemoi-utils[provenance]>=0.4.38
+Requires-Dist: anemoi-transform>=0.1.12
+Requires-Dist: anemoi-utils>=0.4.26
 Requires-Dist: cfunits
 Requires-Dist: glom
 Requires-Dist: jsonschema
 Requires-Dist: numcodecs<0.16
 Requires-Dist: numpy
+Requires-Dist: pytest>=8.4.1
+Requires-Dist: pytest-xdist>=3.7
 Requires-Dist: pyyaml
-Requires-Dist: ruamel-yaml
+Requires-Dist: ruamel-yaml>=0.16
 Requires-Dist: semantic-version
 Requires-Dist: tqdm
 Requires-Dist: zarr<=2.18.4

{anemoi_datasets-0.5.28 → anemoi_datasets-0.5.29}/README.md

@@ -1,9 +1,19 @@
 # anemoi-datasets
 
-**DISCLAIMER**
-This project is **BETA** and will be **Experimental** for the foreseeable future.
-Interfaces and functionality are likely to change, and the project itself may be scrapped.
-**DO NOT** use this software in any project/software that is operational.
+<p align="center">
+  <a href="https://github.com/ecmwf/codex/raw/refs/heads/main/Project Maturity">
+    <img src="https://github.com/ecmwf/codex/raw/refs/heads/main/Project Maturity/incubating_badge.svg" alt="Maturity Level">
+  </a>
+  <a href="https://opensource.org/licenses/apache-2-0">
+    <img src="https://img.shields.io/badge/Licence-Apache 2.0-blue.svg" alt="Licence">
+  </a>
+  <a href="https://github.com/ecmwf/anemoi-datasets/releases">
+    <img src="https://img.shields.io/github/v/release/ecmwf/anemoi-datasets?color=purple&label=Release" alt="Latest Release">
+  </a>
+</p>
+
+> \[!IMPORTANT\]
+> This software is **Incubating** and subject to ECMWF's guidelines on [Software Maturity](https://github.com/ecmwf/codex/raw/refs/heads/main/Project%20Maturity).
 
 
 
@@ -11,6 +21,10 @@ Interfaces and functionality are likely to change, and the project itself may be
 
 The documentation can be found at https://anemoi-datasets.readthedocs.io/.
 
+## Contributing
+
+You can find information about contributing to Anemoi at our [Contribution page](https://anemoi.readthedocs.io/en/latest/contributing/contributing.html).
+
 ## Install
 
 Install via `pip` with:

anemoi_datasets-0.5.29/docs/building/sources/accumulate.rst

@@ -0,0 +1,158 @@
+###############
+ accumulate
+###############
+
+.. note::
+
+   The ``accumulate`` source was previously named ``accumulations``.
+   The API has changed in the following ways:
+
+   - The parameter ``accumulation_period`` has been renamed to ``period``.
+   - The source can be now different from ``mars`` (e.g., ``mars``, ``grib-index``)
+     it must now be explicitly specified as a nested dictionary under the ``source`` key.
+   - The (optional) available accumulation intervals can now be specified using the ``availability`` key.
+
+Accumulations and flux variables, such as precipitation, are often
+forecast fields, which are archived for a given base date (or reference
+time) and a forecast time (or step). These fields are valid at the
+forecast time and are accumulated over a given period of time, with the
+relation: :math:`valid\_date = base\_date + step`.
+
+Because the package builds datasets according to the valid date of the
+fields, it must be able to reconstruct the requested accumulation period
+from the available data in the source dataset. Furthermore, some fields
+are accumulated since the beginning of the forecast (e.g. ECMWF
+operational forecast), while others are accumulated since the last time
+step (e.g. ERA5).
+
+The ``accumulate`` source requires the following parameters:
+
+- **period**: The requested accumulation period (e.g., ``6h``, ``12h``, ``24h``, ``1d``).
+  This can be specified as a string with units ``"6h"``.
+  Periods shorter than one hour such as ``"30min"`` are not supported yet.
+- **source**: The data source configuration. Currently only ``mars`` and ``grib-index`` sources are supported.
+- **availability**: Information about how accumulations are stored in
+  the data source. This allows the package to determine which intervals to use
+  for reconstructing the requested accumulation period (see below).
+- **patch** (optional): Patches to apply to fields returned by the source to fix metadata issues.
+  Default patching is to set ``startStep`` to ``0`` when ``startStep==endStep``.
+
+  .. warning::
+
+     If the data provided by the source does not match the definition provided
+     in the ``availability`` parameter, the package will attempt to check the
+     metadata of the source dataset and fail if the accumulation periods cannot
+     be reconstructed.
+     Defining the period to use to reconstruct the request accumulation period and
+     checking the validity of the accumulation and relies on the metadata provided by the data source.
+     **If the metadata is incomplete or inconsistent, the package may produce incorrect results.**
+
+
+Specifying the ``availability`` of accumulation intervals
+=========================================================
+
+Data accumulation methods differ between datasets. Two common methods are to
+accumulate data either from the start of the forecast or from the previous time step.
+
+-  For ECMWF operational forecasts, the data is accumulated from the
+   beginning of the forecast. For example, if the accumulation period is
+   6h and the valid date is 2020-01-01 00:00, the source will use the
+   forecast [1]_ of 2019-12-31 18:00 at step 6h.
+
+-  For ERA5, the data is accumulated since the last time step (hourly
+   accumulations), and forecasts are only available at 06Z and 18Z. For a
+   6h accumulation with valid date 2020-01-01 13:00, the source will sum
+   the fields from the forecast of 2020-01-01 06:00 at steps 1-2h, 2-3h,
+   3-4h, 4-5h, 5-6h, and 6-7h.
+
+There are multiple ways to specify the ``availability`` parameter:
+
+- `Option 1: Type-based availability`_
+- `Option 2: Availability over fixed periods`_
+- `Option 3: Automatic detection for well-known datasets`_
+- `Option 4: Finer control using explicit list of interval`_
+
+
+Option 1: Type-based availability
+---------------------------------
+
+For more explicit control, use the **type** parameter with ``accumulated-from-start``
+or ``accumulated-from-previous-step``, along with **basetime**, **frequency**, and **last_step**.
+
+.. list-table::
+   :widths: 50 50
+   :header-rows: 1
+
+   * - ECMWF operational (accumulated from start)
+     - ERA5 (accumulated from previous step)
+   * - .. literalinclude:: yaml/accumulations-from-start-mars-ecmwf-operational-forecast-2.yaml
+          :language: yaml
+     - .. literalinclude:: yaml/accumulations-from-previous-step-mars-era5-2.yaml
+          :language: yaml
+
+Option 2: Availability over fixed periods
+-----------------------------------------
+
+If the source provides data accumulated over a fixed period, such as
+``availability: "1h"`` for hourly accumulated data, ``"3h"`` for
+3-hourly accumulated data, etc.
+
+This approach should be used when all accumulation intervals for the fixed period are available
+for all base times.
+
+Additionally, the period provided in ``availability`` must be compatible with the requested accumulation period,
+i.e., it must be a divisor of the requested period in ``period``.
+
+.. literalinclude:: yaml/accumulations-grib-index.yaml
+   :language: yaml
+
+Option 3: Automatic detection for well-known datasets
+-----------------------------------------------------
+
+The simplest approach is to use ``availability: auto``. The package will try to
+infer the availability from the ``mars`` source parameters (class, stream, origin).
+Supported combinations are:
+
+- ERA5 reanalysis (class ``ea``, stream ``oper``)
+- ERA5 ensemble data assimilation (class ``ea``, stream ``enda``)
+- ECMWF operational forecasts (class ``od``, stream ``oper``)
+- ECMWF operational ensemble data assimilation (class ``od``, stream ``elda``)
+- Regional reanalysis (class ``rr``, stream ``oper``, origin ``se-al-ec``).
+- ERA5-Land (class ``l5``, stream ``oper``)
+
+Automatic detection is not supported for the ``grib-index`` source.
+
+.. list-table::
+   :widths: 50 50
+   :header-rows: 1
+
+   * - ECMWF operational (accumulated from start)
+     - ERA5 (accumulated from previous step)
+   * - .. literalinclude:: yaml/accumulations-from-start-mars-ecmwf-operational-forecast-1.yaml
+          :language: yaml
+     - .. literalinclude:: yaml/accumulations-from-previous-step-mars-era5-1.yaml
+          :language: yaml
+
+
+Option 4: Finer control using explicit list of interval
+-------------------------------------------------------
+
+For full control, provide an explicit list of ``(basetime, steps)`` pairs.
+
+.. list-table::
+   :widths: 50 50
+   :header-rows: 1
+
+   * - ECMWF operational (accumulated from start)
+     - ERA5 (accumulated from previous step)
+   * - .. literalinclude:: yaml/accumulations-from-start-mars-ecmwf-operational-forecast-3.yaml
+          :language: yaml
+     - .. literalinclude:: yaml/accumulations-from-previous-step-mars-era5-3.yaml
+          :language: yaml
+
+These two examples are equivalent to those shown in Option 1 above.
+
+.. [1]
+
+   For ECMWF forecasts, the forecasts at 00Z and 12Z are from the stream
+   ``oper`` while the forecasts at 06Z and 18Z are from the stream ``scda``.

anemoi_datasets-0.5.29/docs/building/sources/yaml/accumulations-from-previous-step-mars-era5-1.yaml

@@ -0,0 +1,12 @@
+accumulate:
+  period: 6h
+  availability: auto
+  source:
+    mars:
+      expver: "0001"
+      class: ea
+      stream: oper
+      type: fc
+      grid: 20./20.
+      levtype: sfc
+      param: [tp, cp]

anemoi_datasets-0.5.29/docs/building/sources/yaml/accumulations-from-previous-step-mars-era5-2.yaml

@@ -0,0 +1,16 @@
+accumulate:
+  period: 6h
+  availability:
+    type: accumulated-from-previous-step
+    basetime: [6, 18]
+    frequency: 1h
+    last_step: 18
+  source:
+    mars:
+      expver: "0001"
+      class: ea
+      stream: oper
+      type: fc
+      grid: 20./20.
+      levtype: sfc
+      param: [tp, cp]

anemoi_datasets-0.5.29/docs/building/sources/yaml/accumulations-from-previous-step-mars-era5-3.yaml

@@ -0,0 +1,14 @@
+accumulate:
+  period: 6h
+  availability:
+    - [6, "0-1/1-2/2-3/3-4/4-5/5-6/6-7/7-8/8-9/9-10/10-11/11-12/12-13/13-14/14-15/15-16/16-17/17-18"]
+    - [18, "0-1/1-2/2-3/3-4/4-5/5-6/6-7/7-8/8-9/9-10/10-11/11-12/12-13/13-14/14-15/15-16/16-17/17-18"]
+  source:
+    mars:
+      expver: "0001"
+      class: ea
+      stream: oper
+      type: fc
+      grid: 20./20.
+      levtype: sfc
+      param: [tp, cp]

anemoi_datasets-0.5.29/docs/building/sources/yaml/accumulations-from-start-mars-ecmwf-operational-forecast-1.yaml

@@ -0,0 +1,12 @@
+accumulate:
+  period: 6h
+  availability: auto
+  source:
+    mars:
+      expver: "0001"
+      class: od
+      stream: oper
+      type: fc
+      grid: 20./20.
+      levtype: sfc
+      param: [tp, cp]

anemoi_datasets-0.5.29/docs/building/sources/yaml/accumulations-from-start-mars-ecmwf-operational-forecast-2.yaml

@@ -0,0 +1,16 @@
+accumulate:
+  period: 6h
+  availability:
+    type: accumulated-from-start
+    basetime: [0, 12]
+    frequency: 6h
+    last_step: 18
+  source:
+    mars:
+      expver: "0001"
+      class: od
+      stream: oper
+      type: fc
+      grid: 20./20.
+      levtype: sfc
+      param: [tp, cp]

anemoi_datasets-0.5.29/docs/building/sources/yaml/accumulations-from-start-mars-ecmwf-operational-forecast-3.yaml

@@ -0,0 +1,14 @@
+accumulate:
+  period: 6h
+  availability:
+    - [0, "0-6/0-12/0-18"]
+    - [12, "0-6/0-12/0-18"]
+  source:
+    mars:
+      expver: "0001"
+      class: od
+      stream: oper
+      type: fc
+      grid: 20./20.
+      levtype: sfc
+      param: [tp, cp]

anemoi_datasets-0.5.29/docs/building/sources/yaml/accumulations-grib-index.yaml

@@ -0,0 +1,7 @@
+accumulate:
+  period: 6h
+  availability: 1h
+  grib-index:
+      index-db: /path/to/grib/index.db
+      param: [ tp, cp, sf ]
+      levtype: sfc

{anemoi_datasets-0.5.28 → anemoi_datasets-0.5.29}/docs/building/sources.rst

@@ -19,7 +19,7 @@ The following `sources` are currently available:
 .. toctree::
    :maxdepth: 1
 
-   sources/accumulations
+   sources/accumulate
    sources/anemoi-dataset
    sources/cds
    sources/eccc-fstd

{anemoi_datasets-0.5.28 → anemoi_datasets-0.5.29}/docs/howtos/create/01-grib-data.rst

@@ -92,14 +92,15 @@ after that, the parameters are the same as for the `grib` source.
  Selecting GRIB messages
 *************************
 
-You can select GRIB messages using the MARS language. For example, to
-select all the GRIB messages with a specific parameter, you can use the
-``param`` keyword. For example, to select all the GRIB messages with the
-parameters ``2t``, ``10u`` and ``10v``, you can use the following:
+You can select GRIB messages using the MARS language and eccodes_ keys.
+For example, to select all the GRIB messages with a specific parameter,
+you can use the ``param`` keyword. For example, to select all the GRIB
+messages with the parameters ``2t``, ``10u`` and ``10v``, you can use
+the following:
 
 .. literalinclude:: yaml/grib-recipe4.yaml
 
-It is recommended to have several sources to differentiate between
+It is recommended to join several sources to differentiate between
 single-level and multi-level fields.
 
 .. literalinclude:: yaml/grib-recipe5.yaml
@@ -110,6 +111,20 @@ single-level and multi-level fields.
    using an index, the keys must be present in the index file, and
    should have been provided at index creation time.
 
+For example, to select variables by their non-integer ``topLevel``
+value, ``topLevel:d`` can be used. This instructs eccodes_ to retrieve
+``topLevel`` as a double instead of the default integer type.
+
+The ``build.variable_naming`` option or the ``rename`` filter (see
+:ref:`anemoi-transform <anemoi-transform:list-of-filters>`) can be used
+to include the exact ``topLevel`` value in the anemoi-dataset variable
+name. (Be cautious with exact matching of float values when using
+``:d``.)
+
+.. literalinclude:: yaml/grib-recipe6.yaml
+
+.. literalinclude:: yaml/grib-recipe7.yaml
+
 .. _grib_flavour:
 
 *******************