Possible to join up two Way records to fix a boundary?

Support City/Street/Node Issues
1

Way: ‪Cimarron Hills‬ (‪37436178‬) | OpenStreetMap got separated from Way: ‪Cimarron Hills‬ (‪1305681178‬) | OpenStreetMap

Together, they contribute to an inner boundary of Relation: ‪Colorado Springs‬ (‪113141‬) | OpenStreetMap

If the two Way records can be joined up again, then Cimarron Hills, Colorado - CityStrides can continue to exist in CityStrides. I only have experience with the iD editor, and it’s not allowing me to join the two Way records. I gave it a try in JOSM, but was only successful in producing error messages.

1 Like
2

Done - Changeset: 157696076 | OpenStreetMap

The warning you were likely getting about “modifying an incomplete relation” was because the relation members weren’t sorted, so JOSM thought there was a bunch of unconnected ways. A quick sort fixed that up.

2 Likes
3

Thanks!

I was getting an error while trying to download the initial dataset :confounded: I couldn’t even get to the point where I could attempt to join way records. It kept telling me that I was choosing too large of an area to download. :person_shrugging:

4

:thinking: I found a different/similar issue…

The border of Stansbury Park, Utah - CityStrides seems kinda mangled in OSM in that it’s a combination of two Way records where one of them is open & the other is closed partway through the city which seems to break my street query.
It’s here in OSM: Relation: ‪Stansbury Park‬ (‪198833‬) | OpenStreetMap with these two Way records:

5

I combined those two ways into a single closed way. Hopefully that helps!

Edit: After looking at the boundaries a bit more, I went back and re-separated the ways where it shares a boundary with the neighboring city. The relation for Stansbury Park should no longer have the split across the city though.

1 Like