Correction needed for east end of tracks at Truxton Flyover (Arizona)

Help and support
1

Here is the information that should help fix this issue. I hope that I haven’t forgotten anything necessary or important. I would have fixed this myself, except the iD editor doesn’t seem to work with relations as near as I can tell.

Node: 9732870982 | OpenStreetMap - incorrectly placed switch, should be moved to Main 2
Way: ‪Seligman Subdivision‬ (‪947017622‬) | OpenStreetMap - Main 1, correctly placed
Way: ‪Seligman Subdivision‬ (‪1152578207‬) | OpenStreetMap - Siding, incorrectly attached to Main 1, should be attached to Main 2. Also this way is incorrectly tagged as a Main instead of a Siding.
Way: ‪Seligman Subdivision‬ (‪533612994‬) | OpenStreetMap - Main 2, correctly placed
https://www.openstreetmap.org/relation/1453756 - the relation that needs to be modified. Note that the Siding should not be part of the relation. Other similar sidings are not part of the relation. (The Siding could very well have been a Main prior to 2020).

OpenStreetMap - View in OSM
Google Maps - View in Google Maps

This is the East end of the Truxton Flyover. Main 1 goes over the Flyover. That the middle track is a Siding and not a Main can easily be deduced by the unpowered cut of cars sitting on the track further west in Google Maps.

The Truxton Flyover itself was completed in late 2020. The other changes to this area were made in 2021. There is a YouTube video (https://www.youtube.com/watch?v=trGcWhjMgwU) from December 2020 that shows the changes in progress at the 5:00 mark.

(Note: As a new poster, only three links are allowed, so an extra ‘h’ was prepended to some of the links.)

2

I recommend JOSM for such edits.

1 Like
3

I hereby heartily second Mateusz’ recommendation, as I have many times before (both this specific one and other things Mateusz says and does!)

You CAN edit relations with iD, but (IMO) it’s pretty awkward to the point of being painful. Others disagree and manage to edit relations with iD, I say “yuk” and am entitled to my opinion as much as they are theirs to edit relations with iD.

I highly recommend (and have many times) using JOSM for editing OSM relations, especially for (rail, bicycle, highway, hiking, equestrian…) ROUTES. Routes are only one of the powers that OSM has by being a relational database…multipolygons, sites and boundaries are other relation types.

There is a learning curve involved, but the power (again, IMO) comes from JOSM’s visual presentation of a dialog box (a user interface term for a modal or modeless window) that shows the attributes of relations, and abilities to edit them:

The relation’s tags, up top, fully editable as text objects in a scrolling list of key:value pairs,
A pane on the left side for “map-selected objects” (nodes and/or ways or even other relations),
A pane on the right side for “elements IN the relation” (and the order that they are in, again, editable here), and
some buttons between the left and right panes for moving objects and elements around, sorting them, etc.

With all this, you can do anything needed with relations. Yes, understanding that a relation must have a type, and the value of that key (for example type=route) “makes the relation what it is” should be a crucial first step of understanding. Looking at some examples (of routes, for example) could be next, and can give you an idea of their (proper, good-practice) structure. With that (knowledge, and beginning of practice), you can begin to modify (improve) existing routes, and grow your relation-editing skills to build your own relations.

Ask. Read wiki. There is a lot of knowledge to be shared about relations. And many relations yet to be built in OSM.