on 10-07-2018 04:40 AM
I am trying to export a GPX track from an MP4 video filmed on GoPro 6.
Somehow I'm getting invalid coordinates. I see several problems which appear on the exported GPX track - but which I don't see on the GPS gauge in Quik.
First problem is that I'm getting completely off-the track coordinates. Here's a example:
The video is filmed in Germany (around 8.663, 50.232). A few first points on the exported GPX track lie north of Canada (-128.4998971, 80.8641778). Also the elevation for these points is exported as 20841.167 (in reality should be around 202).
Quik seem to show this track correctly:
The complete video is ca. 3.4GB so I can't reasonably share it. I also don't know how can I cut it while keeping all the streams including GoPro MET.
The .bin file I've exported from the video:
This is how I've exported it:
ffmpeg -y -i GX030039.MP4 -codec copy -map 0:3:handler_name:" GoPro MET" -f rawvideo GX030039.bin
The exported GPX track:
gopro2gpx -i GX030039.bin -o GX030039.gpx
I've tried gopro2gpx from:
With the same result.
Invalid points look like:
<trkpt lat="80.8641778" lon="-128.4998971"> <ele>20841.167</ele> <time>2018-09-29T10:20:53Z</time> </trkpt> <trkpt lat="80.8641778" lon="-128.4998971"> <ele>20841.167</ele> <time>2018-09-29T10:20:54Z</time> </trkpt>
First valid point:
<trkpt lat="50.2319754" lon="8.6630605"> <ele>202.121</ele> <time>2018-09-29T10:23:51Z</time> </trkpt>
Did anyone experienced similar problems?
Are there any official tools for GPS data export from GoPro?
on 10-07-2018 05:48 AM
A further problem I'm facing are coordinate which are completely off track.
This is the GPX track I'm getting:
The tracks looks "exploded" in a few places:
This part here is completely off the track. Quite sure I did not drive there:
Check the "vertical" part here in the middle. Looks quite consistent. Except there's no road there and I did not drive there. Also consider the part in the upper right corner.
I also get severely inprecise coordinates along the track:
Quik shows a somewhat better looking track:
However Quik does not show almost the half of the drack I actually drove.
I don't think these "explosions" of the track can't be explained by the imprecision of GPS. Ok, I'm fine with a few meters, but I see jumps of several hundreds meters if not kilometers here. Also, this is not visible in Quik.
on 10-07-2018 10:03 AM
Hi. Maybe you would like to try the export on trassy.pl? This video shows how it works:
It does not show how to export: there are icon in the top left, one of them allows to export to GPX and CSV.
Please contact me on email email@example.com if you would like to use it - I will grant you n access. Presently the access is limited to invited guests.
on 10-07-2018 12:10 PM
Install and use Dashware. It's free and Dashware and GoPro are cooperating with each other. When you import the file into Dashware, it makes a csv file. Open it with Excel to see everything.
As an alternative or additional, get RaceRender. You can only export 3 minutes with the free version, but you see the entire route. Pay some money and you can export to gpx. See this thread on the RaceRender forum for a lot of explanation and my on-going problems.
I use GPSU to edit/modify data before inputting into a mapping program.
GoPro is notoriously inaccurate in getting gps info. Before starting, take a short video clip to make sure that the GPS is on and had located a satellite.
on 10-07-2018 12:33 PM
Thank you for the suggestions.
Both RaceRender and Dashware give me more or less the same invalid points I get from gopro2gpx.
I just wonder why the track looks fine in Quik.
on 10-08-2018 12:04 AM