GPolygons and GPolylines make unwarranted assumptions about the projection.
In the case of GPolylines, the problem is well understood. The Google code assumes that the projection maps rectangles to rectangles with the same orientation. When the code tries to optimise the rendering by omitting lines that it considers to be well outside the viewport, the test for whether the polyline bounds intersects the viewport can go wrong for custom projections. In the case of GPolygons, I don't understand the details of what goes wrong. I recommend adding your star to issues 709 and 715. http://code.google.com/p/gmaps-api-issues/issues/detail?id=709 http://code.google.com/p/gmaps-api-issues/issues/detail?id=715 -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
