Rendering performance is down to the number of polyline segments, more than a few hundred, and the browser will seem slow, especially MSIE.
So make sure you don't have too much detail in your polylines or try and show too many at once. You should probably remove polylines that go completely off screen as the user pans and zooms. On Feb 25, 3:02 pm, marcelo <[email protected]> wrote: > "KML vs. Encoded polygons/polylines" is like "socks vs oranges", two > completely differnt things. > > Here's the best explanation of encoded > polylines/polygons:http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/ > > -- > Marcelo -http://maps.forum.nu > -- > > On Feb 25, 3:48 pm, jqueryui-vienna <[email protected]> wrote: > > > I want to display a larger KML file showing my bike routes in Google > > Maps (approx. 500Kbytes). It works ok, but I'm seeking a way to > > improve the rendering performance, especially the loading period. > > > I heard Google Map's internal coordinate encoding format (GPolygon/ > > GPolyline.fromEncoded) is a faster alternative to KML. What are the > > differences (e.g. are encoded GPolylines drawn in the browser or does > > the google maps server render them to tiles? What's the difference in > > the file size?). > > > regards, > > > Franz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
