HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gopro
gpmf-parser
C2017–2018
gopro / gpmf-parser

gpmf-parser

Parser for GPMF™ formatted telemetry data used within GoPro® cameras.

2Distinct people
2Mentions
0Explicit recommenders
659GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Parser for GPMF™ formatted telemetry data used within GoPro® cameras.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month2 dated mentions

Observed mentions: 2017-04-24 18:44:48 UTC to 2018-09-20 17:01:37 UTC.

012017-04-01 00:00:00 UTC to 2017-05-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 20172017-05-01 00:00:00 UTC to 2017-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-06-01 00:00:00 UTC to 2017-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-01 00:00:00 UTC to 2017-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-01 00:00:00 UTC to 2017-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-01 00:00:00 UTC to 2017-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-01 00:00:00 UTC to 2017-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-01 00:00:00 UTC to 2017-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-12-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 20172018-01-01 00:00:00 UTC to 2018-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-01 00:00:00 UTC to 2018-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-03-01 00:00:00 UTC to 2018-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-01 00:00:00 UTC to 2018-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-05-01 00:00:00 UTC to 2018-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-01 00:00:00 UTC to 2018-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-07-01 00:00:00 UTC to 2018-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-08-01 00:00:00 UTC to 2018-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-09-01 00:00:00 UTC to 2018-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 2018

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 20172017-04-01 00:00:00 UTC2017-05-01 00:00:00 UTC110
May 20172017-05-01 00:00:00 UTC2017-06-01 00:00:00 UTC000
Jun 20172017-06-01 00:00:00 UTC2017-07-01 00:00:00 UTC000
Jul 20172017-07-01 00:00:00 UTC2017-08-01 00:00:00 UTC000
Aug 20172017-08-01 00:00:00 UTC2017-09-01 00:00:00 UTC000
Sep 20172017-09-01 00:00:00 UTC2017-10-01 00:00:00 UTC000
Oct 20172017-10-01 00:00:00 UTC2017-11-01 00:00:00 UTC000
Nov 20172017-11-01 00:00:00 UTC2017-12-01 00:00:00 UTC000
Dec 20172017-12-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
Jan 20182018-01-01 00:00:00 UTC2018-02-01 00:00:00 UTC000
Feb 20182018-02-01 00:00:00 UTC2018-03-01 00:00:00 UTC000
Mar 20182018-03-01 00:00:00 UTC2018-04-01 00:00:00 UTC000
Apr 20182018-04-01 00:00:00 UTC2018-05-01 00:00:00 UTC000
May 20182018-05-01 00:00:00 UTC2018-06-01 00:00:00 UTC000
Jun 20182018-06-01 00:00:00 UTC2018-07-01 00:00:00 UTC000
Jul 20182018-07-01 00:00:00 UTC2018-08-01 00:00:00 UTC000
Aug 20182018-08-01 00:00:00 UTC2018-09-01 00:00:00 UTC000
Sep 20182018-09-01 00:00:00 UTC2018-10-01 00:00:00 UTC101

What Hacker News says

2 sources
Considering this is HN, does anyone have any input on the latest GoPros vs Garmin Virb Ultra 30, specifically in terms of telemetry formats vs general camera quality? Garmin seems to be the data king here, but I'm curious as to whether the GoPro is perhaps the better camera, and if so, whether this could offset the differences between the data formats. I should note that the telemetry is important for our usage, GPS logs especially. We have two Ultra 30s at work (used in humid areas, mostly at walking speed) and with GPS turned on (obligatory) and 1440p/30fps video we get 90-110mins of continuous footage before the battery is completely drained. Longer battery life would be nice and every now and then we get hiccups/glitches (looks like frames are skipped) with the setting above. Doesn't invalidate the footage in any way and it's rare, bu
Read the rest
t still annoying. Could be a firmware bug, really. Audio is so-so, but that is to be expected (we haven't tried external microphones yet, since the setup needs to be as simple as possible). Would a GoPro help with any of the above or is it a similar experience in terms of battery etc? If anything, the GoPro seems more rugged (for our needs, the Virb needs a case). What about video quality? Interface? (I did read DC Rainmaker's comparison[0] which was what made us choose the Virb, together with the fact that there's an SDK for FIT and at the time of purchase GoPro didn't have a Github repo[1]) GoPro's GPMF data is embedded within the video file, whereas Garmin's FIT[2] format is separate and is logged to whether one is recording or not as long as the camera is turned on. Both have their pros and cons, FIT seemingly being the more flexible format (it's basically a big timeline with events attached) but one also needs to identify what part of the data stream corresponds to which video session and it's not as "linear" to read as GPMF (?). In FIT every single logged coordinate is also timestamped (10Hz GPS), whereas it seems that you only get one timestamp/second for GPMF coordinates (18Hz GPS). I wrote a little parser to extract and integrate the relevant telemetry data elsewhere and have started looking at doing the same for GPMF (I wanted to write it from scratch in a language I'm learning). Since I have no recent GoPro at hand it's been difficult finding raw samples for the GoPro, other than the GPFM GitHub repo - youtube won't suffice since I need the original video with the telemetry intact. [0]: https://www.dcrainmaker.com/2017/03/best-action-cam-2017-gop... [1]: https://github.com/gopro/gpmf-parser [2]: SDK here https://www.thisisant.com
In GoPro Hero 7

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.