search

torty3 / torty3.github.io

1 stars 1 forks source link

Backend problem? #1

Open rumpeltux opened 10 years ago

rumpeltux commented 10 years ago

The tool seems cool, but I’m not sure the backend is working as intended. Considering for example {{drink | name=Juice store | url= | email= | address= | lat= | long= | directions= | phone= | tollfree= | fax= | hours= | price= | content= }} in the city "Larache", the entry cannot be located, although the tool is querying mapquest for "Juice store , Larache". Running the same query in OpenStreetMap or nominatim however yields the right result. Any idea of what’s wrong there?

rumpeltux commented 10 years ago

Looks like the geocoding/batch API doesn't use the nominatim backend. When using http://open.mapquestapi.com/nominatim/v1/search?format=json… instead, it works :)

torty3 commented 10 years ago

Yeah, the Mapquest Open Batch Geocoding API changed sometime in July. Before that, it worked pretty well, similar to the Nominatim results for Points of Interests, but now it works strictly on address only. And OSM address geocoding just isn't at a great standard yet. I could probably switch it to the Nominatim API, though that would mean a new batch request system needs to be implemented.

nicolas-raoul commented 10 years ago

Could the example at http://torty3.github.io/geobatcher.html be modified to avoid this bug? By using 3 POIs with addresses. Right now when executed, both St Paul's Cathedral and Tower of London point to the same point, which is probably confusing for newcomers.