Oneway property should be true, false

[nvkelso]

We've normalized all the other yes related properties in v1 to be True or False, but oneway is still yes.

Example tile:

• http://tile.dev.mapzen.com/vector/v1/all/15/5242/12664.topojson

yes should be True:

properties: {
kind: "major_road",
name: "Stockton St.",
sort_key: 377,
kind_detail: "tertiary",
source: "openstreetmap.org",
oneway: "yes",
sidewalk: "both",
id: 417400763
},

If it's no, should we even export that as False?

properties: {
source: "openstreetmap.org",
kind: "minor_road",
service: "alley",
oneway: "no",
sort_key: 356,
kind_detail: "service",
id: 332383249
},

[nvkelso]

This is a bug fix for tiles in our SemVer doc – and will be an additive change to house styles (which don't show one-way arrows yet). Moving to v1.1

[nvkelso]

Related / duplicate:

• Don't export oneway: no on roads #792 Don't export oneway: no on roads
• Normalise oneway property #453 Normalise oneway property
• Normalize cycleway (& left, right, both variant) values & oneway #782 Normalize cycleway (& left, right, both variant) values & oneway

[nvkelso]

We're prepping to show oneway arrows on all Mapzen house styles.

[nvkelso]

Well, turns out there are valid values besides yes and no:

• https://wiki.openstreetmap.org/wiki/Tag:oneway%3Dreversible
• https://wiki.openstreetmap.org/wiki/Tag:oneway%3Dalternating

Neither have very many uses in OpenStreetMap today. But thinking about the lanes on I-395 in the Washington, D.C. area that do this, those exceptions are exceptional.

Propose we close this, but still act on some / all of the issues related in #1028 (comment).