Changes between Initial Version and Version 3 of Ticket #17496


Ignore:
Timestamp:
2020-01-25T22:59:20+01:00 (4 years ago)
Author:
simon04
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #17496

    • Property Keywords autofilter added

  • Ticket #17496 – Description

    initial v3  
    1 I believe autofilters would be more useful if some tags were inferred when not actually present. For objects missing a layer=* tag, I propose the following scheme:
     1I believe autofilters would be more useful if some tags were inferred when not actually present. For objects missing a `layer=*` tag, I propose the following scheme:
    22
    3 - bridge=*, power=1, location=overhead: assume layer=1 if not specified
    4 - tunnel=yes, tunnel=culvert, location=underground: assume layer=-1
    5 - tunnel=building_passage: assume layer=0
    6 - Other highway=*, waterway=*, railway=*: assume layer=0
     3- `bridge=*`, `power=line`, `location=overhead`: assume `layer=1` if not specified
     4- `tunnel=yes`, `tunnel=culvert`, `location=underground`: assume `layer=-1`
     5- `tunnel=building_passage`: assume `layer=0`
     6- Other `highway=*`, `waterway=*`, `railway=*`: assume `layer=0`
    77
    88A user who had autofilters enabled for the layer tag could then use autofilters as if those tags were present. For example, it is not recommended to tag layer=0, but such a filter would be useful when working on a complex motorway interchange, filtering out all objects not assumed to be at surface level. The autofilter buttons would still only appear when an object with a layer=* tag is in the viewport, as is currently, but whenever an autofilter button appears, there would also be a "0" button between the "1" and "-1" buttons.