Speed Bumps

[saltyone]

I understand at the moment that there is not a method (even map editing) that would allow a user to warn other users that streets are loaded with speed bumps. I would like to suggest that Waze resolve this by allowing users to edit the map to indicate speed bumps. I recently had the unfortunate circumstance to be on a route (inner city) where the entire route kept me on one street for 3.5 miles each of the alternative routes also were speed bumps its a residential area but there are streets that do not have these bumps and it would be nice if Waze could point those streets out. Nothing like bouncing down the road at 5 miles an hour to make your day. Thanks

[porubcan]

most probably there is one possibility how to deal with it.

routing server is giving 5 sec penalty for each junction which is on the route when choosing the best.

example:
there are two routes with similar physical lenght with different number of junctions on them:
Route A: 15 mins of travel + 1 mins total penalty for all junctions on it
Route B: 14 mins of travel + 3 mins total penalty for all junctions on it
In client in alternative routes it should look like:
Route A: 15 mins (preffered )
Route B: 14 mins (as alternative)

note: the travel duration is based on historical data of average speed, which should take into account also time of the day/day of the week.

note2: possibly there are also other factors taken into account, like street types (FW, major/minor HW, etc.)

so you may try to manualy add junctions on the segments with bumps in order to get routing server to penalize this route more.

please correct me if I wrote something wrong.

[gerben]

The additional junctions will only have a 5 sec penalty as long as there is no historical data. As soon as drives are registered, it will penalize the junctions for the actual time it takes to pass them.

Best is to leave the road as it is. As soon as more data is gathered, Waze will know it is a slow road, and will try to find a faster route (which will probably be a route without speedbumps).

[porubcan]

is there any difference regarding penalties when:
1. ETA is calculated?
2. best route is being selected?

I thought, that penalty is still applied for 2, but is not affecting 1.

[AndyPoms]

There is already another (much longer) thread discussing this over here: viewtopic.php?f=10&t=20602

Basically, Waze will know the street with speed bumps is slower than the street without (after people drive it so Waze has speed data for the street), so it is unnecessary to map them.

[Kulg]

I'd like to see speed bumps added to the Maps and an option in Routing to avoid them.

They basically waste allot of fuel & wear out my car over and above making the road very slow to travel. This is why I think it would be a very useful feature to have!

[palmerit]

I think the point being made is:

Speed bumps serve one purpose. To keep traffic slow. As soon as Waze has enough statistical data about the road, it'll already determine that the road is slow and route you along faster roads. In a nutshell, Waze doesn't (and shouldn't) know WHY its slower, just that it is.

Think about it. If we start with speedbumps, where does it end? Its just more data to enter, verify, cross reference, and maintain for no real additional value.

Should we mark pot holes? Stop signs? School zones? Pedestrian crosswalks? Puma crossings? Etc. Etc. You get the point. The system just needs to learn the average speeds.

Sent from my Kindle Fire using Tapatalk 2

[Kulg]

I think that just Speed Bumps should be entered.

The streets that have these speed bumps are not that busy because of the bumps so the statistical data isn't that good for them. For this same reason I see Waze recommending speed-bump ridden routes to me all the time which makes the routing frustrating and counter productive. As an example on my way home every day there is a road that sees little traffic because it has 16 speed bumps! Waze recommends it most days as their isn't much traffic on it. Due to the low traffic stats don't show it as a slow route but with all those speed bumps its way slower than alternate routes in heavy traffic. (I actually measured & compared this route in particular).

So in short I think Waze will be a better routing system working far more accurately if speed bumps are taken into account and routes known to be slower with them.

I think the point being made is:

Speed bumps serve one purpose. To keep traffic slow. As soon as Waze has enough statistical data about the road, it'll already determine that the road is slow and route you along faster roads. In a nutshell, Waze doesn't (and shouldn't) know WHY its slower, just that it is.

Think about it. If we start with speedbumps, where does it end? Its just more data to enter, verify, cross reference, and maintain for no real additional value.

Should we mark pot holes? Stop signs? School zones? Pedestrian crosswalks? Puma crossings? Etc. Etc. You get the point. The system just needs to learn the average speeds.

Sent from my Kindle Fire using Tapatalk 2

[javieruriona]

Hi everyone,

I am also new to waze and I find it an amazing tool to drive because of the collaboration between the community. Therefore, I believe somehow we should keep improving this tool. I also agree that we should have some sort of "sign" to let us know in advance where we are going to find Speed Bumps, here in Lima they don't only slow you down, they are most of the times a real danger for the car, no matter how slow you would be, besides that, almost all the time an street sign, warning about it, is missing, and it causes serious accidents. So I also ask the programer's team to add a "street bump sign", in which we the users could let the others know if it is a minor one or a really dangerous one.

Thank you for your work,

Greetings.

[xteejx]

You could just slow down and be a more observant driver...

Sent from my GT-I9100 using Tapatalk 2