- The route is simplified for the lower zoom levels. This has to be done because otherwise it would be even slower ...
- Regarding very long tracks: we use specially encoded Google API tracks to improve performance (which is already much better than importing single track points, but cannot be improved further since we have to use that API functions).
- You may experience some improvement when using a faster client PC or internet connection.
- Maybe the map is slower than on other sites because it's bigger (needs more time to load).
I have recently uploaded some motorcycle trips. The routes are long 4-6 hours and 150 to 300 km. The performance of the Google Map API on the gps-sport site is very poor.
- The route does not follow the actual track very well unless zoomed in to a very high level.
- Zooming/panning/moving/swtiching from Map view to Terrain view is all VERY sloooooow.
- After a while I consistently lose satelitte view when zooming in/out. Google Maps says it does not have that level of detail when I know it does... even syaing the same when I zoom out.
How much is this a product of a large data file and/or poor performance from the Gmap API insert on gps-sport and/or me having a bad connection (which I don't suffer from for other sites/applications)?
I have noticed that even with relatively small bicycle tracks the performance of the gps-sport gmap API is slow compared to other sites that I can load the gpx on to.