Yea, but the speed limit may not be the same on the entire road. Maybe it is there, but not here…
Nope, same over here but you’re being picky now! 
Damn straight! Speed limits would be more involved to maintain than commercial POI’s! There are way more road segments that commercial businesses.
If someone from Waze is reading - how many road segments currently exist on the US/Canada server? Tens of millions?
But as I said you could limit it to freeways/highways at this stage.
One of the questions we want to explore at Palo Alto is mass editing tools. Adding speed limits, would definitely be a perfect application for a mass editing tool.
Just allow users to report the location of Speed Limit signs. This would fit in easily with the current Reports function/icon.
This would also address the road construction issue. And if you add an alert feature that compares the nearby speed limit signs to your current vehicle speed, include a setting to tweak when the alert pops up (0, +5mph, +10mph over limit).
Ken
+1
The issue with this is that reports are temporary, speed limits are not. This would require significant re-work for Waze to enable in this manner.
In addition, many roads have different speed limits (city limits, curves, etc.). The Waze map is broken into segment, generally at intersections with other roads. Although this is not always the case since there tend to be loads of extra junctions in base-mapped countries.
Would you expect that if you report a speed limit that it’s only valid on the particular segment where you are located? If so. this could mean having to hit the report button 10’s or 100’s of times in a several mile stretch of road.
How do you suggest speed limits get corrected if they are wrong. Newest report overwrites the previous speed limit?
How do we keep speed limit problems from being reported as a Map Issue / Update Request where the map editors get overloaded with reports of speed limit issues?