id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
14804	Unify case handling for boolean tag values	michael2402	team	"We currently have:
- `OsmUtils#getOsmBoolean()` accepting all cases for `true`, `yes`, `1`, `on`
- `OsmUtils#isTrue()`, `OsmUtils#isFalse()` accepting lower case `true`, `yes`, `1`, `on`
- `OsmPrimitive#isKeyTrue(key)` accepting lower case `true`, `yes`, `1`, `on`
- `OsmPrimitive#hasAreaTags()` accepts only `yes`
- `Way#isOneway()` accepting all cases for `true`, `yes`, `1`, `on` and `-1`, but not `reverse`
- Relation map painting respects `oneway=-1`, but not `reverse`
- `ReverseWayTagCorrector` only accepting lower case, but accepting `-1` and `reverse`

In tests:
- `Highway#testWrongRoundabout`: accepting all cases for `true`, `yes`, `1`, `on` for oneway, but none of the reversed.
- `UntaggedWay` test accepts only noname=yes

That's what I found so far. We should unify this and decide on a common policy here."	defect	new	normal		Core