Changes between Version 1 and Version 2 of Ticket #21257


Ignore:
Timestamp:
2021-08-27T22:22:17+02:00 (4 years ago)
Author:
richlv
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21257 – Description

    v1 v2  
    55
    66Now many data consumers break - including OSM traces.
    7 Example: josm-gpx.png.
     7Example:
     8[[Image(josm-gpx.png)]]
    89The straight line does not exist, but is drawn because the GPX is consumed sequentially.
    910In some cases it is much worse, with such straight lines cross-crossing the GPX display.
     
    1415gpsbabel -t -i gpx -f 2021-08-14\ 09.39.58\ Day.gpx -x track,merge -o gpx -F 021-08-14\ 09.39.58\ Day_2.gpx
    1516
    16 This sorts the sequences (trkseg), and the trace looks good when uploaded to OSM - josm-gpx-gpsbabel.png .
     17This sorts the sequences (trkseg), and the trace looks good when uploaded to OSM:
     18[[Image(josm-gpx-gpsbabel.png)]]
    1719This is also how the trace would look if uploaded before editing with JOSM.
    1820