For all the cool things Waze does, this one is so basic and needed. At very least add a reminder or notification that time zone is not factored in so we are aware and not arriving late to places! This has caught us off guard a few times and is frustrating.

If my GPS can do it why can't WAZE?

Have app adjust and project leaving and arrival times per time zones

I have used the planner in my local time zone and it worked pretty well. But the first time we planned a trip from Central to Eastern time zone and had to pick up a person at the airport was when we found out the planner did not account for time change. We were late in picking up the person by 1 hour. Since then, we have travelled through all 4 time zones in the lower 48 states. We still have to remind ourselves that trip planning and ETA needs mental calculation and adjustments. We sometimes bounce between navigation apps to check time and ETA to verify Waze ETA. At least now, no more Daylight Savings Time to worry about.

How can you not have this feature when it is one of the most important things for business travelers to know?

Thanks,

Sublarry

This affected our trip and destination tour today. We were late by an hour and needed to reschedule.

Quando viajamos, para pais fuso horario diferente, devia dizer hora de chegada, atualizada com o pais

I travel across time zones frequently for work and this is an issue for me.

I remembered why I stopped using Waze when I traveled across time zones. Only, I remembered AFTER I was late getting somewhere. I planned my trip the night before and was STILL late because WAZE didn’t factor the time change (cst to est).

I wish you would either fix this issue, have an alert pop up when the trip is crossing time zones or put the time zone in the arrival time so those of us that plan to leave ahead of time aren’t missing important events or work.

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.

The New update needs to include the distance time as it was before. Its a great help to have an idea of approximately how long/far a destination is