You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As hypergrib grows, it feels like one of the main features of hypergrib is the algorithmic generation of the paths of each chunk. This idea is independent of the file format.
Some important NWPs are published as NetCDF files. Perhaps the idea of algorithmic generation of chunk paths could be applied to NetCDF too? Would this be implemented in a separate project ("hyperNetCDF"???). Or implemented within hypergrib? In which case, should we change the name? e.g. to hypergrid (although other projects are called hypergrid).
Conclusion
For the MVP, let's focus on just GRIB. Let's see if hypergrib is useful. If hypergrib is useful, and if there's demand to expand to NetCDF, then let's revisit this question.
The text was updated successfully, but these errors were encountered:
As
hypergrib
grows, it feels like one of the main features ofhypergrib
is the algorithmic generation of the paths of each chunk. This idea is independent of the file format.Some important NWPs are published as NetCDF files. Perhaps the idea of algorithmic generation of chunk paths could be applied to NetCDF too? Would this be implemented in a separate project ("hyperNetCDF"???). Or implemented within
hypergrib
? In which case, should we change the name? e.g. tohypergrid
(although other projects are calledhypergrid
).Conclusion
For the MVP, let's focus on just GRIB. Let's see if hypergrib is useful. If hypergrib is useful, and if there's demand to expand to NetCDF, then let's revisit this question.
The text was updated successfully, but these errors were encountered: