Christoph Hormann

> This looks like a bug in PR https://github.com/gravitystorm/openstreetmap-carto/pull/4717. Currently amenity=parking_entrance is not selected by the SQL query if access is a member of the list, which is surely not...

The shown example is an entrance (https://www.openstreetmap.org/node/9201255147) to an unmapped parking. Based on the data it is impossible to determine if this is a private parking or just a private...

The tag documentation lacks a language and culture independent definition of a _festival_ and a delineation towards other tags in the domain (in particular `amenity=music_venue`, `amenity=events_venue` and `amenity=theatre` + `theatre:type=open_air`)....

This is actually a duplicate of #3990 - closing as such. Any new discussion should go there.

I have looked at the use of the tag a bit and does not look very good. The tag is used to tag things at various locations where objects are...

> I've always found the value of other aeroway features is at least as much for orientation as anything else - I've only flown out of one airport around here,...

`aeroway=launchpad` is not rendered because we have not decided to render it. This is independent of if it is tagged on a node, linear way, closed way or multipolygon relation.

> > #2431: As above, presenting problem is public transport (PT) shelters "hiding" bus stops. But solution of "prioritising" bus stops over shelters (i.e. when they are both being rendered...

> > I assume a sensible option to addressing prioritisation is to introduce > > > ORDER BY start_zoom ASC > > as you propose in #3880, but without (as...

> Don't you need the shelter_type hstore tag as well? When you prioritize bus stops over shelters you can do so for all shelters and not just shelter_type=public_transport. You still...