3-4 days ago I used the tools (0.14.7) to upload about half of a 30GByte 43,000 image set, but there hasn’t been any in progress visible on the usual GUI interface. This is a new camera experiment, but I don’t see anything wrong with the EXIF. I only just completed my other three usual camera sets a day before.
Before I raise this with support I wanted to check that those using the command line tool were having no problems. Like I mentioned, NOTHING has appeared on the GUI despite a successful debug log. The only real difference is that the camera angle is 200 degrees, pointing straight back from the vehicle and a little left.
Thanks for reporting this @bob3bob3, I can see some sequences from 28th of February onwards on your feed. It looks like they should be published by now
The ones you are seeing are likely the other (non test) cameras. They have appeared okay on the GUI.
I have made a few passes at this, the last line of the logs looks quite good;
21:00:09.415 - DEBUG - HTTP POST https://graph.mapillary.com/finish_upload JSON={“file_handle”: “3:dXVpZF9iNzFiN2Y2OWViMGE0OTVmYWIxZWJhZjFkMjVhMmM3ZC5qc29u::ARZO5Qn9NeS4ohky_tu14TUtQ_s03KOL-t-sTYpxQjRcmuEQR7EVIv6aAdVW4GMPcW44wI_nqMBX0h7vN0cSgHn_ukNTOwgYoDVPxpo9DpU82Q:e:1772791209:ARZ7PM6MlI37Crn1YYo”, “file_type”: "mly_bundle_manifest…(2 chars truncated) TIMEOUT=60
21:00:11.092 - DEBUG - HTTP 200 OK (1676 ms): {“cluster_id”: “885077947698598”}
21:00:11.098 - DEBUG - Writing upload history: /home/b/.local/share/mapillary_tools/upload_history/48/17666a5f80bb60342db3c36705203a.json
21:00:12.276 - INFO - ==> Upload summary
21:00:12.276 - INFO - 14 sequences uploaded
21:00:12.283 - INFO - 7.1 GB read in total
21:00:12.283 - INFO - 7.1 GB uploaded
21:00:12.283 - INFO - 2812.478 seconds upload time
There were no ERRORS and only 2 WARNS associated with a duplicate (distance) image. Nothing untoward, so I was just waiting for them to appear on the GUI
Nothing unusual in the bash processing script;
CURRDATENT=20260228NT
/home/b/Thing/Mapillary/lapp600/mapillary_tools-0.14.7-linux-x86_64 --verbose process “/mybook/mupload/$CURRDATENT”
–offset_angle 200
–overwrite_all_EXIF_tags
–device_make RESPONSE
–device_model QV3878
–duplicate_angle 90
–duplicate_distance 0.25
–cutoff_distance 50
–cutoff_time 180
–geotag_source exif 2>&1 | tee -a /mybook/mupload/$CURRDATENT-proc-upload-lapp600-wx.log
/home/b/Thing/Mapillary/lapp600/mapillary_tools-0.14.7-linux-x86_64 --verbose upload “/mybook/mupload/$CURRDATENT”
–user_name bob3bob3 2>&1 | tee -a /mybook/mupload/$CURRDATENT-proc-upload-lapp600-wx.log
I did however deliberately kill and restart the upload job 3-4 times.
Special because I extracted only key frames and the source had good date/time, but wrong Lat/Lon (firmware?), so I used my other GPS unit. The source was also progressive/interlaced, so had to use -vf “select=eq(pict_type,I),yadif” on the ffmpeg line. All geotagging etc was done with exiftool. The result was a 3FPS stream which is about right for country roads.
To me they have appeared to vanish.. I assume that process in progress still appear at the top of the list? The above upload was for images 1-2 days before current so would eventually be laborious to scroll too, but I was checking every few hours. No green tracks as yet.
Okay so the earlier take of the day is now appearing on the GUI, good news. I have however found a red flag fail on the sequence scroll, timed 28Feb 1:47PM. It’s easier to find them now as they are often >800 images per sequence. Strange I didn’t see them before.
I’ll continue the upload and see if the Failed sequence gets “replaced”
