Okay, I see. I guess you can geocode them on the client and display a progress bar as you do so; obviously a large address range could take a while. I'd recommend caching those addresses on the client somewhere, if possible, as I imagine that users will visualize the same addresses repeatedly.
- pamela On Sat, Jun 27, 2009 at 7:40 AM, ed123<[email protected]> wrote: > > Hi Pamela - Just FYI, here's a link to an overview of our GMap > component that outlines our use case. > > http://centigonsolutions.com/components/gmapsmovie/gmaps_intro.html > > > > On Jun 18, 2:46 pm, "pamela (Google Employee)" <[email protected]> > wrote: >> Hi Evan- >> >> No, it's not likely. Our preference is that developers dobatch >> geocoding on the server. Geocoding multiple addresses while the user >> waits is slow, and a waste of geocoding resources if you already know >> the addresses. >> >> - pamela >> >> On Fri, Jun 19, 2009 at 3:44 AM, ed123<[email protected]> wrote: >> >> > Hello, >> >> > Are there plans on the horizon to supportbatch-style geocoding with >> > the Flash API? It would be great to send an array of address values to >> > the geocoder and receive a corresponding array of lat/lng values back >> > to avoid having to time geocoding requests 1 by 1/working around 620 >> > issues. >> >> > Thanks, >> > Evan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" 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-for-flash?hl=en -~----------~----~----~----~------~----~------~--~---
