Just to make you aware, GPX files are not legal for posting to the GPSTC. It doesn't matter what device created them.
Typically GPX files don't carry the accuracy data we need for file checking.

The reason to have a gpx file is for gps-overlay for video editing in Virb-Edit (free to use). I love to see the speed an track overlay data in action video. Although the GoPro cameras support it inside the mp4, the workflow is not very nice. This is why I like to use the gpx files next to the normal accurate formats for gps speed posting.

The problem with Virb-Edit (or Dashware or Race Render or several others) is that, if you use a gpx file separate from the video file, you have to synch the action manually. I look for a jibe on the video then look at where my direction and speed changed in the gpx, and synch them by hand in the program. The software helps you in this but it is is a hassle.

The nice thing about gps data embedded inside the video file is that it is pre-synched. Dashware, Race Render, and some others recognize this in software and synch them automatically. You can also use Dashware and Race Render to synch by hand if you have a video file without embedded gps and a gpx file with it.

GoPro cameras beginning with the 5 Black, and the Contour+ and some other Contours, have gps data embedded inside their video files.

Select to expand quote

decrepit said..
Just to make you aware, GPX files are not legal for posting to the GPSTC. It doesn't matter what device created them.
Typically GPX files don't carry the accuracy data we need for file checking.

Which file should we be using?

.sbp (locosys format), or .ubx.
.gpy is not yet implemented, but will offer the smallest losless filesize.

if using the motion, .OAO. if using a GT31 .SBN or .SBP
once the .GPY is fully implemented, that should be approved shortly after.