If Mapillary image is still being processed, street level panel shows stale image

[1ec5]

This image is currently being processed by Mapillary, so if you click on it right around here, you get a thumbnail image (which I think is for the correct image) with oversized Mapillary branding overlays:

However, if you’ve already previously viewed a Mapillary image that has been processed, then that image shows up in the street level panel along with the current image’s attribution. As you flip through the images along the in-processing track, the street panel appears to be stuck.

[1ec5]

The image that’s in processing hasn’t been joined up into a track yet, as you can see on the map canvas:

The images going westbound are already processed; the images going eastbound have not been processed and exhibit this bug.

[peterneubauer]

So, the creation of the vector tiles for the sequences is sometimes lagging as it is asynchronous and depends on a lot of other processing going through. We are working on a status page exhibiting the processing time etc, coming soon. Eventually, this data will catch up as the system is catching up to the load right now.

[1ec5]

Thanks @peterneubauer, I appreciate that there’s a significant amount of processing going on. Is there anything iD can do to make the images’ status clear? Currently you can only tell that the image is processing if you know to click on the mapillary.com link.

[bhousel]

Following some suggestions from @oscarlorentzon, this should avoid the problem where the viewer starts out bound to an imageKey that it can't actually move to. Now we initialize the viewer with a null key, and issue moveToKey immediately. This also adds some basic exception handling to moveToKey, which actually returns a promise and might fail. In that case, we just quietly log a message to the console.