On Thu, May 27, 2010 at 5:35 AM, René <[email protected]> wrote: > 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.
Just to be clear: v3 will compute level-of-detail for any polylines or polygons that you create. This takes only a fraction of the total time to render polylines or polygons. > 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? I suggest just passing the LatLng coordinates to google.maps.Polyline or google.maps.Polygon. If the performance turns out to be poor, then I'd suggest using the Ramer-Douglas-Peucker algorithm to remove unnecessary vertices on the server before sending the coordinates to the client. Ben > ...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. > > -- 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.
