Add support for VIOFO A229 Dashcam

Open

#685 opened on Oct 3, 2024 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 30/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: python
Domain: cli

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.

Description

feature

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

Record GPS-tagged video with VIOFO A229 Dashcam
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

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

Contributor guide

Open the contributing 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.

Similar issues

[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
[pcied] Honour PCIE_DETACH_INFO on platforms that are not smartswitches Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

sonic-net/sonic-platform-daemons#900 · Opened Sep 21, 2026
MCP client has no httpx timeout, so the event stream fails after 5 seconds Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Azure/azure-functions-agents-runtime#228 · Opened Sep 21, 2026
feat(mcp): friendlier error when `run_cloud_sync` is called on a disabled connection Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

airbytehq/PyAirbyte#1205 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026

More Python issues