> And the caching takes large amounts of space further. Yes, it's true. However you eventually go about it, dealing with 20,000 polylines will consume resources somewhere - whether it is storage or processing, at the client or the server.
> So, is there any problem with the google API to > render some hundreds of polylines at a time? It's not a problem with the API, its a problem with how much rendering the browser can do in a sensible time. So it varies by browser and by client device, as has been said here many times before. Much depends on your target audience - might they use elderly PCs or underpowered mobile devices? This should influence your decisions. A "couple of hundred" is generally considered the maximum for individual polyline objects. "Many" hundred would probably be too much. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
