Waze is the perfect platform to inform drivers of the speed limits. More importantly it is a platform to inform of changes to speed limits with the exact location marked by a POI. In rural Texas it is not unusual to see a speed limit change from 70 mph directly to 45 mph. A ticket for driving 30 mph over the limit can hit you pretty hard. It would be nice to be warned in advance of a change. I had a speed limit change notification on my Becker GPS as a POI function. That one feature was one of the most used as I do a lot of rural driving.
It would also be nice to be warned of speed creeping upwards of 5 mph (or any driver adjusted level) above the limit. Other GPS devices only mark major highway speed limits. Waze can do it for every street with a simple change to the database.
I’m thinking Waze is the Killer App for this ability. You don’t have to send people all over the world to gather information. You have us out here ready, willing, and able to do it for you.
Thats the other nice thing about databases, data does not always have to be populated. Null or missing values can be assumed, similar to the current values they ‘assume’ when you currently add a new segment.
Not really, there’s no real issue with assuming the road type, routing speed, state, city or even name for a new segment. But if the server assumes the speed limit is 60, shows that on the client and you get stopped for speeding in a 30 you’re going to be pretty angry at waze!
Who do you propose fills map data? And maintains it? Because unless it is correct it’s useless! :ugeek:
Why do you expect user provided data to be incorrect by default? Yes, some people will probably set wrong limits, just like they map wrong turn restrictions or driving directions. But I am positive that the vast majority of wazers would give their best to provide correct data and to correct wrong values, just like we correct other map problems right now. Speed limits could not really be abused for vandalism but any wazer could wipe out whole cities in the editor and thus cause much greater damage.
Have a little faith in us non-waze-champs and non-mega-mappers…
If the speed limit data is only used for displaying it in the client and not for routing calculation, we don’t have any problems when data is incomplete, everything would just be as it is now where no data is available. And Incorrect data? What if the speed limit is reported as 100 where it actually is 50? Well, what if Waze tells you to turn right when there is actually no junction? Would you jump off the road? I guess most Wazers are smart enough to rather report a map error in either case…
I don’t think that speed limits is a must-have feature, but I don’t detest it like other people seem to do. Besides, other navigation softwares I know (e.g. TomTom, Navigon, …) do indicate speed limits. I know that this is not an argument to implement it in Waze, too, but it wouldn’t decrease Waze’s attractiveness either.
I don’t, that would fall more under the “incomplete” concern. Waze has been running for 3 years now and there are some vast pockets of incomplete data.
I absolutely do, of course! Would not be here if I felt we had to do it ourselves!
I refer to my reasoning above, if waze makes me take a wrong turn then I tut (or swear), correct myself and carry on. If waze tells me I’m in a 60 zone and I get ticketed for speeding in a 30 then I face a material detriment due to waze. That’s asking for trouble!
Don;t get me wrong, would I like to see it? Yes. Do I think Waze are considering it? Yes, I believe it’s under consideration. Does not having it detract from Waze? No, not really.
Agree with Darren here. It’s a good idea, don’t get me wrong, but adding the data and maintaining it may be too much. Plus the whole “waze told me to do 70 in a 30 so I did and filed a lawsuit” thing.
I’m having a hard time figuring out why “waze told me to do 70 in a 30 so I did and filed a lawsuit” is adding any significant more liability than exists with “waze told me go down this one-way road the wrong way so I did and filed a lawsuit” or even “waze told me turn onto this railroad (pedestrian boardwalk/staircase/runway) so I did and filed a lawsuit.”
Yes they area risks but there is an element of, “look out of your window” to those errors! It’s not always obvious when you’re driving what the current speed limit is, if waze explicitly tells you it’s 60, why wouldn’t you believe it? If waze explicitly said “Turn up this one way road” or “Turn onto the railway” and you do it, you’re going to have a tough time convincing any judge that it was a satnav’s fault!
Having the actual road speed data for segments might be useful. Same way that people on a bus contaminate data, speeding also contaminates it, skewing averages.
If two people drive across a segment at the legal limit of 100 kph and two at 20 kph over the limit, the average for the data is skewed upward by 10%.
In my opinion Waze should then know that if the allowed limit is set, to use that as a cut-off for the stats, or to discard the contaminating data.
The added benefit is that drivers can also then use that info if it is available.
No matter what, it is still ultimately the drivers responsibility to adhere to local laws, hence all the disclaimers should state that. Has anyone read Http://www.waze.com/legal/tos ?
A gentle reminder about speed limits is like a nagging wife: irritating for most of us, but a very important ‘handbrake’ for some (read most) of us males.
Typos courtesy of SlideIT. Posts courtesy of Tapatalk. The waffling is my own doing.
I’m so sure that this is the best way to go. Around here, I always get the feeling I am contaminating the data because I actually drive the speed limit. You would be eliminating an awful lot of data if you discarded data with speeds above the speed limit. The average speed data from the old cartouche was frequently quite a bit higher than the speed limit around here.
You wouldn’t discard the data, just truncate it at the speed limit. ie someone travelling at 80 on a 60, the data used for averages from that driver would be 60. It’s actually a good idea and been suggested a couple of times before. But it still has that massive data requirement and maintenance!
It was also frequently wrong and horribly skewed by editing (eg stretching of segments). The speeds that were visible in cartouche were not those used by the server!
In my experience, on most roads it seems that drivers think the speed limit is the LOWER limit and not the UPPER limit :lol:
If I had two muti-hundred mile highway routes to chose from (assume same milage) and both had speed limits of 55, I’d still like to use the one that had a “real” average of 57 over the one that had an average of 56.
If we truncate at the limit we may as well just use the limit, and then we may as well use an old sat nav. Yes, for roads with actual speeds lower than the limit we’d still get benefits., but that is only part of the picture.
Then it would have to fall back to an advisory or warning. At the very least the current data could be rounded down to the nearest 10mph as a base. Encourages users to push incorrect and weight it towards “my current speed”. Does that make any sense?
