yep,
I have realized that 1st step would be anyway converting “gps” flies into standard nmea and then to gps (gpsbabel).
I think I have managed to do it.
However, I still need to run ‘sample_video’ and ‘process’ separately, while ‘video_process’ does not work for me for some reason.
So:
- convert .gps to nmea (using cat/egrep on Unix or Notepad++ regex on Windows)
- (optional) convert nmea to gpx with gpsbabel. But nmea should work as well
- mapillary_tools sample_video --import_path “path_to_images_folder” --video_import_path “path_to_video_folder” --video_sample_interval 0.5 --advanced
this will create images, but still no exif, as legacy dashcams to not support capture time meta - mapillary_tools process --advanced --import_path “path_to_images” --user_name “mapillary_username” --geotag_source “gpx” --geotag_source_path “path_to_gpx_file” --use_gps_start_time --interpolate_directions --overwrite_all_EXIF_tags --duplicate_distance 0.1
*(optional) you can add --offset_time option to get a better sync between video and gps data
To make life easier, it is worth joining video clips and gps file together before processing, otherwise the above steps would be required for every 5 min clip…
Also, legacy web uploader could be used once gps files are converted into gpx.