R4CLucky14 wrote:There's no sensible, smart way to implement it. And as others have said, there's no real gain from it, except headache.
Nice hyperbole, except there's a difference, those are things you cannot see "from a distance" that AFFECT ROUTING. Speed limits are not.gordonski wrote:bgodette wrote:There really is no gain from adding this, and a long list of downsides, chief amongst them the liability exposure and additional work needed to maintain that data. Get your speed limit information from where your attention should be, the road.
And get your information about dangers from there, too? Restricted turns? Watch the signs! Traffic jams? Keep a look ahead! ...seriously?
Thank you for listing seven reasons why this is a bad idea and effectively impossible to implement without giving wrong information, let alone actually keep the information current.gordonski wrote:I could do my daily commute completely without the assistance of waze. But it's meant to maker things easier for you. I never drove myself in the US, so I'm not sure what it looks like over there. Here in Europe we have roads where speed limits vary a lot. Outside of cities Germany has a general speed limit of 100km/h (~60mph). But these streets could also be limited to any lower value. Furthermore streets with two lanes per direction or where lanes have constructional separations, the limit is 130km/h (~80mph). In cities the general limit is 50km/h (~30mph) except for multilane roads or seprated lanes where it can be up to 70km/h (~45mph). On highways there's no general limit. However there are many sections which are limited. We also have dynamic limits, which are set automatically or manually when traffic increases, or visibility decreases. Sometimes with individual limits for each lane. On 10 miles of highway the speed limit may vary from 60km/h (~40mph) (road construction) to "whatever your car can do". But few hours later the maximum limit could be only boring 120km/h (~75mph).
If waze offered a feature to inform you about the current speed limit, I'm convinced that over here many wazer would use this feature. I definitely would!
So why add something with the appearance of official information, that WILL BE WRONG? Bad information is useless to the driver, is just noise and will be ignored as demonstrated by EVERY navigation device/app that has added speed data.gordonski wrote:Everyone knows, that waze doesn't offer any official information. When you drive too fast because waze told you so and you get caught, it's still your own fault, just like it's your own fault when you take a disallowed turn or go the wrong way in a oneway street. Waze is an assistant, not an autopilot or a controller you must obey in any situation. I guess this is clear to all of us.
It's not resentment, it's resistance to the cold hard realization that it will fall on the community editors to maintain something that adds zero benefit to Waze's primary focus of traffic avoidance. The data will be wrong the day it's imported from whatever source, and will be a Sisyphean task to keep it up to date, all so the driver doesn't have to actually look anywhere but the bumper of the car in front of them.lchamp423 wrote:It seems that the thought of this causes a lot of resentment among the old hands here, ...
Lancaster may be free of UR/MP but this is far from done:ryryryry87 wrote:There are no known (to me, yet) issues to the map in my city, and I constantly look on the map for stuff to do. I am bored because I just wait for URs so I have something to edit. If I had speed limit data to input, I would have something to do with my free time again
Is it?CBenson wrote:Well if Lancaster is routing finebgodette wrote:Lancaster may be free of UR/MP but this is far from done
Being clear of UR/MP only means they're being closed, not that it's free of routing problems. RevCon on a one-way, along with wrong-way speed data.CBenson wrote:aren't you simply showing that node clean up isn't necessarily needed.
dmcconachie wrote:luftms wrote:I agree!
Users browsing this forum: No registered users