[gdal-dev] COG via HTTP POST

2024-01-03 Thread Korver, Mark via gdal-dev
Jan 2024 13:14:09 +0100 From: Javier Jimenez Shaw mailto:j...@jimenezshaw.com>> To: gdal dev mailto:gdal-dev@lists.osgeo.org>> Subject: [gdal-dev] COG via HTTP POST Message-ID: mailto:a...@mail.gmail.com>> Content-Type: text/plain; charset="utf-8" Hi Does it make any sens

Re: [gdal-dev] COG via HTTP POST

2024-01-02 Thread Javier Jimenez Shaw via gdal-dev
Thanks Even. I will tell them about the missing SRS On Tue, 2 Jan 2024, 13:39 Even Rouault, wrote: > Javier, > > According to https://httpwg.org/specs/rfc7233.html#header.range , HTTP > Range requests only apply to GET requests. So COGs delivered through POST > can indeed only be usable after

Re: [gdal-dev] COG via HTTP POST

2024-01-02 Thread Even Rouault via gdal-dev
Javier, According to https://httpwg.org/specs/rfc7233.html#header.range , HTTP Range requests only apply to GET requests.  So COGs delivered through POST can indeed only be usable after full download. BTW, someone should ask CNIG to include GeoTIFF SRS tags. At least, for file pnt_sentinel2

[gdal-dev] COG via HTTP POST

2024-01-02 Thread Javier Jimenez Shaw via gdal-dev
Hi Does it make any sense to provide COG via HTTP POST method? If I understand correctly, the "magic" of downloading only what is needed from the server is done with HTTP Range requests. But I am not sure if that works in POST method (it does work in GET method, when enabled ;). In case it could w