This deviates from the original implementation, in that we used to write lat and lng even when values were present on the venue. I think this is required for the "force geocoding" feature to work correctly.

Ah, good catch. This requirement should be captured in a unit test. I'll go ahead and add one. While we're discussing requirements, why not overwrite every field?

I think we're not overwriting all the fields because there are situations where local users will have a better idea how an address should be written than the geocoder will.

Also IIRC, not all of the geocoding backends actually return all the address fields (and this is especially true for international addresses). We probably want to ensure that the address component from geocoder result isn't blank before trying to set it.

Roger that. I'll write a unit test to force the original behavior.

Okay, old behavior is restored, and I added another unit test to codify the requirement of not stomping on existing values with blank ones from the geocoder.