id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
18698	[Patch] Request: Add (motor_)vehicle combo to highway=path preset	AnkEric	team	"In Closed ticket https://josm.openstreetmap.de/ticket/18642 you have also implemented:
""Add vehicle combo to highway=track preset""
Oké, nice! Appreciated. I get more than I have asked for.

But than I would like to suggest to not only Add vehicle combo to highway=track, but also (and - imo - even more important) to highway=path preset.

Most annoying (to me) a highway=path is added on OSM without any access restriction.
Therefore (default access): bicycle/mofa/moped=yes is implied. Sometimes this is correct, sometimes not. So my GPS might be directing me - on bicycle - over a path which is in fact a ""footway"".
Sometimes this is ""resolved"" the wrong - IMO - way: [highway=path] + [access=no] + [foot=yes].
Because this is ""less work"" than [highway=path] + [bicycle=no] + [moped=no] + [mofa=no] + [horse=no] and better than [highway=path] + [bicycle=no] ?
Next mapper might change to: [highway=footway] + [access=no] + [foot=yes].
Next mapper might change to: [highway=footway] + [access=no] (since ""foot=yes"" is ""needless"").
And now we have a path with no access at all.
Which was ""resolved"" by Reverting ALL thousands of footways in the Netherlands where ""foot=yes"" was removed by hundreds of ""Undiscussed Mechanical Edits"". 
And now JOSM Validator is is bothering me with tens of warnings for each of my Changesets: ""unnecessary tag - foot=yes|designated is unnecessary for highway=footway|pedestrian"".
JOSM Validator is - of course - correct. Does [highway=footway] + [foot=no] exist in ""on the ground""? No! IMO!
And I don't dare to resolve; -))

Correct would have been initial mapping as: [highway=path] + [vehicle=no].
And a JOSM preset might help... a little...

/ AnkEric


"	enhancement	closed	normal	20.07	Internal preset		fixed	highway path motor vehicle access