Hi,
There is something about WFS 2 and paging in
https://gdal.org/drivers/vector/wfs.html
“Paging with WFS 2.0
The WFS driver will automatically detect if server supports paging, when
requesting a WFS 2.0 server. The page size (number of features fetched in a
single request) is limited to 100
Hi,
There are loads of questions in the stack.exchange site where users have
problems with performance when they do something with reading and writing very
large image files. Big files have obviously become much more common now due to
clouds. Users try to solve the problem by increasing GDAL_CA
Dear sir,
Could you please take me off mailing list?
Best,
sowon
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Hi,
I would try with that environmental variable first.
The thing is that there's no way in the vector format conversion tool of
QGIS to specify pure environment variables (GDAL configuration options
can be passed with --config key value, but PGCLIENTENCODING can't be
specify that way). Howe
Hi,
There is some text about client encoding in
https://gdal.org/drivers/vector/pg.html
" By default it is assumed that text being sent to Postgres is in the UTF-8
encoding. This is fine for plain ASCII, but can result in errors for extended
characters (ASCII 155+, LATIN1, etc). While OGR prov
Hi all,
I'm trying to run a command with the GdalUtils.runGdal utility of QGIS
but I get some troubles because of the encoding.
Basically I need to set the encoding to PGCLIENTENCODING=LATIN1. If I
call it in a console, no problem at all (of course :) ). Wondering if I
can set the encoding a
Thank you for the clarification, Even. Now I understand how this works.
I also think the pull request will help to make ogr2ogr behave more as
is intuitively expected.
Have a nice day!
Hernán
Den 2021-11-29 kl. 13:11, skrev Even Rouault:
Hernán,
The URL you specify in the WFS: connection
Hernán,
The URL you specify in the WFS: connection string isn't in general the
one of a GetFeature request, but only the endpoint of the service. When
you specify a GetFeature request, some heuristics trigger, but in WFS 2,
the COUNT parameter is interpreted as the page size, but as this serve
Dear all
I seem to have problems understanding how ogr2ogr interacts with WFS and
hope someone would be able to clarify.
I have this WFS:
https://stationsregister.miljodatasamverkan.se/geoserver/stationsregistret/wfs?
The capabilities document states that it supports WFS 1.0.0, 1.1.0 and
2.
