As reported by @gacarrillor, the following split operation fails:
geosop \
-a "Polygon ((492980.38648063864093274 7082334.45244149677455425, 493082.65415841294452548 7082319.87918917648494244, 492980.38648063858272508 7082334.45244149677455425, 492980.38648063864093274 7082334.45244149677455425))" \
-b "LineString (493825.46541286131832749 7082214.02779923938214779, 492955.04876351181883365 7082338.06309300474822521)" \
split
The polygon (blue) and line (red) in question:
Noding and polygonizing produces 6 polygons; however, point-in-polygon testing finds that only 1 out of those falls within the original, incorrectly reducing the area from 4e-10 to 4e-12. If the code is modified to skip the PIP testing (reasonable if the input has no holes?), the area check still fails because the result area has grown above the allowable threshold (from 4e-10 to 3e-8).
As reported by @gacarrillor, the following split operation fails:
The polygon (blue) and line (red) in question:
Noding and polygonizing produces 6 polygons; however, point-in-polygon testing finds that only 1 out of those falls within the original, incorrectly reducing the area from 4e-10 to 4e-12. If the code is modified to skip the PIP testing (reasonable if the input has no holes?), the area check still fails because the result area has grown above the allowable threshold (from 4e-10 to 3e-8).