Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Confusing display: Name of a major city gets suppressed by name of smaller city #696

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: Sternenfaenger77[at]googlemail.com
[Submitted to the original trac issue database at 2.29pm, Monday, 18th February 2008]

In the following hyperlink you can see the name of the city "Fallersleben" and next to it (more to the right) is a city "Wolfsburg" which city name is not displayed:

http://www.openstreetmap.org/?lat=52.428&lon=10.844&zoom=10&layers=B0FT

This is confusing because Wolfsburg is a much bigger city than Fallersleben. Fallersleben is only a part of Wolfsburg. As I am still quiet new to the community I dont know if it is a bug in the renderer or if it is an error in the map's design (user error). Please modify this ticket's state occordingly.
You can see "Wolfsburg" displayed correctly when you zoom in a bit more.

Kind regards,
Mark

@openstreetmap-trac
Copy link
Author

Author: rjtehpwn[at]gmail.com
[Added to the original trac issue at 7.37pm, Monday, 18th February 2008]

Layer is Mapnik, not osmarender. Osmarender does it right.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 9.45pm, Monday, 18th February 2008]

This happens when the two names would collide - mapnik has a collision detector that removes one of them to avoid the collision.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 9.51pm, Monday, 18th February 2008]

The conclusion seems to be that we need to z order planet_osm_point so that mapnik sees the most important features first, then they will win the collision detection argument.

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 9.55pm, Tuesday, 30th June 2009]

Rendering seems to have been fixed in the year since the ticket was opened. At least city->town->suburb->village->hamlet are now rendered in order, so larger (by tag, not by population) places are rendered first.

Please reopen if there are other bad examples out there, that have obviously different place=* tagging.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant