Opened 7 years ago
Closed 5 years ago
#7057 closed defect (wontfix)
Auto-enabled paging of ArcGIS REST may give corrupted data
Reported by: | Jukka Rahkonen | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | closed_because_of_github_migration |
Component: | default | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description
As explained in http://www.gdal.org/drv_geojson.html GDAL enables automatically paging if ArcGIS REST server that requires. However, current implementation may lead to corrupted data as in gis.stackexchange question https://gis.stackexchange.com/questions/256668/ogr2ogr-get-geojson-from-map-server-misses-features-and-creates-duplicates
The error comes from wrong assumption that the n features that server returns if query is made without "resultRecordCount" and "resultOffset" parameters, where n is the server side setting for maximum resultRecordCount, are the same n features which are returned by having
resultRecordCount=n&resultOffset=0
That is not necessarily the case but server may sort features differently if paging parameters are provided or not. The safe way would be to check the server side resultRecordCount limit and query also the first page with explicit record count and offset.
Because GDAL may turn paging on automatically data corruption may happen without user notising it even there are ways to avoid that with some GDAL parameters https://lists.osgeo.org/pipermail/gdal-dev/2017-September/047230.html.
Change History (1)
comment:1 by , 5 years ago
Milestone: | → closed_because_of_github_migration |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.