id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
10974	Avoiding collateral damages in PTv2 routes	Weide <osm@…>	team	"By far the most damages in Public Transport Version 2 Routes are done by mappers using ""p"" when working in an entirely different context, mostly lanes and speed limits. Some of them dont even know, that relations carrying information in the sequence of members exist and may be invisible. JOSM handles this situation very well if the necessary objects to handle this are already loaded. The advice to the mappers is to use ""p"" each and every time only after selecting the way and it's end nodes and using Alt-Ctrl-D on them. But it would be enough to load all the PTv2-routes having the way as a member and the neighbour elements of the way in their member list. Is there any way to support this automatically?

A few damages in Public Transport V2 Routes are done using the button ""add to relation"". As inserting a member into a PTv2 route without giving the position is nearly always wrong, the button should be deactivated if the destination relation contains type=route and public_transport:version=2.

A function to replace an already existing object by another already existing object (especially a node by a way or a relation or a way by a relation) in every parent relation without changing the position or role would avoid many problems. This process is very error prone if done step by step by the mapper. This occurs mainly in the context of detail mapping of platforms.
"	enhancement	new	normal		Core