Saving unformatted addresses causes future lookup failures about django-address HOT 2 OPEN

Offering an option to discard when an address entered can not be geocoded--or at least an option to ensure the unrecognized address is not used for lookup seems like a good Future Feature.

from django-address.

Hey @jplehmann, my apologies for the huge delay in responding.

The idea behind caching any addresses that weren't able to be looked up was that there are likely going to be some addresses that are not able to be geocoded; the question then becomes what to do with them? Discarding them seems wrong; an address that Google doesn't recognise is not necessarily non-existant. The answer used is to keep the address exactly as the user entered and decide what to do with it later. Addresses that aren't able to be geolocated probably need human eyes to look at them and break them into their respective components.

from django-address.