Thank you for your feedback.
I’m not saying that Mapillary’s double upload check feature isn’t needed.
I said “the implemented check function is harmful”, as the logic of that check function was probably not working even as the logic designer intended.
Over the past year, the operating logic has changed depending on the time of year, but the following symptoms have occurred.
・ After uploading, the time until it is displayed on the Web has become very slow.
・ For a sequence that contains only two identical photos out of 500, there was a time when all 500 photos were eliminated.
・ When I placed some photos within 1m, the important photos were excluded by the double upload check function. (There are many reasons for such an arrangement. I want to be able to read the letters on the signboard, etc.)
And I deliberately uploaded the same data, as shown at the top of this article.
Of course, the coordinates are exactly the same, so the viewer cannot consciously select them.
And for the Mapillary server, there’s extra duplicate data. But that’s it.
I welcome double upload checks that do not malfunction.
However, I hate the various bugs that have occurred as a result of introducing that feature.