OpenStreetMap logo OpenStreetMap

Email icon Bluesky Icon Facebook Icon LinkedIn Icon Mastodon Icon Telegram Icon X Icon

Discussion

Comment from BushmanK on 19 September 2016 at 16:51

First of all, you shouldn’t really care about how it’s rendered on a map since everything is okay with a data. Standard style tries to look good, but it’s still just a technical map, not trying to pretend like it’s a political, topographical or some other specific type of map.

osm.org/relation/136712#map=11/44.9706/-93.2616 - Minneapolis osm.org/relation/136612#map=11/44.9397/-93.1061 - Saint Paul

As you can see, both boundaries have similar border type and administrative level. But what’s different, can you guess? It’s a size (I mean, width).

Comment from Math1985 on 19 September 2016 at 22:06

You can find the relevant code here:

https://github.com/gravitystorm/openstreetmap-carto/blob/master/project.yaml#L1555 https://github.com/gravitystorm/openstreetmap-carto/blob/master/placenames.mss#L57

Names of cities and towns are rendered in the layer placenames-medium. Each place is assigned a score, obtained by multiplying the population by 3 for national capitals, 2 for state capitals, and by 1 for other places. If a city has no population tag, 100000 is used as default.

It seems currently neither of the places have a population tag in the database, but adding both population tags wouldn’t help as Minneapolis seems to be less than twice as big as Saint Paul.

We recently had a big discussion that resulted in the current algorithm, see https://github.com/gravitystorm/openstreetmap-carto/pull/1461.

Comment from maxerickson on 20 September 2016 at 15:18

@BushmanK the boundary relations don’t factor into the label placement or sizing.

I do see population data on the place nodes.

osm.org/node/151538698

osm.org/node/151370941

Log in to leave a comment