Opened 7 years ago
Closed 5 years ago
#6895 closed defect (wontfix)
GeoJSON: ArcGIS-REST hardcoded variable
Reported by: | TobWen | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | closed_because_of_github_migration |
Component: | default | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description
Hi there,
in https://trac.osgeo.org/gdal/browser/trunk/autotest/ogr/ogr_geojson.py#L2259 the output-type &f=geojson is hardcoded.
This leads to Error 400 on several servers when this filetype has another name. On some servers, this output type is named &f=json or even &f=pjson (of course, GeoJSON gets delivered).
Solution: When there's a output-format string in the URL, you don't need to change it:
https://localhost/arcgis/rest/services/web/trees/MapServer/0/query?where=objectid+is+not+null&outFields=*&outSR=25832&resultRecordCount=500&f=json"
Change History (9)
follow-up: 6 comment:1 by , 7 years ago
follow-up: 7 comment:2 by , 7 years ago
Scrolling could potentially be implemnted by issuing a returnIdsOnly=true request, and then using requests like "where=OBJECTID < 50 AND OBJECTID > 0"
comment:6 by , 7 years ago
Replying to Even Rouault:
2 issues :
- GetExtent() indeed not working because f=geojson not supported and returnExtentOnly=true not supported in f=json
- GetNextFeature() doesn't support properly paging and iterates forever on the first features
Yep, paging got implemented in v10.3 and needs to be activated by the administrator. 10.1 and 10.2 don't support paging at all.
comment:7 by , 7 years ago
Replying to Even Rouault:
Scrolling could potentially be implemnted by issuing a returnIdsOnly=true request, and then using requests like "where=OBJECTID < 50 AND OBJECTID > 0"
Or (when the list has whole/jumps etc.): &objectIds=1,3,5,19,39,43 ... until the limit (normally of 1000).
comment:9 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.
Can be reproduced with "https://geoservice.bochum.de/arcgis/rest/services/Internet/Baumkataster/MapServer/0/query?where=objectid+is+not+null&outFields=*&resultRecordCount=500&f=json"
2 issues :