All good discussion. I have managed to figure my issues out, as it turns out it was rather simple. I just had to reference my database info in the LatLng and I was good to go. I ended up not going the geocode route, and instead opted to convert the addresses to lat long points and add these to my database. Bit more effort up front but better in the end. Thanks Guys!
On Nov 2, 1:39 pm, Esa <[EMAIL PROTECTED]> wrote: > On Nov 2, 5:34 pm, tunerGeek <[EMAIL PROTECTED]> wrote: > > > It's poor style/poor technique to repeatedly geocode the same > > addresses over and over. It's simply wasteful of resources, > > regardless of their vastness. > > I agree. That's why I like that Mike's solution is the most > sophisticated. We don't know the required delay, so we start with some > reasonable value. If we get '620', we increase the > delay.http://econym.org.uk/gmap/example_geomulti.htm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
