Over a week ago I corrected an error in Birmingham city centre on the live map which I’m led to believe should have filtered down to the app by now but it’s still not there. I was advised to post here to see if anyone could help to get this resolved, can anyone advise me on what to do next please?
This is a link to the section that I edited.
It depends what type of edit you’ve made to the map. Some edits don’t trigger what’s called a Tile Update, which is the process that updates the live map with any changes made. Usually a Road segment change does trigger an update, but a Place change or Camera change does not.
If you can supply a Permalink to the object you’ve change, I can check to see what the issue is.
When I go to the WME there is no permalink icon to copy, it just says Livemap where the icon should be.
Looking at the permalink in the edited opening post, the segment selected doesn’t have you editing it. The last edit was done by an editor called tbrks on the 19th. Are you sure you saved the change you made?
Keith, the edit history for that segment is a bit screwy - Tony was shown as the last editor on the segment just after I unlocked it for them (see https://www.waze.com/forum/viewtopic.php?t=351441), but there wasn’t anything listed in the full edit history to suggest what change had been made, nor could I see anything obvious by comparing the live and snapshot views.
It’s now subsequently been edited again by tbrks, and as their change has appeared in the history as well as overwriting the “updated by” info, it gives a false impression that Tony has never touched this segment…
Edited to add:
I’ve now also just rechecked Tony’s editing profile page (https://www.waze.com/user/editor/tony7bear) which originally didn’t list any edits having been made by them even a few days after WME was saying they had edited that segment. It now does show them having made one edit on July 12th based on the Editing Activity section at the bottom of the page, though it doesn’t then provide any details about said edit in the Recent Edits section on the left. So yeah, something definitely feels screwed up with how whatever it was Tony tried to do that day has been subsequently handled by the Waze servers.
I’m not sure what happened with my edit but even after others have edited the very same section the routing is still wrong on the app. Before you ask I’ve refreshed the map several times (2##2 etc) over several days, nothing has changed and the routing is still giving incorrect directions.
The app is still getting the routing wrong even though several users seem to have edited the junction to show it correctly, why is that?
Looking at the date this thread was started, could this be related to the tile build roll back?
That could well explain the more recent seemingly failed attempts to fix the problem, but not the original one Tony refers to - his original edit was made well before the rollback period, and seems to be a more obscure problem which is causing some edits not to be properly processed.
Is it worth me trying the edit once again?
Yeah, the segment is still unlocked, so give it another go.
Okay I’ve highlighted the section, selected 2 way and saved the change, hopefully it will work this time!
Ah, this could help explain the discrepancy between the different ways in which Waze shows edits - this segment was already a two-way, so whilst you’re now currently shown as the last person to update the segment, you aren’t listed in the detailed edit history for the segment because your actions didn’t actually alter anything about the segment properties…
So, given the edit you were trying to make has already been done, it’d now be useful to understand why you were trying to make that change, in case the underlying problem is elsewhere.
The reason for making the change this time is because when I first edited it the section was shown as blocked, in between times someone else seems to have corrected it and this time I’ve redone it to make sure!
The original reason is because the routing ignores this section as an option to turn right when approaching from the West and takes you half a mile out of your way only to return and make a left turn up Snow Hill Queensway.
I think I’m just going to have to distrust the edit history for this segment, because I can’t see anything in it that would have accounted for the right turn you describe not being offered as part of a route previously, and Waze is definitely happy to do so now, so I’m at a genuine loss to explain what’s gone on here.
Okay, I think I know what is happening now. I have tried different locations as destinations around that area and sometimes Waze will use that section as a right turn so it appears to be correct now. What has been confusing me is what I consider to be the best route to where I park when at work isn’t the one that Waze will give, I believe it is giving me what it considers to be the fastest route whereas I am trying to take the shortest route.
I’m sorry for any confusion or headaches that I might have caused with this “issue”!
No worries, the “find the apparently fastest route at almost any cost, no matter how weird and illogical it might look to the user” approach for calculating routes is something which catches out a lot of users, and is something those of us who’ve been around Waze for a while now have just had to get used to.
It’s like the long-standing difficulty Waze has in working out which is the optimum direction to set off at the start of a journey, which can lead it to directing drivers off on a tour of the local roads as part of getting them to drive around in a loop so they can head straight past their starting point in the other direction - once you’ve seen the app do that a few times, you start to just ignore it and head off in the direction you think is best, and let the app catch up with you…
Basically, all you have to remember here is that, sometimes, it really is OK to ignore Waze’s directions. Only sometimes though :lol: