On Mar 6, 1:16 pm, Emil Egredzija <[email protected]> wrote: > >> I have a scenario where i do a json call, and it returns array of objects. > >> Each json object is a geo location, either a gmap marker or route/polyline. > >> Every object has properties: id, name, description, kml_url. Kml_url is > >> used to draw a object's kml on a map, > > > Is there some compelling reason to use KmlLayer in this way? It > > strikes me that its become more trouble for you than its worth for > > displaying a handful of 'intereactive' geometries. > > > You could keep your KML data structure and render as ordinary > > overlays, see GeoXml3 > > I just did that today ! :-) > GeoXML3 works superbly, i just couldnt believe that it draws and renders > large amount of kml files instantly. Especially on Chrome. > > I tought that kml server-side rendering was the fastest way to display large > amount of polylines and markers. Was very wrong.
That is all a matter of the processing power and browser you are using. Client-side parsing works OK for powerful modern machines running modern browsers. Server-side tile generation (KmlLayer/FusionTablesLayer) will be better for large data sets on older computers/browsers or mobile browsers. Larry -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
