#2414 closed enhancement (fixed)
route relation editor proposal
Reported by: | jekader | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | |
Keywords: | relation | Cc: |
Description (last modified by )
I've read the wiki page on route relations and found them really difficult to add by hand... Especially the bus stops - you have to type a "stop_<n>" description for every point, while it's even difficult to understand, where it is located on the map.
So I'd really love to see improvements in the relation editor for routes.
First of all, it would be great to have a separate window, where only the selected items are shown.
Second - there must be two lists in the editor - one for the segments of the route, and another for the stops. JOSM can automatically mark all points as stops (as well as all the objects that have the corresponding tags on them)
So, in this list, you just see the stops, and you can move them up and down in the list, thus setting the order. When finished, JOSM should automatically tag the roles appropriately to the position in the list. This way, I won't need to re-number half of the stops if I add a new one in the middle. The position numbers should be shown in the route selection window, so that the result is visible.
Something similar could be done with the first list with the route segments. Each line there can, for example, include two checkboxes - "forward" and "back" - if both are checked, the segment's role remains empty, if just one - then the role is set to one of the variants. And to make things more intuitive - some arrows could be drawn parallel to the ways, so that you can always see the result you're getting.
I believe this variant is not so easy to implement, but I'm sure that it will make adding/editing routes much easier.
Attachments (0)
Change History (2)
comment:1 by , 15 years ago
comment:2 by , 12 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
The role stop_n is depreciated and everything else is implemented in some kind of way.
Currently stop_n are not needed anymore: I think this ticket could be closed.