Skip to content
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

Do not show current relation in dropdown #7648

Closed
boothym opened this issue Jun 2, 2020 · 5 comments
Closed

Do not show current relation in dropdown #7648

boothym opened this issue Jun 2, 2020 · 5 comments
Labels
usability An issue with ease-of-use or design

Comments

@boothym
Copy link
Contributor

boothym commented Jun 2, 2020

When adding a new bus route relation, I accidentally clicked a relation in the dropdown next to the one I wanted to choose, as it had a similar name.

However this relation was already added to the way - should it even be available to select from the dropdown? Surely relations can only be added to a way once?

@1ec5
Copy link
Collaborator

1ec5 commented Jun 2, 2020

I’ve previously mapped bus routes that loop back over themselves, requiring double membership, but I don’t know how common that is.

@quincylvania
Copy link
Collaborator

Even if it's really uncommon, if it's possible then we should support it in iD. But I agree it's too easy to accidentally add the same relation twice. We should at least style these values differently in the list and possibly add a label.

@quincylvania quincylvania added the usability An issue with ease-of-use or design label Jun 2, 2020
@boothym
Copy link
Contributor Author

boothym commented Jun 2, 2020

Let's say a route uses the same roads in and out of a bus station, or the same roundabout twice - how would that work? Would you just add the same relation to the way twice (perhaps with forward and backward roles?)

Maybe another issue should be opened for this, but what about listing recently used relations first in the dropdown? That way you don't have to scroll down to find your last used relation.

Sorting the relation dropdown by type would also be useful #5997

@BjornRasmussen
Copy link
Contributor

Let's say a route uses the same roads in and out of a bus station, or the same roundabout twice - how would that work? Would you just add the same relation to the way twice (perhaps with forward and backward roles?)

A long time ago, this was not possible to represent in OSM, so people created a newer system for mapping bus routes called PTv2, which requires that the roads be added to the bus route relation in the order that they are covered by the bus. If a bus route uses the same road twice, then the road will be part of the relation twice, but in different parts of the parent relation. See this wiki page, specifically the section on adding a bus route, for a better explanation.

Also note that in the newer system, all roles were dropped for roads, so no forward or backward roles are used.

@1ec5
Copy link
Collaborator

1ec5 commented Oct 15, 2024

We should visually distinguish any existing relation membership without preventing the user from adding it: #10501.

@1ec5 1ec5 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usability An issue with ease-of-use or design
Projects
None yet
Development

No branches or pull requests

4 participants