Lysdexia Eht
My feedback
5 results found
-
316 votes
-
300 votes
An error occurred while saving the comment -
2 votes
An error occurred while saving the comment Further to this, the two pictures linked is as I imagine how the editor could work.
When you select a node, two checkboxes are visible. One for traffic lights, the other for lanes.
When you select traffic lights, the nodes on each segment are already flagged as being controlled by traffic lights, no other action is required, and a 30 second penalty is added to that node for routing purposes. Beyond that those nodes will over time calculate time of day penalties based on real traffic wait times (granularity is up to Waze, 30 second, minute, quarter hour, half, or full hour etc).
Lane Guidance would become available once you select a segment and is visible as a button with a separate simple editor window only offering lane choices through combo boxes (number of lanes) which populates a series of lane comboboxes with arrow choices.
The greatest problem facing development is the UX of implementing lane guideance, this could be a representation issue, next to the arrow comboboxes the direction of travel related to the arrows may need to be represented such as A -> B or B -> A (vertically) independent of the orientation of the editor window for the segment being edited which will imply editors can adjust their orientation properly ... similarly only offering 4 directional arrows would only be necessary, being left, right, up (straight), and U-turn.
Permitted turns on the node (existing implementation) would augment the lane guidance, for example in the linked example there's a left turn permitted, but the left turn is a straight arrow, meaning it would direct users to the left straight lane to turn left (represented by a straight arrow with a left arrow branching off) but from an editor perspective it would simply direct people to only add as straight not left arrow.
-
1,545 votes
AdminElla (Waze Team) (Admin, Waze) responded
An error occurred while saving the comment If this is meant to be working, it didn't on a recent drive. I routed and panned the route prior to losing reception, however around 2 hours later towards the end, tiles had failed to load with the final 30 minutes or so a patchwork of missing tiles. This was an approximately 40km mountainous road.
-
54 votes
An error occurred while saving the comment Found this old suggestion and decided it needed some love as I was about to come and post something similar.
We really need the tiles for the route to be cached while the route is active, and also record GPS track so that if cellular reception is lost routing still works, and when reception comes back, the GPS track can be sent to the servers for traffic reporting etc.
This would be great, having a standalone rest stop category with facility options (toilets, showers, undercover, etc) as well as any restrictions (truck only, car only, etc) could then be combined with an in app option to "Find nears rest stop, include X feature" or have an on screen indicator that shows the rest stop and its features on map.
Next to finding where to go ... finding somewhere to stop along the way can be equally important at times.