-
Notifications
You must be signed in to change notification settings - Fork 18
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
Implement Yandex.ru Geocoder additionally to to OSM-Nominatim #369
Comments
@navid-kalaei I guess the Russians soon will complain, that they can not find any address. Then you just could replace the geocoder in their frontend by Yandex... |
If Yandex is too complicated, we can try google: https://developers.google.com/maps/documentation/geocoding/overview |
Hä, did you just solve this @flosse ? |
no but we have tooo many open issues so we can re-open this issue again if there is someone who wants to solve this or if there is a funding. |
... see also #477 |
Problem
Our Russian partners will not be happy with our Geocoder in the frontend, because the open streetmap hardly finds any adress. OSM is really bad in Russia.
For the ofdb-cli it is the same. I can not find any of the adresses, I want to import.
Solution
Yandex.ru offers a free (for up do 25.000 requests per day) geocoder https://yandex.com/dev/maps/geocoder/
We should integrate their geocoder, in case OSM-nominatim does not return any results, as a fall back solution. So we basically would be in use of two geocoder at the same time.
(We somehow have to know, if Yandex was in use for a certain entry, because officially we would have to show credits to them on the map, but in this case, rather on the profile page of the geocoded entry.)
Test adresses:
121609, г. Москва, Рублевское шоссе, 28
Смоленская обл, пгт Кардымово, Октябрьский пер, д 1, кв 1
Geocoding with Yandex:
— Requests to the Geocoder HTTP API. https://yandex.com/dev/maps/geocoder/doc/desc/concepts/about.html
— Calling the geocode() function. : https://yandex.com/dev/maps/jsapi/doc/2.1/ref/reference/geocode.html
The text was updated successfully, but these errors were encountered: