id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
20995	Why are presets not unified across editors?	roqimas	team	"So, this is less of an issue with JOSM specifically, but something that JOSM IMO should consider.

OSM Wiki notes ""Presets have not been standardized across editors""([https://wiki.openstreetmap.org/wiki/Preset]). It seems a first attempt at doing this was considered some years ago ([https://github.com/osmlab/editor-presets]), but nothing ever came of it.

My question is: Why not?

There are a ton of obvious benefits to having unified presets. Data quality of OSM, ease of use for editors, communicability of editing practices, accuracy of rendering by editors would all increase massively if presets (and therefore tagging schemes) were standardized more. The wiki, in integrating that standard preset scheme, could offer even better documentation of those tagging schemes. Changes in tagging could easily propagate across geography and time, past tagging could be understood better as a result of previous unified standards, editing and adding data would be simplified considerably and the barrier of entry for new editors (and editor solutions) would be lowered as well.

Why haven't there been more attempts at integrating the presets JOSM, Potlach, iD and other editing solutions use? We see some convergence; StreetComplete uses iD's presets, Vespucci uses JOSM's. But still, a (IMO highly unnecessary) rift remains, only getting worse with time as more editors, editing solutions and tagging discrepancies emerge.

iD issue: [https://github.com/openstreetmap/iD/issues/8537]
Vespucci issue: [https://github.com/MarcusWolschon/osmeditor4android/issues/1412]"	enhancement	new	normal	Longterm	Internal preset	latest		preset standardization; preset unification; presets