I’m excited about the idea of getting Fortuna’s roads and trails entirely covered with Mapillary. It makes editing OSM much easier for me, being able to look back on any bit of road I’ve driven on. I hope that the machine learning Mapillary does can one day make OSM mapping much, much quicker.
My main frustration with Mapillary (Android app) is that it has a poor sense for where the camera is pointing. I tell it my camera points forward, but 1/5 of the pictures are like, “are you sure you weren’t pointing 150 degrees backward.”
No. Normalize sequence.
Discussion
Comment from Strubbl on 30 January 2021 at 22:10
Nice read. Thanks for sharing. Oh i see. There are a lot of building to draw in your area. Keep on having fun.
Comment from JesseAKARaccoon on 1 February 2021 at 07:26
Strubbl – Thank you, I will! >95% of the buildings there now were drawn by me, but it looks like I still have work to do. XD
Comment from vorpalblade on 1 February 2021 at 14:41
IIRC, the Mapillary app may not use the actual compass direction, instead using the direction of travel (to be fair, many devices’ compass is… horrible, to say the least). I think you can change that in settings somewhere, but I could be wrong. Its been a little while since I used their application.
So, if you (a) go backward, or (b) are at a traffic light, and the GPS jumps around, you may have pictures pointed in the wrong direction.
Comment from JesseAKARaccoon on 1 February 2021 at 23:10
vorpalblade – Thanks! Yeah, I know that stuff. I already have the camera set to forward, not compass – so you’d think that each image would point to the next image in the series by default. But nope, some photos still point off in a random directions. I suspect it’s because some perceived mismatch in the “computer vision” mapillary uses the create a 3D model of everything.
After getting a bit more experience, I think that with longer and straighter trips, the proportion of weird-direction pictures can go down to 1-ish percent, since the computer vision has more to work with.