Jack Kelly

@mpiannucci I see that commit 01745ada07d892a6059930958ffe7ae12998abc8 implemented [`MessageMetadata::as_idx(&self, index: usize) -> String`](https://github.com/mpiannucci/gribberish/blob/c3c22f4d2a0405e85ed3a8dc3c0c349a89438657/gribberish/src/message_metadata.rs#L52-L102). Is the intention of this github issue to implement a `MessageMetadata::from_idx(idx_data: &[u8]) -> MessageMetadata` method?

@emfdavid wrote: > the real work in rust is reading the grib files I hear you: The main performance benefits of using Rust will come from reading the grib files...

@mpiannucci wrote: > I would LOVE to have [a `MessageMetadata::from_idx` function] as part of the gribberish Great! Let's make it happen :slightly_smiling_face: First, please may I ask a few quick...

That's great to know, thanks @martindurant. Sorry to ask a slightly off-topic question but: What does kerchunk do if the metadata changes over the course of a dataset? e.g. an...

On the topic of how to handle `.idx` metadata in `gribberish`... I'm sure everyone has considered this already but it feels like there are three distinct _types_ of message metadata:...

This is all super-useful, @emfdavid! ## `.idx` spec I _think_ I'm up for trying to fully understand the `wgrib` source code, and to build something in `gribberish` that can understand...

Have NOAA hinted that they might have appetite for maintaining a public manifest for NODD?

> The full dataset for all products, all steps & runtimes is billions of chunks for a single perturbation of GEFS Yeah. I'm interested in defining a very concise manifest...

(BTW, I'm going to propose that we move discussion of giga-scale manifests etcetera to the `hypergrib` discussion forum, so we can focus this `gribberish` GitHub issue on the question of...

@mpiannucci I've made a start on parsing `.idx` files into `gribberish`'s parameters. I don't (yet) have great Rust macro skills. Please may I ask your advice: Do you think it...