Hi Jukka,
yes it would make sense for the driver to use a larger page size. You
can file an issue about that
Actually we could reuse the same logic as the QGIS OAPIF provider that
determines the page size from the limit.schema.maximum and
limit.schema.default values of the /api response:
Hi,
The OAPIF driver is using page size of 10 features by default
https://gdal.org/drivers/vector/oapif.html#open-options.
"PAGE_SIZE=: Defaults to 10. Number of features to retrieve per
request. Minimum is 1, maximum 1."
I know that 10 is the default page size ("limit") also in the standa