Thanks, geocodezip and Martin. I think Martin's suggestion (which I should have thought of, of course) will be adequate for the time being. The polyline encoding looks very slick, but a bit complex and I don't have the resources to test with a panoply of browsers, which looks to be desirable.
My GPS tracks are airplane flights at a 1/second sample rate, basically long straight lines punctuated with brief periods of circling for photography. So I will probably also write a simple test to skip points where nothing is really changing. That should help reduce verbosity a lot too.. -- 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.
