John Coryat actually gave me some good advice for a similar problem a couple days ago. Try simplifying your polygon data using Douglas Peucker before encoding it.
On this page: http://www.bdcc.co.uk/Gmaps/Services.htm <http://www.bdcc.co.uk/Gmaps/Services.htm>I found this JS: http://www.bdcc.co.uk/Gmaps/GDouglasPeuker.js <http://www.bdcc.co.uk/Gmaps/GDouglasPeuker.js>Which I used to simplify my polygon data before encoding (351 polygons, almost a hundred thousand points), and it's a lot faster now. I still have to use Google Maps Flash; most browsers just can't render this much data with any speed. There is a tradeoff; the more accurate, the slower. But if you have polygons that touch each other like city boundaries, then the less accurate the polygons are, the more they'll overlap and look bad. Try running the algorithm on your data a few times, playing around with the Kink level, to try to hit the sweet spot between accuracy and speed. Good luck, I'm going to try to post what I've done with this when I get a chance. Here's the map I'm working on: http://www.theformsproject.org/index.html I set my kink level to 20 meters, I bet I could simplify it a little more. 240 meters was a faster, but I had overlappers. Dan http://www.eot.state.ma.us/developers/ On Fri, Jul 31, 2009 at 12:11 PM, Rossko <[email protected]> wrote: > > > One thing I noticed is the Map tile. But I am unclear how to do this. > > Start with John Coryat's workshop > http://www.youtube.com/watch?v=IYqfT9i1las > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
