Bug
A feature layer selection query geometry is distorted when activated at small spatial scales.
| Bug ID Number | BUG-000126585 |
|---|---|
| Submitted | November 7, 2019 |
| Last Modified | February 14, 2025 |
| Applies to | Portal for ArcGIS |
| Version found | 10.7.1 |
| Operating System | Windows OS |
| Operating System Version | 2016 64 Bit |
| Status | Will Not Be Addressed |
Additional Information
This is by design and is expected. When using hosted feature services, a “quantizationParameters” object is passed in when performing the query. This can be seen this by opening up a browser’s developer tools and inspect the network traffic. When zooming in, there is a query call made similar to this: https://tmerhige1.esri.com/server/rest/services/SampleWorldCities/MapServer/1/query?f=json&returnGeometry=true&spatialRel=esriSpatialRelIntersects&geometry=%7B%22xmin%22%3A-10018754.171396945%2C%22ymin%22%3A0.000004984438419342041%2C%22xmax%22%3A-5009377.085700965%2C%22ymax%22%3A5009377.085700965%2C%22spatialReference%22%3A%7B%22wkid%22%3A102100%2C%22latestWkid%22%3A3857%7D%7D&geometryType=esriGeometryEnvelope&inSR=102100&outFields=*&outSR=102100&quantizationParameters=%7B%22mode%22%3A%22view%22%2C%22originPosition%22%3A%22upperLeft%22%2C%22tolerance%22%3A9783.939620499961%2C%22extent%22%3A%7B%22xmin%22%3A-180%2C%22ymin%22%3A-89.9000244140625%2C%22xmax%22%3A180.0001220703125%2C%22ymax%22%3A83.62371826171875%2C%22spatialReference%22%3A%7B%22wkid%22%3A4326%2C%22latestWkid%22%3A4326%7D%7D%7D When decoded, it comes across as: https://tmerhige1.esri.com/server/rest/services/SampleWorldCities/MapServer/1/query?f=json&returnGeometry=true&spatialRel=esriSpatialRelIntersects&geometry={"xmin":-10018754.171396945,"ymin":0.000004984438419342041,"xmax":-5009377.085700965,"ymax":5009377.085700965,"spatialReference":{"wkid":102100,"latestWkid":3857}}&geometryType=esriGeometryEnvelope&inSR=102100&outFields=*&outSR=102100&quantizationParameters={"mode":"view","originPosition":"upperLeft","tolerance":9783.939620499961,"extent":{"xmin":-180,"ymin":-89.9000244140625,"xmax":180.0001220703125,"ymax":83.62371826171875,"spatialReference":{"wkid":4326,"latestWkid":4326}}} The quantizationParameters object is sent as { "mode": "view", "originPosition": "upperLeft", "tolerance": 9783.939620499961, "extent": { "xmin": -180, "ymin": -89.9000244140625, "xmax": 180.0001220703125, "ymax": 83.62371826171875, "spatialReference": { "wkid": 4326, "latestWkid": 4326 } } } This is documented at https://developers.arcgis.com/rest/services-reference/query-feature-service-layer-.htm In addition to https://developers.arcgis.com/javascript/3/jsapi/query-amd.html#quantizationparameters The reason for this extra parameter is to help performance. Places with many detailed vertices, such as a coastline, would take longer to render to add every single one of its vertices. The query “generalizes” the geometry by adding this quantizationParamaters. The tolerance can be overwritten manually. To get around this, set FeatureLayer.autoGeneralize = false. By default this is true to help with rendering and performance. If this is not a concern, this can be turned off and the more detailed geometries is displayed. Here is an updated sample showing this, https://jsbin.com/kusokitegi/1/edit?html,outputSteps to Reproduce
Bug ID: BUG-000126585
Software:
- Portal for ArcGIS
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App