There are some circumstances (migrations especially) in which good geocoded data already exists. In these cases we don't want to allow the geocoder module to geocode the data as it would be a waste of resource (google does limit api calls). A simple flag could be added to just pass the already good values along and save them without running everything to the coding service. A patch follows.

Comments

lliss’s picture

lliss’s picture

Patch for 1.0 tag is attached

simon georges’s picture

Status: Active » Needs review

Changing status, as there is a patch.

puddyglum’s picture

@lliss, this is a year late, but do you have an example implementation in your Migration class?

Pedro Lozano’s picture

StatusFileSize
new718 bytes

I'm currently using a simpler patch that allows me to skip geocoding for all field in an entity.

marcusx’s picture

Issue summary: View changes
Status: Needs review » Closed (won't fix)

There is a solution in migrate for this. See: #2023505: prevent geocoding during migration