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
Describe the bug
It looks like there some issues with locality for some returned regions.
In this particular case, locality is not present in whosonfirst response.
In whosonfirst-data-admin-ua-latest.db that I use, I can confirm the data is present.
This module is able to perform point-in-polygon lookups, but it doesn't 'guess' the nearest Point-based geometry, this is a design decision we've made to avoid errors when guessing.
A good fix for this issue would be to replace the point 23.959225, 49.898366 with a Polygon, after the data is fixed all addresses and venues which lie inside that shape will have the correct locality associated.
Describe the bug
It looks like there some issues with locality for some returned regions.
In this particular case, locality is not present in whosonfirst response.
In whosonfirst-data-admin-ua-latest.db that I use, I can confirm the data is present.
For example:
https://api.dev.geocode.earth/v1/autocomplete?size=30&boundary.rect.max_lat=49.909829&boundary.rect.max_lon=24.132048&boundary.rect.min_lat=49.757474&boundary.rect.min_lon=23.883483&lang=en&text=%D0%9A%D1%83%D1%80%D0%BE%D1%80%D1%82%D0%BD%D0%B0&api_key=ge-1e618cf3d7bd023d
Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
The following request should return the data in https://spelunker.whosonfirst.org/id/101862523/ locality
Pastebin/Screenshots
Could you guide me on what the problem might be? Happy to contribute if needed
The text was updated successfully, but these errors were encountered: