Using a Garmin Forerunner 305, a recent trip it concatenated the track data with the previous recorded trip, which happened 3 days earlier. Is there an editing tool that I can use to split the two ?
CalTopo is one way. Go to the location of the track, import the gpx track, select it at the location you want to split it, select Split, export a gpx file. Choose one of the tracks to export, and export. Export again, choosing the other track.
GPX Editor works great for this kind of task. It's available at SourceForge: https://sourceforge.net/projects/gpxeditor/
Fred Mailey of Notheast Ohio O club (NEOOC) recommended the use of this application: JGPSTrackEdit
It does require the java runtime system be present on your system.
can do the trick as well.
Mr Wonderful, so nice to see you jump into the GPS-data fray and fire pit.
Soooooo, i was indeed just using QuickRoute at the start of this, but couldn't see a way to selectively select pieces of the data and edit/split/whatever. What are the actions to be taken in that app ?
I just do it in Notepad. See my post in this thread
I also use Topofusion, which lets you do it on a map. I've got the $60 licensed version, though. Pretty sure the free version works. It's good for editing tracks to correct things, such as to create a gpx for a ride.
I'll confirm at home, but from memory, it's something like: use the trim track functions and then there's an export .gpx option.
Use the scissor icon to crop route. Select before/after etc as appropriate.
File | Export | gpx
One other point on this thread: I helped Alexis (@sherpes) with his files directly and produced GPX files that he successfully uploaded. The original GPX files were encoded in UTF-8 and needed to be changed to ANSI. I used Windows Notepad's File->Save As and selected ANSI as the Encoding, before Saving. Then I edited the GPX files with JGPSTrackEdit as mentioned above to separate the track segments. Some GPX (XML) file parsers cannot handle the hidden bytes at the beginning of the UTF-8 encoded files.
I'm one of the original authors of the GPX format, and I maintain the spec and documentation. GPX is based on XML, so tools that support GPX need to be able to handle UTF-8 and ANSI-encoded files, including proper handling of the hidden byte code markers at the start of the file.
Here are a few dozen more solutions that you can use to edit or view your GPX data:http://www.topografix.com/gpx_resources.asp