> The bad thing is if I have like > 2000-5000 points that correspond a path in the map that would be > really sooooo slow to complete....
Good. It's a shared service, and other users won't want you hogging it, so Google put in maximum request rates. There are more elegant ways to try to go as fast as allowed http://econym.org.uk/gmap/geomulti.htm but its always going to be deliberately slow. If you are trying to reverse geocode all those points time someone looks at your webpage, that's the wrong approach. Do your geocoding one time, ahead of the time you need to display the results. Or better still, only do the points people are interested in. Do your users really read all 5,000 addresses? What for? -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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.
