[SEDONA-639] Fix GeometrySplitter accuracy issues when splitting LineStrings #1542
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Did you read the Contributor Guide?
Is this PR related to a JIRA ticket?
[SEDONA-XXX] my subject
.What changes were proposed in this PR?
The algorithm we used before computes the intersection points of the input and the blade and splits the input using the intersection points. The problem is that the intersection point may not perfectly lie on the input LineString due to precision issues of the overlay algorithm, so the input LineString won't be split correctly.
This PR uses a more robust algorithm for splitting LineStrings using LineString blades. It simply computes the difference between the input and blade geometry to derive the split result.
How was this patch tested?
Pass existing tests and a newly added test.
Did this PR include necessary documentation updates?