Greetings; I am trying to update an existing Euclidean projection class from the V2 API to the V3 API. From reading various threads and documentation, it appears the old V2 zoom calculations the projection uses are no longer valid. So, I am trying to use the Euclidean projection code found in this thread: http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/50421ba5c4dd307b/
Running into two issues: 1. The markers on the map change their location on the map when you change zoom level. 2. Panning the map around results in the markers moving to a different location as if the map wrapped even though we have not hit the extent of the world tiles. It appears that at zoom level 0, there are six tiles, each 256x256. However, the edge tiles have some white space padding in them before you hit the actual map detail. I've tried adjusting the values for the EUCLIDEAN_RANGE constant, scaleLat/Lng, and offsetLat/Lng with varying results. Best I can get is altering offsetLat/Lng so the markers display correctly at one zoom level but not others. You can see at this URL what the V2 results look like: http://lorebook.lotro.com/wiki/Special:Advancedsearch?type=npc&action=search&name=&qst=n&map=y&territory=1879061048&service[]=sv_bard And here is what my V3 work currently looks like with no modifications to the various constants/variables: http://home.comcast.net/~sprak/tmp/map.html Can't wrap my noggin around what I need to do to "efine the world size implicitly within your projection's fromLatLngToPoint() and fromPointToLatLng() methods." Any help is appreciated. -- 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.
