whoaitspete
My feedback
55 results found
-
87 votes
We are looking to feasability for this suggestion and will update when we have some answers.
whoaitspete supported this idea · -
429 voteswhoaitspete supported this idea ·
-
40 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!
whoaitspete supported this idea · -
19 voteswhoaitspete supported this idea ·
-
17 voteswhoaitspete supported this idea ·
-
252 votes
Hey!
Thank you for this suggestion.
This is not a priority for the team at the moment and we won’t move forward with it.
We encourage you to keep on coming up with great suggestions
Best,
An error occurred while saving the comment whoaitspete supported this idea · -
500 votes
Hey,
Please note we're changing the status of this suggestion to Not right now, 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!
whoaitspete supported this idea · -
26 voteswhoaitspete shared this idea ·
-
45 votes
Hey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it.Please note there is no ETA for it yet.
Best,
Heziwhoaitspete supported this idea · -
86 voteswhoaitspete supported this idea ·
-
85 votes
Hey,
We have looked at this suggestion, and in order to make some decisions about it, would like to kindly ask you to provide us with more data about it.
Please share some examples for when and where this restrictions apply? (use cases)
And any country you know relevant for it.
Thanks!
whoaitspete supported this idea · -
53 votes
Hey !
Can you please share some more details and examples for this issue which you would like to address in this suggestion?
This will help us to better understand what will be the best solution.Thank you
An error occurred while saving the comment whoaitspete commentedHere is an example: https://waze.com/en-US/editor?env=usa&lat=42.71186&lon=-73.81114&marker=true&zoom=5&segments=65278838,75894143
In this situation, Waze wants a user to turn left out of the parking lot road (sometimes a difficult turn) and use Wolf Rd to head to the second segment. This is a 0.8 mile route with 2 traffic lights on a heavy-traffic road.
In reality, turning right (rarely has a wait) and taking a route through the PLRs to the roundabout is quicker at the PLR's real-world speed limit (and likely even faster when considering real-time speeds), has only one stop sign, and is 0.6 miles (0.2 miles shorter).
We would not want to use a local street here, as that could potentially cause shortcutting through the mall's property between the roundabout and Wolf Rd (and vice versa). A private road would also not be appropriate, as that will cause a double penalty since another road type transition is added. These outer roads have no parking spots, but are set as PLR because that PLR penalty is needed - it would be great to have a way to tell those segments to use real-time data over a set speed (especially when the PLR set speed here is less than half the speed of the speed limit) while keeping the road type penalty. This also has the bonus suppressing traffic displays, which we don't really need to see once already on the mall property.
whoaitspete supported this idea · -
66 voteswhoaitspete supported this idea ·
-
46 voteswhoaitspete supported this idea ·
-
6 votes
Great thinking! We’ll share with the team; they’re always interested in new feature ideas.
whoaitspete shared this idea ·
@YogiJB Yes, but it appears as just another normal lane. That is not preferred when the lane shouldn't be used by most drivers. We would like to have a specific marking to indicate that the lane is a bus, motorcycle, HOV, etc. lane.