|
Hi, I'm new here so I hope this question is to the right audience. I'm developing software that wants to use the nominatim API for geocoding. We have all the technicalities solved, and get satisfactory results as long as the entered address data is correct. But of course there are situations where the address data we send to nominatim is incorrect. We now have an algorithm as follows: 1) try to get the geocode for street + house number, city, (state,) country code (we add state only for US addresses) 2) if 1 fails, try to get the geocode for city, (state,) country code 3) if 2 fails, try to get the geocode for (state,) country code Unfortunately I can only use country codes, no country names. Now I have two questions:
|
|
Regarding the Netherlands: Nominatim is giving the location based on relation 47796. This includes the 'mainland' part (in Europe), as well as several islands in the Caribbean. These are all part of the country of the Netherlands, so it appears the OSM data is actually correct. But it seems Nominatim is calculating the centre point of all of this, which is somewhere in the Atlantic. I don't know whether this should be mapped or tagged differently. Maybe Nominatim could somehow calculate the centre of just the mainland part. Or use the location of the node with role admin_centre. This should probably be discussed on the appropriate mailing lists. Thanks. Funny to be punished for colonialism even today :-) So, what are the "appropriate mailing lists" to address this issue? (Sorry, I'm a newbee here.)
(16 Sep '11, 09:19)
msol
|
|
If you can accept solutions next to Nominatim's geocoding, have a look at Navit or OsmAnd (both opensourced) how they can find their addresses and how they output if some locations fail. |
