Thanks, Noam!

You said "everything", but would it be possible for you to list the issues/features which are in the roadmap to be fixed/added? I am specifically interested in the following:

• A>B route sharing (missing feature)
• Turn instructions list for each route (missing feature)
• Origin/Destination switching (bug)
• Tap for popup options in mobile browsers (missing feature)
• Problem description not relayed to WME (bug)

I have the same suggestion above.

In addition, when we simulate a single-way route in parallel (to identify possible returns), Livemap does not identify the correct route (since they are very close in parallel and the zoom level is not sufficient). For the Livemap the point of origin and destination are in the same segment, however it is not true and this is not how you would like to do the route simulation.

From the suggestions given by our friend above, I also think it is very important to show the instructions: turn around, this is to identify flaws in the route instructions. We currently have the Script Route Checker, but it does not always work properly.

Does Livemap not use the same search algorithm as the application?

When I look for the Address: Rua Antonio Delpizzo Junior, number 269 (City: Tubarão, State: Santa Catarina, Country: Brazil):

In Livemap: Shows on the correct street, but in the wrong numbering.
In APP: Shows the correct location.
PS: WME is edited correctly.

Thanks for the reply.

For some reason in particular? That way I will not be able to simulate a correct route in Waze.

Any feedback from the developers?

Hello, there is a detail that has been bothering me for some time. see below:

A route indication is described as "fastest" but it is not the fastest, see that the second option is 1 hour faster, it is not only indicated as the first option, since there is an unpaved road that comprises 30 minutes driving on the road of land. Would not it be nice to change the names there? For example: Instead of writing fastest, leave writing, best option. And when there is long unpaved road, leave written next (long unpaved road). Leave some information more clear why this route was not indicated by Waze as the first option.

Permalink

I found a bug with livemap's in the closure icons.
In the regular livemap, the icons are shifted right, but in the embedded map it is correct.

Please see attached images.
Thanks.

@Staff team:

I like the changes with moving the Edit the map button from the bottom left to the right to regroup everything, nice one

Question1: Are the 5 routes of different colors definitely gone to favor 3 blue routes only? The new design looks good I'm just wondering if it's a test or if "less is more" is the definitive way you decided to go in the end.

Question2: Are you aware of this request regarding some Emojis being incompatible with the Livemap?
https://waze.centercode.com/project/fee ... BFAB5DF%7D (BUG 3610) on Centercode

RussPA wrote:

Babbegeier wrote:Er - sorry - am I too stupid or is the feature that showed the turns and routing instructions of a route no longer available?
THAT was useful for me.

I agree, the turn instructions were very helpful to solve routing issues. Any chance they can be returned, or is that already in the roadmap?

Upvote this feature.

Two more things that should be fixed:
* The search in the Live Map does not give places from WME, only from Google maps.
* There is no X on the popup window for a route search, that can close the route.

I recently noticed (maybe as of live map update 7/30/19) that the iframe has stopped working in Edge and IE. It works properly in Chrome however. The Live Map website also does not work in Edge or IE either. Is this an ECMA Script 2016 version issue?

Reproduce by navigating to https://www.waze.com/livemap using Edge or IE 11.

Error Message in browser console:
https://i.stack.imgur.com/vqb92.png