INTERSECTS does not respond correctly with geometry with an inner ring

[mblackgeo]

Describe the bug
Technically a duplicate of #241, but I am still seeing incorrect behavior when running INTERSECTS using a geometry with an inner ring. Consider this example below, where the lines 1,2,3,4 are stored in Tile38 and the query is being run using the green polygon:

INTERSECTS matches lines 1, 2, 3, and 4. This is incorrect as line 2 does not intersect. For reference WITHIN only returns line 4, as expected.

To Reproduce
Steps to reproduce the behavior:

• Insert the lines GeoJSON into Tile38
• Query using the GeoJSON of the green polygon with an inner ring.

Expected behavior
Expected that INTERSECTS would only return 1,3,4 in the result.

Operating System:

• OS: Linux
• CPU: Intel
• Version: 1.29.1
• Container: Docker

Additional context
Originally raised in #241.

[iwpnd]

Hey @mblackgeo

You are correct. It appears to only check an intersection with the polygon exterior ring as linestring in those cases.

[tidwall]

@mblackgeo I pushed a hot fix moments ago. Thanks for reporting.
@iwpnd Thanks for finding the where it's happening.

[iwpnd]

🫡

[tidwall]

ref: tidwall/geojson@5d24577

[mblackgeo]

Thanks for fixing and releasing this so quickly 💯 !