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
The grib-rs project looks great! Thanks so much for all your work on grib-rs!
I'm interested in lazily opening petabyte sized GRIB datasets on cloud object storage. For example, the NOAA Open Data Dissemination (NODD) project has released 59 petabytes of data to public cloud object storage.
I've recently started a Rust project called hypergrib. hypergrib won't implement the decoding of GRIB messages. Instead, hypergrib will allow users to lazily open huge GRIB datasets (with millions of GRIB files).
Essential to this plan is the ability to interpret the .idx files that are published with many large GRIB datasets. A classic .idx file might look like this:
The columns are message number, byte offset, NWP init datetime, parameter name, vertical level, product type, and ensemble member.
Does grib-rs already implement the ability to decode .idx files?
Proposed Solution
To quickly decode the parameter name, I presume we'd want a HashMap keyed on the name? I must admit I haven't fully understood the codegen part of grib-rs so I'm not sure what the value of the HashMap would be?
Additional Context
No response
The text was updated successfully, but these errors were encountered:
A quick update: I've created a small crate called grib_tables which loads the GDAL CSV files into memory and allows users to get the GRIB parameter details from the abbreviation string (e.g. "TMP") or the GRIB numeric ID. Comments very welcome!
Motivation
The
grib-rs
project looks great! Thanks so much for all your work ongrib-rs
!I'm interested in lazily opening petabyte sized GRIB datasets on cloud object storage. For example, the NOAA Open Data Dissemination (NODD) project has released 59 petabytes of data to public cloud object storage.
I've recently started a Rust project called
hypergrib
.hypergrib
won't implement the decoding of GRIB messages. Instead,hypergrib
will allow users to lazily open huge GRIB datasets (with millions of GRIB files).Essential to this plan is the ability to interpret the
.idx
files that are published with many large GRIB datasets. A classic.idx
file might look like this:The columns are message number, byte offset, NWP init datetime, parameter name, vertical level, product type, and ensemble member.
Does
grib-rs
already implement the ability to decode.idx
files?Proposed Solution
To quickly decode the parameter name, I presume we'd want a
HashMap
keyed on the name? I must admit I haven't fully understood the codegen part ofgrib-rs
so I'm not sure what the value of theHashMap
would be?Additional Context
No response
The text was updated successfully, but these errors were encountered: