Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

INTERSECTS not working with Polygon inner bounds #241

Closed
genesor opened this issue Dec 14, 2017 · 2 comments
Closed

INTERSECTS not working with Polygon inner bounds #241

genesor opened this issue Dec 14, 2017 · 2 comments

Comments

@genesor
Copy link

genesor commented Dec 14, 2017

Hey,

We are currently facing an issue with Tile and the INTERSECTS command and inner bounds of a polygon.

When using INTERSECTS Tile doesn't seem to be taking the inner bounds into account and still returns a polygon even if the point isn't intersecting with the polygon as it is in the "hole" defined by the inner bounds.

image

Here is a GeoJSON gist with some example data https://gist.github.com/anonymous/2b2b3f68f7debdb32f7333e04d8b7265#file-map-geojson

Here is the command used:
This one shouldn't match but it is 🙈

INTERSECTS cities OBJECT {"type":"Point","coordinates":[2.253119945526123,48.841404318083505]}

This one should match and it is.

INTERSECTS cities OBJECT {"type":"Point","coordinates":[2.2564244270324703,48.83788774899389]}

Maybe I'm not using Tile38 as I should and this is intended but it seems weird.

Thanks !

@genesor genesor changed the title INTERSECT not working with Polygon inner bounds INTERSECTS not working with Polygon inner bounds Dec 14, 2017
@tidwall
Copy link
Owner

tidwall commented Dec 15, 2017

That looks like a bug. I'll need to do some investigating. Thanks for the descriptive example.

@tidwall
Copy link
Owner

tidwall commented Dec 18, 2017

I found the issue and pushed the fix. Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants