Allowing multi-selection on the basis of common tags #4311
Comments
|
Author: stevage How about this:
I'm guessing that name=* is by far the most likely candidate for such a grouping. Are there other likely use cases? (I generally think it's better to handle a specific use case well, rather than having a general tool that handles a wide range of use cases - especially if most of them aren't useful. Happy to be corrected though.) |
|
Author: stevage ...and once again, I fall victim to Trac formatting:
|
|
Author: Richard Mann ref= might be another (and I can envisage that others might well be useful) Contiguity probably involves more code (and recursion, which I'd avoid unless essential), and I don't think it's necessary. One addition, though: the ability to deselect if not equal (ie AND) |
|
Author: stevage By contiguity not being necessary, you mean you'd select all ways with the same name (or ref/...) even if they weren't contigous? That would get a lot of false positives... Ok, if we need to support other tags like ref (which I agree with), then what could the interface look like? A dropdown box next to the Key field feels too intrusive (imho) for a pretty niche feature. Maybe a button on the same row as Delete and Add, "Find related"? Hold down Ctrl and click a tag? Btw can you spell out your "AND" requirement? You want to be able to specify multiple tags, and select all ways that match all of them? Is this important? Is one tag not enough? What's the use case? |
Reporter: Richard Mann
[Submitted to the original trac issue database at 12.01pm, Thursday, 22nd March 2012]
At the moment I can click on a little drop down menu next to a relation, and "select all members". I can even try to be clever by deselecting ones that are members of another relation...
I'd like similar functionality (select/deselect) but based on a tag. So for instance I select a way that's one part of a street, and want to multi-select all the ways that form that street. I'd envisage being able to do that on a dropdown menu next to the name=whatever tag. That would query the currently loaded data and multi-select anything that matched.
That'd only be available in advanced mode, but it would be quite a powerful tool. It would get round many of the issues about how additional detail (bus routes, cycle provision, bridges, lanes etc etc) break up ways into ever-shorter sections.
The text was updated successfully, but these errors were encountered: