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

[amenity-points] Split POIs into prioritised groups #3006

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

[amenity-points] Split POIs into prioritised groups #3006

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

Comments

@openstreetmap-trac
Copy link

Reporter: tom[at]acrewoods.net
[Submitted to the original trac issue database at 9.46am, Monday, 24th May 2010]

Now that we are adding ever more POIs to the stylesheet, areas with dense POIs lack any sense of priority. Post offices are obscured by hairdressers, pub names don't render for fear of conflicting with the name of a bakery.

They should be split into a few different sets in the stylesheet, so that high priority POIs (e.g. bus stops, museums) are rendered first, followed by generally useful POIs (e.g. pubs, post offices), followed by all the rest (e.g. takeaways and hairdressers, and most shops).

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 11.41pm, Thursday, 3rd June 2010]

The more POIs are added to dense areas, the more this idea has merit.

We'll of course be having countless discussions about all the intricacies of the order these things should be rendered in, but the basic idea is good.

@openstreetmap-trac
Copy link
Author

Author: tom[at]acrewoods.net
[Added to the original trac issue at 7.33am, Monday, 21st June 2010]

Here's a nice example... a mosque being obscured by a little hahal convenience store next door:

http://www.openstreetmap.org/?mlat=51.45739&mlon=-0.072641&zoom=18&layers=B000FTF

@openstreetmap-trac
Copy link
Author

Author: math1985
[Added to the original trac issue at 3.24pm, Friday, 1st August 2014]

This issue is now being discussed on Github: gravitystorm/openstreetmap-carto#802
Therefore, I will close the issue here.

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