Cache and/or shared chunk in app?

[wachsylon]

Wouldn't it be better to add a logic within the app that only one chunk is needed for all 12?

Yes, something like that would be smart, but there are a few edge cases that make it annoying:

• We need at least 12 textures to render HEALPix reasonably efficiently, which means we might have to split a chunk into several. Of course, there may also be cases where we have 2, 4, or even 7 chunks...
• If we have more than 12 chunks (e.g., 48), then it's probably better to have one texture per chunk, because it's the easiest way to load or remove entire textures. Of course, this only works if the chunking really fits the data precisely.
• We may have cases where we have multiple time steps or (soon) multiple levels in one chunk. You have to take that into account, and above all, even in such a case (when moving the time slider), you probably wouldn't want to load or decompress the chunk multiple times...

So yes, that kind of logic would be cool, but getting it right in all cases takes a moment or two...

[Karinon]

there is a PR in zarrita.js which could fix that for us, but is not merged as of now:
manzt/zarrita.js#296