While migrating some apps over to v3, I discovered that encoded polylines are gone. That's kind of disappointing, since one of my Google Maps applications uses them and, well, I like the feature. Having an 8-core server pre-encode the polyline seems a lot smarter than having to generate them programmatically in the v3 API -- unless I'm missing something.
Can anyone suggest a best practice, performance-wise, for displaying long, complex polylines? I mean, should I use something other than the Douglas polyline encoder for computing them (well, I know I have to -- but in what format). And then, on the client-side, how should I generate/display them? ...Rene -- 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.
