photon
photon copied to clipboard
komoot
Photon is unable to locate exact house number
When I look for an exact house number, photon is giving wrong results
http://photon.komoot.de/api/?q=Mainzer%20Landstra%C3%9Fe%201,Frankfurt%20am%20Main&lang=de,
When I search the same address through openstreetmap , getting correct results. https://nominatim.openstreetmap.org/search.php?q=Mainzer+Landstra%C3%9Fe+1%2CFrankfurt+am+Main
I'm having this issue a lot in Canada and the US, i noticed it can't find any result for the US Whitehouse.
http://photon.komoot.de/api/?q=1600%20Pennsylvania%20Ave%20NW,%20Washington,%20DC%2020500,%20United%20States
returns an empty object:
{"features":[],"type":"FeatureCollection"}
I am experiencing the same issue while using the Android implementation (Acastus Photon):
https://github.com/gjedeer/Acastus/issues/10#issue-548932533
@getorca If you get rid of the "NW", it seems to work: http://photon.komoot.de/api/?q=1600%20Pennsylvania%20Ave,%20Washington,%20DC%2020500,%20United%20States
Experiencing the same issues here when directional elements are added.
I am also having this exact same problem.
When I search for "51 Bourke Rd Alexandria Sydney" using Nominatim I get the correct result, but with Photon I get nothing:
https://nominatim.openstreetmap.org/ui/search.html?q=51+Bourke+Rd+Alexandria+Sydney https://photon.komoot.io/api/?q=51+Bourke+Rd+Alexandria+Sydney
If I remove the "51", then I get a result from Photon.
All these examples boil down to the fact that Photon should be better at ignoring unknown parts. For the Frankfurt and Sydney addresses the exact house numbers are missing from the database. For the Washington address we don't have the directional suffix.
It's relatively high on the list but I need to find time to dig more into this. Paid work gets priority for obvious reasons.
@lonvia I have sent you an email to discuss contributing money to implement this fix.
@lonvia I am off project for this week, perhaps into next week. I'd like to look into this
