|
Using Nominatim, I'm able to retrieve a full address from a reverse search. I click in the map, generating a lat/lon value for my click and it will bring back a full address, as such: If I query either raw OSM data (HERE) I'm only able to see the street name. Where is OSM getting the rest of the data from? Am I able to achieve a similar level of depth? I'm currently running a web server hosting |
|
The answer is Nominatim. Nominatim builds an address hierarchy using information from the element's address tags and associatedStreet relations, places in the element's proximity, administrative boundaries enclosing the element and so on. Some of these steps are explained at the development overview. If you open your link and click on details you can see the address hierarchy Nominatim has built and which other OSM elements were used to create this hierarchy. Also note that there are some other geocoders for OSM. 1
I also thought that Nominatim included a few other sources than just pure OSM data (e.g. Tiger address data)
(16 Aug '16, 09:50)
escada
Yes, for the US Nominatim also uses Tiger address data as far as I know. Maybe similar additional data is used for some other countries. I still haven't found any good documentation for all this stuff.
(16 Aug '16, 09:53)
scai ♦
|
SELECT string_agg( place,',') as place FROM (
SELECT name AS PLACE, SUBSTRING(planet_osm_polygon.admin_level FROM '[0-9]{1,2}')::INT AS admin_level_int
FROM
planet_osm_polygon
WHERE
boundary = 'administrative' AND
ST_Intersects('SRID=4326;POINT(78.44131 17.51671)'::geometry, way)
ORDER BY admin_level_int desc
) AS geocoder
|
