@h4n5antw: thank you for the feature request about supporting separate GPX - we will add it to the backlog!
@micmin1972 - good news! This should already be working, the video should be sampled at one image every 3 meters, so if you are stopped at a red light Mapillary should not show duplicate images. Have you tried uploading with a recent version of mapillary_tools or the desktop uploader? If you’re still seeing this issue, could you share a link to a recording on mapillary.com?
ok, I will try. Is that 3 meter threshold not to low? My dashcam gps fluctuates sometimes 5-10 meters…
Normally (with manual upload) I just create images every 1 second and skip consecutive images closer than 10 meters (also because of limiting my processing time / storage needs)
Anyway, it looks like my cheap AZDOME GS63H dashcam is supported with this Uploader and I can use it in linux , which is great 
Dear @Boris, edited after 5mins to add point 1b/
1/ would your reply imply that uploading the not-yet-stitched .insv video files is indeed supported? That would be a great incentive to get the Insta360 one RS Twin, as there is fairly fast (20Mb ~ 1¾MB/sec) broadband upload available.
1b/ Clocks tend to diverge, the Hero9 runs 42 seconds/week fast, in addition won’t set clock before every sequence - hence please consider two adjustment settings : one comparing the camera clock via photos with the GPS to determine time offset, the other specifying how many seconds the camera clock gains (of looses) per week or per day.
2/ regarding ‘recent version’:of Command Line Uploader : took quite some time to install and set the python command line uploader up, wouldn’t really know how to update;
also ‘fear’ that a new command line will need to be composed - the current .bat file was written by a friend - my computer competence is strictly Windows’ ‘Point&Click’.
Met als immer vriendelijke groet,
Boris, just found out that using the desktop tool the generated images have wrong aspect ratio…
The GS63H dashcam records 4k with 2880x2160 pixels (and re-stretches back out to 3840x2160 automatically on playback using most players).
So generated images from video also need a resize correction for dashcams using 2880x2160 compressed format 
1b & 2. We should be taking GPS time now, can you try uploading with the latest desktop uploader or mapillary_tools to see if this is still an issue for you? Generally I would recommend the desktop uploader for simple install and drag & drop support: Desktop Uploader
@micmin1972 - could you provide a raw sample video for us for that camera using Google Drive or another method?
sure, I send you message.
Super, thanks so much, I received it and can replicate the issue. I’m not entirely sure on the complexity of the fix, but we’ve added it to the backlog to take a look! Does the camera have any settings to use non-stretched capture as a temporary workaround?
How is development on the separate GPX going? I think I can only upload my Insta 360 X3 videos once that feature becomes supported.
hi, saw your recent spreadsheet. You can correct it a bit : GS63H dashcam upload works fine (drag & drop) for all other resolutions!
Its just that specific 4k format that needs additional stretching and can therefor not use the uploader yet.
Do you have these instructions written up anywhere?
Thanks for the feedback @micmin1972 - we’re updated the spreadsheet with your input. Do you have a mapillary.com link with examples from GS63H by chance?
New beta version (4.1.0) is ready for testing!
This version brings support for uploading videos with separate GPX files. It will pick up GPX files that are in the folder with the video and have the same file name. You will be able to see the route on the map before upload.
You can download the latest beta version for Windows , Mac & Linux .
Thanks for testing and sharing your feedback!
yes. correct result of desktop uploader for resolution 1920x1080 for example here Mapillary
Super, thanks @micmin1972 - I’ve added your example link to the Mapillary Video Support spreadsheet.
Thank you, found the Insta360 money back guarantee isn’t at the level a consumer in the EU would expect, thus not going for that brand.
I just uploaded some files (Linux Mint). The app (mapillary-uploader-4.1.9-beta.AppImage) complains of no GPS inf. available. If I open same files with Azdome windows software GPS infs. are available.
Any suggestion?
Can you try it in the latest version (4.3.0) from Desktop Uploader ? If it doesn’t work, please send us the video so we can investigate. Thanks!
Often the Azdome does not find gps first minute of recording. And as I use 5-minute video batches, the first file of a trip is mostly not uploaded because of missing gps data also…
(As a workaround, I start driving after waiting gps signal shows green color, then start new recording from that moment…)