The limit is based more on the computer hardware running the browser than anything else, older, slower computers will generate the dreaded "Slow Script" error with a lot fewer objects than a quad processor with oodles of ram. Depending on the market for your page, you have to consider this. The consensus is that keeping the number of markers below 150 or 200 will ensure your page will work in just about any browser/hardware combination that can run the API, polylines and polygons are more flexible, probably 1000 points is a good measure there. Using encoded polylines and polygons can increase this number a bit if used correctly.
The bottom line is you'll need to test your specific application on many different computers to see if it fails. The best bet is to keep the numbers of overlays to the minimum and if lots of them are needed, use image overlays instead of polylines, polygons and markers. -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 -~----------~----~----~----~------~----~------~--~---
