Allow "Replace Geometry" on ways not in OSM database as well with utilsplugin2

[rickmastfan67]

The reason I'm suggesting this is because sometimes you need to split a way into multiple pieces. An example is when you need to add in a bridge. Since only one of those ways keeps the original ID, the ones that don't can't use the "Replace Geometry" feature.

What I suggest is allowing all ways to be able to use this regardless if they have an ID in the database AS LONG AS the one way has some nodes in it with IDs in the database that you're trying to replace (the way with the nodes that have IDs would be the one to be replaced). That would allow people who just want to fix up a small area of road in the middle of a way to split the section off; trace in a new alignment for it; replace the old data with the new alignment; and then recombine the way together after that's done without having to reverse ways and stuff to allow the section they want to edit to keep the ID. It would make it a lot easier to do some spot editing inside of a very long way.

It's that or create a GUI interface that allows us to select which ID=0 way gets replaced by which one. ;)

Either way, I think this would be a worthwhile enhancement for the "Replace Geometry" function in utilsplugin2. ;)

[Zverikk]

Fixed in o26805. Sorry for the long delay. "Old" way must not contain new nodes, then it is considered not new.

[rickmastfan67]

Thanks Zverikk! I can live with it this way. :) Should help out a ton when I split a way for a bridge, but need to retrace an area after it that doesn't have an ID. :)

Also, just an FYI, but put "[]" around the OSM changeset number for it to show up as a link here like this: [o26804]. ;) Also, link to the one that had the code changed in it (it's the version number that's shown inside of JOSM), not the one it was built in. ;)

[rickmastfan67]

I'm just curious, but is there a way to tweak this to also allow the first or last node to be new and it to still work? The reason I'm asking is because sometimes, you need to add in a new node where the bridge ends/begins and the way that is "ID=0" will sometimes contain that node preventing you from using the "Replace Geometry" on a redrawn way where the "original" way still has only "database" nodes (minus the beginning/ending new node from the bridge split).