>
> For me, viking is still slow
> if i view large gpx track files (1000 up to 20.000 track points)
> I do not feel any improvment with the skip-same patch
Are these points all in a single track or multiple tracks?
Do these trackpoints have extended info VDOP, HDOP, PDOP etc....
What is the spec of your machine again, especially CPU & RAM?
Do you have an NFS home partition, or some other less common setup?
Otherwise, I still can't think of any particular reason to explain this
behaviour.
> I am still using this script to simplify the track to %25
> and I apply it so many times until viking can handle the track fast:
Note that you can apply a simplify operation within Viking itself (albeit using
gpsbabel in the background)
TRW Layer -> Filter -> Simplify All Tracks...
Then you can delete the original track.
Of course if Viking feels too slow to begin with it's not so useful for you!
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/
