Stuck Sequences
I am still fighting with yellow sequences stuck in “Map Data Processing”. Unfortunately, I have not figured out any true cause or effective workaround for this issue. What I have observed though is the fact that it is almost certain for a sequence to get stuck in processing when it has an optical or GPS track loop. Limiting sequence image count does not help evidently either. So far, the only mitigation against this issue have been repeated uploads. However, this strategy is cumbersome, time consuming, and a gamble. Not to mention that it is costly for both contributors and Mapillary. I really wish and hope this issue to finally get resolved for good.
Dynamic Reconstruction Bundle Sizes
@paulinus Although I do not know whether these subjects are connected, I have observed that all sequences are split into exactly 75 (or was it 50?) image count bundles for reconstruction. Have you thought about per sequence dynamic reconstruction bundle sizes based on image resolution and average GPS spacing (initial baseline)? Or, are dynamic bundle sizes infeasible at Mapillary’s scale of reconstruction (or maybe I am totally confused)? Thank you.
Why Arbitrary Sequence Grouping is Important
Some contributors want to manage a more or less curated dataset. The current feed, filters, and bbox based queries work just okay for now. Contributors want to find, access, and organize their imagery efficiently. As the platform and user contributions grow, the needs for clear data structures and organizing tools grow too. See also A timeline approach for Mapillary road imagery.