On Aug 11, 1:46 am, William <[email protected]> wrote:
> 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).
I have fixed it to deal with other cases in which the area of the
triangle is zero but the vertex is valid.
Please grab a fresh copy of:
http://www.polylib.us/polycluster.js
> 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.
PolyCluster uses a slightly different set of VML tags:
<v:shape
coordorigin=
coordsize=
filled='True'/'False'
stroked='True'/'False'
path=
>
<v:fill
color=
opacity=
>
<v:stroke
color=
opacity=
>
I do not know whether the results are similar because I cannot test
VML on my PC.
--
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.
