id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
17391	complain about unreasonably narrow highway=pedestrian	mkoniecz	team	"==== What steps will reproduce the problem?
1. Create way
2. Tag it `highway=pedestrian` `width=0.5` `name=Foobar`
3. Run validator

==== What is the expected result?

Validator offers automatic fix to `highway=footway`

==== What happens instead?

Nothing.

==== Please provide any additional information below. Attach a screenshot if possible.
I propose 2 m as the edge value. Optionally 1 m.

Inspired by https://lists.openstreetmap.org/pipermail/tagging/2019-February/043221.html

> Venice is a globally unique (or maybe almost unique) exception anyway, but
> what we currently have there is the result of people reclassifying all the
> footways as pedestrian roads, even if they are 50 cm wide. I have started
> in the past several attempts to open a discussion on this, but it felt like
> Don Quixote. See this as an example:
> https://www.openstreetmap.org/way/488627565/history I have surveyed it
> myself, like many others, where I began to reclassify the very narrow
> footpaths from pedestrian to footway, but I am not local and people destroy
> the finer grained distinction of footway and pedestrian as soon as you add
> them, I guess they do not want the red dots. It is unfortunate, because it
> makes the Venice map much harder to read and less useful. If you are local,
> please try to improve the situation, we do not need new tags, it would be
> sufficient to apply the existing ones consistently rather than
> indiscriminately.

iD equivalent at https://github.com/openstreetmap/iD/issues/5991

{{{
URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-02-23 17:46:51 +0100 (Sat, 23 Feb 2019)
Build-Date:2019-02-24 02:30:49
Revision:14802
Relative:URL: ^/trunk

Identification: JOSM/1.5 (14802 en) Linux Ubuntu 16.04.5 LTS
Memory Usage: 418 MB / 869 MB (182 MB allocated, but free)
Java version: 1.8.0_201-b09, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Dataset consistency test: No problems found

Plugins:
+ OpeningHoursEditor (34867)
+ buildings_tools (34867)
+ continuosDownload (82)
+ imagery_offset_db (34867)
+ measurement (34867)
+ reverter (34867)
+ todo (30306)

Last errors/warnings:
- W: No configuration settings found.  Using hardcoded default values for all pools.
}}}
"	enhancement	new	normal		Core validator			template_report