mapillary / mapillary/mapillary_tools
"GPS Image Direction" is set to an incorrect value
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 315
- Forks
- 145
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 2
Description
Basic information
- Release version:
0.5.3 - System:
Linux - Capture Device:
Action Camera|GoPro HERO3|Garmin Logger
Steps to reproduce behavior
- 0.5 seconds time lapse shooting with the GoPro HERO3 (GoPro HERO3 doesn't have a built-in GPS).
- Record the location with the Garmin GPS logger.
- Add "GPS Image Direction" to the Exif with the following command.
mapillary_tools process_and_upload --advanced --user_name kudarisenmon --geotag_source "gpx" --local_time --interpolate_directions --overwrite_EXIF_direction_tag --overwrite_EXIF_gps_tag --geotag_source_path 2020-02-11.gpx --import_path /media/DCIM
Expected behavior
All photos will have the correct Exif "GPS Image Direction" tag embedded in them
As a result, the value of "MAPCompassHeading" in "Image Description" is also correct.
Actual behavior
One out of two, "GPS Image Direction" is set to an incorrect value (0).
"MAPCompassHeading" in "Image Description" is not correct.
Corresponding data
One in two isn't right because the time lapse is 0.5 seconds.
- sample Sequence key
YEAlqO5djLS5a9ZH31H1sg
https://www.mapillary.com/map/im/waM3T8xr0jMpl6NMMidO8A
- correct direction

- incorect direction

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the process_and_upload command and reproduce the issue using the GoPro HERO3 images, Garmin GPX file 2020-02-11.gpx, and the listed interpolation options. Compare consecutive 0.5-second time-lapse images and verify that GPS Image Direction and MAPCompassHeading are populated with the correct direction rather than 0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100