Hmm - I got an additional idea - I will test it with the official Google Maps page - at the same resolution, and see how that works.
Thanks, Adrian On 11/27/09, Adrian Popa <[email protected]> wrote: > Hmm, thank you for your example. > > So - it might me OpenLayer's fault, not Google API's... > > I didn't know OpenLayers was in the gray area with regard to > respecting the terms of usage... I always felt that everything that > has "Open" in their name is inherently "Good" :) > > I will do additional tests with various layers of Google Maps (I had > tried with the satetlite composite map) and see if I can reach a > conclusion. > > Regards, > Adrian > > On 11/27/09, maps.huge.info [Maps API Guru] <[email protected]> wrote: >> I take that back, only two subdomains were used, mt0 and mt1. >> >> -John Coryat >> >> -- >> >> 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. >> >> >> > -- 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.
