The satellite imagery layer visible on Mapillary’s web and mobile apps will be temporarily disabled for maintenance purposes. We aim to introduce a new satellite imagery layer as soon as we can.
If you need satellite imagery layers in the meantime, we recommend viewing your imagery in iD Editor using the Mapillary photo overlay.
Best,
Said
The satellite imagery layer visible on Mapillary’s web and mobile apps will be temporarily disabled for maintenance purposes.
Well, in my understanding this temporary maintenance is long over. 
Anyway, since serving satellite imagery on a website surely demands some considerable fees, it is understandable that finding some suitable replacement is not that easy. However, website visitors may not be obliged to pay license fees. Hence, I would like to suggest that for now, you add a URL option layer so that Mapillary users can at least make use of their favorite imagery provider. While at it, you could also add a projection option as a bonus because many free of charge open data imagery providers (usually government organizations) use proprietary projection parameters (often with aerial imagery) best suited for the geography they cover. However, for now the web default projection EPSG:3857 would be better than nothing.
By the way, what is the update cycle of the “Mapillary streets” layer? Imho it is a bit slow and somehow inconsistent too. Some tiles seem to be more often updated than others. Yet others maybe never.
For all those who need a 
or 
imagery background 
layer with Mapillary data on top in the web browser without having to login; you can use: Rapid Editor
As an added bonus, you get lightning 
fast performance too!
And a distance ruler. The first thing I mostly do in Rapid is to turn Mapillary off. Rapid is too zoomed in and could cause map damage by the innocent incompetent.
You probably mean “turn OpenStreetMap data off”?
Sorry, I use ID from Mapillary. I might try Rapid again, it seems quick. But I turn off the Mapillary layer.
There is too much Mapillary in my region, I use a big Mapillary window for my defibrillators.
And the Mapillary picture tracks are not ready in time.
Sorry, I use ID from Mapillary.
Just to clarify things: iD is not from Mapillary. iD is developed by the OpenStreetMap community at large. Rapid is a fork of iD from Meta with own extensions (which is good because this is open source working at its best enabling rapid innovation). Both projects also exchange code.
@nikola There is also something wrong with the rendering of the OpenStreetMap layer. There seems to be a bi‑linear filter applied.
I think we’re using the same raster tiles so maybe the difference is due to the fact that we’re using MapLibre to render the map.
Anyhow, it looks ugly. 
Can you switch to nearest neighbor filtering? Thank you.
