On Apr 16, 1:20 pm, Brett <[email protected]> wrote: > Perfect, makes sense. Thanks for all the help!
Sorry, I didn't look real closely at what you were trying to do. With IE it is the number of objects that you manage on the map. Your file contains several hundred individual polylines (690 to be exact...). Even if you encode them, IE will be slow. Somewhere there was a thread with a rule of thumb for polylines, I don't remember the number for reasonable performance. Unless you can combine the polylines, you will probably need to make a custom tile layer to get reasonable performance. Here is one thread that talks about this: http://groups.google.com/group/Google-Maps-API/browse_frm/thread/bb34cab86749ef1c/06c81d2a25cd25bf?lnk=gst&q=encoded+polyline+performance#06c81d2a25cd25bf Some more (that I found trying to find the "rule of thumb"): http://groups.google.com/group/Google-Maps-API/browse_frm/thread/2b507d94a1bcaa17/44eb9ad18b2542b4?lnk=gst&q=polyline+vertices+performance#44eb9ad18b2542b4 http://groups.google.com/group/Google-Maps-API/browse_frm/thread/f228733c0dab2d27/b93320d85a0d4ead?lnk=gst&q=polyline+vertices+performance#b93320d85a0d4ead http://groups.google.com/group/Google-Maps-API/browse_frm/thread/e7b707c2b29fa77b/ea49c53476541aa1?lnk=gst&q=polyline+vertices+performance#ea49c53476541aa1 ================= quoted from the thread above ============= Mike Williams wrote: Wasn't it John Cotton who wrote: >I'm going to be displaying around 60-80 polylines, roughly 500 points >each. There's a lot of variability depending on the exact details of the polys, but I'd guess that that would be unacceptably slow whether you encode them or not. (Except, possibly, in Google Chrome or TraceMonkey). ==================================================== http://groups.google.com/group/Google-Maps-API/browse_frm/thread/b5bfb103e682e3f7/637e0fec0e6d3536?lnk=gst&q=polyline+vertices+performance#637e0fec0e6d3536 http://groups.google.com/group/Google-Maps-API/browse_frm/thread/4f73b420ea15eec/dbac0b01b0975305?lnk=gst&q=encoded+polyline+performance#dbac0b01b0975305 http://groups.google.com/group/Google-Maps-API/browse_frm/thread/41d98cd953ac8a33/f2e7c54984365caf?lnk=gst&q=encoded+polyline+performance#f2e7c54984365caf -- Larry > > On Apr 16, 3:11 pm, "[email protected]" <[email protected]> > wrote: > > > > > On Apr 16, 1:03 pm, Brett <[email protected]> wrote: > > > > Wowza! I dont know why I hadn't seen this stuff on encoded polylines > > > before. Thank you much. > > > > I'm still a little confused at how encoding polylines would make a big > > > difference in the discrepancy between load times for IE and Firefox. > > > IE (all versions, but it is getting better) is less efficient at a lot > > of operations than FF. It supports a lot less markers or points in > > lines than FF before it gets unusable. > > > -- Larry > > > > I will go ahead and learn and get in the practice of encoding my > > > polylines, but I still don't think this is the reason underlying IE > > > being so much slower than firefox in this case. > > > > On Apr 16, 2:29 pm, "[email protected]" <[email protected]> > > > wrote: > > > > > On Apr 16, 11:35 am, Brett <[email protected]> wrote: > > > > > > Hmm. Yes, I could certainly shorten the line coordinates for fewer > > > > > decimals, but I'm guessing that's not the heart of my problem here. > > > > > > And, unfortunately, being a novice, I don't know (even after looking > > > > > at the two examples) what is meant precisely by 'encoding the > > > > > polylines'. Could someone explain a bit more, if and how this is > > > > > really likely to speed up load time in IE? > > > > > See Mark McClure's discussion of encoded > > > > polylines:http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/ > > > > > > On Apr 16, 1:11 pm, "[email protected]" <[email protected]> > > > > > wrote: > > > > > > > On Apr 16, 10:53 am, Brett <[email protected]> wrote: > > > > > > > > Hello. Just wanted to say thanks ahead of time to everyone that > > > > > > > posts > > > > > > > answers on these threads (esp Mike Williams). I've learned a TON > > > > > > > recently. > > > > > > > > Anyhow, I'm very new to websites and coding (social scientist by > > > > > > > trade), so I could be missing something basic.. I've created > > > > > > > several > > > > > > > google maps reading from xml files now, and they all seem to work > > > > > > > pretty well on IE7 (and even better on Firefox). > > > > > > > > However, my latest is causing a major headache. The page is: > > > > > > > >http://www.terevaka.net/dc/databases/rosendahl_1994/Lapakahi.html > > > > > > > > My problems are: > > > > > > > 1) Load time: Load time in Firefox is about 3-10 seconds on my > > > > > > > machine. Load time in IE7 or IE8 is about 60 seconds! Other maps > > > > > > > of > > > > > > > mine have had differences but nothing as drastic as this. One > > > > > > > other > > > > > > > source has told me that load time for his machine on the same > > > > > > > page in > > > > > > > IE7/8 is much better than on mine, but still doesnt compete with > > > > > > > Firefox. > > > > > > > 2) Sometimes in Firefox I have to refresh a few times before I > > > > > > > get a > > > > > > > 'clean' load. By that i mean other times the map and data loads, > > > > > > > but > > > > > > > the browser continues to process indefinitely (making the map > > > > > > > unusable). > > > > > > > 3) In IE8 clicking on lines produces no infowindow pop-ups. > > > > > > > > --I've tried to read as much as possible before posting. I don't > > > > > > > think > > > > > > > it has to do with IE loading images for markers, because the > > > > > > > custom > > > > > > > marker images are the first thing to load, and if i strip the xml > > > > > > > file > > > > > > > down to just points (as opposed to points and lines), it's a > > > > > > > pretty > > > > > > > quick load in FF or IE. > > > > > > > > --I don't think it has to do with each line storing mouseover and > > > > > > > mouseout functions because i tried commenting those out, and the > > > > > > > IE > > > > > > > load time is still around 50-60 seconds. > > > > > > > > So, it must have something to do with the lines i'm loading...? > > > > > > > Too > > > > > > > much for IE? > > > > > > > 1. try encoding the polylines > > > > > > Compare these 2 > > > > > > polylines:http://www.geocodezip.com/GenericMapBrowser.asp?filename=I5Polyline.x...... > > > > > > > 2. you could speed up the loading of the xml file by making it > > > > > > smaller > > > > > > (you don't need 11 decimals of accuracy for the latitude and > > > > > > longitude). > > > > > > > -- Larry- Hide quoted text - > > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
