I think I may be less knowledgeable than other people playing with encoded polylines because I feel like you've answered my question but I didn't entirely understand your answer!! I've been more detailed below...
On Aug 28, 2:43 am, "maps.huge.info [Maps API Guru]" <[EMAIL PROTECTED]> wrote: > Looks like a great trip! > > I see you're using the encoding levels parameters and it looks like > you've taken the trouble to use a simplification routine when building > it, however, it appears as if you're not being aggressive enough in > simplifying your points with the encoding. There's way too much detail > visible with the line when the map starts out, that's what's causing > the problem with the line. Actually, I just used a script that I found on this page http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/ . I think I pretty much left it at the defaults that were set when I found the script. How exactly would I go about being more aggressive? I've tried playing with the various parameters but apparently to no effect... ? > Also, that page has a lot of JSON (or > appears to) that makes up your dialog. That may also be impacting the > performance of the page. Yes my site is a mishmash of my own old PHP code adapted to work with a sort of poor-man's pseudo AJAX that is a result of my attempts to learn javascript while reading web tutorials about how to go about doing AJAXy things. Someday I will re-do it with my now somewhat improved knowledge, but that day will likely not be until I am done driving across the world (this trip that is :) ). > > You have a couple of options: > > 1. Simplify the line more when encoding it, a lot more, on the order > of 100 miles or so. That won't really change the appearance of the > line when zoomed out nor cut down on the detail as the zoom moves in > but it will simplify the work the browser has to do before the display > appears. Can you offer any more guidance here? I can't figure out how to simplify it when encoding...?? As I didn't write my own encoding script, I'm not entirely sure how to go about modifying it and such? > > 2. Abandon the polyline method altogether and go with a tile overlay. > A lot of work for this type of page but it will eliminate any > performance bottlenecks from too many points. not a bad idea for this purpose... but of course the amount of learning does sound high for the time being. > > 3. Perhaps change the JSON approach for loading your dialog and use a > straight dump when the page is created. That will eliminate some large > Javascript objects. Not sure how feasible that is or if you want to > get into that much programming. I'm not entirely sure what you mean by this? I'm not actually using JSON (as far as I know?). All the text and such comes from a PHP script that spits it out when asked to from my MySQL database... > > 4. Break up the polyline into bits. This can help during loading but > is more of a bandaid approach. Breaking the line into chunks of 100 or > 200 points will help slower computers digest the data though. Would it not mean encoding 100 or 200 lines causing 100 or 200 the amount of encoding time AND displaying 100 or 200 times the amount of points? > > Good luck on the trip and don't get kidnapped! Thanks! If we are, you'll at least know where! Josh --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
