Author: shaunmcdonald131[at]gmail.com
[Added to the original trac issue at 3.01pm, Sunday, 8th June 2008]

This is down to the way that the points are downloaded, and the fact that there is no way to be able to tell from the API where one track stops and the next starts.

Is there an option in your app to not draw lines between the points?

Author: dantje
[Added to the original trac issue at 8.42pm, Sunday, 8th June 2008]

Would it be sensible to assume that those points that are located on the
bounding box are endpoints of their respective tracks?

Author: shaunmcdonald131[at]gmail.com
[Added to the original trac issue at 10.04pm, Monday, 9th June 2008]

That will reduce the problem, but won't work for tracks that stop or start in the middle of the bbox.

Author: dantje
[Added to the original trac issue at 11.41am, Saturday, 26th July 2008]

This preference could be the maximum length that will be drawn: 0m for no connections at all, 100m for connections between node that are closer than 100m.

Author: koying
[Added to the original trac issue at 9.24am, Sunday, 10th August 2008]

I implemented the on/off switch of displaying track segments for now. If someone feels dantje solution should be implemented, please reopen.

Author: dantje
[Added to the original trac issue at 11.32pm, Friday, 3rd October 2008]

I commited a patch (r11030) that uses a fixed threshold of 100m.