- Have an address that is correct, right name and point according to `geocomplete.js` in our Frontend App. - Edit an object that creates a map to visualise the point saved, but the lat,lng point and address update to something different to what is stored in the DB - We think that when the form is populated with the current values of the object: - [this line](https://github.com/Papercloud/active_admin_geocomplete/blob/master/app/assets/javascripts/active_admin/geocomplete.js#L34-L36) kicks in and sets the map to the point required. - that then updates the address with what google deems as correct for that location (different to what we have stored) and changes the address field - _when the address field is changed_ the standard geocomplete function is triggered and the new address is searched which returns a different set of coordinates. - the result is that for some addresses an address and coordinates different to the DB are shown on the form.