Hi everyone! I’m experiencing a strange issue on Mapillary and was wondering if anyone else has encountered it.
While navigating the map, I’ve noticed that many image lines disappear depending on the zoom level. This happens both on desktop (Chrome) and the iOS app. In image 01, all areas show green lines (with images). However, when I change the zoom level (image 02), many lines and photos are missing.
Additionally, I’ve realized that some of my uploads have completely vanished. Is this normal? Could they have been flagged or hidden for some reason? Is there a way to check why specific uploads were removed?
Hello! I manage inbound support requests for Mapillary, and can speak to both of these
This is a known map tile rendering issue in areas with many captures. We’re working on a fix—hang tight!
I’d like to work with you further on this: please submit a ticket to the Mapillary Help Center and share as much detail as you can (roughly how many uploads are missing, when did you notice their deletion, etc.). It is possible that your captures could have been reported by another user. If that was the case, I do think there’s an opportunity to better inform those who’ve had captures removed.
Kind regards,
Marcie
P.S. Congrats on an amazing year of capturing! #13 all-time is an incredible feat.
There are places where, depending on the zoom level, no trail is displayed, not even the most recent one. Even when adjusting the date filter, these trails still don’t appear. So, I understand that the most recent ones are not being shown, as you mentioned. This significantly impacts usability in certain areas.
We are still experiencing the same issue here, and I notice that it occurs in a specific area. The photo below clearly shows the difference within the area marked by the red square.
We use the images for traffic management and signage here at the municipality, so it would be very helpful if this issue could be resolved.
Below are two images that clearly illustrate the case.
@abalys is there anything new to add here, or is this a known issue that we are looking at fixing for the long term (this year) but don’t have an immediate solution for?
We’re yet to figure out the solution to this - perhaps the only clarification that I’d like to make to @jaderbavaresco is that the filters don’t matter. The cap is global and not for a specific combination of filters. All the recent sequences should be available though, so your new uploads should take precedence - let me know if you experience otherwise.
@jaderbavaresco the solution we used while doing a large scale city mapping was to create a routes plan using OSmand based on the streets that needed to be mapped and then marking the streets that had already being mapped in Osman (you can color these differently), without relying on Mapillary to tell us that.
From what @abalys said, if I understood correctly, even though the tiles might not show it, the data in the backend should be there and can be retrieved by API, so whatever you mapped is not lost, it’s just not shown in the UI.
I’ve been following this issue and it seems like there’s still no definitive solution. In our case, we use Mapillary specifically to track changes over time, so it’s common for us to have multiple lines of captures on the same street.
Has there been any progress toward displaying all of this data on the website?
Also, a colleague (@Canaless) mentioned that the images are stored on the server and can be accessed via the API. Could someone point me in the right direction to start learning about this? Is there any recommended interface or tool for visualizing the imagery through the API? I’d appreciate any suggestions!
@jaderbavaresco - we’re working on updated UI to display this more easily, but unfortunately it is not available yet (likely later this year). To learn more about the API see the API Documentation - but this will involve writing code to do what you want.
This looks like a graphics optimization to me, where you do not render all sequences on every zoom level but only on the highest zoom level, which is generally a smart thing to do. @TheWizard’s example shows this very well. Basically the same happens when rendering the road graph. Lower rank roads are dropped from rendering on ever lower zoom levels. I think the issue with sequences becomes glaringly visible when a higher zoom level tile has single sequence captures only (a street or road has been captured only once) and none of its sequences are rendered on the next lower zoom level tile. @abalys@nikola Maybe this is the exception rule to dropping sequences from the next lower zoom level tile you are looking for?
Btw, I have also noticed that the web app makes heavy use of multiple GL rendering contexts and is constantly switching between them. It works … but basically only well on desktop GPUs. Mobile GPU performance tanks horribly from this because most of them do not support hardware context switching. If I am not mistaken the Snapdragon 8 Gen 1 is the first consumer mobile SoC to feature GPU context switching (but I may be wrong). I do not know about the iApple side of things. Anyway, you may want to optimize the web app to use only one rendering context over the whole rendering stack for the entire canvas, at least on mobile.
