Skip to content

Tyler Russell

My feedback

4 results found

  1. 24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Tyler Russell commented  · 

    Bottom Line: Use data already being collected by Waze to get you home faster based on a forecast rather than current traffic conditions

    Summary:
    While traveling with Waze, I usually pick the route that will take the least amount of time to get home initially. I have noticed that there are nodes (decision points) at which I should either change my route or stay on the originally chosen path based on both current traffic AND how much I anticipate traffic to change between now and arrival.
    Should I stay on the highway and main road knowing it will likely get slower in the next 10 minutes or drive slightly further out of my way, but having less forecast traffic enroute?

    I know that Waze can update you based on the current traffic conditions and recommend a re-reroute. I would like to see a forecasted route guidance feature. I usually check Waze to re-calculate my best route several times while driving and manually note the changes among the three proposed routes to my house. I then recheck a few minutes later so I can see how much each route option has changed in the last few minutes of time. That rate of change noted for the time to destination on each route (usually traffic getting slower at rush hour) will lead me to guess that in the next few minutes things will either be better or worse that what is noted in the app.

    It would be nice if the app would recommend a route that currently takes longer, but accounts for that anticipated rate of change automatically (i.e. I know that when I get to the choke point in traffic 10 minutes from now the traffic will be longer than the current projected 10 minute delay, maybe 20 thus making another option the best choice). It seems with all the data, an algorithm could capture this live change and maybe even reference historical data to estimate which path to take.

    Tyler Russell supported this idea  · 
  2. 916 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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!

    Tyler Russell supported this idea  · 
  3. 1,728 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Tyler Russell supported this idea  · 
  4. 1,262 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Tyler Russell supported this idea  · 

Feedback and Knowledge Base