Force re-encoding of already geocoded data

Would it be acceptable to log the debug info to watchdog log instead? Or just dump it to watchdog if devel is not available?

I changed the scope of this issue. It only deals with regeocoding of existing data. I removed the "debugging output" and devel references. Geocoding service exceptions are already logged to watchdog, so that's not really relevant. Issue summary and title are updated as well.

Here's another patch which simply adds a variable to the module config page and which allows you to bypass cached geocoding results.

Thanks, that's really fast! ^^

@pol The variable check is in the current code, but the system setting form part in geocode.admin.inc isn't. Is this intentional? Regular users now have no means to enable this recoding, nor is it documented as a developer option (by setting it through drush for example).

All I'm saying is: this part of my patch is not in the current codebase. So there's no checkbox in the geocoder settings form to enable / disable this variable. Is this intentional?

$form['geocoder_recode'] = array(
   '#type' => 'checkbox',
   '#title' => t('Force re-geocoding'),
   '#description' => t('Enable forced re-geocoding of all geocoded fields on entity save even if there are no apparent changes.<br/><em>This option can slow down bulk saves and increases the amount of calls to the geocoding service.</em>.'),
   '#default_value' => variable_get('geocoder_recode', 0),
);

Try this patch.