I’ve been wondering about the heading bug that’s been causing iOS app captures when travelling above walking speed to have a 90 degree heading offset for months now. The Mapillary algorithm figures out the correct direction, and a separate corrected FOV cone is shown while viewing an affected image after processing.
So is there any reason that the green cones on the map can’t all show the true heading instead of whatever the capture-device’s sensors erroneously showed? A couple of years ago, another bug had every direction flipped 180 degrees. Working with imagery on OpenStreetMap would be easier if the true heading was shown automatically.