topic Re: Error 400 "quantizationExtent parameter is invalid" for a particular layer in ArcGIS Online Questions

Error 400 "quantizationExtent parameter is invalid" for a particular layer

JINANYI — Mon, 28 Nov 2022 19:23:01 GMT

Hi,

Our company has an ArcGIS Online account and I am the admin. I tried to add the VT parcel data layer (https://services1.arcgis.com/BkFxaEFNwHqX3tAw/ArcGIS/rest/services/FS_VCGI_OPENDATA_Cadastral_VTPARCELS_poly_standardized_parcels_SP_v1/FeatureServer) into our web app. When the layer is in the web map, it is functioning properly, but in the web app, it doesn't show up.

Upon inspection, I found that when the web app is requesting this layer's data, the response is the following json:

{ "error" : { "code" : 400, "message" : "Cannot perform query. Invalid query parameters.", "details" : [ "'quantizationExtent' parameter is invalid" ] } }

Which I think is caused by the corresponding request url: https://services1.arcgis.com/BkFxaEFNwHqX3tAw/arcgis/rest/services/FS_VCGI_OPENDATA_Cadastral_VTPARCELS_poly_standardized_parcels_SP_v1/FeatureServer/0/query?f=pbf&returnGeometry=true&spatialRel=esriSpatialRelIntersects&geometry=%7B%22xmin%22%3A-8139626.26903582%2C%22ymin%22%3A5445373.896267351%2C%22xmax%22%3A-8139014.772809589%2C%22ymax%22%3A5445985.392493581%2C%22spatialReference%22%3A%7B%22wkid%22%3A102100%7D%7D&geometryType=esriGeometryEnvelope&inSR=102100&outFields=*&outSR=102100&resultType=tile&quantizationParameters=%7B%22mode%22%3A%22view%22%2C%22originPosition%22%3A%22upperLeft%22%2C%22tolerance%22%3A1.1943285668550647%2C%22extent%22%3A%7B%22xmin%22%3Anull%2C%22spatialReference%22%3A%7B%22wkid%22%3A4326%7D%7D%7D

After decomposing the query string, the quantizationParameters looks like this:

{"mode":"view","originPosition":"upperLeft","tolerance":1.1943285668550647,"extent":{"xmin":null,"spatialReference":{"wkid":4326}}}

Without further knowledge, I believe the "extent" part should include actual values but not just null. I say so because this happens in the web map, where the quantizationParameters looks like this:

{"extent":{"xmin":-8153690.681237178,"ymin":5277212.432810176,"xmax":-8152467.688784616,"ymax":5278435.425262738},"mode":"view","originPosition":"upperLeft","tolerance":2.388657133911135}

I don't know how to fix this, but I think it needs to be fixed by ESRI. Can someone enlighten me?

Re: Error 400 "quantizationExtent parameter is invalid" for a particular layer

SteveDuquette1 — Tue, 29 Nov 2022 15:32:22 GMT

We've been seeing this issue also. What has worked in the past was to rebuild the spatial indexes of the given layers and wait a bit of time after - it takes time after the process for the layer to start behaving even if the process says it's completed... However, last night the rebuild did not solve this issue...and we are investigating this once more this morning...hoping someone from ESRI will comment...

Re: Error 400 "quantizationExtent parameter is invalid" for a particular layer

JINANYI — Tue, 29 Nov 2022 15:37:29 GMT

Sorry for my ignorance, but it sound like you either work for ESRI or is Vermont gov's GIS specialist?

Are you saying multiple users of this layer have encountered this before?

Re: Error 400 "quantizationExtent parameter is invalid" for a particular layer

SteveDuquette1 — Tue, 29 Nov 2022 15:45:47 GMT

Not an ESRI employee nor a Vermont GIS person. I work for the Canadian Federal Gov. We've been seeing this error on some layers that we use. Did you try rebuilding the indexes on AGOL ?

Re: Error 400 "quantizationExtent parameter is invalid" for a particular layer

JINANYI — Tue, 29 Nov 2022 15:51:27 GMT

No, I am just a consumer of their web service, so I can't do that. I am currently working with ESRI tech support too, hope they can fix it.

Re: Error 400 "quantizationExtent parameter is invalid" for a particular layer

JINANYI — Thu, 01 Dec 2022 15:40:03 GMT

The GIS person in VT gov suggested that it might be caused by reprojection from Vermont State Plane (EPSG: 32145) spatial reference to Web Mercator. He told me to use another layer (https://services1.arcgis.com/BkFxaEFNwHqX3tAw/ArcGIS/rest/services/FS_VCGI_VTPARCELS_WM_NOCACHE_v2/FeatureServer), which solved the problem