Group: Forum Members
If storage or memory space is an issue, logging a position at a fixed time interval isn't the most efficient procedure. It would be best to take a position reading every second and then make a determination whether to store the point or discard it based on the momentary turn rate.
So if I were flying in a straight line, SD would acquire a fix every second but, based on my straight course, decide not to store each successive point because it doesn't add any new information (a straight line only requires two points to define it unambiguously). When I am in a tight turn, SD would store every acquired point because each deviates significantly from the straight line course. You could take the current rate of turn and, based on that, decide on the momentary frequency at which you log points. Since that frequency is bound to change over a flight (it would be storing a lot of points during portions that you turn and only few points during straight and level flight) you would also have to store the acquisition time together with each point.