Intersect activity errors - set geometry tolerances?
Results from an intersect between polygon layers shows that some vertices are being dropped. Almost like the input geometry(s) are being generalised or simplified prior to the intersect.
Most of the differences are quite small, but may accumulate for jagged boundaries on large areas and this is not desired, especially just the perception by people drilling down and seeing that the vertices don't match thinking it's more of an issue than it might actually be...
An example of an intersect result is attached
Does anyone know of any way to improve this behaviour such that it does not occur?
For example, is there any way to set a tolerance for the output vertices or forcing it to follow exactly the inputs?
Thanks for any ideas.
-
I 'think' I finally got to the bottom of this... this issue arose when using geometry read directly from the rendered features.
This behaviour was not evident when the geometry was directly queried from the data source.
Duh! Appears the geometry was retrieved or rounded to appropriate sig. figures for the scale prior to rendering. understandable. Lesson learnt.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
1 kommentar