Yes, that's something I may have to consider, the problem being in this instance is that they aren't providing them one at a time - they simply paste in a list of up to 100 postcodes along with the details in csv format in a textarea. These details are then stored for later on in the process and the requirement is that they are in a future stage presented with all of these details later on in a map. It may be that we have to introduce another stage that goes through thr list one at a time and updates the table with the geocoded results so that we can use them in the map stage. I guess this is viable, but it just seems like a long-winded way around what I thought was going to be simple.
Thank you, Mark On Dec 9, 10:01 am, Rossko <[email protected]> wrote: > > The reason for this approach is that the user has already entered the > > postcodes previously in the process and also provided some extra > > information about them. What I want this step to do is to just load up > > all of the postcodes he has previously entered, along with a pop up > > message for each postcode with the relevant data that they entered for > > it. > > Consider a different approach ... geocode at the point of entry. If > there is any doubt about the location at that stage, the user is > likely to know what they meant. You could provide a map to display > what you think is the (geocoded) location they'e provided, and allow > them to confirm or adjust it before submitting to your store. -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
