-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labeling priority #3278
Comments
Yes. On z7, the label for Нижний Новгород (Nizhniy Novgorod) is hidden by the label for Нижегородская область (Nizhny Novgorod Oblast). The former is a (The perfect solution might be to shift slightly the label for the boundary relation, but that’s technically not so easy…) |
Thank you for your reply. I guess that label shifting is not a big algorithmic problem nowadays but unfortunately I'm not familiar enough with Carto's rendering process to understand technical difficulties. As for relative importance of federal state labels and big city labels, maybe ideally it should depends on the country, for example, on Google maps there no federal state labels in Russia and Kazakhstan by default, while in China and the US federal state labels have higher priority than cities. |
In general, we try to use the same algorithm all over the world to create a consistent feeling of this rendering style, so likely we won’t treat Russia different from China. In #1391 some there is yet some discussions about using “grid” placement to solve this problem. Therefor, I’ll close this issue as duplicate. Thanks for your report! Discussion can be continues in #1391 |
On the screenshot taken at zoom level 8 you can see Нижний Новгород(Nizhniy Novgorod) and Дзержинск(Dzerzhinsk) cities, but on the level 7 Nizhiny Novgorod disappears, though Dzerzhinsk, which is in fact several times smaller city, remains on the map. Is there any reason for that?
Links and screenshots illustrating the problem
https://www.openstreetmap.org/#map=8/56.263/43.863
https://www.openstreetmap.org/#map=7/56.263/43.863
The text was updated successfully, but these errors were encountered: