mapillary / mapillary/mapillary_tools

GoPro MAX video - upload export rectilinear 360° images spaced by GPS distance.

Open
#747 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
315
Forks
145
Avg merge
3d 10h
Merged PRs (30d)
2

Description

Camera: GoPro MAX
Format: Video
Extension: *.360

Issue: Functionality of mapillary_tools working, however there's a limitation due to software provided by GoPro
.360 video editor called GoPro Player used merge video from two lenses into one rectilinear 360° video, when run on Windows platform does not support exporting GPMF binary stream along with rectilinear 360° video (mp4) this option only works for Mac version of GoPro Player.

Adding *.360 file from GoPro Max directly to mapillary_tools only grabs first stream of the video which is front facing camera not the 360° image. If i want to add true 360° image to mapillary instead of basic from front camera.

Suggested solution 1: make mapillary_tools export both front/back images from *.360 file with suffix _front.jpg / _back.jpg so people can batch stitch them together themselves and then upload along with gps data stored in separate .GPX file.

Suggested solution 2: if i generate mapillary_image_description.json from the *.360 file with GPS distance three meters between images then add functionality to use mapillary_image_description.json for sampling the frames from rectilinear *.mp4 file (generated by GoPro Player and has no built in GPMF stream).

Suggested solution3: Allow to source images from mp4 file that does not have GPMF stream, with option of GPS distance three meters and allow to specify original file .360 video as source of GPMF data. Both .360 file and .mp4 file have same timecode its just use .360 file for source of GPMF and use .mp4 file for source of images.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how mapillary_tools reads .360 and rectilinear .mp4 inputs, selects video streams, extracts GPMF GPS data, and samples frames by distance. Compare the three proposed workflows and establish one precise input/output contract, including how matching timecodes and missing GPMF data are handled. Done means the chosen workflow produces true 360 imagery at the requested GPS spacing with usable GPS metadata.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
audio-video-rtc, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.