Unfortunately, I’m not allowed to share the GeoPackage at the moment. I will
get back to you as soon as I have permission or managed to reduce the dataset
accordingly.
In the meantime, I found out, that the Error is not raised, if I use e. g. the
`-where` or `-sql` statement. Here is a command
Leo,
could you provide your GeoPackage file and the layer you're converting ?
(privately possibly)
Even
Le 02/01/2024 à 15:09, Leo Fuhrmann via gdal-dev a écrit :
Hi,
I’m using ogr2ogr 3.8.2 to import a (layer of a) GeoPackage into a
PostGIS database:
```
ogr2ogr --debug ON -f PostgreSQ
Hi,
I’m using ogr2ogr 3.8.2 to import a (layer of a) GeoPackage into a PostGIS
database:
```
ogr2ogr --debug ON -f PostgreSQL "PG:dbname=XX host=XX port=XX user=XX
password=XX”
```
However, I’m seeing an error in the logs that I cannot sort out (see mail
subject and/or logs below). Despite
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
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
+1 Javier
On Tue, 2 Jan 2024, 12:56 Even Rouault via gdal-dev, <
gdal-dev@lists.osgeo.org> wrote:
> Hi,
>
> I have prepared an advanced-of-time GDAL/OGR 3.8.3 release candidate,
> mostly
> to fix a 3.8.0 regression that has been reported lately
> (https://github.com/OSGeo/gdal/issues/8998), that
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
Hi,
I have prepared an advanced-of-time GDAL/OGR 3.8.3 release candidate, mostly
to fix a 3.8.0 regression that has been reported lately
(https://github.com/OSGeo/gdal/issues/8998), that causes content of boolean
fields in GeoPackage or FlatGeobuf datasets to be incorrectly read when
using
the A
