srbhiscock wrote:A navigation type that would utilise a generic economy algorithm would be useful, perhaps avoiding lots of stop-start situations...
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.
Users browsing this forum: No registered users