mapillary / mapillary/mapillary_tools

Add support for VIOFO A229 Dashcam

Open
#685 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I am unable to convert and upload videos from a VIOFO A229 Dashcam which records geotagged video. It throws the error "failed due to MapillaryGeoTaggingError". Please consider adding support since VIOFO dashcams are a very popular choice.

Basic information
  • Release version: 0.11.2
  • System: Linux
  • Capture Device: VIOFO A229 Dashcam
Steps to reproduce behavior
  1. Record GPS-tagged video with VIOFO A229 Dashcam
  2. Run the script `mapillary_tools video_process toconvert --video_sample_distance -1 --video_sample_interval
Expected behavior

Geo-tagged images produced successfully

Actual behavior

Error:

2024-10-03 13:08:19,624 - INFO    - Check the description file for details: toconvert/mapillary_sampled_video_frames/mapillary_image_description.json
2024-10-03 13:08:19,624 - INFO    -       13 image(s) read in total
2024-10-03 13:08:19,624 - ERROR   -            13 image(s) failed due to MapillaryGeoTaggingError
2024-10-03 13:08:19,624 - ERROR   - MapillaryProcessError: Failed to process 13 files. To skip these errors, specify --skip_process_errors

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 reproducing the reported failure with mapillary_tools video_process and inspect toconvert/mapillary_sampled_video_frames/mapillary_image_description.json. Compare the VIOFO A229 output with the processing expectations; done means GPS-tagged images are produced without MapillaryGeoTaggingError.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.