Automatic registration of bumpy roads and potholes

[grinvaldsjanis]

...

[dmcconachie]

If someone running waze (for an accelerometer to notice it) has an accident then yes, waze will already detect the traffic flow is running slower than the average, and create a jam.

I'm not talking about a jam. I'm talking about automatic reporting of the accident to someone that can help!

[grinvaldsjanis]

Also there would be possible to figure out algorithm of registering severe accidents for example if phone feels very hard deceleration, but user is not responding to phones questions after following stopping of car. We could warn local community that PROBABLY accident took place.

There is some merit in this one perhaps, more so on remote roads

Again I disagree. Again you are suggesting a User have to interact with the device. And again, Waze already has a mechanism in place for it. If there is a hard stop and the User doesn't touch his phone.. Waze is going to see that the averagecspeed for that segment just dropped drastically, and create a jam. WhY does this need to prompt the User for anything OR require extra code/development/and QA time for a feature we already have.

Every single thing mentioned in this thread so far is already handled by Waze learning average speeds!

As for portholes.. come on now.. locals are going to go around them.. non-Locals will likely drive around them also if they are paying attention to the road instead of pressing even more pop ups in their nav app.

I personally vote NO for every feature that has been suggested in this thread. Waze already handles it, and the have better things to prioritize.

Sent from my Kindle Fire using Tapatalk 2

Yeah?! Right! And How about helping? How about not only warn but make impact on road providers, and make other effects unrelated with Your personal, "little world" interests? You will collect cents from little cheaper gas, but not help to someone when accident, not just soft tire or running out of oil happens around? But if such pop-up appears... You could save someone for real. It could also be too far to closest police or ambulance and city "jams", dense traffic. Don't want to inform that road is not only slippery, cobbled, dusty, but real killer for car or trouble some for sleeping baby? I am not talking about holes only. And please take in account development at different countries - absolutely new, reconstructed roads can change to moon surface quite frequently and You indeed will be soon tired to warn about all hazards there. Some situations could be felt by phone and registred...esp. if conditions are relatively permanent.

I really don't wish You to get into situation when You will just wish if such features would be available!

I Don't understand Your worries about extra codes/development if device resources grows every year and I'm sure that also waze enterprise is not getting smaller or less wealthy. Name these better things! Cheapest grocery? Cleanest toilet? - And You'll refuse to push one button to confirm that "This wasn't impact. Everything is ok! Don't send alarm!" and only after powerful (de)acceleration of device and complete stop of vehicle?

We are generating another feature here: First aid sequence wizard/helper. Waze users could use it at very stressful and first experience situation without searching in web or other aid application.

Try to play all possible scenarios and figure out how waze could be more helpful and if it's really so bothering and impossible to implement. I repeat again that some of bothering or "unnecessary" functions could be disabled. But real social users could appreciate these features.

[Scorp42]

Also there would be possible to figure out algorithm of registering severe accidents for example if phone feels very hard deceleration, but user is not responding to phones questions after following stopping of car. We could warn local community that PROBABLY accident took place.

There is some merit in this one perhaps, more so on remote roads[/quote]

Again I disagree. Again you are suggesting a User have to interact with the device. And again, Waze already has a mechanism in place for it. If there is a hard stop and the User doesn't touch his phone.. Waze is going to see that the averagecspeed for that segment just dropped drastically, and create a jam. WhY does this need to prompt the User for anything OR require extra code/development/and QA time for a feature we already have.

Every single thing mentioned in this thread so far is already handled by Waze learning average speeds!

As for portholes.. come on now.. locals are going to go around them.. non-Locals will likely drive around them also if they are paying attention to the road instead of pressing even more pop ups in their nav app.

I personally vote NO for every feature that has been suggested in this thread. Waze already handles it, and the have better things to prioritize.

Sent from my Kindle Fire using Tapatalk 2

[grinvaldsjanis]

people,

for comum peopole to understand, a easy way to solve this and an simple idea:
when editing roads can't we just put the street type as coblbled? This would be easy to set up for Waze and would help a lot on some "historical" ou "not that rich" cities that have cobbled roads (that me and my car hate a lot!).
an exemple: I rather to more 10% more ETA than have to pass on cobbled roads.
Waze, pelase add this feature.

Then, anyone can choose their proper journey. =)
What do you think?

Waze it all! - mpa

Great suggestion! I live in Riga(Latvia/LAT/LV), which is originally ancient town with old-town in the center and many roads there are cobbled, also some major downtown roads are cobbled, but some argues that speed on cobbled roads are lower so usually waze will not suggest to make routes through them. But I also think that in same options window where we chose to not use long gravel roads there could be also option to not suggest too long sections with cobbles or just include cobbles to same preference, but there also must be possibility to show cobbled roads in the map editor.

[mpa_pt]

people,

for comum peopole to understand, a easy way to solve this and an simple idea:
when editing roads can't we just put the street type as coblbled? This would be easy to set up for Waze and would help a lot on some "historical" ou "not that rich" cities that have cobbled roads (that me and my car hate a lot!).
an exemple: I rather to more 10% more ETA than have to pass on cobbled roads.
Waze, pelase add this feature.

Then, anyone can choose their proper journey. =)
What do you think?

Waze it all! - mpa

[grinvaldsjanis]

If running Waze had any potential to contact authorities simply because I didn't dismiss a pop up in time.. I'd stop using it IMMEDIATELY.

When I drive, I don't talk on the phone. I don't text, I dint interact with Waze or any other app. To require me to do so is a safety concern. Not only tot me, but for every other driver and pedestrian along my route.


With that said, I think this thread was a good discussion, but I don't think I need to spend any more time in it. Cheers!

Sent from my Kindle Fire using Tapatalk 2

We are running in circles here. As I said, if we talk about smoothness of road or potholes, waze could record only similarly, repetitive patterns of same segments of road. In such solution You must not talk or push something on phone.

Vote for This feature on uservoice!

Other case is when possible impact and following complete stop of vehicle happen. You should be able to respond on phone's dialog... phone could also make signals and flash to attract Your attention to make You answer. Anyway - it must be clear that You are not driving, vehicle is not moving - accelerometers are still, gravity sensor is still, gps data same for some minute.

Vote for This feature on uservoice!

[Scorp42]

If running Waze had any potential to contact authorities simply because I didn't dismiss a pop up in time.. I'd stop using it IMMEDIATELY.

When I drive, I don't talk on the phone. I don't text, I dint interact with Waze or any other app. To require me to do so is a safety concern. Not only tot me, but for every other driver and pedestrian along my route.


With that said, I think this thread was a good discussion, but I don't think I need to spend any more time in it. Cheers!

Sent from my Kindle Fire using Tapatalk 2

[dmcconachie]

You see no merit at all in the auto reporting of an accident on a quiet rural where no one else might come across it?
Waze most definitely does not already handle that!

[dmcconachie]

Screaming? So You don't want to be warned about cobbled surface? Even in foreign city/town?

No, my eyes do a perfectly good job of that.

Application could warn only about highest level problems on road. You see, in turn we would release users from imputing Alerts about situations which phone can notice it self.

potholes that just wobble the car should not be reported. Those that are wheel-breakers you're likely to avoid and report manually so anything automatic wouldn't help.

Also there would be possible to figure out algorithm of registering severe accidents for example if phone feels very hard deceleration, but user is not responding to phones questions after following stopping of car. We could warn local community that PROBABLY accident took place.

There is some merit in this one perhaps, more so on remote roads