Ashton-under-Lyne, Tameside Unlock request

Hi Editors,

I would like to be able to edit the following segments.
Your help will be greatly appreciated.

Permalink: https://waze.com/en-GB/editor?env=row&lat=53.49119&lon=-2.10168&marker=true&zoomLevel=18&segments=392808812
Reason: I am not too sure whether there is a need for a fix here, but when travelling to IKEA Manchester, the app informs you to go up to the top of the car park and not the street level, this should be changed so navigation ends before the up-hill slip?
Unlock to level: 2

Thank you in advance,

You’ll have to give some information on what you select for navigation. If you review the mapping on WME you will see that the nav point for this location is not on the up ramp so using the Waze venue will not direct you wrong.

Yes,

When putting in Waze the destination of IKEA Manchester, the end route of the nav point is all the way to the top of the building.

I think it should just end before the ramp, so people can use the street-level car park before heading up?

Your thoughts?

Have you looked at the nav point in WME :?: If this differs from what you are seeing in your app you need to determine where the app is getting your data before asking to correct Waze info, then we can be certain what needs to be corrected.

The entry point on waze shows it just after the roundabout but on Waze it shows you have to travel to the top?

Waze link - https://www.waze.com/live-map/directions/gb/england/ikea-manchester?to=place.ChIJA_NXfoa2e0gRbw9BBIc_gdo&from=place.ChIJq7M964y4e0gRJ2XaINteiJo&utm_medium=lm_share_directions&utm_campaign=default&utm_source=waze_website

So where is Waze getting the wrong info from :?:

I am not entirely sure, how it’s being directed to the roof car park.

I’ve approved your PUR as linking the Google data is likely to fix for this issue, when navigation leads to a different place to the expected nav point mapped in Waze it is usually due to search results prioritising other companies data, Google, ad pins, etc.

Thank you, the next time the map tiles update. I’ll have a look if it works alongside whenever i travel next to IKEA.

I suspect the cause was selecting the Google result in the search results. Google has the pin in the centre of the store. The closest segment is on the roof.
Could Waze be prioritising the segments drawn inside the area place over the navigation point?
If you look at Aldi just to the south, Dean St is inside the area place and Waze navigates to that point instead of the nav point set at the car park entrance.
Perhaps removing the segments drawn inside the area place will cause Waze to use the nav point instead?

I think you may be correct here. I have had another look since the last tile update and it shows the same navigation?

It could be the segments on the roof that need removing and the segment on the ramp being stopped at the start?

your thoughts?

https://www.waze.com/live-map/directions/gb/england/ikea-manchester?to=place.ChIJA_NXfoa2e0gRbw9BBIc_gdo&from=place.ChIJq7M964y4e0gRJ2XaINteiJo&utm_medium=lm_share_directions&utm_campaign=default&utm_source=waze_website

Silly question this, but I’m not sure if this is just being overcomplicated for no particular reason? For anyone that has not been to Ikea (Manchester) There are two entrances to the store, one is at ground level which you then need to use the stairs/lift to actually start at the entrance to the store. The second is the upstairs car park that is fully signposted as ‘The entrance’ which again you need a lift/stairs to go to the main start point of the store. Is this not just a non-issue?

You are quite right, but the app should stop the navigation at a set point, shouldn’t make people goto top level, initially. As there is most likely space on ground level, if that makes any sense lol ;/