I am not sure if empty segments are expected to ever happen, but I believe the gpx standard supports them. I am currently woirking on generating gpx files for Gadgetbridge, which generated an empty trkseg due to a bug. I have since fixed it, but felt like I should open this issue, since the fix is probably trivial. Feel free to close this if you consider the gpx file invalid.
If a gpx file contains an empty segment (
<trkseg/>
), the other segments will become overlapped:Attached a small sample that causes the issue: empty-seg.gpx.txt
I am not sure if empty segments are expected to ever happen, but I believe the gpx standard supports them. I am currently woirking on generating gpx files for Gadgetbridge, which generated an empty trkseg due to a bug. I have since fixed it, but felt like I should open this issue, since the fix is probably trivial. Feel free to close this if you consider the gpx file invalid.