One answer would be to create any tiles with an intersecting point, and store them in a temporary cache. When a tile is requested, check the temporary cache for any partially created tiles and use that one to start with, if not in the cache, start with a blank one.
Another fairly easy to implement answer is to shift the "dot" so that it doesn't appear on a tile boundary. This is a very good solution as it requires no cache and as you're talking about 10 pixels, would hardly impact the accuracy of the display. If the user zoomed in, the dot would no longer be on a boundary, or would still be shifted only 10 pixels. I use this method in one of the demos I created for last year's workshop on custom overlays. http://www.usnaviguide.com/ws-2008-02/demotilecookies.htm You can find the entire presentation at: http://www.usnaviguide.com/ws-2008-02/presentation.pdf and a YouTube video of the workshop: http://www.youtube.com/watch?v=IYqfT9i1las -John Coryat http://maps.huge.info http://www.usnaviguide.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
