GeoJSON Point in Polygon searches? about tile38

[rbastian]

NEARBY with a distance of 0 also works:

NEARBY cities POINT 33.4255 -111.94 0
{"ok":true,"objects":[{"id":"tempe","object":{"type":"Polygon","coordinates":[[[-111.9787,33.4411],[-111.8902,33.4377],[-111.895,33.2892],[-111.9739,33.2932],[-111.9787,33.4411]]]}}],"count":1,"cursor":0,"elapsed":"10.386782ms"}

[tidwall]

I finally got around to fixing this issue. You can now issue an INTERSECTS on a point:

INTERSECTS cities OBJECT { "type": "Point", "coordinates": [ -111.9400, 33.4255] }

Though it's not possible to do a WITHIN because a within search find all objects that are fully contained inside of an object. And in your case that a Polygon cannot be fully inside a Point.

Let me know if you run into any problems and thanks for finding this bug.

[tidwall]

@windrunner99

In 1.19.3 the behavior of the tile38-cli was changed in order to fix a bug. 66af8ab

It now requires that when an arguments has a space, like the geojson in your example, it must be encapsulated in quotes.

INTERSECTS cities OBJECT '{ "type": "Point", "coordinates": [ -111.9400, 33.4255] }'

[tidwall]

WITHIN and INTERSECTS cannot be used with points, only polygons or boundaries. This is a limitation of Tile38. But there are workarounds.

It is possible to use your point if it's represented as a polygon:

INTERSECTS cities OBJECT { "type": "Polygon", "coordinates": [[[ -111.9400,33.4255],[ -111.9400,33.4255],[ -111.9400,33.4255],[ -111.9400,33.4255]]] }

Or you can use the BOUNDS keyword:

INTERSECTS cities BOUNDS 33.4411 -111.9787 33.4411 -111.9787

Finally you can use NEARBY and provide a small sub-meter value:

NEARBY cities POINT 33.4411 -111.9787 0.0001

Tile38 should support the Point type for INTERSECTS and WITHIN. I filed a bug #26.

Thanks for reporting this.

[tidwall]

Well that's even better. Thanks for the tip and for reporting this issue.

[icemau]

This does not seem to work anymore. Running this result in:

INTERSECTS cities OBJECT { "type": "Point", "coordinates": [ -111.9400, 33.4255] }
(error) invalid data

Was this revered in a following release?