On Aug 10, 10:50 pm, bratliff <[email protected]> wrote: > > Thanks again for your test cases. "Backtracking" confuses the "on-the- > fly" point reduction algorithm. The "before" / "after" slope > comparison is equal which causes the intermediate vertex to be > dropped. I will have to compensate for it. > Also because these test cases are in pure VML, it's a problem that affects both google.maps.Polyline and polycluster when backtracking. Like you say it's most likely to happen during on-the-fly point reduction, where the detail of a turnaround is reduced to a single vertex (or as you said it might be removed altogether if the algorithm isn't correct).
However regardless of on-the-fly point reduction, the original data might also contain these backtracks and I think the only workaround is to introduce an extra artificial point at the turnaround point when rendering using VML. ... -- 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.
