What's acceptable performance is very subjective and depends on the hardware, Internet connection speed and browser. Unless you know that your user is using Chrome or SpiderMonkey, my recommendation would be to not use more than 100 GPolyline overlays.
Last I heard, using GGeoXml to render your KML limits you to 50 objects. Using EGeoXml or GeoXml to render your KML causes your lines to be displayed as GPolyline overlays, so that takes you back to the first case. A single transparent EInsert overlay is fine, as long as the image size isn't too large, but it becomes unwieldy if you need to show fine detail when the user zooms in. The ultimate solution is to create a tile layer overlay, with sets of transparent tiles for different zoom levels. You can either create the individual tile images beforehand, or write a server to generate each tile on demand, as happens here (with polygons rather than polylines, but the principle is the same): http://maps.webfoot.com/HousingOverlays.php -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
