The restriction of this change brought is that the actual scale between adjacent levels must exactly 2. In V2, you can have arbitrary scales, for example, 1:2000 at one scale then 1:5000 at next level, which is common in certain type of apps.
Another issue you may need to address is explicit scale if you are dealing with real world coordinates, not virtual world like in a gaming app. In those cases, the world may not fit in 256 pixels at zoom 0, so a scale ratio must be calculated. Take a look at the Projection implementation in this example: http://code.google.com/apis/maps/documentation/javascript/demogallery.html?searchquery=Projection Hope this helps. On Aug 3, 9:53 pm, Ray <[email protected]> wrote: > Hey everyone.. > > Ok so I'm updating a Map API implementation from v2 to v3. It uses a > Euclidean Projection formulae that's dependent upon the old 'zoom' > parameter from the v2 interface. > > I looked at the API reference to see if perhaps that was still > available as an overload along side just LatLng, but it doesn't appear > to be. > > So my question is, is there a way to still get zoom in > fromLatLngtoPoint()? > > Barring that, could someone explain the change to me and why zoom was > necessary to formulae before for custom projections, but isn't > necessary now? It'd do wonders in giving me a headstart on this > update. > > Thank you for any help. -- 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.
