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
Because I'm writing test generators that build a variety of tests from more basic inputs, I'm seeing this occur a few times in cases where a MultLineString a is created via duplicating another LineString b twice: a = MultiLineString([b, b]).
I'm confused because the problem doesn't occur if the LineStrings that comprise a have no intersection:
However, if the LineStrings that make up a share a vertex, and that vertex intersects with l, then it seems like the LineStrings are combined into a single LineString, then crosses is computed. Anyway I'm just taking some notes here and reporting on my progress.
Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Critical (currently preventing usage)
Please provide a clear description of problem you would like to solve.
This issue is that a MultiLineString made from two identical linestrings changes its
crosses
result as opposed to using the linestrings individually.Because I'm writing test generators that build a variety of tests from more basic inputs, I'm seeing this occur a few times in cases where a MultLineString
a
is created via duplicating another LineStringb
twice:a = MultiLineString([b, b])
.I'm confused because the problem doesn't occur if the LineStrings that comprise
a
have no intersection:However, if the LineStrings that make up
a
share a vertex, and that vertex intersects withl
, then it seems like the LineStrings are combined into a single LineString, then crosses is computed. Anyway I'm just taking some notes here and reporting on my progress.As you can see, the
crosses
result of a MultiLineString is not taking theand
oror
result of crosses on all the individual LineStrings.Describe any alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: