Hi, While I agree with the sentiment, I'm not sure I agree about some of the details. It assumes that on ZARR ZIPs, you need to make twice as many reads, for the local file headers and for the data. But the information in the local header is already available in the central directory, so you can seek directly to the data. This assumption is then used throughout the analysis.
But there are things I don't really like about the format, like the very flexible data model and physical organization, the implicit assumption that everything is lat/lon, and the lack of overviews. I'm also a bit skeptical about the Python ecosystem. My impression is that Zarr just tries (and manages) to be a better NetCDF. Laurentiu On Thu, Feb 27, 2025, at 06:06, Michael Sumner via gdal-dev wrote: > Just clueing into why you might be working with this, have you seen this > critique? (was a bit shocked to see that this is apparently going forward > for Sentinel 2, let alone that it was even considered!) > > https://github.com/csaybar/ESA-zar-zip-decision > > Also glad to see a working example outlined that I can follow, Thanks! > > Cheers, Mike
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
