id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
8135	history spam when splitting ways	dieterdreist	team	"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."	enhancement	closed	normal		Core	latest	duplicate	way split history id