It's great to see the active Drupal 7 development of this module. Quick question: Does this module do the actual geocoding or is it just meant to store the coordinates that are geocoded by some other module?

On our end, the goal is to be able to have users 1) enter a street address, 2) geocode that address, 3) store it as coordinates, 4) display it as a map, and then 5) perform proximity searches on it. Does this module do all five parts?

If the module allows users to enter a street address (which is subsequently geocoded by the module), is that address input as one field, multiple fields (address, city, state, zipcode, country), or is it configurable?

And are international addresses supported?

Thanks... sounds like a real promising module! :-)

--Ben

Comments

p0miki’s picture

p0miki commented

@Ben: Not an active developer on this, but I palyed around with this module a abit.
1) enter a street address - check.
2) geocode that address - check. uses google js map api v3. you might want to check their terms and condition as well as the limits on geocoding. (http://code.google.com/apis/maps/terms.html, http://code.google.com/apis/maps/documentation/geocoding/#Limits).
3) store it as coordinates - check. however, at the time being, it doesn't save the address. when you re-enter a post, it will show the marker on the google map, but not the address.
4) display it as a map - check.
5) perform proximity searches on it - not yet. see, if haven't already here: http://drupal.org/node/241484

If the module allows users to enter a street address (which is subsequently geocoded by the module), is that address input as one field, multiple fields (address, city, state, zipcode, country), or is it configurable? - address input is one free text field just as in google maps. not configurable as far as i can see.

And are international addresses supported? - As said before, the geocoding is actually done by google, so it support multilingual input ( i checked it out in hebrew, work fine) , if that is what you ment by international addresses.

BenK’s picture

BenK commented

@p0miki: Thanks for sharing your experiences with the module. Very helpful.

It sounds like the module does most of what I need it to do. Based on your explanation, we'd just need two things:

1. A way to store the address that is entered. That storage wouldn't necessarily need to be provided by the module. I would just need a way to automatically "export" that address to another field or fields at the same time that it was being geocoded. One possibility would be Rules integration: If the module fired a Rules event when the address is about to be geocoded, we could use a generic Rules action to populate another field with the address.

2. Support for the Address Field module (http://drupal.org/project/addressfield). We'll be using the Address Field module as part of Drupal Commerce. So will a lot of other people. So I'd love to be able to get the module to geocode an address that is stored as an Address Field.

I'd love to hear the thoughts of the module maintainer when he has a chance...

--Ben

derjochenmeyer’s picture

derjochenmeyer commented

Thanks for sharing your thoughts and experience.

At the moment Geolocation Field only stores latitude/longitude pairs along with some precalculated data to speed up (yet to implement) proximity look ups. This is the core functionality of Geolocation Field and I'd like to keep it as simple as possible. But of course it would be sad to lose all the location information returned by Google (or any other yet to implement widget).

I don't know if its a good idea to store address information along with lat/lng. Here are some thoughts about that:
#1036056: Suggestion: Populate custom fields with geocoded data

BenK:

On our end, the goal is to be able to have users 1) enter a street address, 2) geocode that address, 3) store it as coordinates, 4) display it as a map, and then 5) perform proximity searches on it. Does this module do all five parts?

This is exactly the intention of this module. To store geolocation for entities (users, nodes, ...).

Patches, ideas, co-maintainers welcome...

michaellander’s picture

michaellander commented
Component: Code » Geolocation field

Have tested this module in a sandbox, it's off to a GREAT start. Really like how smooth and easy it is to use. I am however on the side of argument viewpoint that address should be stored. Perhaps when adding a field, you can have the ability to select between 'address' and 'search'(which it is now) field displays. The alternative would obviously be for someone to use the addressfield module, however I think it would be nice if the modules could somehow place nice together.

jm.federico’s picture

jm.federico commented
Status: Active » Closed (duplicate)

I'm marking this a dup of #1040640: Store and display geocoded address information AND/OR address data entered by users since it seems like it is the only point still not solved.

Proximity searches are also on the works, no issue yet. You can open one if you want. Plz keep 1 issue per request.

Cheers