You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an umbrella issue for various bug reports about failure cases in OverlayNG operations.
The cases always (?) involve nearly-coincident linework (either in a single input or between inputs). The result of overlay operations is obviously incorrect (i.e. it is drastically different from the expected result).
Previously an area-check heuristic was added in #812, but this does not handle all cases. Any fix should be tested to see if it handles the cases resolved by that fix (shapely/shapely#1216, GEOS-1144.
Options for fixing:
add a heuristic sanity check based on the envelopes of the inputs (analogous to the heuristic area check). This will not catch all cases, however
use a more expensive area-based check, utilizing the IntersectionArea approach. This should be (almost?) fully robust, at the cost of decreased performance
The text was updated successfully, but these errors were encountered:
dr-jts
changed the title
OverlayNG produces wildly incorrect results in some situations
OverlayNG produces obviously incorrect results in some situations
Aug 21, 2023
This is an umbrella issue for various bug reports about failure cases in OverlayNG operations.
The cases always (?) involve nearly-coincident linework (either in a single input or between inputs). The result of overlay operations is obviously incorrect (i.e. it is drastically different from the expected result).
Previously an area-check heuristic was added in #812, but this does not handle all cases. Any fix should be tested to see if it handles the cases resolved by that fix (shapely/shapely#1216, GEOS-1144.
Options for fixing:
IntersectionArea
approach. This should be (almost?) fully robust, at the cost of decreased performanceThe text was updated successfully, but these errors were encountered: