topic Re: REST API Query Geojson Format Error in ArcGIS REST APIs and Services Questions

REST API Query Geojson Format Error

MaryEllen_Perko — Mon, 02 Apr 2018 17:18:45 GMT

Hi. I’m looking for some help with an error I get using the geojson query format when querying a particular map service layer hosted in AGS. The error returned is “{"error":{"code":400,"message":"Failed to execute query.","details":[]}}” and seems to only occur on certain features.

If you are interested, you can see what I mean here:

https://gis11.services.ncdot.gov/arcgis/rest/services/NCDOT_STIP/MapServer/1/query

In the WHERE clause, you’ll get a returned feature if you enter OBJECTID=284. If you enter OBJECTID=285, you’ll get the error.

Any ideas on what’s going on or where to look is much appreciated.

Thanks.

Re: REST API Query Geojson Format Error

MarieAlexander — Wed, 11 Jul 2018 13:24:56 GMT

Have you ever figured out the cause of this? We are having the exact same problem! Some polygons return the error, some don't...

Re: REST API Query Geojson Format Error

BrianCollins — Fri, 12 Oct 2018 18:00:22 GMT

We have this problem as well. Our issue seems to be related to polygons with complex (multipart or donut) geometry. We get a successful response with all other formats but geoJSON throws an error. I'm going to open a support case on the issue.

Re: REST API Query Geojson Format Error

MalcolmMeyer2 — Tue, 05 Feb 2019 16:38:17 GMT

Did you ever solve this issue? I am getting rendering errors on complex polygons from a GeoJSON pulled from a feature service query. GeoJSON that is pulled from my open data site does not result in rendering errors. In the image below the brighter area is not there. I prefer the query method as it is slightly faster and it guarantees access to the latest data.

Re: REST API Query Geojson Format Error

MarieAlexander — Tue, 05 Feb 2019 18:42:11 GMT

We ended up using a different format other than GeoJSON – I believe we just used JSON

Re: REST API Query Geojson Format Error

LeithBritt1 — Mon, 30 Dec 2019 18:50:32 GMT

I was just able to resolve the issue by tracing the bad feature, which was a polyline, attributing the new one and then deleting the old bad one.