The problem is that 2 LatLng corners do not uniquely define a LatLngBounds. I suggest you project 1 corner then compute the relative position of the other corner. On 10 Dec 2010 21:24, "Rossko" <[email protected]> wrote: >> I'm trying to use a large projected overlay which covers from the east >> edge of Alaska to the center of Australia. I'm using these bounds: >> "overlayBounds": [-36.84, -141, 71.1, 174.75] > > The API wraps it round the world "the shortest way". I think the only > cure is to break your overlay into less than hempshere-sized chunks. > > -- > 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.
