[Tagging] Feature Proposal - RFC - key:rubbish=
dieterdreist at gmail.com
Wed Feb 18 12:45:02 UTC 2015
2015-02-18 13:23 GMT+01:00 Dave Swarthout <daveswarthout at gmail.com>:
> ? I don't buy into the notion that there are too many amenity tags.
yes, this is something that occassionally pops up, but there is really no
actual problem behind this.
Maybe the idea is that someone offering presets to his users (for example)
would have them grouped just the way the tags are, and someone would have
to open the "amenity list" and find thousands of values, so they think if
we introduced eat_and_drink as key and move related POIs over there we
could "relieve" the "pressure" on amenity, but this is not how it works.
Other issues might be "catch-all" rules of some kind.
Clearly, having more different keys allows for easier pre-filtering and
maybe faster lookup with some database schemes, but the way osm-carto works
until today (column-based) puts a very high hurdle on every new key before
it could get rendered.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging