Dear Andrew...and indirectly dear Mike.. thanks for the hint on the GMercatorProjection...you were right.. I had to change it to GMercatorProjection(20) and now it works... London Profiler is still alive... When I have some time..after the markings..I am planning on migrate to V3 and most of all on trying to build a tile server...there are too many layers... We'll see..
On 11 June, 09:36, Andrew Leach <[email protected]> wrote: > On Jun 10, 10:46 pm, Rossko <[email protected]> wrote: > > > > > I do get a script error during map initialisation, associated with > > fromPixelToLatLng, which suggests something to do with your custom > > map. Couldn't say what, not familiar with those. > > You're right; I do too, now. > > It looks like theAPItries to do its calculations at zoom 19, so > Mike's caveat > > Potential Pitfalls > > 1. SomeAPIfeatures, such as polylines and ground overlays, > perform their calculations at zoom level 17, rather than at the max > zoom level of the map type. These features will fail if the > GProjection() of the map type ahs less than 18 zoom levels. > << > looks out of date. Try using new GMercatorProjection(20) in the code > and see if that fixes it. > > > You are asking for v=2 but getting served 2.242c ; I'm sure that ought > > to be 2.225 according to the changelog > > See this thread, which details the update > strategy:http://groups.google.com/group/google-maps-api/browse_thread/thread/7... > -- basically, update the code then get round to telling everyone, then > do something about documenting it all. Maurizio may be the first > casualty with the new v=2. -- 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.
