Oneway Direction

[liamc70@…]

What steps will reproduce the problem?

1. Press on a track/edge with "oneway"="1"
2. It changes to "oneway"="-1"
3. Press R again and it changes to "yes" instead of 1

What is the expected result?

It should say "1" instead of "yes".

What happens instead?

It said "yes"

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

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-12-01 23:10:15 +0100 (Sun, 01 Dec 2019)
Build-Date:2019-12-02 02:30:57
Revision:15553
Relative:URL: ^/trunk

Identification: JOSM/1.5 (15553 en_GB) Windows 10 64-Bit
OS Build number: Windows 10 Pro 1909 (18363)
Memory Usage: 1178 MB / 1820 MB (285 MB allocated, but free)
Java version: 1.8.0_201-b09, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: \Display0 1920x1080, \Display1 1920x1080, \Display2 3840x2160
Maximum Screen Size: 3840x2160
Program arguments: [%UserProfile%\Box\Digital Rail Platform (UoH Only)\99_Data\_NR_2019_12_08.osm]
Dataset consistency test: No problems found

Plugins:
+ imagery_offset_db (34908)
+ measurement (35221)
+ turnrestrictions (34977)
+ utilsplugin2 (35238)


Last errors/warnings:
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!
- W: Unable to convert property z-index to type class java.lang.Float: found eval(1 + tag("ref:load:forward")]) of type class java.lang.String!

[GerdP]

oneway=1 is not wanted, oneway=yes is the preferred tag. If you want to undo the change you can use the undo button.

[stoecker]

JOSM converts all boolean values to yes/no whenever you modify them.

[liamc70@…]

Why are they preferred?

I completely disagree.

1. Using digits 1/0 is more efficient in terms of storage size and memory usage. Also, pressing undo will also undo all the changes, not just the "oneway".

2. It should be consistent. If a user has used digits then it should keep within digits (1/-1). If someone has used characters then it should stay within words ("yes"/"no").

3. Why have digit support at all (draw arrows) if "yes" is preferred?

4. If you want to stick with the rule of using "yes"/"no" then make oneway say "no" instead of "-1". Better yet, you could when saving changes automatically change 1/0 to "yes"/"no" via the API layer to ensure that the preferred is always used.

[Don-vip]

Whether you agree to it or not, it's the OSM community consensus for many years. We won't change it. Please read ​https://wiki.openstreetmap.org/wiki/Key:oneway