id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
3047	Relation sorting adds new members - destroying data!	xylome	team	"example: http://www.openstreetmap.org/api/0.6/relation/59065/full
initially has 59 members. after sorting one member is duplicated.
i know sorting osm relations is a pain (circular ways, Ts, ...) so there should be a due diligence test after the sort process. e.g. same number of members, same members as before...

as long as this is not fixed: disable sorting... it destroys data without notice!"	defect	closed	blocker		Core	latest	duplicate	relation sorting