It's happened a few times now that an activity records elevation that doesn't exist, out by thousands of meters. Can't seem to find a related thread? Any idea how I can fix it?
The elevation. For the run should have been ~208m, instead it's clocking 35 165m
