Motivation
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:
1:0:d=2017010100:HGT:10 mb:anl:ENS=low-res ctl
2:50487:d=2017010100:TMP:10 mb:anl:ENS=low-res ctl
3:70653:d=2017010100:RH:10 mb:anl:ENS=low-res ctl
4:81565:d=2017010100:UGRD:10 mb:anl:ENS=low-res ctl
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
Motivation
The
grib-rsproject 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.hypergribwon't implement the decoding of GRIB messages. Instead,hypergribwill allow users to lazily open huge GRIB datasets (with millions of GRIB files).Essential to this plan is the ability to interpret the
.idxfiles that are published with many large GRIB datasets. A classic.idxfile 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-rsalready implement the ability to decode.idxfiles?Proposed Solution
To quickly decode the parameter name, I presume we'd want a
HashMapkeyed on the name? I must admit I haven't fully understood the codegen part ofgrib-rsso I'm not sure what the value of theHashMapwould be?Additional Context
No response