Alessandro Amici
Alessandro Amici
At the minimum we need: - [ ] doctrings for public entry points - [ ] README with working examples - [ ] [requires more effort] set up a read...
Data providers have download policies and often require bulk download to be authenticated or limited. We don't intend to make too easy for users to make bulk downloads, instead we...
Proposed by Nicolas Cadieux here: https://lists.osgeo.org/pipermail/qgis-user/2016-March/035876.html NASADEM ami to be a "state-of-the-art global digital elevation model (DEM) derived from a combination of Shuttle Radar Topography Mission (SRTM) processing improvements, elevation...
Suggested by Paolo Cavallini @pcav on qgis-user: https://lists.osgeo.org/pipermail/qgis-user/2016-March/035871.html
Due to the fact that the NetCDF data model is much more free and extensible than the GRIB one, it is not possible to write a generic `xarray.Dataset` to a...
The tests `test_50_sample_data.py::test_canonical_dataset_to_grib[era5-levels-members]` and `test_50_sample_data.py::test_canonical_dataset_to_grib[regular_ll_msl]` fail the round trip test. We observe waring like: ``` WARNING cfgrib.messages:messages.py:171 failed to set key 'number' to 0 WARNING cfgrib.messages:messages.py:171 failed to set key...
Support for *dask* and *dask.distributed* is currently quite good from the point of view of the correctness. We are able to perform complex operations on 320Gb of data from 20...
At least `time_dims` and `extra_coords` should be documented.
Following the other major Open Source projects I intend to move *cfgrib* ` to manage its version with `setuptools_scm`. https://github.com/pypa/setuptools_scm Most of the implementation is taken from *xarray*. This makes...
*cfgrib* relies on the ECMWF *ecCodes* C-library for encoding and decoding the GRIB format, including everything related to the coordinate systems. GRIB files encoded in a `gridType` not supported by...