For your 60-80 polylines (500 vertices) it sounds like encoding would
improve performance for you.

Try the interactive polyline encoder here:
http://code.google.com/apis/maps/documentation/polylineutility.html

and test it out. (you can paste your own lat/lng's into the 'point
list')

Mapperz
http://mapperz.blogspot.com/

On Nov 1, 12:32 pm, John Cotton <[EMAIL PROTECTED]> wrote:
> Is it nobler to reduced download time for the data and the increased
> client side effort to decode the strings or vice versa?
>
> Does anyone have any strong views/evidence about whether it's better
> to encode polylines or not?
>
> I'm going to be displaying around 60-80 polylines, roughly 500 points
> each.
>
> Has anyone run any tests on this?
>
> Regards and thanks for you view
>
> John
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to