For the more common options we don't want to deal with fully supporting, just have them be pointers to the "Other vehicle" option that gets its speed ignored.
For example, bicycles. We know people use Waze on bicycles, so if we have a bicycle option for them to pick, I bet they are more likely to do so. Especially if it makes their icon into a bicycle
They don't need to know the details that it behaves the same as if they picked "other" and we and Waze don't need to do anything beyond setting up the "other" option.
YES YES YES. I think at this early stage - especially because the S.O.P. in the United states is to specifically disconnect bike and walking trails from the driving roads, the idea at this stage should be to get faulty data away from private driving - and that means giving users the option to enjoy nav, map issue reporting, incident reporting, or reporting gas prices, while not accepting their speed data in the context of private vehicles.
It looks like a feature, quacks like a feature, and mostly lets Waze's intelligent speed routing get smarter.
AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA