Opened 5 years ago
Last modified 4 years ago
#19095 new enhancement
Warning about "*:lanes=*" tagging without "oneway=yes"
Reported by: | skyper | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core validator | Version: | |
Keywords: | lanes-tagging forward backward | Cc: |
Description
What steps will reproduce the problem?
- Have a way with
turn=right
orturn:lanes=through|right
and withoutoneway=yes
- Run validator
What is the expected result?
A warning demanding to use forward/backward
What happens instead?
No warning
Please provide any additional information below. Attach a screenshot if possible.
All lanes-tagging keys like destination
, destination:*
and turn
with or without suffix :lanes
suffer the same problem.
The same is true for:
placement
with or without suffix:lanes
except of valuetransition
change
with or without suffix:lanes
except valueno
orchange:lanes=no|no
in combination withlanes=2
Additionally all *:lanes=*
like access:lanes
, Transport_mode:lanes
(e.g. bus:lanes
), maxspeed:lanes
, surface:lanes
and width:lanes
are a problem.
Probably combinations with oneway=yes
and oneway:*=no
need to be checked, as well.
Relative:URL: ^/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2020-04-13 22:05:56 +0200 (Mon, 13 Apr 2020) Revision:16294 Build-Date:2020-04-14 01:30:47 URL:https://josm.openstreetmap.de/svn/trunk
Problem are
change:lanes=no|no
andsource:lanes=*
which should be excluded but I still want a warning ifturn:lanes=left;through
is present.