-
Re: [TOPP trac] #1993: Don't save coordinates if it can't be geocoded (was: Don't save address if it can't be geocoded)
from "The Open Planning Project"on 2008-06-23 14:12 #1993: Don't save coordinates if it can't be geocoded ----------------------------------------+----------------------------------- Reporter: pw | Owner: pw Type: defect | Status: new Priority: important | Milestone: Geocoding People & Projects Component: opencore.geotagging | Version: Resolution: | Keywords: Confirmation: | Blockedby: Time_to_complete: | Blocking: ----------------------------------------+----------------------------------- Description changed by pw: Old description: > In opencore.geocoding, if the user enters an address that google maps > can't geocode, > we give a javascript warning but we happily save the bad address when you > submit the form anyway. > Maybe we should instead revert to the old saved value, if any? > > Filing this for later as I'm punting on it for now. New description: In opencore.geotagging, if the user enters an address that google maps can't geocode, we give a javascript warning but we happily save the bad address when you submit the form anyway. UPDATE: New spec: We shouldn't save the address at all, see #2631. But need to be sure that the old lat & lon are preserved if there's an error. -- -- Ticket URL: <http://trac.openplans.org/openplans/ticket/1993#comment:2> The Open Planning Project <http://www.openplans.org> Trac - The Open Planning Project