TurnpikeWarrior wrote:I think the most logical solution is to disregard data from motorcyclists.
OldGnome wrote:fvwazing wrote:Please, do NOT add cyclists and pedestrians to the set. Any new vehicles should be able to drive (a subset of) the car-network.
How exactly are bicycles different in this discussion from long-haul trucks? Restrictions on where they can drive, potential impact to the average speed on the chosen roadway, etc. I would consider it an advantage while driving to know that both are on my route.
OldGnome wrote:fvwazing wrote:It may be different in the states - but DUTCH cyclists are notorious!
All the more reason to know where they are.
WeeeZer14 wrote: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.
And if sometime in the future we actually do support bicycles in a more complex manner, then the backend can change and the client already is set to bicycle.
p1l0t wrote:I would absolutely use a bicycle mode. We already can designate bicycle/walking paths so why not allow navigation for them in a mode that isn't going give bad data to car drivers. Plus how cool would it be to see a little bicycle wazer going by on the map. I use this app for avoiding traffic and road hazards (or plain navigation if I don't know the way somewhere) but a bicycle mode would add additional functionality for me. I'm 30 years old and getting kinda fat I try to ride my bike like every other day because it's helping me get back in shape. Plus the town I live in is HUGE on bike riding so it would get mapped for bicycles in a hurry. Also many other navigation apps to offer these modes so it will help make sure Waze keeps on crushing the competition.
Users browsing this forum: Google Feedfetcher