Thanks for the nice post. I use the mapillary-tools as well, but inside a docker container. It may be valueable to use a docker container as system changes/updates will never harm your running setup. And the mapillary-tools can never mess up your systems data.

I’ve built an Dockerfile out of what’s on github and added installation of Piexif

RUN pip install –upgrade git+https://github.com/mapillary/Piexif

The MP4 vids from my Gopro are laying in a home-subfolder /home/user/gopro/ and will be bound to the docker container at startup (1736 are the first 4 digits of the docker image). The videos are then available in /goprov inside the container image: sudo docker run -it –mount type=bind,source=/home/user/gopro,target=/goprov 1736 /bin/bash

The videos will be processed into single pictures under /home/usr/gopro/processed with the following call.

mapillary_tools video_process –advanced –import_path /goprov/processed –video_import_path /goprov –geotag_source “gopro_videos” –geotag_source_path /goprov –interpolate_directions –video_sample_interval 0.5 –overwrite_EXIF_gps_tag –use_gps_start_time –user_name MY_MAPILLARY_NAME

After checking the results I’ve upload the images: mapillary_tools upload –import_path /goprov/processed

but you can do it in a single command with: mapillary_tools video_process_and_upload

Thanks for sharing, so I adding my two cents in the hope to help you with some of your annoying points. I also decided to use the GoPro Hero 7 Black with a professional bike frame mount to take Mapillary pics for mapping purposes after my mobile phone crashes on the road several times. To get a good GPS result, I switch on the GoPro (right button) for 30 seconds before starting my mapping tour than I switch it off and start the recording at a later time with the red button. After the tour I copy the MP4 videos to my computer using the USB-C connector on the camera and a USB3 connector on my PC. I have a lot of hassle with that at the beginning. Hint: A lot of connector cables are garbage, but a good cable did the job; the camera must be switched on (right button) during connection. Using Linux (not Apple), but I think the OS is not the problem here.

For processing the images and uploading I use the mapillary tools https://github.com/mapillary/mapillary_tools . The –interpolate_directions option should fix your wrong direction arrows issue. It’s possible to divide the processing and uploading in two steps, so you can sort out images.The bad thing about the mapillary tools is that they are running on an very old python version (2.7), to not mess up my system I’ve put the mapillary tools inside a docker container.

For tour planning I’m using OSMAnd (Android) with mapillary option on. This is more useful than the Mapillary app, because you get a (bike) offline navigation, too,

Up to now I never ran out of memory with a 128GB SD, but a fresh battery is dead after 1-1,5h tour at, so a reserve battery is useful.

Finally, thinking there is a minimal legal risk for you with those setup in germany, because the “freedom of panorama” (§ 59 UrhG) is only applicable to pictures taken without helper tools from a pedestrian perspective. Google Streetview had problems with it, but Mapillary is not that popular yet.Link in german: https://www.spiritlegal.com/de/aktuelles/details/paris-sehen-und-dann-sterben-kleiner-leitfaden-zur-panoramafreiheit-im-deutschen-recht.html#perspektive