Make Geocoding Optional [#60049]

I would like to make the geocoding support in location optional, i.e. have a checkbox to turn it off.

I have a separate geocoding service I use that is more accurate. It is easier for me to determine what addresses need to be geocoded if I have empty fields.

Comments

Comment #1

geodaniel commented 24 April 2006 at 12:25

I think that's a good idea to make geocoding optional. I'd actually be in favour of moving the geocoding capabilities to a geocoder.module or something and use location.module as an API only. The same should then apply for mapping capabilities, map links etc. But that's a little off topic for this post.

To solve your issue without code changes, you could remove the data from the zipcodes MySQL table, so no data is being pulled from there to geocode your items. You can then geocode them the way you wish to.

Comment #2

JohnG-1 commented 10 April 2007 at 13:33

Priority:

Normal

» Critical

@ #1.1 geodaniel

I'd actually be in favour of moving the geocoding capabilities to a geocoder.module or something and use location.module as an API only

If I understand correctly you're talking about separating location.module into an independant location.API that deals with proximity searches (etc) on decimal lon/lat co-ordinates, and a dependant geocoding.module to deal with converting idiomatic zipcode (etc) data to decimal.co-ords. I think this is a critically important feature (even a year later!), but I haven't been able to find the relevant discussion thread. Please could someone point me ?