Please add.

The easiest temporary solution would be to add the time zone (EST, CST, MTN...) to the departure and arrival times listed. This would make it so you can easily see what your looking at and make the proper adjustments to departure times.

It would also be helpful if there were a banner or alert in the planned drive section warning about this.

This would be incredibly helpful cuz I run into this same issue all the time!

Since this has worked so long one way, it might introduce problems to suddenly change it. Here's my recommendation for fixing this. In any route that crosses a time zone boundary (or which includes a "trigger" tile that indicates that the time zone may be uncertain), simply append the time zone to the expected arrival time.

As the time and time zone will change when the user switches cellular towers to one in the different time zone, the expected arrival time will always be valid, in that users can make the adjustment, when they see that the "wrong" time zone is used, without confusing users who already knew that they needed to make an adjustment.

I regularly travel between Indiana and Illinois. It would be great to not have to constantly do the math to know what time I will be arriving.

Garmin GPS did this 10 years ago, why can't a tech app do the same?

Would love this option.

Yes!

This is a no brainer!! Airlines do it and so should all gps.

Silly. Arrival time should always be arrival time locally at the destination Either way currently it is unacceptably unclear and took a fair amount of digging to figure out the current behavior. When you enter a trip across time zones, either way there should be a comment noting this and saying how it's treated.

Exactly, this is such an inconvenience. It's so frustrating please do something about this.

Compared to the parking lot area "feature" that was rolled out this would be a great addition to the app. Understand that some developers aren't in the situation where multiple times zones affect their drives but the whole planned drive doesn't work well if the destination is in a different time zone.

Suggest use this
"Arrival Time Should Reflect Destination Time Zone"

https://waze.uservoice.com/forums/59223-waze-suggestion-box/suggestions/2772849-arrival-time-should-reflect-destination-time-zone

What kind of GPS app doesn’t understand that you need to know your arrival time in the destination’s time zone? This shouldn’t be a request, it should have been a core feature. Every other gps app works this way. Absolutely absurd, Waze.

This really needs to be a thing…or at least indicate the time zone that the the arrival time is in. I’m struggling with my departure time for this very reason.

easy enough to add an exclusion zone for border counties and flag them

So many votes for such an obvious oversight. Mind boggling that Waze has been too lazy to fix this. ESPECIALLY when sharing my drive with someone in that other time zone. It confuses them so much.

PLEASE ADD THIS ASAP. CAME ON SUPPORT BOX TO FIND/REQUEST THIS SPECIFIC FUNCTIONALITY!!!!!

You would think that Waze developers live in a country with only one time zone. ;-)

Such a major bug and presumably simple fix that I've been reporting for years. It makes the arrival time useless when travelling across time zones. I'm sure many people who don't know about this bug make plans with friends at their destination in a time zone east of theirs not knowing that they'll be an hour late until it's too late.