id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
18488	Lane count validation	gaben	team	"The current lane validation rule only warns if the `lanes` < `lanes:forward`+`lanes:backward` values.
I think a not equal rule would be more useful.

==== What steps will reproduce the problem?
1. Tag a way with eg. `lanes=3` `lanes:forward=1` `lanes:backward=1`
2. Run the validator

==== What is the expected result?
A warning informs the user that the values don't match

==== What happens instead?
Nothing

==== Please provide any additional information below. Attach a screenshot if possible.

{{{
Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-12-29 22:32:02 +0100 (Sun, 29 Dec 2019)
Revision:15624
Build-Date:2019-12-30 02:30:57
URL:https://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (15624 hu) Linux Debian GNU/Linux 10 (buster)
Memory Usage: 321 MB / 1990 MB (81 MB allocated, but free)
Java version: 11.0.5+10-post-Debian-1deb10u1, Debian, OpenJDK 64-Bit Server VM
Screen: :0.0 1912x1020
Maximum Screen Size: 1912x1020
Java package: openjdk-11-jre:amd64-11.0.5+10-1~deb10u1
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-22
fonts-noto: fonts-noto:all-20181227-1
Dataset consistency test: No problems found

Plugins:
+ tageditor (35258)
+ turnlanes-tagging (283)

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