When I drive my car, sometimes I exceed with the throttle and I reach a speed too high. Why don’t we add a field in the edit menu where we can add the speed limit for that road? This limit shuold appear on the screen when we exceed.
The second suggestion is about altitude: I know the gps receive 3 values (lat, lon, altitude), so I thought than is possible to use the altitude to implement an auto-level between two streets. If the altitude is the same, the street are in the same level.
I agree. Unless i’m wrong, i thought traffic is is signaled by some algorithm of how long you’ve been under the average speed for that specific road, probably other factors as well. The problem is if this average speed is just from the users that have driven the road. It could either be too fast or too slow depending on how they drive. So i agree it would be nice to set an speed limit for any road you would like.
We are looking to collect the altitude (z) parameter as well.
Regarding the speed, usually it’s associated with road type. While we did consider adding it, it’s more or less a constant in most cases and as we want to provide information based on the real driving information, the calculated average is a better indication. If there is enforcement, most people will drive the limit, but where it is customary to drive somewhat faster (as an example, tickets are given for speeding 15% above the limit), we want to be able to adjust to that and provide the commonly used information.
Well…that is great unless you end up with erroneous average speeds like in this segment.
http://www.waze.com/cartouche/?zoom=6&lat=33.05681&lon=-97.01196&layers=BTFTFFFFFFTFTTFFTTTTTT&seg-1=46155639
Or this segment.
http://www.waze.com/cartouche/?zoom=6&lat=33.0568&lon=-97.01196&layers=BTFTFFFFFFTFTTFFTTTTTT&seg-1=46163783
This value in the speed field you can ignore. It’s not used anywhere and indeed it’s an error since it is affected by the editing of a segment (I.e. if this segment was changed, it’s length was changed and hence it’s speed was altered since the time it took to drive it is a constant). We’ll either correct it or remove this field all together.
Also, the gps altitude is notoriously poor. Especially for small differences in heights, like between roads. Often people who want some altitude that is reasonable use a gps device with a built in altimeter rather than relying on the gps altitude signal. (or use differential gps with a known altitude as the reference.)
We can use an option in the client to choose betwen “Respect the limits and save money” or “Don’t care about the limits” and continue to collect data for average. I can receive an alert when I encounter traffic (speed below the average) and when I exceed whit speed (speed above the limit).
even if the altitude could not be used to diferenciate two crossing roads, you could record this parameter, in order to make a 3D map in the future. For example, lets say that I want to go to a mountain… if you see that all the road you get higher and higher altitude, you could draw in a 3D map as a mountain
It’s better to record more data, becouse recording the road information it’s not easy, and we don’t know future applications that we could use…
It’s only a opinion
Regards and sorry for my bad english
That’s a very cool idea, and your English is fine 
In fact, I would say probably use it only for this, and not for bridging… the smartphone GPSes are hardly good enough for mapping in two dimensions! :lol: However, in the case of tracking general elevation changes, this would be really cool if Waze would ever want to do a 3D map that you could zoom out on, showing kind of the elevation cross section of parts of the world.
We are looking to add the altitude collection as well (if possible)
great, I agree that it won’t probably to accurate but as the rest say… just to see the map in 3d would be lovely… something like navigon have in their newest:
Note that GPS accuracy for altitude is worse than it is from a horizontal view just because of the nature of getting position from satellites overhead.
Wow, that looks really cool… (btw, nice car! 
My brother just got a '95 940, I love it!)
Of course the altitude calculated by triangulating your gps position is going to be inaccurate, trying to figure that out from satellites in orbit can’t be easy… but then again… Nothing said anything about it having to be exact at this moment, and to be honest, most phones isn’t that accurate at the normal x and y coordinates either, but for a simple 3d map it’s enough to take the median from the runs and hope that is about right! to make a map that shows some mountains etc.
I hope no one is trying to land airplanes using waze… not yet anyway!
Without speed limits shown on the roads, when you’re travelling at 30 mph in a 60 mph zone then you expect that there is something wrong with the traffic! Yet as this is an acceptable speed limit on some roads, will other get confused that the car travelling at 30 mph is supposed to be doing 30 mph, ie its driving on a road with a 30 limit instead of being stuck on a road with a 60 limit behind a tractor doing 29mph?
Because the majority of travel on that road will have happened at 60 or 70 mph, setting the average speed. A road with an established average speed of 65 mph is going to throw traffic alarms for someone going 29, whereas a road with an average speed of 30 mph will not throw the alarm for 29 mph.
Regarding Speed Limit:
The algorithm for traffic calculation can remain the same. The driver just wants to know what the speed limit is for a particular segment so that he/she can choose to either obey the speed limit or drive with the flow, and this can be accomplished by storing speed limit data and simply displaying it on the main nav screen.
Regarding Altitude:
Nothing needs to be done with the altitude data just yet. The driver just wants to know his/her current altitude when driving in mountainous terrain, and a guess would be just fine (since smartphone GPS altitude data is inaccurate). Displaying the estimated altitude on the main nav screen, without storing the data, would be just fine.
In another navigation app I have used, a speed limit sign appears on screen, showing the posted limit on the road in which you are traveling. Nice!
Even nicer is that when you exceed the limit a little, the sign color changes from white to yellow.
If you exceed by over 10 mph the sign changes to red.
I love this feature, and am hopeful the Waze could add a similar feature sometime in the near future.
Not to be rude or anything, but do you have a suggestion on how to get that speed limit data and keep it properly updated without requiring more effort from Area Managers (who already have a pretty big amount on their plate) and while still keeping this application free?
Not sure how other apps do this, but the data is “out there”.
I do agree that putting that responsibility on map editors would be too cumbersome and also prove inaccurate and faulty.