If you go to mapillary.com and set the basemap to “Mapillary light”, the name of the POI will be displayed.
If you go to mapillary.com and set the basemap to “Openstreetmap”, the name of the POI is not displayed.
In openstreetmap.org, the name of the POI is not displayed.
Where do you get the names of POIs that are not registered in openstreetmap?
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.
Thanks for your reply.
I never knew that the carto rendering engine is used and that many tags are not displayed.
However, the question is valid. Mapillary shows POIs which are not available in the OpenStreetMap database. Where do they come from?
Maybe Overture Maps or Map libre.
Touch the info mark on the maps of mapillary and select “地図データ規約”.
I ask again: where do you get map data from for mapillary?
This is the most important Tomei Expressway in Japan. mapillary light does not render the Tomei Expressway. It is rendered in Openstreet map.
It appears that there is a serious problem with map data in mapillary.
The simple answer is that the data for every map layer comes from different sources, except “OpenStreetMap carto”.
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.
I like to have a look, but you give no link.
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.
@nikola - POIs on the mapillary maps come from Overture now, is that correct?
Yes, the maps (“Mapillary light” and “Mapillary dark”) are built using data from Overture. More information here: https://overturemaps.org/
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.
@GITNE - thank you for sharing your thoughts as always. BTW - Meta (and Mapillary through Meta) is a big supporter of OpenStreetMap. We just announced a $178K EUR contribution to OSM to support community and core infrastructure: Meta Contributes to 178K EUR to OpenStreetMap | OpenStreetMap Blog
Thank you for sharing the blog post and I am happy that OpenStreetMap can count on many high profile sponsors, including Meta. 
And, I also understand that for certain use cases companies may need or may want to combine data from commercial sources with OpenStreetMap data, where Overture Maps comes in and tries to deliver a framework and tools for this. For example, I sincerely understand that some people may need something like GERS (which imho just cannot work as a concept because of philosophical issues down the line, like identity dynamics and evolution, associative versus tree structure memory organization, etc. Mapbox has tried to do something similar with exactly the same issues. But, this is a topic of its own). What makes me worried is that over time Overture Maps may become the go to place for commercial users (and thus also end users) and OpenStreetMap be sidelined. Where collecting and sharing data together in a community effort into a common database may be replaced with combining proprietary data only, where already OpenStreetMap’s road network (currently) serves as only one of many data layers. Therefore, Overture Maps has the potential or danger to become not an open data platform but a marketplace for combining commercial data only, which is vastly different from OpenStreetMap’s initial mission. Sure, no organization, including Overture Maps, is required to share the same mission as OpenStreetMap and everybody is free to choose their own goals but every OpenStreetMap data user should consider contributing back to OpenStreetMap (this is at least the idea behind the ODbL), especially commercial users. So honestly, I fail to see any incentive for Overture Map data users, consumers, and customers to contribute back to OpenStreetMap, or any other open shared database for that matter. But, maybe I am missing something?
However, what is really bothers me about Overture Maps is their self‑concept. This becomes particularly apparent in their approach on standards. In other words, their incredibly arrogant claim that they are single‑handedly entitled to declare standards. Standards are the product of a consensus or a vote after debates over drafts and proposals, not a decree.
A friend in need is a friend indeed.