rocketsciguy
My feedback
70 results found
-
78 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
rocketsciguy
supported this idea
·
-
85 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
rocketsciguy
supported this idea
·
-
99 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
rocketsciguy
supported this idea
·
-
70 votesrocketsciguy
supported this idea
·
-
184 votes
Thanks for supporting this suggestion! We've added it to the WME team's backlog, and hope to get to it in the near future. We will follow up here when we have an update, or need more info from the community.
rocketsciguy
supported this idea
·
-
98 votesrocketsciguy
supported this idea
·
-
273 votes
Hey,
Please note we're changing the status of this suggestion to Currently Not Planned since we finalized our plans for 2024 and this idea won't be implemented this year.
We hope to include it in our plans for later down the line.
Thanks!
rocketsciguy
supported this idea
·
-
196 votes
An error occurred while saving the comment rocketsciguy
supported this idea
·
-
919 votes
Hey,
Please note we're changing the status of this suggestion to Not right now, since we finalized our plans for 2023 and this idea won't be implemented this year.
We hope to have it included in our plans for later years and will keep you posted.
Thanks!rocketsciguy
supported this idea
·
-
17 votesrocketsciguy
supported this idea
·
An error occurred while saving the comment rocketsciguy
commented
Specifically add support for Visual Instructions with road shields in the next turn display, please and thank you!
For better navigation, make the following changes to routing behavior when starting a new drive:
* If the user is on a two-way segment, and speed is less than some threshold, e.g. 6 mph or 10 km/s, and there is no current route, then make the travel direction undefined.
* Upon setting a destination, calculate two routes, one assuming initial travel in the A->B direction, and another in the B->A direction.
* Select the shortest ETA route but keep the other available as a nearby alternate (dotted route with "+# Minutes" indicator)
* Make the initial instruction "Head [Cardinal Direction] on [Segment Name]" or "Head [Cardinal] towards [nearest named segment]" when starting on unnamed segments (PLRs, PRs). The cardinal direction should be calculated from the geometry or junction nodes on the segment nearest the user's location. Better directions when the user is very near a junction node (e.g. on a corner) might be to "lookahead" 30 ft (10 m) and use the name of the segment and closest cardinal direction in that direction.
- Keep the other direction's route available just in case the user decides to drive that way or cannot drive the recommended way, so Waze can quickly switch routes without another computation. A UI button to switch driving direction may also be helpful in some cases.
- Once the speed is greater than some threshold (maybe 12 mph / 20 km/s) or the user has traveled some distance (maybe 50 ft / 15 m), drop the alternate route and proceed with normal driving behavior.
This "start driving" phase would provide users a more clear set of initial directions and better ETAs in many situations, for example, when starting from residential driveways or parking lots where they may drive in either direction without difficulty, or on two-way streets where U-turns are not difficult.