Closed hemmingway-1 closed 11 months ago
GPXSee is designed to work with real data, not the nonsense you have in your data file. Because of the nonsense timestamps in your data, the pause detection algorithm evaluates this part of track as a pause and "filters" the path. You may switch the pause detection to manual and set the minimal speed to 0.1km/h to get the "desired" route, but in general GPXSee is not the right tool for working with artificial, broken-by-design (you have even time skews in your data where the time goes backward...) data. You better use some tool like RouteConverter that does not care about the "physics" of the track and does not use any statistics methods to filter data or handle workout pauses like GPXSee.
Your note works for me. So I can compare two tracks with different colors. Thank you for your work, Bernhard
This part is shown correctly by RouteConverter. The part is added manually in RouteConverter. Before adding it was a single line. Flamingoroute.csv The csv file is a gpx file.