GeoCoding wrong answers

[GoogleCodeExporter]

I made various tests to compare the Nominatim public site 
(nominatim.openstreetmap.org) with the Gisgraphy demo site. 

I used an area I know well. I always entered the exact OSM spelling, as 
displayed in openstreetmap.org. 

With Nominatim, most results - except 2 - were OK: perfect positionning on 
openstreetmap + relevant addressing, usually with: street/hamlet, city, county, 
state, country. 

With Gisgraphy, I noticed that a large percentage of places were not properly 
found (sometimes even the town is not correct): 

- la grande rue, chateau-thebaud
- rue des camélias, chateau-thebaud
- rue des écoles, chateau-thebaud
- rue du Coteau, chateau-thebaud
- route de la poterie, chateau-thebaud
- la bauche, chateau-thebaud
- les croix, chateau-thebaud
- caffino, chateau-thebaud
- la choltière, maisdon sur sèvre (first result is bad, second result is 
nearly correct)
- bonne-fontaine, maisdon sur sèvre
- rue de la maine, maisdon sur sevre => result = Rue de la Sèvre 
Saint-Fiacre-sur-Maine (!)
- rue de la mairie, maisdon sur sevre => result = Rue de la Sèvre 
Saint-Sébastien-sur-Loire (!)
- rue beau soleil, maisdon sur sevre => result = Rue Beau Soleil Luc-sur-Mer (!)

For the following, geolocation is ok, but the address is quite weak (just the 
town: "Maisdon-sur-Sèvre"):
- rue des garennes, maisdon sur sevre
- rue felix dugast, maisdon sur sevre 
- rue beau soleil, maisdon-sur-sevre

And I've not been able to find any hamlet with Gisgraphy. 

Are those issues due to old OSM data? 
I read in the forum that a V4 is on its way. Can we expect those issues to 
disapear? 

Original issue reported on code.google.com by mathieu....@gmail.com on 29 Apr 2014 at 1:15

[GoogleCodeExporter]

Hi 

Yes, the V 3.0 has old data (3 years old) the v 4.0 is currently in beta test 
for france poland and germany, and seems very promissive.

Let me know if you want to join the betatest.

David

Original comment by davidmasclet@gmail.com on 2 May 2014 at 8:41

• Changed state: Started

[GoogleCodeExporter]

hi 

I have checked, all is fixed in v 4.0 except 
la bauche, chateau-thebaud
les croix, chateau-thebaud
la choltière, maisdon sur sèvre 

David

Original comment by davidmasclet@gmail.com on 3 May 2014 at 8:48

[GoogleCodeExporter]

the three results are not correct because it is hamlet and the main city is 
find first

but if you type la bauche, les croix (but not the first result) it is correct
la choltière seems not imported. i will have a look

Original comment by davidmasclet@gmail.com on 3 May 2014 at 8:55

[GoogleCodeExporter]

It sounds promising. 
I'm OK to do some beta-tests on the V4. 

Some context about my need: 
I'm the developer of OSMBonusPack, a library for OSM maps apps on Android. 
This lib already provides a replacement of Google Geocoder, based on Nominatim. 
As yourself, I'm convinced that having a good Geocoding solution for OSM maps 
is a strategic point. 
Nominatim made huge progress in one year, but has still one strong drawback: no 
support for mispelling (Mozar instead of Mozart). 

So my interest for Gisgraphy. 

IMO, some Must-Have features: 
1) Ability to do a world-wide search. In a general purpose map application, it 
is not acceptable to ask the user to specify the country (even if the option to 
restrict to a specific country can be useful for specific needs). 
2) OSM data maintained up-to-date on the demo site. 

And some important features: 
- A "maximum results" param - equivalent to Nominatim "limit" param
- An option to get the enclosing polygon - equivalent to Nominatim "polygon" 
param
- Support for a "prefered viewbox" - equivalent to Nominatim "viewbox" & 
"bounded=0". So that when the user is looking at an area, results are 
preferably (but not exclusively) targeting this area. 

Original comment by mathieu....@gmail.com on 4 May 2014 at 2:14

[GoogleCodeExporter]

hi

the country code won't be required anymore for v 4.0
data will be up to date (import will be done periodically)
max result is already peresent with 'to' and from parameter for pagination
polygon is not implemented yet,but point/radius is already done in v 3.0. I 
plan to have the ability to give a higher score for nearest feature when point 
is given.

David

Original comment by davidmasclet@gmail.com on 4 May 2014 at 7:09

[GoogleCodeExporter]

For beta-testing, do you have a V4.0 installed and accessible with a public 
url? 

Original comment by mathieu....@gmail.com on 6 May 2014 at 8:55

[GoogleCodeExporter]

Just a note: 
I had a simple Web interface for doing Geocoding and Reverse-Geocoding with 
Nominatim. 
I ported it to Gisgraphy API. 
You can find it here: http://comob.free.fr/nominatim/gisgraphy.html

Based on Leaflet and JQuery, this is a light-weigth solution: just an html 
file. 

I've not been able yet to implement the full-text search (due to lack of json 
callback in the API). 

Original comment by mathieu....@gmail.com on 9 May 2014 at 2:21

[GoogleCodeExporter]

Original comment by davidmasclet@gmail.com on 14 May 2014 at 6:39

• Changed state: Fixed