The problem is, where to get the data from, and who updates it. Everything currently in the map, can over time be determined by watching people drive. But speed limit is not (as some people speed <gasp>).
And after all the work to enter speed data (segment by segment across the continent) and keep it current, how useful is it really, when the signs are already right there on the road where the Wazer is? Other than putting up a warning when exceeding the speed limit–which I expect many users would disable immediately–I just don’t see a very big return on investment, when that time could be spent solving existing URs, making sure the highways are navigable, labeling ramps, etc…
Then there is the added liability. We already have cases of people suing GPS companies for driving them down unimproved roads, or into a river. Even with the disclaimer that no one reads, there might be just a little to much added liability here, for what has been pointed out, little return.
If not in town, then according to the segment type and to the country, the speed limit is easy to find for “deafult” value. Is there is a special road with another limit, AM are there to change them.
If in town, the speed limit is easy to find as “default” value, according to the country. And if there are some streets with special limits, AM are there again.
In the US where each state sets their own “defaults” and then the individual counties and cities may have their own on top of that.
And as a person who may take the speed limit as an, um, suggestion sometimes, if Waze made a noticeable effort to tell me I was over, I would quickly tire of it and want a way to disable it. I can see users actually stop using Waze over something like this.
We have a problem in the US where some speed limits are set artificially low and easily 80% of traffic travels at 10mph over the posted limit.
Learned at the Palo Alto meet-up (side conversation with Ehud, Waze founder and CTO). Waze is considering adding speed limits in the future (at least in the United States). They consider it a safety feature.
Also, they are looking into whether they can implement with some existing data. Not clear if this import will be a one-time thing and then Wazers will be responsible to update or whether it will be a full external source with updates.
Also not clear on the time line of this feature.
There was a general - if the back end database needs to change for any new features, this will push these types of changes to > 6 months out. Waze is re-working the infrastructure to allow for a new tile updating system. This is expected to take some time…
BIG NO! I disabled this on every gps I used so far - not because I speed all the time, but because the continuous false alarms this feature gave. Of every map, speed seems to be the first part that is outdated. Housenumbers is less work than this - housenumbers tend to stay over the years. Speeds tend not to.
Given that all the big map-providers have a lot of problems doing this right I am very sceptic that Waze can do this by means of importing, regulary, of updated speeds from a mystical, all-knowing source of speeds. Waze may get some data from some source and then rely on the crowd to set and keep it right.
If I understand correctly, for each road, Waze keeps a record of the the average hourly speed. They could use the maximum hourly average to estimate the speed limit. Based on that, like somebody suggested a few weeks ago in a post, change the color of the speedometer to let you know that you may be above the speed limit (green if you’re at or bellow the speed limit, yellow for 10% above, etc.) That’s less likely to create problems than displaying an incorrect speed limit on the screen.
While I agree that the “average speed” is nowhere near the true speed limit, I think that iahim’s point may have been that the “average speed” data could be used as a temporary initial value in the database for the new “speed limit” field, until such a time as the AM’s and other editors can get the true speed limit values entered for the segments in their areas.
Sorry, I don’t agree with using anything other than the actual speed limit data. You absolutely can not present an estimated speed limit as the ‘speed limit’. That is wrong.
So you are going to tell the police that pulls you over for speeding: ‘I am using Waze and it says the speed limit is 52 mph.’ The police will respond: ‘oh really, isn’t that the free gps software that lets you report our speed traps, distract you when driving, and now makes up the speed limit? Well since you are so smart and the speed limit is actually 25 mph on that last curve I’m going to write you up for speeding, wreckless driving, and texting too. How about that!’
My point was that Waze could do something to help the drivers with the data it already has. Seeing a red speedometer would make you slow down and look for a real speed limit sign on the road. I’m 100% against displaying a speed limit on the screen because it could be incorrect. It’s just impossible to keep up with all the speed limit changes, especially temporary changes during road work.
Adding speed limit data is a good idea, it will allow for more accurate initial estimates of travel time (though it needs to be able to dynamically update for those of us who do speed). And contrary to the poster above who dislikes GPS devices that give the speed, I really like them. I mount my GPS on my windshield or dash and that puts the screen and my travel speed closer to my field of vision than the speedometer.
The warnings can be helpful for people driving in a new area who might have missed a speed limit sign and not realize a change in the legal limit was just made. Also having that data, with those warnings helps us to see where more corrections need to be made. That was one really annoying thing with my last GPS before I discovered waze, there were so many wrong speed limits encoded that the data was often of little use.
But with Waze we can get the warning that we’re traveling 50 in a 25, see the sign on the side of the road saying the speed is actually 50 and fix it. (A very real and specific problem with my last device. I tried reporting and fixing it through that GPS provider’s site but two quarterly updates had passed without it being fixed.)
I know I’m new to the forums but I feel this would be a very valuable addition to the system. And showing the limit on the screen can both warn a driver of a changed limit, warn them of the fact that they are going rather fast, or let them know the data needs to be fixed and fix it. As to keeping up with temporary changes, why is that any harder with keeping up with any other temporary construction issues? A one day slowdown wouldn’t need to be posted but a multi-month construction project like I constantly see warnings for is no issue. And frequently changing roads is why we love the ability to edit in waze.
I also think that it would be a very useful feature to be able to set a speed limit for raods in the map editor so that the client can display warnings when you’re going too fast. Most navigation softwares do this and I like that. The user could set the level of warnings to recieve e.g. “voice alert”, “visual information” like a red speed indication or “no warnings”.
Living in a country with highways without speed limit (don’t forget to implement the “infinite speed” option in the map editor ;)) I enjoy fast driving, but there a high penalties for speeding and not all speed traps are reported by other users. Plus, we have the lovely ProViDa (Proof Video Data System): police measuring your speed from civil cars. You can’t report these on Waze. :roll:
So in case I missed the speed limit sign and I don’t know wether I may go 100km/h, 130km/h or whatever I please, it would be really cool if Waze could remind me!