I was trying to configure Nominatim OSM DB on my own server and facing so many issues while using planet file. So as per the suggestions of experts on forums, I did this job for particular small city "Bremen" in Germany and I was successful to do so. Now my issue is, when I am checking the lat/lon of a place from that city I am getting following result: My query: http://MY_SERVER/reverse.php?format=xml&lat=53.078717&lon=8.801239 My result:
</reversegeocode>
While you can see the actual result here for the same lat/ lon: http://nominatim.openstreetmap.org/reverse.php?format=xml&lat=53.078717&lon=8.801239 So please suggest why all this tags (pedestrian, neighbourhood, suburb , city, state, postcode etc.) are missing on my server. what is my mistake in configuration or import? What can I do to solve this? More (Another question), As I have already nominatm installed for one city on my server and now I want to do it for planet. So should I do all the things from the begening? or there is some update kind of mechanism which will upgrade my installation to planet level from the current city level? Please anwser. asked 28 Jun '12, 07:03 Ravi Kotwani |
Small extracts have the disadvantage that they often do not contain the relations of higher administrative units, city and state in your case. Or they are missing some of the boundary ways, which probably happens with the neighborhood. There are two possibilities to fix this:
answered 29 Jun '12, 08:17 lonvia Thanks for your answer. I am going with solution one. So doing process from scratch for Germany.
(29 Jun '12, 10:06)
Ravi Kotwani
@lonvia Hi, I have imported the Germany data from scratch as you told in your option 1. Still I am facing the same problem. Some details: 1043 tables are in DB and following errors I faced while importing: -- type "planet_osm_ways" does not exist -- type "nearplace" does not exist -- type "nearfeature" does not exist -- relation "planet_osm_rels" does not exist Please suggest the solution.
(02 Jul '12, 11:38)
Ravi Kotwani
2
If "planet_osm_ways" and "planet_osm_rels" do not exist then something went wrong already with the osm2pgsql import. Make sure you have the latest version of Nominatim (not older than a week) and that you use the version of osm2pgsql that comes with it.
(02 Jul '12, 20:13)
lonvia
I upgraded my osm2pgsql version as you told. But still facing all the same error. There was no difference even in one small error. Everything was same as previous. Please suggest any other solution. Thanks in advance.
(03 Jul '12, 14:28)
Ravi Kotwani
|
Hi is a old questiond, but i resolved with reindexed data, give the solution for someone in need ... whit this resolved indexed all "place", before the "placex" is a 30%, now is a 100% of a "place" table.
Gracias a todos por su ayuda answered 15 Nov '13, 17:26 alveniz |