The bug is only triggered when two sequential vertices have the same
absolute latitude, one north versus one south. This case is rare in
practice, so if you are just testing you can ignore the bug and we'll fix it
in the next release. However if you need to work around the bug this week,
you can insert 1 extra vertex on the equator between the two endpoints,
like:
var pts = [
new google.maps.LatLng(13.4155, 103.8923),
// HACK: Split the polyline at the equator to work around a geodesic
bug.
new google.maps.LatLng(0, (103.8923 - 76.107) / 2),
new google.maps.LatLng(-13.415, -76.107)
];
- Ben
On Thu, Oct 21, 2010 at 2:11 PM, jfaba <[email protected]> wrote:
> Thanks a lot.
> I've been working for one month on migrating my website from v2 to v3 and I
> would apreciate to know if I have to go back to v2 or wait for this bug to
> be fixed. I really need to use the flight route polyline.
>
> --
> 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]<google-maps-js-api-v3%[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.
