Hi Greg, > Is anyone else seeing this?
I am suffering the same problem. I use 1s logging interval because I also use my gps tracks for OSM and so there are more detailed. E.g. I am on a bike tour, usually about 4 hours I also get around 14400 track points. In my Pentium 1.86GHz 2GB RAM this track is unusable in viking. I can't zoom or drag around because viking is busy all the time. As a workaround I first merge and simplify the track with gpsbable. The simplify mechanism in gpsbabel keeps the shape of the track very well and only removes track points that are redundant. gpsbabel -t -i gpx -f input.gpx -x track,pack,split,title="%D" -o gpx -F merged.gpx gpsbabel -t -i gpx -f merged.gpx -x simplify,count=1000 -o gpx -F simplified.gpx ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
