Hi, Thanks for the responses.
I was checking COG and its different compression, and I found that JPEG2000 has few advantages over COG. One major advantage is its resampling method for the overview levels, which I found superior to all the other resampling options available at the COG driver. On Sat, Apr 29, 2023 at 7:53 AM Ujaval Gandhi <uja...@spatialthoughts.com> wrote: > What about using JPEG compression with GeoTIFF files instead and thus > enabling you to use COGs? In my experience, you can get pretty close to the > JPEG2000 file size with a GeoTIFF with JPEG compression. > --- > Ujaval Gandhi > Spatial Thoughts > www.spatialthoughts.com > <https://mailtrack.io/trace/link/f9609ee3ad14467596aab38dba52bda35825bff6?w=bXRvYmJ5NTlAZ21haWwuY29t&url=http%3A%2F%2Fwww.spatialthoughts.com&userId=8747767&signature=0f058cfed806f1e3> > > > > On Fri, Apr 28, 2023 at 12:21 PM Tobby Moalem <mtobb...@gmail.com> wrote: > >> I am looking for a way to use my JPEG2000 over object storage (s3) >> efficiently. JPEG2000 structure is progressive by resolution, meaning that >> in order to get the maximum resolution of a tile, all previous resolutions >> have to be decoded. This leads to performing many GET request that cause >> slow performance for the user. >> >> I know that JPEG2000 is extremely flexible, so I wonder if there is a way >> to store each resolution level by itself (similar to COG structure), so >> that with one GET request I will receive the entire resolution level of a >> tile. >> >> Thanks in advance, >> Tobby >> _______________________________________________ >> gdal-dev mailing list >> gdal-dev@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/gdal-dev >> >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
