First diagnose the gap
A blank span may come from the file, the import or the map display.
A GPX line is built from ordered route or track points. When part of it appears missing, the cause can be an explicit break between track segments, separate track elements, absent points during a recording, rejected non-conforming data or a viewer that does not support the file's structure.
The map underneath can disappear independently too. Missing offline map detail does not mean the GPX geometry is absent if the route line is still visible. Conversely, a complete basemap does not prove that the route sequence is continuous.
Start by deciding whether the route line itself stops, a straight bridge appears, or only the background mapping is blank. Those are different problems.
Structural breaks
Track segments preserve places where continuity was not recorded.
The GPX 1.1 schema specifically recommends a new track segment for each continuous span when reception was lost or the receiver was turned off. A correct segment-aware rendering can leave a blank between those spans. Another renderer may join the endpoints with a straight line, which hides the structural break rather than repairing it.
- New
<trkseg>The points remain in one named track, but the file does not state a direct connection across the boundary. - New
<trk>The line belongs to a separate track object. Any relationship to the previous track must be established separately. - Missing samplesA recorder cannot describe a path it did not observe. Far-apart points may produce a long chord unless an exporter preserves a break.
- Empty segmentThe schema permits a segment with no track points. It contributes no visible geometry.
After export
A receiving tool can lose or misread part of otherwise present data.
A file may contain both routes and tracks while a viewer reads only one type. A collection may include several lines but show only the first. A parser can reject points with invalid latitude, longitude, element order or XML syntax. A conversion can also filter points, split a track or write a partial output after an interrupted process.
Very sparse geometry usually looks like long straight sections rather than a blank gap. Aggressive simplification can remove bends, but a normal line simplifier still leaves connections between retained points. Distinguishing a gap from a shortcut matters before choosing a repair.
Compare the same source in another standards-aware viewer and inspect the XML. If the points exist in the source but not the imported copy, the issue occurred during the handoff. If neither file contains them, no viewer can reconstruct the travelled line from GPX evidence alone.
A deliberate repair
Do not treat the shortest connection as the missing route.
- Preserve
Keep the original file unchanged.
The gap is evidence that continuity is unknown or was represented separately.
- Locate
Inspect the points and elements on both sides.
Check segment boundaries, track names, timestamps and the distance between endpoints.
- Verify
Use a trusted plan or current map evidence.
A previous planned route can support a repair. A straight line across open space cannot.
- Edit
Create a separate repaired copy.
Make the added geometry clear and review its access assumptions, junctions and direction.
- Test
Import the result into the destination app.
If beacen still omits geometry that is present in a valid source, use Support with a privacy-safe example.
Sources & scope
What this answer is based on.
The schema defines track segments, multiple tracks and required point coordinates. Viewer support, parser errors and a particular file's missing data require direct inspection.