jallison

Competing is fun. Seeing people compete is fun. The OP wants you to click a link and get stoked, there is no more to it than that.

Thanks for you help, folks. I've concluded that no matter the processing, the data will never be nearly as rich coming from a gopro as it is in a Flysight log. At least I tried! I got myself a Flysight, and I am now very happy with my logs

I figured I should make my own parser to output a CSV similar to that of a Flysight, so here goes : https://github.com/j-allison/gopro-to-flysight Before (using data from the util cited above: https://tailorandwayne.com/gopro-telemetry-extractor/) : After using my parser, based on `gpmf-extract` and `gopro-telemetry` libraries: I'm feeling happier with those results; they seem to be way less "smoothed out". Still work in progress. (Is it outrageously wrong to calculate N/E velocity components by using lat or long difference over time difference from point A to point B ? )

I'm realizing as I read you that I'm relying on my GPX data without questioning its origin. Here's how I proceeded: Extracted raw data from mp4 into a raw file, using ffmpeg : ffmpeg -y -i "/path/to/theFile.MP4" -codec copy -map 0:3 -f rawvideo outputFile.bin Used the "gopro2gpx" util from this repo to parse raw data into gpx : https://github.com/JuanIrache/gopro-utils Here's where I was wrong - step 1 preserves all data. Step 2, not so much. I overlooked the fact that it might leave data behind while parsing the binary extract into gpx. So I'm currently trying out this other util (slower, in JS) : https://github.com/JuanIrache/gopro-telemetry And... I seem to get a 3D velocity! I get a more thorough output in JSON, I still have to convert it to gpx though. Files attached, work in progress! Also included, GPS data in CSV. Fun stuff!! chablais.json chablais.raw flares.json flares.raw GH010928-gps chablais.csv GH018648-gps flares.csv

Spot on. Thank you for the simple explanation on different constellations. The gps fix is nowhere near 12-18, I've consistently had a value of 3 (best case scenario). Again, you're absolutely right. There's no 3D velocity in the GoPro's data so it has to be calculated from position afterwards. Far from ideal. Thank you so much for clarifying those points, that's exactly the kind of precision I was hoping for.

Sure thing, I'll add it to the original post. It's an automator script, so OS X only, and you'll need ffmpeg installed on your machine for it to work. It does exactly the same thing as this website : https://tailorandwayne.com/gopro-telemetry-extractor/ extractgpx.zip

Thanks for the input. I'll take 18Hz over 5-10 anytime, more data can't hurt in this context. Ease of use: I've made a script on OS X - drag and drop mp4 file onto it -> outputs a .gpx -> ready to import in any analysis website or software No audio feedback: good point, I'll have to try this out when I can get my hands on a flysight!

I recently managed to extract GPS data from my GoPro hero 7 footage. I was in the market for a Flysight unit but I think I might reconsider now. The (crappy) GoPro Quik app used to tell me my footage hadn't recorded any GPS data for lack of satellite fixes. That doesn't seem to be true as there actually is data attached to the mp4 files. Use https://tailorandwayne.com/gopro-telemetry-extractor/ to extract data from the mp4 file Export to .gpx file Import in baseline.ws, or Flysight viewer, or whatever gpx interpreter app Now for the nerdy part. I've never owned a Flysight unit, nor analyzed any data coming from one. But according to the specs, it seems to output data at a ~5Hz rate, whereas the GoPro GPS chip writes ~18Hz worth of data. That's more than 3 times the rate of a Flysight. There seem to be a few outliers here and there, but overall I'm pretty impressed with the GoPro's GPS feature. I wouldn't have bet on this level of accuracy. Especially coming from a device that freezes out from time to time, or chews up a whole battery while powered off. Here are a few acro lines (Funk 3): https://baseline.ws/tracks/d91e5f18-fc01-4b7f-9a6b-581dfd8ae8ea https://baseline.ws/tracks/87a4aed6-ed70-4605-8fc6-a604ad2d29e9 https://baseline.ws/tracks/2ca462ea-6173-4610-b5c0-8e20be9c62e1 And a Freak 2 (heli skydive) line over the swiss Alps: https://baseline.ws/tracks/8afcce5a-ef26-48e4-bf69-ebef01ccd157 Flysight nerdy users: what's your take on this? Does the data from my GoPro seem reliable? Are there too many outliers compared to a Flysight?

I'd hate to be the party pooper here, but buying an S3 seems to be a huge step-up from 13 jumps on an Indy? Maybe you should check with your mentor if there are any intermediate suits to rent nearby, Versos, Hawks or similar older "French level 2" suits? The Indy is a great suit to start for your first jumps. But it's an old, low-pressure design. Your position when pulling from an Indy won't matter much. The S3 on the other side, is a race car in its own category, not to be underestimated. Again, check with your mentor. You're in for another 7 jumps before you can get your "niveau 2" anyway

@Lukasz_Se, got home yet ?

Shot using a friend's Rylo, no unicorn mount, just the usual cookie roller mount on a G3 + a couple of small ~1-inch GoPro extender thingys. Far from being a snag-free config ;) https://www.youtube.com/watch?v=YdEyhLSimyE (Ignore cheesy visual & sound effects, we're aiming for a "friends & family" audience ;) )

That's not on you, their shady marketing techniques are really to blame here. "The brand new GoPro 7 white" is basically a dishonest repackaging of deprecated hardware. Fixed battery, fixed lens cover, no 4k, no screen, no 16:9, ... :(

Not even close http://elproducente.com/gopro-hero7-black-silver-white-review-all-specs-compared/ Even the entry-level "GoPro 2018" will do a better job. Especially with a firmware upgrade to make a GoPro 5 black out of it!