A map line does not guarantee a complete recording
Float GPX Editor calculates statistics from the current track’s stored points. A file can have coordinates without usable elevation or time. When a number is unavailable, inspect Original recording in Data before assuming that the map failed.
The rules below describe this app’s calculations. Another fitness or mapping app can show different results because it applies different smoothing, terrain correction, pause detection or segment handling.
Distance is measured within each segment
Distance uses a spherical Haversine calculation between neighboring coordinates in each segment, then adds those segment distances. It does not measure along the road network, include the height component or bridge segment gaps.
For example, two 2 km segments with a gap between them contribute about 4 km, regardless of how far apart their endpoints are. Moving a point changes these distances. Deleting one point can shorten a corner; deleting a middle range leaves separate segments.
Elevation range and cumulative ascent are different
The elevation range shows the lowest and highest recorded values. Cumulative ascent adds positive changes between adjacent known elevations in the same segment; descent adds negative changes in magnitude. Repeated ups and downs can therefore produce more ascent than the highest-minus-lowest difference.
For a synthetic sequence of 100 → 120 → 110 → 130 meters, the range is 100–130 m, ascent is 40 m and descent is 10 m. The app does not smooth the readings, so small measurement fluctuations can affect totals. Missing values are not interpolated and make the displayed ascent or descent partial.
Read the elevation curve as recorded data
Click the curve to select a corresponding real track point. Segment boundaries and missing elevations stay visible as breaks; a blank curve means no usable elevation was recorded. On long tracks, the drawing uses a reduced set of samples for display, while editing and export keep all actual points.
Moving a point sideways does not fetch a new terrain height. Inserting a point creates no elevation reading. A curve is therefore a view of the retained recording, not a live profile generated from the basemap.
Duration includes stops inside segments, not gaps between them
Every point must have a valid time, and timestamps must strictly increase within each segment. If they do, duration is the sum of each segment’s end time minus its start time. A one-point segment contributes zero duration.
For segments covering 09:00–09:30 and 10:00–10:20, duration is 50 minutes, not 80. Stops inside either segment remain included. Average speed is total segment distance divided by this duration when it is positive; it is not moving speed.
Why editing can make speed disappear
An inserted point has no timestamp, so a previously timed track may no longer have a computable duration. Reversing a track preserves original times and can make them decrease. Moving points keeps the original times, so any remaining speed calculation describes edited geometry against those original times.
The editor does not generate replacement timestamps or correct a fitness activity. Keep the original recording if you need the measured activity data, and use the exported geometry for the purpose you actually intend.