3 ms·
No, not really. If you are just looking to work with the data you want to read about extracting from grib2 format. One of the faster ways off the ground is to
by jasonmarks_ 10mo ago
No, not really. If you are just looking to work with the data you want to read about extracting from grib2 format. One of the faster ways off the ground is to use the Pywgrib2_s python package and iterate against the model files using python to extract the fields that are interesting. I have a container on docker hub that has pywgrib compiled with all its dependencies if you want to tinker.
pywgrib
https://www.cpc.ncep.noaa.gov/products/people/lxu/cookbook/about/ https://www.cpc.ncep.noaa.gov/products/people/lxu/cookbook/a...
containerized
https://hub.docker.com/repository/docker/jmarks213/containerized_wgrib2/general https://hub.docker.com/repository/docker/jmarks213/container...
- counters 10mo agoIt's far, far simpler for users to simply use eccodes[1], particularly as implemented in xarray[2]. [1]: https://github.com/ecmwf/eccodes https://github.com/ecmwf/eccodes [2]: https://docs.xarray.dev/en/stable/index.html https://docs.xarray.dev/en/stable/index.html
- jasonmarks_ 10mo agoThat is another viable path, no more no less.