Hi,

Is there a way to change the spacing between the points in the log that shows your track? The tracks are sometimes very 50 pence piece-like instead of smooth curves, as shown in the image below. I'm using the SD MD unit and I can't see anything obvious in the menus. I'd like to be able to assess the consistency of my flying holds and approaches but there are too few points to tell very much.

Thanks

Ray

Hi Tim. Sorry about the delay (I've been away) but thanks for taking a look at this.

The SD-generated log appears to contain points every few seconds but the spacing between the points that are displayed in SD Plan on the PC is much greater - maybe every tenth point or something like that. However, if you export from SD to .gpx and display it in Google Earth, all of the points are shown, as this screen shot from Google Earth illustrates (using the same log file that I used for the SD screen shot in my OP).



The corresponding log file is here (in .gpx format) and here (in native SD format)

Ray

Forgot to mention that I am using the latest version of SD.
Ray

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.

-- Chris.