No, I'm not talking about "resampling"; I'm not even sure what that does to the accuracy of a track. I'm concerned that will make the mileage of a track less accurate.
There used to be the ability to increase the number of waypoints in a track if there were too many, from 1,000 to 3,000 to 5,000. That ability seems to be gone. Now, when there are over 1,000 waypoints in a track, it warns you editing will be slowed, with no option to increase the number, even when the number of waypoints is below 3,000 for instance.
Meghan on 11 Nov, 2021 09:13 PM
I think you may be confusing two different things. The warning that you reference in the browser has to do with browser performance- if there are too many points in the line, it can really slow down the browser, making it hard to edit. If you want to change the number of points (vertices) in a line, then the way to do that is through resampling. Resampling will evenly distribute the new number of points along the line, either subtracting or adding points overall. You can resample based on distance or the number of waypoints you want overall. Whether or not resampling makes the track more (or less) accurate really depends on a number of factors, including how accurate the original GPS track was in the first place. For example, if you want to smooth out a wild GPX track with lots of GPS noise, resampling at the right intervals could help make the track more accurate.