There are essentially two way of creating a route overlay on a Google map. One is to convert each track point to a Google map point (using client JavaScript) and the other is to pass the entire track to the GGeoXml constructor. Here is the point-by-point example (the gpx file format was converted to Google HTML map page), and this is the whole route example (I used GPSBabel to download the track in KML format). Initially I thought that the point-by-point was slower, but after a number of runs I’m not sure. The performance of Google maps (Javascript) on OS X Firefox is unpredictable. In the case of the whole route, I pass the KML version of the route to the GGeoXml function. The information on the points of interest, e.g., latitude, longitudes, … are there but are lost when Google renders the route.
May 28, 2007 at 4:13 pm |
Personally I think that the point-by-point example runs faster here (MacOS X, Camino) and yields “better” results. For the whole-route example it almost looks like somebody is doing a spline-interpolation between way-points. While it is not a problem with the sampling rate you used, it may look weird if the sampling frequency is decreased (means, less samples per time).
May 31, 2008 at 8:46 pm |
hi,
Interesting. I was thinking the same that a single line will be more efficient than having multiple points. Nevertheless, there is one problem when using multiple markers especially when you have more than 200 markers. Google only shows 200 markers at most in one go. You will need to click on next button to see other points. Check my post to see exactly what I have been trying to do
http://ragrawal.wordpress.com/2008/05/31/garmin-forerunner-301-to-google-maps/