When a GPS track jumps, first check whether recorded points are unusually far apart or whether the trace only looks different from the mapped trail. The official sources checked on October 28, 2026, identify general factors that reduce accuracy. They do not quantify track jumps in valley bottoms or forests. This article explains what each comparison can help you check.
Two ways a track can appear to jump
An apparent jump can arise in at least two ways. One point in the time-ordered sequence may be far from the points immediately before and after it. Or the points may form a continuous track that runs away from the line for the trail. The latter can look the same if the position of the trail or other features on the base map is wrong.
This is our editorial team's reasoning. An error in the map changes where the drawn trail appears. It leaves the spacing and order of the recorded points unchanged. A sudden long gap in the sequence followed by a return to the earlier pattern is difficult to explain by a map error alone. This is a clue, and the actual cause remains to be checked. Both problems can occur at once.
What the sources say about valleys and woods
GPS.gov lists signals blocked by buildings, bridges or trees, reflections off structures (multipath), and radio interference among the causes of poorer accuracy. Woods fit the tree blockage example directly. The guide does not discuss valley bottoms. Our editorial inference is that valley walls may narrow the view of the sky and that reflected signals from the slopes might reach the receiver too.
The GPS.gov guide cites a typical accuracy radius of about 4.9 m for smartphones under an open sky. It says accuracy worsens near obstacles like buildings. This is an example for open spaces. It gives no estimate for forested terrain or valley bottoms. A separate table summarises 2022 GPS positioning service evaluations, including 95th-percentile horizontal error standards of at most 8 m globally on average and 15 m at the worst site. The archive says it has not been updated since February 2025. These are separate from signal user range error (URE) and do not measure your device or mountain conditions. They cannot be used to judge the size of a jump.
Distinguish the API's accuracy field from the app's circle
Android Developers explains that Location.getAccuracy() reports estimated horizontal accuracy as a radius in metres. The confidence level is the 68th percentile. A circle drawn with that radius around the reported position has an estimated 68% chance of containing the true position. By definition, the true position can still be outside that circle. The radius is an estimate. It applies only horizontally, gives no altitude accuracy, and is valid only if hasAccuracy() is true.
The definition applies to the value returned by Android's API. The sources consulted do not say whether a map app draws its circle with exactly this radius. Apps can also differ in whether they store accuracy in the track file. Check your app's explanation before treating the circle as a 68% range. These sources do not describe the definitions used by other operating systems or dedicated GPS devices.
Checks to make after the hike
Our editorial team suggests doing these checks at home. Each helps you test a possibility while leaving the cause open. Skip a step if your app lacks the feature.
Step 1. Look at the sequence of points. If your app can display points individually, inspect the spacing and timestamps around the jump. If one point is far away and the others follow the previous pattern, a coordinate outlier is more likely.
Step 2. Change the base map. Overlay the same track on another map. If the offset from the drawn path changes, the map contributes to the way it looks. If a point remains separated from the others, investigate the recorded coordinates.
Step 3. Look for an accuracy field. Check the exported file or the track view. If accuracy appears there, look for a large change around the jump. A point can be an outlier even when the estimated radius stays small. If the field is missing, leave it out of your assessment.
Step 4. Check the terrain. Use the topographic map to see if the affected section was in a narrow valley or a forest. A match with the factors in the sources gives you a possibility to investigate without confirming the cause.
Step 5. Record what remains uncertain. For example, “The track looks unusual here. Use the distance and elevation as rough estimates.” Record the section and how you are treating it. A separate article discusses how to report GPS errors in trip logs.
Decisions on the trail are different. If you notice a jump, avoid looking at or using the screen while walking. Stop where you have secure footing and will not block the trail, then compare the map with signs and the terrain. If you cannot stop in a suitable place, leave the check until you can. If you are unsure of your position, leave room to skip the section or turn back from a safe point before you reach a hazard. Your confidence in the track comes second.
Check points, accuracy and map display separately
Separating the recorded points, the device's accuracy estimate and the way the track is drawn helps explain what remains uncertain. The sources show that obstructions such as trees and multipath can reduce accuracy. They also define Android's getAccuracy() as a horizontal estimate at 68%. Investigate valley behaviour, the app's circle and the cause of a jump with the device and app you actually use. After your next hike, try the first two checks on the most recent track.