-
Notifications
You must be signed in to change notification settings - Fork 569
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
Tile38 Nearby Does not produce results as expected #710
Comments
Even the following command produce the wrong result, it given OSM&&WAY756852510 as ids INTERSECTS LRS_TEST BUFFER 10.0 WHEREIN meta.layer_id 1 WAY IDS OBJECT "{"type":"Feature","properties":{},"geometry":{"coordinates":[145.02898743753536,-37.834040127081664],"type":"Point"}}" |
NEARBY will only ever consider the center point of linestrings and polygons, hence the result you see. |
@iwpnd , Interesting, It seems like that information is missing from the documentation. What would be the better approach for achieving the same ? My idea is to find all the nearby linestrings to a given point within a specified radius and retrieve them in of ascending distance from the given point.
I tried the above it seems to be working, but the issue is results are not in the order of ascending distance from the given point |
You can use a tool that provides you with the required capabilities such as PostGIS or you can calculate distances in your application and order instead of relying on Tile38 here. |
Sure thank you. |
Describe the bug
I've following Geometry objects in Tile38
To Reproduce
Use the above commands to get the output
Expected behavior
Expected behaviour is to provide me the closest road to the point provided in the NEARBY, and it should produce this output ["OSM&&WAY756852509"], but currently it gives ["OSM&&WAY10592122"] for ids instead of.
Additional context
Tile38 Docker compose:
The text was updated successfully, but these errors were encountered: