I’m not sure if it’s the case here but the default OSM rendering, carto, does not display many tag details even if they are in OSM. So it may just be the case that the Mapillary rendering is displaying more details but the underlying data is the same.
The simple answer is that the data for every map layer comes from different sources, except “OpenStreetMap carto”.
“Mapillary light” and “Mapillary dark” comes from Mapbox using an amalgamation of different sources, including the OpenStreetMap database, Mapbox “Who is on First?” address and POI database1, and other sources. Mapbox customers — in this case Mapillary — can create custom map layer style sheets and declare sources for their vector tile maps. Hence, they can decide to render POIs from for example either OpenStreetMap or Mapbox’ geocoded database. One Mapbox default street style sheet renders a nice combination of OpenStreetMap and Mapbox POIs.
“OpenStreetMap carto” is sourced from the OpenStreetMap database only.
“Esri navigation” is also an amalgamation of sources from esri.
Do not worry, there is no problem. Most of the time the Mapbox vector tile map layers just have to catch up with the OpenStreetMap database or other databases they source data from. By design, Mapbox uses an impression count (basically download and search count) heuristic to determine which map tiles to update first and which to update later. Generally, the Mapbox system is tuned so that the entire globe of map layer tiles gets updated about every month but customers can pay for shorter update intervals globally or for select areas only. There is no need for Mapillary to pay for a short update interval because the Mapillary product is not time critical in this context.
The most probable cause for why you do not see that particular segment of the expressway in the “Mapillary light” map layer is because some OpenStreetMap contributor has edited or deleted this segment some time ago. Just give it some time and it will return.
1Imho “Who is on First?” is conceptually seriously flawed but this is a discussion for another topic.
If you like, you can mess around with Mapbox POIs and addresses here: https://labs.mapbox.com/contribute
It is a horribly unmaintained mess…
OpenStreetMap is not perfect either but far better maintained.
Yes, the maps (“Mapillary light” and “Mapillary dark”) are built using data from Overture.
This may be so but POIs, address data, and search seem to come from Mapbox’ geocoded database because the POIs in the Overture Maps Explorer (Beta) are very different from what we can see on the Mapillary map layers but basically match those from Mapbox. Unfortunately, you cannot search for POIs and addresses in the Overture Maps Explorer (yet?). You would not have a demo link to the Overture Maps database, would you?
By the way, the Overture Maps Foundation can only be labeled as big tech’s next stroke of madness to rule them all and is definitely a step backwards in collaborative mapping. At least half of Mapillary’s success can be solely attributed to the fact that it was built to support the evolution of OpenStreetMap and not some corporate consortium. I, like probably most Mapillary contributors, contribute because of OpenStreetMap (effectively the ODbL) and not for the gain of a corporate gated data stash that does not give back to the community effort. Overture Maps basically intends to reinvent OpenStreetMap but with every aspect exclusively corporate governed, from data types, specifications, data gating (affectionately called QA) to licensing. @boris Be very wary going down the path of the Overture Maps Foundation because it is a dead end.