Way can be reasonably assumed to not be oneway.

[matkoniecz]

Currently on editing road without oneway tag "One Way Unknown" is presented. It encourages adding useless tag "oneway=no" everywhere (I did it at start).

It would be better to display "Assumed to be no" instead of "Unknown".

[bhousel]

Agreed, now the oneway field will not show the unknown option.

[jfirebaugh]

I'd rather go with @mkoniecz's suggestion of changing the placeholder text to "Assumed to be no" than changing the field type to defaultcheck. There are a few cases where oneway=no is useful: in order to avoid mapping errors in areas where oneway streets are common and to override the assumed default of oneway=yes on things like junction=roundabout and highway=motorway.

[bhousel]

Ok. We'll need to fix the check field to support changing the placeholder text, but that's probably easy.

Also I noticed that junction=roundabout with oneway=no still renders the oneway markers. I can fix iD.Way.isOneWay() so it returns false if oneway is explicitly tagged falsy.

[jfirebaugh]

👍 Sounds great!

[matkoniecz]

Note that junction=roundabout and highway=motorway (and maybe other?) should display "Assumed to be yes".

Is it possibly to modify it so isOneWay and tagging interface will check single source to get default onewayness?

[bhousel]

Note that junction=roundabout and highway=motorway (and maybe other?) should display "Assumed to be yes".

For highway=motorway, I think iD tries to add an explicit oneway=yes tag. (wiki suggests this is good behavior).

For junction=roundabout this is trickier because we don't have an actual preset field for it. There is some discussion on #1841, #2062, #1264. If we create it as a preset, we would need to add one for every kind of highway. If we create it as a field on the highways, we'd really want it to only show up for closed highway=* ways, which fields can't currently do. (Edit: or maybe not, since a roundabout could really be made up of a bunch of non-closed ways connected together?). Roundabouts/jughandles may work better as an enhancement on the turning restrictions that @jfirebaugh is working on, rather than trying to fit them into the existing preset/field ui.

Is it possibly to modify it so isOneWay and tagging interface will check single source to get default onewayness?

I could make a global Object similar to area_keys (oneway_keys?) if the onewayness really is used in a few places.

[bhousel]

Is it possibly to modify it so isOneWay and tagging interface will check single source to get default onewayness?

I could make a global Object similar to area_keys (oneway_keys?) if the onewayness really is used in a few places.

I ended up doing this because it turned out that there are a few places where we want to check for implied onewayness, and it turns out that there are more tags that imply onewayness than I realized (piste stuff, etc.)