Opened 10 years ago

Closed 5 years ago

#2090 closed defect (duplicate)

[placenames] Place nodes and polygons rendered differently

Reported by: augustus.kling@… Owned by: mapnik-team@…
Priority: major Milestone:
Component: mapnik Version:
Keywords: hamlet, font rendering, place polygon, place node Cc: fiveisalive

Description

Names of places should be rendered using the same visual style disregarding being tagged on a node or a polygon.

Example region: http://www.openstreetmap.org/?lat=47.85085&lon=9.92267&zoom=16&layers=B000FTT[[BR]] Node Staighaus: http://www.openstreetmap.org/browse/node/380983273[[BR]] Polygon Hünlishofen: http://www.openstreetmap.org/browse/way/33473121[[BR]] Both objects are tagged as place=hamlet and name=*. There are no other tags.

Current rendering: Hünlishofen is rendered in a small black font. Staighaus is rendered using a bigger gray font.
Expected rendering: Using the same font type for both objects. I propose the bigger gray font since it's more similar to village or town name rendering.

The description above applies to zoom levels 16 and higher.
Zoom=15: Both objects are rendered with black font.
Zoom=14: Staighaus is rendered in black, Hünlishofen isn't rendered (enough space is available).
Zoom=13 or smaller: No object is rendered (equals expected rendering for this zoom levels)

Change History (9)

comment:1 Changed 10 years ago by Ldp

Owner: changed from steve8@… to mapnik-team@…

comment:2 Changed 10 years ago by fiveisalive

Cc: fiveisalive added

comment:3 Changed 9 years ago by siberiano

This issue affects me too. I've faced this issue when tried to draw a local place (which is a toponym with a clear boundary, but not any administrative unit).

The issue was that there's a trade-off between accuracy and visibility: 1) a node is rendered in big font at scale >=13, which is wide enough. 2) a polygon is precise, but its title is rendered in small font and only from scale 15.

Toponyms are used by locals, but a non-local won't find it by himself. The map is supposed for finding, not for locals to admire their places, right?

Right now I can put nodes for the toponyms and forget this, but it's better to draw boundaries, so that if 2 places are near and confused, it were clear when looking at the map.

comment:4 Changed 9 years ago by siberiano

to be clear: a polygon with tag place IMO should be drawn as a node is drawn now, in big font and up to scale 13.

comment:5 in reply to:  4 Changed 8 years ago by spod

Also reported in #3705

comment:6 Changed 7 years ago by drnoble

This also appear to affect place=isolated_dweling, which is rendered on nodes, but not areas.

Expected outcome, both would be rendered (and be the same) whether a node or area is used.

Current situation: Rendered as node example: http://www.openstreetmap.org/?lat=57.29931&lon=-4.29038&zoom=17&layers=M Not rendered on areas example: http://www.openstreetmap.org/?lat=57.338485&lon=-4.21507&zoom=18&layers=M

see also https://trac.openstreetmap.org/ticket/3181 - request to render place=isolated_dweling

This part is not a big issue, but would be great if someone were able to fix it.

comment:7 Changed 5 years ago by math1985

Summary: Place nodes and polygons rendered differently[placenames] Place nodes and polygons rendered differently

comment:9 Changed 5 years ago by math1985

Resolution: duplicate
Status: newclosed

This is now also being discussed on Github:

https://github.com/gravitystorm/openstreetmap-carto/issues/103

Therefore, I will close the issue here.

Note: See TracTickets for help on using tickets.