25.03.2009 14:51:46 UTCgeändert am 25.03.2009 14:52:39 UTC
I think currently Run.GPS saves every Koordinates received from the NMEA Raw data without any filtering.
Would be nice if Run.GPS could optimize while exporting to GPX/KML but it doesn't (Many other programs do this). RunGPS must even have an optimizer because if you load a GPX-Track it gets optimized in Run.GPS. But unfortunately there is no option to export optimized GPX/KML files.
Currently there is only the way to use GPSBabel or something to optimize the tracks.
I have been thinking the same. Would be great to get control of the position savings interval. I don't know how it works right now (does anybody?) but it would be very nice to have a few options to choose from, such as 1s, 2s, 5s, 10s and some kind of 'smart value' with a ~1/speed dependency.
17.03.2009 05:03:26 UTCgeändert am 17.03.2009 05:09:09 UTC
recorded tracks generate large gpx files
I'm impressed about the possibilities of the software. And I hope it's going to be improved each update.
I've noticed the tracks are simplified when uploaded to the community portal. Thousands of recorded trackpoints turn out to be only hundreds after this process.
Maybe it should be useful to have the ability to (automatic or manually) control the position update rate when recording slow speed tracks such as hiking, trekking, walking, or mountain bike. In this case the resulting recorded track would be a smaller file.