WPLA Dev 3.0 \\ RESEARCH 03 - Solve issues with PyGRIB when running on Windows #56
Labels
high priority
This issue is given a high priority
investigation
This issue does not deal with fixing an issue, but currently is about finding out the cause only.
research
This issue type indicates the search for alternate solutions to current methods
The goal of WPLA is to be as OS independent as possible. All models, tools, API functionality, etc. should be available for any standard OS
(most Linux distributions, the currently supported Windows versions, and MacOS).
One thorn in this project's side on this has been the parsing of GRIB files.
For python the packages cfgrib and pygrib exist for handling GRIB files, but both of these require the ECCODES toolset for some less standardized access methods for the more complex GRIB files.
Unfortunately ECCODES isn't doing too great on Windows OS installations..
Project Goal:
Find a way to keep OS dependency at zero by either finding a reliable way to use the ECCODES toolset from within any Windows environment without forcing people to do things like install Conda, or by removing the ECCODES toolset from the equation entirely _(though this would likely mean moving away from cfgrib and pygrib...).
Note: One direction to start with is the observation that ECCODES for Windows mostly seems to not work anymore with python 3.7 nowadays. If this proves to be the case, the only people that would still have problems would be those running the API from Windows without Conda (manually installing ECCODES on Windows using Conda allows WPLA to fully work still, even if it is a bit of work).
The text was updated successfully, but these errors were encountered: