Is it possible to make geocoder work with Nominatim and our own implementation of Nominatim ?

Comments

phayes’s picture

Yes very likely. Write a geocoder plugin!

michee.lengronne’s picture

How is it possible ? Do I have to write it myself or is it forecasted ?

phayes’s picture

It's not currently planned for. Check out /plugins/geocoder_handler/ for some examples

les lim’s picture

Version: 7.x-1.0 » 7.x-1.x-dev
Component: Miscellaneous » Code
Status: Active » Needs review
StatusFileSize
new2.23 KB

Here's a plugin for MapQuest's implementation of Nominatim.

les lim’s picture

StatusFileSize
new2.26 KB

Whoops, spaces need to be converted to "+" before sending the request. New patch attached.

Actually, on second look, the problem with the earlier patch was urlencode() on the address, which happens within drupal_http_build_query() already. This patch should work anyway.

phayes’s picture

Status: Needs review » Fixed

Thanks! This has been committed at 1f719d9c152de56885784bdaf7f434c5241df395

PDR’s picture

Don't know whether it is okay to post this here, when issue is marked as fixed, but thought it might reach the right people.

Is there any way to use the reverse-geocoding function as per the example below, with this handler?

http://nominatim.openstreetmap.org/reverse?format=xml&lat=52.54874297149...

Or is it affected by any of the issues mentioned in http://drupal.org/node/1334838#comment-5673206 ?

Thank you all for the good work with geocoder.

phayes’s picture

HI PDR,

There is an issue open here asking for general reverse-geocoding support: #1461164: Reverse-Geocode support

Perhaps you could drop your comments in there?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

les lim’s picture

Status: Closed (fixed) » Needs review
StatusFileSize
new569 bytes

Whoops, left a dsm() in that last committed patch. I should've been more careful.

duaelfr’s picture

Thank you Lim for these patches
+1 RTBC

phayes’s picture

Status: Needs review » Fixed

Done!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.