Generate and design netCDF4 files using a YAML configuration file.
Project description
H5Yaml
Description
This Python package let you design the abstract data model of your HDF5/netCDF4 files. Where the Abstract Data Model is a conceptual model of data, data types, and data organization. We choose the human-readable data serialization language YAML to define the Abstract Data Model with the following components:
- Groups which define its Hierarchical structure
- Dimensions the size(s) of the variables
- Variables the datasets to hold your data
- Attributes the meta data of the File, Groups, or Variables
From the YAML files, you can create HDF5 or netCDF4 files, which are small because the Variables may still be empty. Thus the abstract data model and storage model can be shared among your colleagues for review, or for metadata compliance checks. For example the CF conventions or the ACDD, by using:
And finally, you can implement the file-structure in JAVA, C++ or Fortran. But of course you can also simply generate the empty products and fill the datasets using Python.
In short, this approach has the following advantages:
- you define the layout of your HDF5/netCDF4 file using YAML which is human-readable and has intuitive syntax.
- you can reuse the YAML configuration file to to have all your product have a consistent layout.
- you can make updates by only changing the YAML configuration file.
- you can have the layout of your HDF5/netCDF4 file as a Python dictionary, thus without accessing any HDF5/netCDF4 file.
The package h5yaml provides the classes YamlToH5 and YamlToNc to generate a HDF5/netCDF4 formatted file from a Python dictionary.
- The class
YamlToH5uses the h5py package, which is a Pythonic interface to the HDF5 binary data format. The generated HDF5 file should be compatible with the netCDF4 format. YamlToH5 is slightly faster than the netCDF4 implementation and generates smaller files. - The class
YamlToNcuses the netCDF4 package, which provides an object-oriented python interface to the netCDF version 4 library. You should use this class when strict conformance with the netCDF4 format is required. However, packagenetCDF4has some limitations, whichh5pyhas not, for example it does not allow variable-length variables to have a compound data-type. - Both classes inherit the class ReadNcYaml, which read the Yaml files and combine the data in to a Python dictionary.
Installation
The package h5yaml is available from PyPI. To install it use pip:
$ pip install [--user] h5yaml
The module h5yaml requires Python3.10+ and Python modules: h5py (v3.14+), netCDF4 (v1.7+) and numpy (v2.0+).
Usage
Example 1) Use the class YamlToNc to generate a template netCDF4 file:
from importlib.resources import files
from h5yaml.yaml_to_nc import YamlToNc
yaml_list = [
files("h5yaml.Data") / "nc_testing.yaml"),
files("h5yaml.Data") / "h5_global_attrs.yaml",
]
# show the YAML configuration as a Python dictionary using pprint
aa = ReadNcYaml(yaml_list)
print(repr(aa))
# generate an in-memory HDF5 file
aa = YamlToNc(yaml_list)
fid = aa.diskless()
# Optional, set any unlimited dimension to a fixed length
aa.set_dims()
# write data to datasets of the file
# ...
# write netCDF4 file to disk
res.to_disk(fid, filename)
Example 2) Use the class YamlToH5 to generate a template HDF5 file:
from importlib.resources import files
from h5yaml.yaml_to_h5 import YamlToH5
yaml_list = [
files("h5yaml.Data") / "h5_testing.yaml"),
files("h5yaml.Data") / "h5_global_attrs.yaml",
]
# show the YAML configuration as a Python dictionary using pprint
aa = ReadNcYaml(yaml_list)
print(repr(aa))
# generate an in-memory HDF5 file
aa = YamlToH5(yaml_list)
fid = aa.diskless()
# Optional, set any unlimited dimension to a fixed length
aa.set_dims()
# write data to datasets of the file
# ...
# write HDF5 file to disk
res.to_disk(fid, filename)
Example 3) Use the class YamlToH5 to generate a template netCDF4 file on disk and add data later.
from importlib.resources import files
from netCDF4 import Dataset
from h5yaml.nc_from_yaml import NcFromYaml
res = YamlToNc(files("h5yaml.Data") / "nc_testing.yaml").create(filename)
with Dataset(filename, "r+") as fid
# write data to variables of the file
...
The YAML file should be structured as follows:
-
The top level are: 'groups', 'dimensions', 'compounds', 'variables', 'attrs_global' and 'attrs_groups'.
-
'attrs_global' and 'attrs_groups' are added in version 0.3.0
-
The names of the attributes, groups, dimensions, compounds and variable should be specified as PosixPaths, however:
- The names of groups should never start with a slash (always relative to root);
- All other elements which are stored in root should also not start with a slash;
- Hoewever the non-group elements require a starting slash (absolute paths) when they are stored not the root.
-
The section 'groups' are optional, but you should provide each group you want to use in your file. The 'groups' section in the YAML file may look like this:
groups: - engineering_data - image_attributes - navigation_data - science_data - processing_control/input_data -
The section 'dimensions' is obligatory, you should define the dimensions for each variable in your file. The 'dimensions' section may look like this:
dimensions: days: _dtype: u4 _size: 0 long_name: days since 2024-01-01 00:00:00Z number_of_images: # an unlimited dimension _dtype: u2 _size: 0 samples_per_image: # a fixed dimension _dtype: u4 _size: 307200 /navigation_data/att_time: # an unlimited dimension in a group with attributes _dtype: f8 _size: 0 _FillValue: -32767 long_name: Attitude sample time (seconds of day) calendar: proleptic_gregorian units: seconds since %Y-%m-%d %H:%M:%S valid_min: 0 valid_max: 92400 n_viewport: # a fixed dimension with fixed values and attributes _dtype: i2 _size: 5 _values: [-50, -20, 0, 20, 50] long_name: along-track view angles at sensor units: degrees -
The 'compounds' are optional, but you should provide each compound data-type which you want to use in your file. For each compound element you have to provide a list with its data-type and optionally its number of elements. The 'compound' section may look like this:
compounds: stats_dtype: time: [u8] index: [u2] tbl_id: [u1] saa: [u1] coad: [u1] texp: [f4] lat: [f4] lon: [f4] avg: [f4] unc: [f4, [2,]] dark_offs: [f4] -
The 'variables' are defined by their data-type ('_dtype') and dimensions ('_dims'), and optionally chunk sizes ('_chunks'), compression ('_compression'), variable length ('_vlen'). In addition, each variable can have as many attributes as you like, defined by its name and value. The 'variables' section may look like this:
variables: /science_data/detector_images: _dtype: u2 _dims: [number_of_images, samples_per_image] _compression: 3 _FillValue: 65535 long_name: Detector pixel values coverage_content_type: image units: '1' valid_min: 0 valid_max: 65534 /image_attributes/nr_coadditions: _dtype: u2 _dims: [number_of_images] _FillValue: 0 long_name: Number of coadditions units: '1' valid_min: 1 /image_attributes/exposure_time: _dtype: f8 _dims: [number_of_images] _FillValue: -32767 long_name: Exposure time units: seconds stats_163: _dtype: stats_dtype _dims: [days] _vlen: True comment: detector map statistics (MPS=163)
Notes and ToDo
- The layout of a HDF5 or netCDF4 file can be complex. From version 0.3, you can split the file definition over several YAML files and provide a list with the names of YAML files as input to H5Yaml and NcYaml.
- From version 0.4, the classes
H5YamlandNcYamlare replaced byNcFromYaml. You can use moduleh5pyto write the netCDF4 file ornetCDF4using the keyword 'module'. Then the classesH5CreateorNcCreateperform thedictto netCDF4 conversion.
Support [TBW]
Road map
- Release v0.1 : stable API to read your YAML files and generate the HDF5/netCDF4 file
Authors and acknowledgment
The code is developed by R.M. van Hees (SRON)
License
- Copyright: Richard van Hees (SRON) (https://www.sron.nl).
- License: Apache-2.0
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file h5yaml-0.5.1.tar.gz.
File metadata
- Download URL: h5yaml-0.5.1.tar.gz
- Upload date:
- Size: 22.6 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.14.6
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
9ce5510ac2c56c482faab72096a97a5043f45ac3b286053976a17029cd96be05
|
|
| MD5 |
8267936680f9520d18654aa94f353e5f
|
|
| BLAKE2b-256 |
cb11ff4720fc4d0c3b9913f21765d1bf6eeec1c624dd8c2a033df4780b1b1801
|
File details
Details for the file h5yaml-0.5.1-py3-none-any.whl.
File metadata
- Download URL: h5yaml-0.5.1-py3-none-any.whl
- Upload date:
- Size: 28.3 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.14.6
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
21a28b19c79bd5f310ce9e82cb5c7587aa4492feae20f36587a19f52e1471219
|
|
| MD5 |
a4ed94607cb8924d4a7fe767d0ec8d78
|
|
| BLAKE2b-256 |
5a83945f066f051511c7bad19a84a9b30a1ec3ae87d37d1202ded66740c389ba
|