id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5910	When deduplicating nodes, give preference to existing nodes, instead of new nodes	fsteggink	team	"For importing landuse data in both Canada and the Netherlands it is necessary to deduplicate nodes. Thankfully this is happening fast now, due to an earlier ticket being resolved :) However, in case of the Canadian import I would like to reuse nodes of forest areas I've uploaded earlier, but the ways / relations can be removed, because the attributes have been updated.

When I perform a node deduplication with the validator, it often gives preference to new nodes, instead of existing nodes. I hope that this can be changed be changed. Reason: much less upload of data will be required. Currently I'm importing a sheet near Trois-Pistoles, Québec, and there are about 50k changes (including other data). Of this about 32k are new features, and 16k are features to be removed. Many of the latter features are ""old"" nodes which are being uploaded again, in exactly the same position."	defect	closed	normal		Core	latest	irreproducible