On Sep 1, 6:26 am, Paul Kulchenko <paulclin...@gmail.com> wrote: > Bratliff, > > it all makes sense and it seems to work, but there is one small detail > that bothers me. This is the link:http://my-test.dreamhosters.com/gmap.html > > I've implemented the logic as described in this thread and seem to be > getting the correct results, but they are still slightly different > from what gmap is doing. For example, this is what you'll see when you > load the map above: > > Should I simply ignore the difference or is there a bug in my > calculations?
If you look at: www.polyarc.us/experimental you will see the same tile discrepency. It is entirely off screen. It does not really matter. I have not really tried to figure out what is causing it. I recycle tiles which means I must allocate enough tiles for the worst case: (pixelwidth>>8)+2 (pixelheight>>8)+2 I believe Google allocates an extra tile along each edge also. If you measure from the center pixel rather from the top-left pixel, tile replacements will occur at different points. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to Google-Maps-API@googlegroups.com To unsubscribe from this group, send email to google-maps-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---