Buffer returns wrong size
The smaller buffer is VertiGIS, and the larger is Esri.
Both are supposedly 450-m buffers.
Esri is correct out of the two. VertiGIS's buffer is closer to ~200-m.
What would be the reason behind this?
-
Actually, I forgot I changed the VertiGIS size, so it's supposed to represent a 400-m buffer, not 450-m.
When I realized this, I figured one was radius while the other was diameter, so I tried doubling VertiGIS's numbers. This actually gives me a better result, but it's still wrong. E.g., I changed 400 > 800 and ran the same query. I got a ~470-m buffer.
0 -
Hey Alexander Bureaux thanks for bringing this up, I remember encountering this as well previously. I suspect this is related to the spatial reference of the map here. If the map is in Web Mercator you need to perform a geodesic buffer (using the geodesic parameter on the activity), or perform the buffer operation in a different spatial reference that supports accurate distance measurements.
There is a comment about this on the Esri buffer method that we call: https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-geometryEngineAsync.html#buffer:~:text=The%20GeometryEngine%20has,geometryService.buffer()
Notice the difference in sizes when toggling the Geodesic input of the Buffer activity. The bigger one is Geodesic = true.
So, try throwing true in here on your buffer activity:
1 -
Geodesic was indeed the issue! Thank you for you help. I am glad this was a straight-forward issue.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
3 kommentarer