This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
error reverse geocoding osm_id using nominatim #5249
Assignees
Comments
|
Author: lonvia osm_id geocoding is working fine, e.g. http://nominatim.openstreetmap.org/reverse?format=json&osm_type=W&osm_id=210534388 The way you are referencing is simply not in the database, possibly because it doesn't have a name. |
|
Author: lonvia I've confirmed in the code that unnamed minor highways are ignored. This is not a regression, it has always been that way. Minor highways are the following: service, cycleway, path, footway, steps, bridleway, track, byway, motorway_link, primary_link, trunk_link, secondary_link, tertiary_link |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reporter: t_cmore
[Submitted to the original trac issue database at 7.45am, Friday, 21st November 2014]
the reverse gecodeing of an osm id is not possabily at the moment.
when i send the following request:
http://nominatim.openstreetmap.org/reverse?format=json&osm_type=W&osm_id=182332025
i get this error: Unable to geocode
i also tried it with other valid osm_id, but each time i get the same error. Three weeks ago evrything works fine.
The text was updated successfully, but these errors were encountered: