Recorders and exporters get things wrong: an action camera writes ten points per second all stamped with the same whole second, a logger jumps back in time, an export leaves out elevations, a converter writes the bounds with the wrong sign, and under trees the GPS drops a point kilometres away. Any of that makes another program refuse the file or show nonsense. Healing goes through the whole track once and fixes what it finds, then tells you what it changed.
FAQ
What happens to my file?
Your file is sent to the Reisezoom server for processing, handled there and deleted immediately — nothing is stored. So that the web tool and the desktop app arrive at the same number, both use the same component — and that one runs on the server.
My camera's GPX is refused by the video software but a navigator's GPX works. Why?
Cameras often write ten points per second with the same whole-second timestamp and bounds without a sign. Zero time differences and points on the wrong side of the world make a strict importer refuse the file. Heal spreads the points evenly over the second and rewrites the bounds; the result looks like a normal recording.
What exactly does it change?
Points without coordinates or at 0/0 are removed, exact duplicates removed, seconds with several points spread evenly, backwards time jumps smoothed, missing times interpolated by distance, GPS outliers above the top speed removed, missing elevations interpolated, bounds recomputed. Everything else stays as it was.
Can it delete good points?
Only outliers above the top speed you set, and exact duplicates. Start and finish always stay. Check the distance afterwards: it should only drop by the nonsense.
Which formats can I load?
GPX, FIT, TCX, KML, KMZ, GeoJSON and NMEA. Download as GPX, KML, KMZ, TCX, GeoJSON or CSV.