Opened 8 years ago

Closed 4 years ago

#3298 closed defect (duplicate)

[amenity-points] Don't render guideposts as tourist information points

Reported by: augustus.kling@… Owned by: mapnik-team@…
Priority: major Milestone:
Component: mapnik Version:
Keywords: ambiguity, tourism, information, guidepost, guide post, sign post Cc: augustus.kling@…

Description

The Mapnik layer on OSM currently shows the letter “i” for tourist information points (tagged by tourism=information). This is the correct behavior.

However if nodes are tagged by tourism=information and information=guidepost those are also rendered as “i”. Because the icon is usually used for information offices the rendering of guidepost is highly ambiguous and distracting.

Expected behavior (preferred): Render the guideposts with an own icon, like the Osmarender layer does.

Expected behavior (alternative): Don't render information points at all unless also tagged information=office.

Data usage according to taginfo.openstreetmap.de: tourism=information is used 68765 times. information=guidepost is used 39196 times (61.3% of usages of information key). Assuming that information=guidepost is only specified in combination with tourism=information (as stated in the wiki) this affects about 57% cases where the “i” is rendered. Additionally, other values of the information key also lead to a confusing rendering.

Change History (3)

comment:1 Changed 8 years ago by augustus.kling@…

  • Cc augustus.kling@… added

I coincidentally found case #1961 that is very similar. Although the cases are not really duplicates, solving one should also solve the other.

comment:2 Changed 4 years ago by math1985

  • Summary changed from Don't render guideposts as tourist information points to [amenity-points] Don't render guideposts as tourist information points

comment:3 Changed 4 years ago by math1985

  • Resolution set to duplicate
  • Status changed from new to closed

This issue is now being discussed on Github:
https://github.com/gravitystorm/openstreetmap-carto/issues/324

Therefore, I will close the issue here.

Note: See TracTickets for help on using tickets.