v1.1.6

This release fixes a bug in sorting points after timestamp during import of tracks from CSV or GPX files. The fix should in practice improve the matching accuracy of tracks that contain points with different geocoordinates with the same timestamp.

• When two points have the same timestamp, which can unfortunately occur in practice, for example when two GPS points are measured within the same second but the timestamp resolution is only seconds, then sorting these points by timestamp can lead to a change of order. Usually, points with the same timestamp are already in the right order in the import file, because they were written in that order, so the order should not be changed even when the timestamp is the same. Not all sorting algorithms fulfil this criteria, but there is std::stable_sort that we already used, which guarantees the order of elements with the same value. The regular std::sort does not keep the order of elements with the same value. However, we mistakenly did not only order by timestamp previously but also by geoposition in case the timestamp is the same. This is not really useful and lead to std::stable_sort not being able to keep the order, because our sorting criteria was wrong. This is now fixed.

Full Changelog: v1.1.5...v1.1.6