If you look at the performance curve, it is flat to about 100, then starts to drop and is still workable at 250-300 but then goes down the tubes over that.
If you have static data, then it's always better to just make a tile layer, the number of tiles is really irrelevant. If your data is of a dynamic nature, then tiles are not really the best idea. A third solution is a hybrid approach. Check out this demo: http://www.usnaviguide.com/ws-2008-02/countyoverlay.htm This one creates the overlay image on the fly based on the bounds of the selection box. This demo uses over 3000 polygons and is extremely quick. The source, data and page for this demo are all open source. You can download it by going to the index of that subdirectory. -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 -~----------~----~----~----~------~----~------~--~---
