[kylebarron]

You could, you'd just have to be wary of how large the header metadata would be. If you had a single Cloud-Optimized GeoTIFF of the world with internal tiles up to zoom 14, the header metadata could be a few MB, which wouldn't be ideal to load in every client.

[simonw]

Sad to say it but these days loading a few MB to a client is par for the course. I don't think it's a reason not to try and get this working - the range header trick does sound particularly relevant to this format.

UPDATE: Just read https://kylebarron.dev/blog/cog-mosaic/overview which is excellent and clearly you're already very on top of the range request mechanism!

[gregsadetsky]

The posts on this topic on your site are really fascinating!

https://kylebarron.dev/blog/cog-mosaic/overview

https://kylebarron.dev/blog/cog-mosaic/naip

[kylebarron]

Thanks! The text is still relevant but those demos are a little old. If you're curious these demos are from last week (using Cloud-Optimized GeoTIFFs under the hood to serve image data quickly):

- https://studio.unfolded.ai/public/9a2c5cd8-f0f0-43ce-b231-78...

- https://studio.unfolded.ai/public/96c70224-dd89-431f-ae7a-0a...

- https://studio.unfolded.ai/public/af792fd8-1990-4cdc-bf2b-99...

[kylebarron]

See also: https://github.com/pangeo-data/cog-best-practices/issues/9