reports of "Missing bridge overpass"
As I am editing maps I see a lot of user reports of "Missing bridge overpass".
Usually, there is nothing I can do about the report because I don't see any sign of a Missing bridge overpass anywhere nearby.
Sometimes I can tell that the road has an intersection that should be an overpass with no intersection and I can fix that.
I suggest that there are three major categories of things needing to be reported:
1) immediate traffic problems due to movable objects.
a) traffic problems
b) hazards
2) long term problems due to changes in permissible traffic
a) location and types of roadways
b) allowed turns and traffic direction
3) points of interest (can sometimes effect traffic flows) landmarks
I am torn as how to best handle some things like roadways with underpasses with limited clearance and bridges with speed limits.
In any case, cases requiring changes in long term traffic flow (map errors) need to be clearly distinguished from reports requiring immediate action due to road work, wrecks, traffic jams, traffic lights out, or other 'traffic problems' and 'landmark needed' reports.
The client should make sure that the user understands how to report particular problems so that every UR is informative and useful.
bz2012
shared this idea
AdminElla (Waze Team)
(Admin, Waze)
responded
-
bz2012
commented
type 1 problems should immediately effect traffic routing. These include traffic reports, missing signs, broken traffic lights, weather problems, road closures due to construction.
Some of these are ALSO long term problems, such as road closures due to construction. Sometimes these merit changes to the map, sometimes they do NOT merit changes to the map.
Currently, drivers sometimes make type 2 reports for type 1 problems. This has several bad effects: 1 there is no prompt change in routing, although one is needed.
2 valuable time of map editors is wasted. 3 changes are made to the map that later need to be reversed. 4 by the time the map changes are downloaded to the clients, the drivers are given wrong driving directions.
These problems start with the design of the user interface on the client. That is where the solution needs to start.