- transalated as Dermaptera (which incidentally are called skorki in Polish)
- shown at totally inappropriate low zoom level because of the previous point (presumably that Wikipedia article was more linked to or had much more languages, which could be used to decide importance rank)
Consider all the various *name* tags in OSM and how they are (mis-)used to please specific renderers and geocoders. E.g. do you apply (semi-)standard abbreviations of street names or do you write names in full so that they fill the map? It's fuzzy in OSM: https://wiki.openstreetmap.org/wiki/Abbreviations
(I'm all for everyone using the map style that works the best for them - after all, it's open data and open source.)
Seems the search box is tripping on that (not considering places on North 14th Street for a search like N 14th St).
Hence, it's complicated and not "moronic" e.g. to make use of Wikidata for labels and to use external datasets to improve geocoding.
I'm not really arguing with you, just questioned the 'fill the map' characterization and pointed out the more fundamental motivation.
Meaning here in Singapore there are a lot of local bus interchanges that get labels like "Bedok International".
Names don't always have exonyms.
After all, you don't expect the literal label 'New York City' for the city and 'New York State' for the US state on a map; just 'New York' for both, with styling and size indicating which is which. Any map which does want to render these names with their classification can do so by adding '(city)' or '(state)' to the label if they want to. It just shouldn't be part of the name in the data source.
Map labels are complicated, so leave that complexity to a project which deals with map data; i.e., OpenStreetMap.
I agree with you.
Also note that you can chose your map style.
Municipality of Bled... in the middle of the forrest... who the hell searches for "Municipality of bled" and wants to be pointed to a forrest? But somehow, it's probably the middle of the polygon of the actual municipality, and the label is put there and visible even when very zoomed out (along with other municipalities,... but not city names, like actual Bled - https://osmapp.org/#8.33/46.3350/14.1244 )
Another criticism I would make is that different levels are displayed the same, for example in France I can see both "Pas-de-Calais" and "Hauts-de-France" in the same style, at the same time, although one is part of the other.
And for some reason, the province of Luxembourg becomes "District Luxemburg", which seems to suggest it's Dutch, but the Dutch name would be "Provincie Luxemburg".
Luxembourg itself (the country) does have districts, but this is the Belgian province, not a district of the country of Luxembourg.
I think Switzerland has the same kind of problem but with German being used for most names.
…and sure enough. This app uses one of those moronic map styles which doesn't just use the names for places in the OpenStreetMap database, but also draws them for Wikidata. Great. Those often suck for use on a map, because they tend to include stuff like 'Province X' for a province named 'X', and because the translations stored in Wikidata are often archaic or plain wrong.
The argument the developers who use the wikidata IDs stored in many place name objects to draw in 'missing' translations is that this is surely better than just showing the local name, but this completely misses that in OpenStreetMap name data is already really quite accurate, whereas Wikidata…
As an OpenStreetMap contributor I am not interested in having to keep two databases up-to-date to get names (exonyms and endonyms) to show up correctly. I know a number of developers are pushing this dumb solution, but it is hurting the project more than it is helping.