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

Names of Nodes Tagged as Islands and Airports Rendered At Much Too Low A Zoom Level #1835

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


Copy link

Reporter: ezekielf[at]
[Submitted to the original trac issue database at 6.01am, Monday, 18th May 2009]

In the area of Vermont, USA linked to below you will see that the map is full of island and airport names. These are all quite small islands and airports which should not show up at zoom 10. The place name of the largest town in this area (Burlington) is not being rendered at zoom 10. I presume this is due to the crowding of these island and airport names. These islands and airports were all created through the recent GNIS placenames import.

Current Rendering Example:

Copy link

Author: ezekielf[at]
[Added to the original trac issue at 12.23am, Friday, 29th May 2009]

A more extreme example off the coast of Maine:

Copy link

Author: Ldp
[Added to the original trac issue at 12.23am, Wednesday, 19th August 2009]

When looking at nodes, such as the extreme Maine coast island example, it's impossible to know whether the island is big or just a glorified boulder sticking out of the water, making it very hard to make good rendering decisions.

The place=island wiki entry suggests it is also used on polygons. Having place=island on a polygon (closed way, area=yes) would make intelligent rendering decisions possible.

Place name rendering is being looked at, so it takes more precedence. Airport rendering could be looked at as well, but how to discern the major airports from small airstrips?

Copy link

Author: imrehg[at]
[Added to the original trac issue at 4.33am, Tuesday, 25th August 2009]

I also feel that zoom levels of 10 and less are not good enough for the airport signs.

I'm working on [ Taiwan Taoyuan International Airport] and the behaviour of the aeroway=aerodome node currently is:[[BR]]
Zoom level:[[BR]]
... - 9 : no name or sign[[BR]]
10 : airport name and sign[[BR]]
11 - 12 : name only[[BR]]
13: no name or sign[[BR]]
14 - ... : name (rendered differently)

I think Zoom 10 covers such a huge area that it is not practically used for searching for things on the map. It would be more useful if the airport sign was rendered down at least to 12 or 13.

One possible objection is that the sign shouldn't obscure any other map features, but on those zoom levels there's not much resolution anyway, and one just want to orientate themselves...

Copy link

Author: Ldp
[Added to the original trac issue at 10.58pm, Wednesday, 16th March 2011]

This issue has appeared on the tagging ML a few times now. No solution has been agreed upon. In the absence of more descriptive tagging, we cannot do anything more than we're currently doing in the renderer.

Please reopen if or when the data schema has been amended to take importance into consideration.

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

No branches or pull requests

1 participant