yes/no/maybe bicycle & walking values

[nvkelso]

We're always including yes, no & other values on the new walking, bicycling ways. But should we only include no or yes values contextually?

• http://vector.dev.mapzen.com/osm/all/14/2616/6328.topojson?api_key=vector-tiles-HqUVidw

For instance, motor_vehicle: "no", is interesting here because tracks are assumed to be motor_vehicle: "yes",, but foot: "yes", I think is assumed to be yes, so why export that?

type: "LineString",
properties: {
kind: "path",
bicycle: "yes",
name: "Alta Tr.",
sort_key: 354,
landuse_kind: "national_park",
horse: "yes",
source: "openstreetmap.org",
motor_vehicle: "no",
foot: "yes",
tracktype: "grade2",
id: 239140918,
highway: "track"
},

[nvkelso]

Another example, no isn't useful here for cycleway, we only want to know when it's yes.

• https://www.openstreetmap.org/way/22731214

[nvkelso]

Related to #453.

[rmarianski]

Should we normalize it to yes if the value isn't no? It can be other values like "lane". Or do we want to pass it through as long as it isn't no?

[nvkelso]

Pass thru as long as it's not no and not none.

(I suspect some of those other values could probably be normalized (there look to be variants), but let's just pass them thru for now.)

[nvkelso]

Correctly updated. There's more work to be done to normalize all these, that's tracked in #792.