Ask a Question
GoPro Support Hub Ask a question. Share an answer. Find a solution. Stay stoked.
Announcements
Is your GoPro gear up to date? Check to see If it is on our Update page.
Reply
This is an open group. Sign in and click the "Join Group" button to become a group member and start posting.
Hiker
Posts: 48
Re: Extracting the metadata in a useful format

You may also try trassy.pl solution. This video shows how to display GP5/6/7 MP4:

https://youtu.be/hHXP77R2LEw

Then you can export the GPS in GPX or CSV format (use the small button in upper left corner).

cheers

Watch your locally stored GoPro movies together with maps trails and altitude, speed, GPS signal quality charts:- go to https://trassy.pl- login with Faceboo...
Hiker
Posts: 28
Re: Extracting the metadata in a useful format

@kajuna - I hope I understand you manage GPMD2CSV..

 

Any chance you can label the track in the .gpx with the filename so that they are easier to work with when imported into google earth or any other GPX editor?

 

All it needs is a single element:

 

<trk>
<name>GH012091</name>
<trkseg>

...

 

Thanks!

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

@plawa Good idea. Should be good now.

Hiker
Posts: 28
Re: Extracting the metadata in a useful format
[ Edited ]

Awesome, this helps a lot when I'm trying to find the file with a specific section of the trail... or checking what part of the trail is the video from.

 

Thanks for the quick response.

 

Sightseer
Posts: 1
Re: Extracting the metadata in a useful format

So i successfully generated the data as .csv, .json, .kml and .gpx files. But how can i use it in After Effects to create my own charts? I'm really an advanced AE user, but not good at coding. What is needed to convert the data into After Effects keyframes?

 

1.JPG

Simply loading the .json file into AE only gives me hundreds of data sets below my layer, but no keyframes.

 

2.JPG

 

Thank's for your help.

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

Hi @julianl065

 

At the moment I cannot spend time explaining how the process works. It's pretty complex (as using the data in After Effects was experimental). The only way I know of achieveng this is by using the Processing sketch ( https://github.com/JuanIrache/gyrocam ). It analyses the extracted CSV and creates additional CSV files that you can copy and paste (its contents) on After Effects layers. You won't need to do real coding, just adapt the basic values (framerate,frame size...) to what you filmed and the results you expect. There was some discussion on how to do this here, but unfortunately most of it is in Spanish: https://github.com/JuanIrache/gyrocam/issues/2

Tourist
Posts: 4
Re: Extracting the metadata in a useful format
[ Edited ]

Hey,

 

I just tested the bat with my Hero 7 black and I didn't encounter any big problems. I haven't checked the full integrity of the data, but it seems reasonable.

I didn't get any temperature data it seems.

 

If it helps, I can provide some sample files. I have a bit of coding experience, but not nearly as much as y'all do. I hope I can help further this project!

 

Cheers,

Lemmi

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

Thanks @jm-lemmi,

 

I just tried my new 7 Black and I'm surprised at how inaccurate GPS data is. The camera was chest-mounted while riding a motorbike, but I drove for like 20 minutes and there are barely a couple of acceptable locations, let alone anything similar to a track.

 

Those with experience with GPS-enabled GoPros, is this normal? I was expecting a bit more... this is unusable.

Hiker
Posts: 28
Re: Extracting the metadata in a useful format

How did you start the recording? Using the one-button start or from standby? I have no problem recording GPS data when I turn the camera on, let it get GPS lock and then record a video but there's never any data in the one-button videos

 

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format
I turned the camera on first, but did not wait for a GPS lock. I assumed it would get a lock eventually and record the data. Will wait for a lock next time. Thanks
Tourist
Posts: 4
Re: Extracting the metadata in a useful format

My first first testvideo only had 0; 0 Coordinates, which is pretty disappointing. I started it first and then recorded. Its was a 10 minute bike ride with the camera on my chest and the GPS should have no problem, as it was in a small suburb.

 

My second Test was today on the fields, with the camera mounted on my head, the result is not ideal tbh. It lost contact, as soon as I entred the housing, even though there really shouldnt be that much interference. My phone works just fine.

 

I also have a problem with the codec. I recorded in HEVC instead of H264, when I turned it back to H264, it doesnt seem to register. Might have to test later again.

Screenshot (347).png
Tourist
Posts: 4
Re: Extracting the metadata in a useful format

Ah, I just realized that H264 is not compatible with 4k60. My bad

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

@jm-lemmi Keep in mind that your phone takes its position from land antennas too. So it will keep a lock when it can't read GPS satellites. The GoPro cannot do that.

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

Thanks to a contribution by Alex Denning the GPMD2CSV tool has been improved:

http://tailorandwayne.com/gpmd2csv/

Tourist
Posts: 8
Re: Extracting the metadata in a useful format

I appreciate the work being done here.  I didn't know this message board existed, I'll have to spend some time reading and catching up.

 

A summary of the changes I made to GPMD2CSV:

There are now two batch files:

GPMD2CSV.bat (Processes a single .mp4 file, just drag and drop on the script)

GPMD2CSV Folder Process.bat (processes all .mp4 files in the source directory, just drag and drop a single file on the script)

 

GPMD2CSV.bat:

Drag a file on from any directory and it outputs to a sub directory under that file path (no need to move the files to the same directory as the batch file).

It runs the processes minimized so FFMPEG windows don't pop up during processing.
Displays a "Processing file" message in the main window during file processing along with info on what is being processed.
Can now nest the output directory under another directory (Edit line: Set BatchOutputFolder=).  Default is "GoPro Metadata Extract\"
It doesn't process files if the export directory exists (assumes it's already been processed).  Delete the older directory if you'd like to reprocess.
 
GPMD2CSV Folder Process.bat:
Drag an MP4 file from any directory onto that file.
It will process ALL MP4 files in that folder and output to the nested directory ("GoPro Metadata Extract\<Source File Name>\")
This batch file calls "GPMD2CSV.bat".  So, edit the line: "Set BatchOutputFolder=GoPro Metadata Extract" to change the default export directory.
 
Alex
Hiker
Posts: 28
Re: Extracting the metadata in a useful format
[ Edited ]

Good stuff, except the filename subdfolders seem redundant since the files are all labeled with the name and it makes it a lot more cumbersome to process the output files - there's no easy way to import all the .gpx into Goole Earth or any other external program, you need to fish all of them out of their subdirectories..

 

Any chance to either revert this or make it an option?

 

M.

Tourist
Posts: 8
Re: Extracting the metadata in a useful format

Ok, added the option to create the nested subdirectories or not.  Save the new code as "GPMD2CSV.bat".  I've done limited testing, should work though.

 

Switches:

This is the name of the overall subdirectory.  If you don't need a subdirectory, just set "BatchOutputFolder=" to nothing.

 

:: Name of the folder that is created to output to (Optional)
Set BatchOutputFolder=GoPro Metadata Extract

 

 

This is the optional nested subdirectory by filename.  Set "Set IndividualSubDirs=No" and it won't make the inddividual subdirectories.

 

:: Make Individual Subdirectories for each file?  Type in Yes or No
Set IndividualSubDirs=Yes

 

 

Examples:

To Output to "<Source File Directory>\GoPro Metadata Extract\<Source File Name>\<FILES>" Set:

Set BatchOutputFolder=GoPro Metadata Extract
Set IndividualSubDirs=Yes

 

To Output to "<Source File Directory>\GoPro Metadata Extract\<FILES>" Set:

Set BatchOutputFolder=GoPro Metadata Extract
Set IndividualSubDirs=No

 

To Output to "<Source File Directory>\<Source File Name>\<FILES>" Set:

Set BatchOutputFolder=
Set IndividualSubDirs=Yes

 

To Output to "<Source File Directory>\<FILES>" Set:

Set BatchOutputFolder=
Set IndividualSubDirs=No

 

 

Copy the code below and save as "GPMD2CSV.bat":

 

@ECHO OFF

:: Name of the folder that is created to output to (Optional)
Set BatchOutputFolder=GoPro Metadata Extract

:: Make Individual Subdirectories for each file?  Type in Yes or No
Set IndividualSubDirs=Yes

:: ==========================================
:: You shouldn't need to edit below this line
::===========================================

:IndividualSubDirCheck
if '%IndividualSubDirs%'=='Yes' goto IndSubDirY
if '%IndividualSubDirs%'=='yes' goto IndSubDirY
if '%IndividualSubDirs%'=='Y' goto IndSubDirY
if '%IndividualSubDirs%'=='y' goto IndSubDirY
if '%IndividualSubDirs%'=='No' goto IndSubDirN
if '%IndividualSubDirs%'=='no' goto IndSubDirN
if '%IndividualSubDirs%'=='N' goto IndSubDirN
if '%IndividualSubDirs%'=='n' goto IndSubDirN
Goto IndividualSubDirCheckError

:IndSubDirY
Set IndividualSubDirs=1
GoTo RunIt

:IndSubDirN
Set IndividualSubDirs=0
GoTo RunIt

:RunIt

Set SourceScriptDirectory=%~dp0
Set SourceFile=%1

cd "%~dp1"

If '%IndividualSubDirs%'=='1' (
	If exist ".\%BatchOutputFolder%\%~n1\%~n1".gpx goto :eof
) Else (
	If exist ".\%BatchOutputFolder%\%~n1".gpx goto :eof )

mkdir "%~n1"
if [%1]==[] goto :eof
:loop
"%SourceScriptDirectory%\bin\ffmpeg" -i "%~1" > output.txt 2>&1
for /F "delims=" %%a in ('FINDSTR "gpmd" output.txt') do set line=%%a
echo "%line%"
set stream= %line:~12,3%
echo "%stream%"
CLS
ECHO.
ECHO **************************************************
ECHO **************** Processing file: ****************
ECHO "%~nx1"
ECHO ***************** In Directory: ******************
ECHO "%~dp1"
ECHO **************************************************
@ECHO ON
START "" /WAIT /MIN "%SourceScriptDirectory%bin\ffmpeg" -y -i "%~1" -codec copy -map "%stream%" -f rawvideo "%~n1".bin
START "" /WAIT /MIN "%SourceScriptDirectory%bin\gpmd2csv" -i "%~n1".bin -o "%~n1"/"%~n1".csv
START "" /WAIT /MIN "%SourceScriptDirectory%bin\gopro2json" -i "%~n1".bin -o "%~n1"/"%~n1".json
START "" /WAIT /MIN "%SourceScriptDirectory%bin\gps2kml" -i "%~n1".bin -a 1000 -f 3 -o "%~n1"/"%~n1".kml
START "" /WAIT /MIN "%SourceScriptDirectory%bin\gopro2gpx" -i "%~n1".bin -a 1000 -f 3 -o "%~n1"/"%~n1".gpx
DEL "%~n1".bin
DEL output.txt
Mkdir "%BatchOutputFolder%"

If '%IndividualSubDirs%'=='1' (
	Move /Y "%~n1" ".\%BatchOutputFolder%\"
) Else (
	Move /Y "%~n1\*" ".\%BatchOutputFolder%\"
	RMDIR /S /Q "%~n1\" )

shift
if not [%1]==[] goto loop
GoTo eof

:IndividualSubDirCheckError
cls
ECHO **********************************************************
ECHO ************************* ERROR **************************
ECHO ***** "IndividualSubDirs" is not formatted correctly *****
ECHO *** Check "GPMD2CSV.bat" and verify it is = Yes or No ****
ECHO **********************************************************
pause
exit

 

 

Sightseer
Posts: 8
Re: Extracting the metadata in a useful format

This thread is a godsend. Thank you all so much.

i look forward to trying this - I've been so frustrated with my GoPro 7 black and the entire GoPro software stack.

I'm shooting wingsuit videos in 4k/60 and the entire workflow of adding visualization / gauges is just horrid. I don't want to make a 30 sec highlight reel and quik desktop would just freeze on large videos.

 

i was ready to return my 7 after 2 months of frustration but you guys have given me hope of extracting gps data for use with virb Edit.

 

thank you

Tourist
Posts: 8
Re: Extracting the metadata in a useful format
[ Edited ]

vg071, good to hear!

 

I use Garmin Virb edit for all of my overlays as well.

 

I wrote a guide for applying video overlays using Virb Edit, any action cam (GoPro Hero 3) and data files from a bike computer.  The bike computer outputs data files similar to what is extracted using kajuna's tool.  You might find it useful, but, you'd of course use the files from the extract tool instead of from a bike computer/fitness device.

 

https://docs.google.com/document/d/1eUmBCdN6dIZXLHaLAdoTw7wRYn_1dBV60JxWPscwONU/edit?usp=sharing

Sightseer
Posts: 8
Re: Extracting the metadata in a useful format

thank you, everyone.

with your brilliant data extraction and importing into virb edit, it all works!

 

no more of gopro's software rubbish.

 

you guys made my gopro useful again! thank you

 

 

Sightseer
Posts: 8
Re: Extracting the metadata in a useful format

Noticed a couple of things (that I don't recall reading here - though I suppose you folks already know of it)

The gps data gathering seems to start once the camera is powered on and a gps fix is obtained - not when the actual recording starts (does that make sense?)

 

I was going over the csv file - and I see at some point, the altitude goes negative.

Guessing that might be an elevation thing (though i am testing it at more or less 0 feet above sea level)

 

 

this is fascinating (and go pro can well learn from virb edit how to write software...still bitter, but less so, thanks to you all)

Tourist
Posts: 4
Re: Extracting the metadata in a useful format

If there are any motorsports GoPro users out there, you might be interested to give serious-racing.com a try (disclaimer, I'm one of the co-founders).

 

We've recently added support for GoPro to serious-racing.com so you can turn your GoPro into a GPS lap timer. I did a bit of a write up of the technical implementation here:

 

https://serious-racing.com/blog/how-users-helped-us-develop-gopro-lap-timer/

 

There's no software to install - we extract the data from the video right from your browser, and turn it into laps for comparison with other users.

 

We'd be particularly interested in users with GoPro Hero6 or Hero7 to give it a try - we think it should work fine, but have only had users with GoPro Hero5s using it so far.

 

Cheers, Tom

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

Hi @boldbeach40806,

 

I just uploaded a Hero7 Black track to your system and I'm not sure I'm seeing what I'm supposed to see. I just see a list of "laps" but when I click on them they display as standalone points. I might be doing something wrong, as I never used your system.

By the way, I'm the author of the github repo you mention in your article. It's great that you managed to go full JavaScript on this. I'd like to try that too for my tools when I get some spare time. Your article appears to miss that the repo includes a batch tool for easy extraction (it combines the ffmpeg and go processes) but that does not matter much now that you've solved it through the browser. I'm guessing your code is not open sourced in case I want to have a look at it, is it?

Cheers and welcome to the group.

Tourist
Posts: 4
Re: Extracting the metadata in a useful format

Hi,

 

Ah, so the data you've uploaded won't look so great on the site as it's designed for tracks and so there are some built in assumptions about what makes up a track that the data on the beach won't work with. I've sent you a friend request on serious-racing.com - if you accept that you'll be able to see my laps, to get an idea of what it looks like.

 

In terms of the data you uploaded, here's a screen grab showing the GPS trace. Does this look right? If so, that's a pretty good indicator that this would work for a Hero7.

 

Yeah, we wanted to avoid people having to upload the entire video in the browser, which was why we went the javascript route to be able to pull just the GPS data out, but great that your repo does that. The code isn't open sourced, but I'd be happy to contribute back to your repo code showing what I'm doing, but it'd be python. Is that of interest?

 

Thanks, Tom

gps_trace.png
Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

@boldbeach40806 Yes, the map is correct. And the info on your app looks great (just checked your tracks).

Did you end up using some of the code from my repo? It works well with all cameras after Hero5, as far as I know, so if it's based off of that you should have no problems.

I'm considering re-creating the repo from scratch when I get some time off from work, as for now it's just a fork of the unmantained original project. I'm not sure how python code would fit in all that. It would be interesting to see, and useful when/if I get into developing an online version of the metadata extracting tool. So, maybe if you see where your code could fit in the repo you can send a pull request.

Tourist
Posts: 4
Re: Extracting the metadata in a useful format

I didn't end up using any code from your repo, as the project is in Python. I'm not really sure a PR would make sense given that, but the code I'm using is this:

 

https://pastebin.com/mqbKKeSn

 

It's a very stripped down version of what you're doing, as I'm only pulling out the data points/types I care about for my specific application rather than parsing all the GoPro data.

 

Thanks, Tom

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

@boldbeach40806 Thanks. It's really interesting to see such a concise implementation. 

Tourist
Posts: 8
Re: Extracting the metadata in a useful format

what is your repo?

try to get in how to extract .gpx from gopro 7 silver video.

 

sadly, gought gopro without scout a situation, thinking, a gopro is leader in actioncams, and all must be very ok....

such **bleep**ty software i do not encounter for ages, must say :(

 

Tourist
Posts: 8
Re: Extracting the metadata in a useful format

>I didn't end up using any code from your repo, as the project is in Python. I'm not really sure a PR would make sense given that, but the >code I'm using is this:

 

>https://pastebin.com/mqbKKeSn

 

>It's a very stripped down version of what you're doing, as I'm only pulling out the data points/types I care about for my specific application >rather than parsing all the GoPro data.

 

>Thanks, Tom

 

python code - it is good.

run it with python3 interpreter on macos, with extracted MET stream, but in output get 39 bytes file with content:

 

 

timestamp,latitude,longitude,speedmps

 

 

 

 

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format
@drago76 My repo is compiled as a bundle that allows you to export the gpx files by just dropping your video files (windows only): https://tailorandwayne.com/gpmd2csv/
Tourist
Posts: 8
Re: Extracting the metadata in a useful format

Ok, get it, windows is not interesting - thanks to god, i get off of microsoft nightmare about since 2006.

 

there is a solution for mac / linux?

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

@drago76 You will then have to do manually the steps that the batch script does. Everything is included here: https://github.com/JuanIrache/gopro-utils

- Extract the binafy with ffmpeg

- Convert to GPX with the gopro2gpx tool (you will have to compile it with GO first, or run the .EXE one if you can do that on your Mac)

Tourist
Posts: 8
Re: Extracting the metadata in a useful format

try to process MET stream as described, import that .gpx file to garmin virb edit - yes, visually

route was right on map.

 

but virb edit telemetry do not show speed, only bearing and distance.

speed stays 0, gravity indicator too.

 

ok, gravity not very important there, but speed was important, why it stays zero?

 

PS and why there is no python script to convert .bin file to gpx?

it was much more handy, because of python was in default in almost any linux distro, for example.

 

also sadly, in readme file was no any info, how to use gopro2gpx.go script - it takes a time to get, i must run

 

go run  gopro2gpx.go -i input -a 500 -f 2 -o filename

 

and also must have a 

bash-3.2$ go run  gopro2gpx.go -i out-0001.bin -a 500 -f 2 -o gopro1.gpx

gopro2gpx.go:14:2: cannot find package "github.com/JuanIrache/gopro-utils/telemetry" in any of:

/usr/local/Cellar/go/1.11.4/libexec/src/github.com/JuanIrache/gopro-utils/telemetry (from $GOROOT)

/Users/john/go/src/github.com/JuanIrache/gopro-utils/telemetry (from $GOPATH)

 

so, i must install it by

 

go get github.com/JuanIrache/gopro-utils/telemetry

 

yes, python script may be much, much better alternative, i suppose... :\

 

PS do anyone use a garmin virb cameras? how is it, comparing with gopro in general?

i know, it is very hard to make product worse than gopro, but anyway.... its soft and UI / firmware is better, not such murky and buggy?

Tourist
Posts: 8
Re: Extracting the metadata in a useful format

if there is any programmer, may it take a look in moviepy?

 

it looks lika a python script, who allow to place various overlays over a video.

i start to investigate it, and it looks very promising at start...

 

https://github.com/Zulko/moviepy/issues/222

 

https://zulko.github.io/moviepy/getting_started/getting_started.html

 

https://www.youtube.com/watch?v=Fg8Sf4fPCwY

 

 

Muchas veces hacemos videos montando en bici y nos gustaría saber ¿ a cuanto pasé por aquí ? ¿ que pendiente tenía esta rampa ? ¿ Cuantos Watios meto subiend...
Sightseer
Posts: 1
Re: Extracting the metadata in a useful format

I just hacked together a python3 implemention of the entire process based on the pastebin script a few posts back. I wanted it simple to use and able to process multiple videos at once into once track. I tested it with strava and it looks to be working OK.

 

https://github.com/krisp/gopro2gpx/blob/master/gopro2gpx.py

 

usage: python3 gopro2gpx.py GP010010.MP4 GP020010.MP4 GP030010.MP4 out.gpx

 

probably works on windows and mac, linux is tested. if ffmpeg is somewhere other than /usr/bin/ffmpeg, edit the script accordingly.

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

That's fantastic, thanks for sharing

Tourist
Posts: 8
Re: Extracting the metadata in a useful format

Kajuna's GoPro utilities has recently been update with a new batch script "Metadata Copier.bat". This has the capability to copy the metadata from a source video file to a post processed video file that lacks the metadata of the original.

 

I post process and color corect my GoPro files using DaVinci Resolve. The problem I had is when exporting video from DaVinci Resolve, the metadata and timestamp information was being stripped out, so all of my GPS data was lost. I developed this script to copy all of that useful metadata from the original GoPro files to the post-processed files. This script just copies the data, so the source file length and framerate should be the same as the original, or you might have issues.

 

To run the script, you'll want to have your input files (original GoPro files with metadata) and corrected files (with the edits, color corrections, etc.) organized correctly. Drag an original GoPro source file onto the script and it will process all of the source .MP4 files in that directory that correspond to a corrected file in the "EditedVideoPath".

 

You may edit the top portion of the batch file to change the default settings, if necessary. The script will look at the source GoPro .MP4 files and use the settings chosen to search for a corresponding edited file to process. You may change which folder edited files are in, and anything you have prepended or postpended to the file name (the base filename needs to remain intact). You may also edit the batch file to change which folder the script will output files to and any prepended or postpended text to the filename.

 

Tip: Use Bulk Rename Utility to easily manage file naming:

https://www.bulkrenameutility.co.uk/Download.php

 

Example (using defaults):
Original GoPro files (source files for metadata): "C:\Source Files\GoPro Video 1.mp4"
Edited (color corrected files, source for video/audio): "C:\Source Files\Edited Video\GoPro Video 1.mp4"
The metadata corrected files will export to: "C:\Source Files\Metadata Fix\GoPro Video 1_MDF.mp4"

The options you can edit in the batch file:

 

:: This is the name of the nested directory that contains the edited/color corrected video files.
set EditedVideoPath=Edited Video

:: Edit this to tell the script anything that has been prepended to the filename of the edited/color corrected video files.
set EditedPrepend=

:: Edit this to tell the script anything that has been postpended to the filename of the edited/color corrected video files.
set EditedPostpend=

:: Directory to export the processed files to (nested under source file directory).
set ExportVideoPath=Metadata Fix

:: Optional text to postpend to the exported video files (with the correct video/metadata)
set MetadataFixedPostPend=_MDF

 

FYI, I mostly used this process to color correct my video files. Credit to "The Loam Ranger" for the awesome process:
Part 1: https://www.youtube.com/watch?v=2YEePcJZcFI
Part 2: https://www.youtube.com/watch?v=NXnBCkF9jUQ&t=633s

It's the ultimate action cam / GoPro tutorial. HERES PART 2: https://youtu.be/NXnBCkF9jUQ No BS, all solid info. Professional videographer and photographer R...
Part 2/2 from my GoPro and action cam series is here! In this tutorial video, I cover exactly how I take my raw, unprocessed GoPro footage and turn it into s...
Tourist
Posts: 8
Re: Extracting the metadata in a useful format

bash-3.2$ python3 gopro2gpx.py GH010001.MP4 01.gpx

  File "gopro2gpx.py", line 149

    print(

         ^

TabError: inconsistent use of tabs and spaces in indentation

bash-3.2$ 

Tourist
Posts: 4
Betreff: Extracting the metadata in a useful format

Hello, 

 

Is there a similar way to extact the metadata of the accelerometer of a H7 or is there a simple way to see the data in gopro quik?

Or is this method compatible also with H7?

 

Thank you 

Nomad
Posts: 1,122
Betreff: Extracting the metadata in a useful format

@bluecreek74714 It's compatible! Just drag and drop your files on the batch script (for Windows)  

 

https://tailorandwayne.com/gpmd2csv/

Sightseer
Posts: 1
Re: Extracting the metadata in a useful format
Hi,

I'm reading through all postos but still I have an issue. I use BAT script to extract GPX data. But When i load that data into VIRB edit, my speed value isnt correct. I ride my bike 140 km/h and speedometer says 7 Km/h. Only correct value is when I'm standing still, than both speed are at 0 :)

I have tried to correct
SET AccuracyFilter=500
SET FixFilter=3

Vithout success. If I use file in GoPro Quick than speed is shown correctly. ALTitude, Time and other values are shown correct.

I use GH5Black, sw. 2.60

I like this VIRB app a lot, but without speedometer it is useles to me. I tried with calculated speed, measured speed, ...

Here is some data from extract:
<?xml version="1.0" encoding="UTF-8"?>
<gpx xmlns="http://www.topografix.com/GPX/1/1" version="1.1" creator="https://github.com/tkrajina/gpxgo">
<trk>
<name>C:\Users\ivank\Desktop\GPMD2CSV\\GoPro Metadata Extract\GOPR0510\GPMD2CSV</name>
<trkseg>
<trkpt lat="45.8046646" lon="16.2435384">
<ele>151.984</ele>
<time>2019-03-09T14:35:00.715Z</time>
<cmt>GpsAccuracy: 194; GpsFix: 3</cmt>
</trkpt>
<trkpt lat="45.8046638" lon="16.2435428">
<ele>151.979</ele>
<time>2019-03-09T14:35:00.770Z</time>
<cmt>GpsAccuracy: 194; GpsFix: 3</cmt>
</trkpt>
<trkpt lat="45.804663" lon="16.2435473">
<ele>151.968</ele>
<time>2019-03-09T14:35:00.825Z</time>
<cmt>GpsAccuracy: 194; GpsFix: 3</cmt>
</trkpt>
<trkpt lat="45.8046622" lon="16.2435518">
<ele>151.958</ele>
<time>2019-03-09T14:35:00.880Z</time>
<cmt>GpsAccuracy: 194; GpsFix: 3</cmt>
</trkpt>
<trkpt lat="45.8046614" lon="16.2435562">
<ele>151.961</ele>
<time>2019-03-09T14:35:00.935Z</time>
<cmt>GpsAccuracy: 194; GpsFix: 3</cmt>
</trkpt>
<trkpt lat="45.8046606" lon="16.2435606">
<ele>151.97</ele>
<time>2019-03-09T14:35:00.990Z</time>
<cmt>GpsAccuracy: 194; GpsFix: 3</cmt>
</trkpt>
<trkpt lat="45.8046598" lon="16.2435651">
<ele>151.97</ele>
<time>2019-03-09T14:35:01.045Z</time>
<cmt>GpsAccuracy: 194; GpsFix: 3</cmt>
</trkpt>
<trkpt lat="45.8046589" lon="16.2435696">
<ele>151.976</ele>
<time>2019-03-09T14:35:01.100Z</time>
<cmt>GpsAccuracy: 194; GpsFix: 3</cmt>
</trkpt>


If I use same GPX data on this web site (https://tailorandwayne.com/dji-srt-viewer/), a get correct speed values

Any idea?
Tourist
Posts: 4
Re: Extracting the metadata in a useful format

Im having the exact same problem with Virb edit not showing my speed :(.  It even shows the track correctly, but speeds wont display.  Just swaps betwen 0, 1 and 2 mphs.  Speed displays fine in dashview or quik.

Sightseer
Posts: 8
Re: Extracting the metadata in a useful format
Same here.
While Virb Edit fills the need of having a good desktop application that can render GPS overlay videos, it’s not the ideal solution for non Garmin stuff. And I suppose that’s to be expected - why should they care about non Garmin nuances?
We’re just lucky some stuff works.

Go pro needs to seriously write a desktop application that can handle the data overlays of their cameras.

(Go pro quik is rubbish, absolute trash)
Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format
Does anyone have a GPS file that works in Virb Edit so that I can compare them? If it's a formatting issue I should be able to adjust the GPMD2CSV tool
Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format
[ Edited ]

I updated the GPMD2CSV tool and now it also includes timestamps in the KML files. Maybe Virb edit can load those files too? I'm guessing the problem is Virb does not read the milliseconds from the timestamps right.

I also enabled exports to GeoJSON, but those do not include timestamps, so not useful for reading speed.

 

Working on more cool features :) Comming soon... I hope.

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format

It looks like Virb Edit cannot read milliseconds properly. I can provide a workaround but it will be some days until I have a user friendly solution. In the meantime, if anyone wants their GPX files adapted for virb they can send them to me privately.

Hiker
Posts: 27
Re: Extracting the metadata in a useful format

"Does anyone have a GPS file that works in Virb Edit so that I can compare them? If it's a formatting issue I should be able to adjust the GPMD2CSV tool "

 

Is it possible that VIRB edit is using a GPS speed value for the speed readout (and not finding one in the GPX files from this otherwise excellent tool, because it doesn't generate them in the GPX)? I see the speed values are extracted and are in the CSV file with the GPS info like this:

 

<extensions>

<gpxtpx:TrackPointExtension>

<gpxtpx:speed>6.86</gpxtpx:speed>

<gpxtpx:course>271.06</gpxtpx:course>

</gpxtpx:TrackPointExtension>

</extensions></trkpt>

 

I was going to dust off my VBA skills to use that CSV to export another GPX file that would have the speed in the GPX xml, but then I figured maybe it could be added to the export by the experts.

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format
I will try. I didn't build the GPX part of my tool, but will have a go at it when I find a moment. If anyone can fix it now just send a pull request on github :)

https://github.com/JuanIrache/gopro-utils/blob/master/bin/gopro2gpx/gopro2gpx.go
Sightseer
Posts: 8
Re: Extracting the metadata in a useful format
[ Edited ]

Hi,

 

I don't think it's a formatting issue - from what little I know.

 

I was going over the csv data from your excellent extraction tool - and it seems the gopro goes into negative values for altitude (speed I havent looked at yet)

 

Unfortunately, I cannot vouch for the speed data - as I have no external way of checking that just yet (getting a FlySight soon though)

 

But if it helps, even on successful video overlays in ViRB Edit, it has the altitude off by around 900-750 feet or so - that I can just about look at footage and mention specific points where it's off.

 

i can give you lots of data if you need :) including the raw video if you need it

Nomad
Posts: 1,122
Re: Extracting the metadata in a useful format
Altitude is not relative to sea level, that's why it can go negative. Fixing that is in my to-do list