jump from stop to correspondig way and vice versa

[Polyglot]

An enhancement that would be nice to have in a specialised Relation Editor for public transport routes, is a way to jump from a stop to the corresponding way and vice versa from a way to corresponding stop(s).

It's possible to use zoom, then select, of course.

Another button in such relation editor could apply
public_transport:version=2

(or help with setting it back to 1, in case 2 was not correct)

[michael2402]

How and why do you want to jump to that way? Select it in the relation editor, or select it in the map view?

[skyper]

I would use this function when I have small variants part of bigger variants. Right now I first add the longest variant and clone this relation for smaller variants where I have to remove stops and ways and maybe add some ways and stops at the top or bottom afterwards.

Instead of a button, I'd rather go with a new context menu item in the memberlist but maybe in future the buttons in relation editor will be manually configurable like the main toolbar.

I'd like to jump to the member in memberlist but have to think about it again, I guess.

[michael2402]

@skyper

If you remove the stops, you cannot go to the way. If you remove the way first, you cannot go to the stop. So for deleting ways this feature won't be of much use.

For this, you would rather need a way to see which stops belong to which way quickly (and which ones do not belong to a way)

Would highlighting the removed stops after removing their way solve your issue?

Or a graphical version:

[skyper]

You got me wrong. I remove some ways or stops on top and now I need to find the corresponding way/stop for the remaining first stop/way to find and remove the unneeded remaining opposite objects after the first removable.

I have to admit that I do not use the special layer most of the time, so I am only working with relation editors and data layers.

[michael2402]

Replying to skyper:

You got me wrong. I remove some ways or stops on top and now I need to find the corresponding way/stop for the remaining first stop/way to find and remove the unneeded remaining opposite objects after the first removable.

So your workflow to remote the first two stops of the route would either be:

• Remove the stop / platform members
• Now search the way that belongs to the new first stop
• Remove all ways before that.

This is what the relation members would look like after removing the first stops when we indicate the stop numbers. The ways to remove can be found when scrolling through the list (it is everything before the 1).

Second workflow:

• Remove the members that represent the way
• Now search the stop that belongs to the new first way
• Remove all stops before that

This is what the relation editor would look like then - you can find the two removed stops easily.

So my question is: Do we still need this feature for some other workflows or is scrolling / viewing in this situation not enough for some reason?

[skyper]

The highlighting looks nice and is useful.

To be honest, I fear it will not work for me in some cases as I often work with only partly downloaded members and I use my method also in the middle or the end of bigger relations where scrolling does not work that well. As an example, see SBG Bus 7342 (​4285797 aka ​PTNA) which I plan to update soon according to its ​GTFS-Data.