I am about finished testing the sampling and processing of imagery data with mapillary_tools and have tested an small upload of pre-processed data.
Now I’ve got some questions to clarify.
- Front facing dashcam Blackvue DR650S-1CH (with built-in gps logger)
- Rear facing BlueSkySea B1W daschcam (without built-in gps logger)
I have prepared a set of frames, 2 fps from each camera, aligned between one another.
Gps log from the frontcam was used to geotag both front and rear camera imagery.
Rearcam imagery was processed with --offset_angle 180
As a result for every point I have 2 images, 1 front +1 rear, both having IDENTICAL EXIF Datetimestamp and coordinates, only diference is the angle (rear is offset by 180)
I have uploaded a sample set of 15 frames front + 15 frames rear
My thought was that Mapillary will automatically stitch them together and user will be able to “switch” between the front and rear while following the sequence and will also be able to see that the points are ‘two-directional’ (compass with be showing 2 sectors).
But as a result I’ve got 2 separate sequences:
now the questions
when user clicks on one of the points on the map - he defaults to ‘rear’ sequence, meaning that he can’t see front unless he will ‘rotate’ using a navigation arrow (not always present btw).
What should I do to make front facing sequence showing as a default one?
I only suspect that images uploaded later override, so, maybe making rear queued first, followed by front will help. But this is odd…
Something weird happens with navigation arrows in the rear sequence. Angles (compass) in the images are set correctly as you could see. But, for some reason, after processing, mapillary has altered movement direction somehow and it is not matching the reality. So, the front/backward navigation arrows are not aligned with the road/driving direction.
I guess the issue is related with ‘North’ not being aligned by mapillary properly (it difers between front and rear by approx. 60 degrees, not 180 as it should…
Having said the above, does it really make any sense for spending extra effort on two-directional processing?