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. 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.
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. 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. 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. 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. Good luck on the trip and don't get kidnapped! -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 -~----------~----~----~----~------~----~------~--~---
