-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider moving some POIs to new infrastructure, other layers #715
Comments
I've found it useful to imagine that someone has a style which renders everything in the Personally, I think BBQs and picnic tables would fit that "generic POI" description, although it's definitely a grey area. But I think showing a power pole or pylon as a generic POI would be pretty confusing. It's a bit like when we added ferries to the |
Straw man proposal:
|
Process changed. |
Following up from discussion in #706, if we create a new
infrastructure
layer for putting power lines, gas lines and other "utility" infrastructure, should we also move some of the related POIs into the same layer, or leave them in thepois
layer?For instance,
power_pole
andpower_tower
are paired with power lines.But there are many other values that could be included (maybe they should, maybe they shouldn't). For instance:
man_made
features go here?bbq
amenity: life_ring
amenity: picnic_table
The pro: Moving features into a dedicated infrastructure layer would mean there's less chance of them getting displayed mixed in with regular business pois, but...
The con: it also increases the complexity of where to find things to build the map style.
We had been discussing centralizing even more "poi" like features into the pois layer – we do this now for shops and other tags present on buildings, we peal those off and put them into the pois layer leaving only (icon-less) label placements behind. But in the landuse layer label placements should generally have icons so we already mix this up a bit.
Where would features like amenity: bbq and amenity: life_ring and amenity: picnic_table go? Seems like most of these features could just go into an infrastructure layer just as well as a pois layer. Sure they have an amenity tag from OSM, but looking at it not knowing the history it's not clear. Less layers seems better.
The text was updated successfully, but these errors were encountered: