Map unavailable: the GPX file could not be loaded.
These figures are derived automatically from your GPX track file.
Time and distance accumulated while moving outside the activation zone at a speed above the stationary threshold (default 0.3 km/h). Periods where you were stopped (waiting at a trailhead, taking a break) are excluded and counted separately as Rest Breaks.
Stationary periods outside the activation zone lasting longer than the rest threshold (default 3 minutes). Anything shorter is ignored as normal GPS noise or a momentary pause. Rest break time is shown inside the Hiking Time box for reference but is not added to hiking time.
All time spent inside the activation zone, regardless of whether you were moving or stationary. This captures the full period from when you first entered the zone to when you left, including any walking around the summit, setting up gear, and operating.
The activation zone boundary is determined by one of two methods (see below).
The elapsed time from the first to the last GPS trackpoint in the file. This equals Hiking Time + Activation Time + Rest Breaks + any unclassified transition time at the boundaries.
Gain and loss are the cumulative altitude climbed and descended across all trackpoints. Each uphill step between consecutive points adds to gain; each downhill step adds to loss. Out-and-back routes will show roughly equal gain and loss.
Peak is the highest elevation recorded in the GPS track. It is also used as the starting reference for the activation zone when a terrain-based zone is used.
Average speed calculated as Hiking Distance ÷ Hiking Time. Only moving segments outside the activation zone are included, so rest stops and summit time do not drag the average down.
The full length of the entire GPS track, from the first to the last trackpoint, including time spent in the activation zone.
Terrain-based zone (currently active): The boundary extends to where the terrain drops 25 metres below the summit, following the official SOTA rule. It comes from SOTLAS, which publishes boundaries at roughly 1 meter detail. This is the most accurate method available. It comes from activation.zone, which uses lower resolution elevation data. SOTLAS is tried first and had no boundary for this summit.
Radius method (currently active): The activation zone is approximated as a circle of metres around the highest GPS point. This is less precise than the API method because it ignores terrain shape, but works without an internet lookup or summit reference in the log.
For better accuracy, turn on terrain-based activation zones in Settings → Activator Toolkit and make sure your log includes the summit reference.
My Summit: ' . esc_html($display_summit) . '
'; } ?>| Date / Time | Callsign | Frequency | Mode | Their Summit | Comments | ' . esc_html($formatted_date) . ' ' . esc_html($tc['time']) . ' | ';
echo '' . esc_html($tc['callsign']) . '' . ($s2s ? 'S2S' : '') . ' | '; echo '' . esc_html($tc['frequency']) . ' | '; echo '' . esc_html($tc['mode']) . ' | '; echo '' . esc_html($tc['their_summit']) . ' | '; echo '' . esc_html($tc['comments']) . ' | '; echo ''; } ?>
|---|