@Crell tweeted this earlier today, and it's probably worth keeping an eye on.


From the description

Geocoder is a library which helps you build geo-aware applications. It provides an abstraction layer for geocoding manipulations.

The library is splitted in two parts: HttpAdapter and Provider:

HttpAdapters are responsible to get data from remote APIs. Currently, there is one adapter for Buzz, a lightweight PHP 5.3 library for issuing HTTP requests.


phayes’s picture

This looks *awesome* - we should totally support these geocoding services.

phayes’s picture

Title: Watch this library (Geocoder) » Geocoder Library Integration
Category: task » feature
Priority: Minor » Normal

So this is how I would like to run this:

1. I don't want to ask users to install TWO libraries, so first let's get geoPHP onto drupal.org (first need https://github.com/phayes/geoPHP/issues/15)
2. Once that's done we can ask users to *optionally* install geocoder library
3. Add a bunch of additional handlers. We only return handler info if the geocoder library is installed.

A. We need this issue in geoPHP fixed: https://github.com/phayes/geoPHP/issues/19
B. Once we have A, we need to decide on a standard way (within the geocoder module) for handlers to attach additional geocoding info onto $geometry->data;
C. Implement reverse-geocoding from geocoder library

phayes’s picture

So all the requisite changes are in place for this. We can go ahead with this library integration if we want to.

PDR’s picture

My encouragement to anyone with the skills to implement this! Getting reverse-geocoding into Geocoder would be incredibly useful.

steinmb’s picture

Let's see if we can close this and continue in separate issues. 7.x-1.1 now correctly depend on http://drupal.org/project/geophp.

Followup issues:
#1461164: Reverse-Geocode support

We need to decide on a standard way (within the geocoder module) for handlers to attach additional geocoding info onto $geometry->data;

I was unable to find a followup issue, and I'm not really 100% sure what it means. Anyone care to explain an use case and how it is supposed to work?

steinmb’s picture

Status: Active » Fixed
Brandonian’s picture

Status: Fixed » Active

This isn't fixed, b/c it hasn't been implemented. If we've decided to not use the library mentioned in the original post, then we should mark as either postponed or won't fix.

steinmb’s picture

Sorry, I mixed up due to comments in #2.

Have anyone been following http://geocoder-php.org lately and know how much momentum it got? I'm voting for a postponed status.

willdurand’s picture

Hi, I am William, the creator of Geocoder.

We, the Geocoder team [1], would like to integrate Geocoder with Drupal, and this module looks perfect. That is why I am bumping this issue. Based on the few issues I read so far, Geocoder could be a good fit for this module (reverse geocoding, supporting more third-party APIs, etc.).


[1] http://williamdurand.fr/2013/08/29/taking-geocoder-to-the-next-level/

Pol’s picture

Issue summary: View changes

Hi all,

I'm working on the version 2.x of Geocoder, it's now based on Geocoder PHP library.
You can find the repository here: https://github.com/drupol/geocoder

It's still in heavy development but it's getting along pretty nicely.

The Drupal 8 version could also be based on the same code, as I'm using Service Container for the 2.x.

Let me know what you think.