I see that Google's version 2 of their API now includes geocoding. Have you considered using that? I see that you'd prefer not to be concerned about geocoding and leave that to the Location module but this seems like a very nice solution to add to this powerful module.

Thanks for your nice work!

Dan

Comments

Lupin3rd’s picture

Lupin3rd commented

I agree with you!
This feature can be optional (if location is active, gmap don't insert values in database).

webgeer’s picture

webgeer commented
Assigned: Unassigned » webgeer
Status: Active » Fixed

The geocoding of Google is currently used by gmap_location.module if you use the built in location.module replacement abilities.

Note however, that the module does not store the address, it just uses it to get a lat/long

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)
marcoBauli’s picture

marcoBauli commented
Version: » 4.7.x-1.x-dev

How does the gmap_location.module confrontate with Google Terms of Use and Terms of Service?

This problem was raised on a issue in the Location.module project page, here.

Thank you

marcoBauli’s picture

marcoBauli commented

How does the gmap_location.module confrontate with Google Terms of Use and Terms of Service?

This problem was raised on a issue in the Location.module project page, here.

Thank you

webgeer’s picture

webgeer commented

In order to get the API key you have to agree to the terms of service:
http://www.google.com/apis/maps/signup.html

I don't think that there is much that would be a problem for most websites.