-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAPIF: Increase the default page size #8522
Comments
Cf https://lists.osgeo.org/pipermail/gdal-dev/2023-October/057759.html for suggested algorithm |
elpaso
added a commit
to elpaso/gdal
that referenced
this issue
Oct 16, 2023
elpaso
added a commit
to elpaso/gdal
that referenced
this issue
Oct 16, 2023
rouault
pushed a commit
that referenced
this issue
Oct 17, 2023
bradh
pushed a commit
to bradh/gdal
that referenced
this issue
Oct 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current default page size in the OGC API Features driver is 10. While this default value is also defined in the OGC API Features standard, for practical use it is all too small. See discussion in the mailing list thread https://lists.osgeo.org/pipermail/gdal-dev/2023-October/057758.html
I think that the larger the page size, and so the less requests needed for reading the data, the better. For that reason the page size could be the maximum limit that is defined in the API of the service. It is of course possible that a service provider has not considered what is a reasonable max limit but just blindly used the value 10000 as it appears in the standard https://docs.ogc.org/is/17-069r4/17-069r4.html#_parameter_limit. For my mind GDAL could still trust on the information that the /api endpoint of the service delivers.
The text was updated successfully, but these errors were encountered: