A wazer passing the road crew putting up the new sign enters an update request and the speed is changed by the crack area manager before the police have a change to park in the shade of the new sign. Isn’t this how the world works?
Sounds like a Waze utopia to me.
Unfortunately it would be more likely that the user passing by would submit a blank “general error” update request, and then wouldn’t respond to the AM’s “I have no idea what the heck the problem is” email.
If Waze uses a third party source for speed limit data, and can ensure Wazers are not going to be putting in Update Requests to fix it, then Waze should consider.
As stated, I and many other map editors are already significantly overloaded with getting the basic mapping updated to allow for proper routing. So having to update speed limit data on EVERY segment of the road is not feasible.
Really, just look at the posted signs on the road. Isn’t that good enough?
Even assuming it works that way, rather than the way unwallflower describes, those changes go into effect only where there is an active AM who is also able to stay on top of the volume of URs in his area. In other areas, look at the average age of URs to see how long it would probably take for those updates to go into effect…
The other problem with speed limit data is that on many roads the speed limit changes frequently. So even if we as editors could keep up with the update requests, it would be almost impossible to know exactly where on the map the speed limit needs to change. If the speed limit changes mid-segment, a new junction would need to be inserted just for the speed limit change.
Otherwise the presented speed limit will be less than accurate. IMO, it’s more frustrating to have inaccurate information than just not to include it at all.
In Europe we have quite some dynamic speedlimits that adjust to the traffic density (ex. Germany) or weather type (ex. France).
Exactly my point. For example, in the United States there are still millions of road segments that don’t have the proper directionality, city, state, turn restrictions, etc set. To have to populate another field, and go back to every segment that has been edited in the past 2 years to add the speed limit is unreasonable unless there are 50x more active Waze map editors than there are now.
If there were as many Waze map editors as there are people updating Wikipedia, it would not be an issue. But there are not…
Yep, another complication. School zones is another. ‘Speed limit 25, when children are present’.
Different speed limits for different types of vehicles. Speed limit 65. Speed limit 50 when towing a trailer. Speed limit 60 for tractor trailers.
Speed limit 50 mph. Speed limit on this turn 25 mph. Opps, now it’s 35 mph.
I am having convulsions even thinking about this…
I don’t think “it would be hard work” is really a valid argument against it. The variable limit however definitely is!
And what value does this add getting you to your destination fastest (remember, commuter GPS with a focus on traffic avoidance)?
The speed limit sign is posted on the roadway already. It’s not necessary to be coded into your GPS also.
Traffic jams are not posted on the side of the road. Nor is ETA to every destination known to man. Hence the value that Waze provides to get you to your destination via the fastest route, factoring in traffic.
I never said it did but the fact people are mentioning it means on some level some people see it as a requirement, or perhaps a nice-to-have.
It’s just as (un)useful as police reports or speed cams or red light cams but they’re all core parts of the app now.
That said, don’t get me wrong, I do not think it’s feasible to have speed limits!
Just to be clear, that was essentially my point as well.
Yes, agree. The ‘avoid toll roads’ feature is very necessary and affects routing!
Reinforces what I have been saying. There are other features that affect the core functionality that need to be addressed prior to features that are ‘nice to have’. And ‘nice to have’ should not over-burden the editors to keep it maintained.
In San Diego, very few toll roads so it’s bearable. But in other parts of the United States, many more toll roads, toll bridges, etc.
Well, why not implement both at the same time? That way, we would only have to go back to those segments once (to set as toll and set the speed limit) instead of having to edit them twice. 
Although it is 100x or 1000x or 10,000x more segments to edit with speed limit data vs toll road data/checkbox.
How do you define the “whole road route.” If there is a toll bridge on a freeway, what gets marked as “toll?”
So how does this work when non toll perpendicular roads cross through the landmark? What about toll roads that are hundreds of miles long?
I think it’s going to have to be an attribute of a road segment…
A road segment that crosses under or over the toll road. It has to cross the landmark therefore would be mis-classified as toll.
There is no level functionality on landmarks now and that would be mighty confusing.
Indeed… I would have to revisit tens of thousands of roads (let alone segments) that I edited during the last two years. That easily makes millions of roads worldwide.
I’m still not sure that’s a reason not to include this. Are we saying there will never be other attributes to add to a segment?
Even if we limited ourselves to major roads, with the select entire road feature of papyrus it doesn’t seem so daunting.
Just to reconfirm, I don’t think it’s feasible for other reasons listed above but let’s make sure we push it down the priority list for the right reasons!