Opened 13 years ago
Closed 9 years ago
#8135 closed enhancement (duplicate)
history spam when splitting ways
| Reported by: | dieterdreist | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | way split history id | Cc: |
Description
In certain circumstances splitting could be optimized for better db history. This is what happened to me: clicked on junction to start a new way. Drew the way. Then I saw that the new way was a prolungation of another way that also ended at the junction. I split the two ways at the junction and noticed that the original way got marked as new and the new way got the old ID.
Even though I didn't make any edit (in the end, well I moved some nodes actually) to the existing way it will look in the changeset as if I had removed all nodes and added some new nodes. While this is sometimes not avoidable, in this case it is particularly evident.
My suggestion is to assign on way splits the old ID to that part that has most of the original nodes in it.
Attachments (0)
Change History (2)
comment:2 by , 9 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Closed as duplicate of #10730.
This makes sense for parts with only new nodes but one big advantage of the current implementation is the option to have the user decide which part will get the new id through changing the way direction as right now the first part will always keep the id.