The big issue with encoding is whether you encode the points correctly, or just encode them to reduce bandwidth. A correctly encoded polyline would show less detail of the line when zooming out and more detail when zooming in. This is controlled by the encoding level string. Unless this is done, you're wasting the processing power of the client and probably would be better off not to encode at all.
As Mike pointed out, that many points and lines will most likely be a painful user experience. There are other ways to display such things, such as using a tile or image overlay which would be fast and efficient. -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 -~----------~----~----~----~------~----~------~--~---
