1. Include the city and state in the "Subject:" line of your post
2. Include a Permalink to the segment(s) you wish to unlock or have updated
3. Provide a short explanation of why you need the unlock or update done.
4. Thank the user who solved the request and mark the thread Solved.

Please note that a higher level editor may choose to fix an unlock request themselves so higher value segments will remain protected at their level.

Post Reply
Forum rules
1. Include the city and FULL state name in the "Subject:" line of your post
2. Include a Permalink to the segment(s) you wish to unlock or have updated
3. Provide a short explanation of why you need the unlock or update done.
4. When completed, THANK the user who solved the request and mark the thread SOLVED.

Routing Enigma?? (Jackson, NJ)

Post by Kobes1878
I have been working on resolving this UR for literally days now and am just about ready to throw in the towel.

This Wrong driving direction Report on the selected segment https://www.waze.com/editor/?zoom=3&lat ... s=79572693 reads:
Problem: Will not allow navigation along W. Veterans Hey between Stump Tavern Rd and Hawkins Rd.
Segments on either side of the problematic road are https://www.waze.com/editor/?zoom=3&lat ... 4,65847189 Take a look at the LiveMap routing between those segments when simply trying to cont straight. Same deal when the points are reversed. (App produces same results.)

I did find the elevation to be off on the segment with the UR and fixed it. I also found a "Lone Node" at the intersection here which I deleted. I tried changing the geometry as well. Still nothing...

Is there anyone out there who can help me solve this conundrum?? I implore you for your assistance.
Kobes1878
Map Raider
Map Raider
Posts: 675
Has thanked: 172 times
Been thanked: 296 times

POSTER_ID:16951451

1

Send a message
[img]https:///P87dIo[/img][img]https:///nVuW1N[/img]
State Manager: NJ | Country Manager: USA

Post by CBenson
WME reports that you have edited this segment today, which makes it difficult to troubleshoot the issue. However, I have inquired to waze staff about a couple of similar issues recently where routes bypass a junction but there is nothing on the map that appears incorrect. They have all been in areas where the tile had not been updated in awhile, so the advice was simply to make any edit in the area to trigger a tile rebuild. This has solved the problems I have had. I'd see whether the issue remains after the next tile rebuild.
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 608 times
Been thanked: 1642 times
Send a message
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by CBenson
Kobes1878 wrote:Have you?
There seems to be different issue. One is a junction becomes corrupted in the database and you can't route through it (in at least one direction). Others are small little detours that waze routing seem to think are faster.
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 608 times
Been thanked: 1642 times
Send a message
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by Kobes1878
Thank you for the response CBenson. I was hoping you would see this as I know you've been dealing with these "mystery routing" segments for quite some time now.
CBenson wrote:WME reports that you have edited this segment today, which makes it difficult to troubleshoot the issue.
I did find the extra node today, so I will definitely wait on the tile refresh.
CBenson wrote:However, I have inquired to waze staff about a couple of similar issues recently where routes bypass a junction but there is nothing on the map that appears incorrect.
I have only come across the issue in places like here where there was an intersection/red light ahead and its possible the fastest route would actually have been to exit and get back on. (That specific location has since been corrected with the tile rebuild trick) But never on a clear 2 mile straight shoot. Have you?
CBenson wrote:They have all been in areas where the tile had not been updated in awhile, so the advice was simply to make any edit in the area to trigger a tile rebuild. This has solved the problems I have had. I'd see whether the issue remains after the next tile rebuild.
This is why I waited a few days to post this. I have reconstructed both intersections here multiple times and it should have been corrected on the tile updates which occurred on the 13th and 14th. Being that I deleted the node mentioned above after the last update, I will wait for the next rebuild though and report back.

NOTE to forum moderators: I see this was moved into the US unlock forum. It should either be in the Navigation & Routing or the NJ forum.

Thanks!
Kobes1878
Map Raider
Map Raider
Posts: 675
Has thanked: 172 times
Been thanked: 296 times
Send a message
[img]https:///P87dIo[/img][img]https:///nVuW1N[/img]
State Manager: NJ | Country Manager: USA

Post by Kobes1878
@Cbenson Interesting. These bugs are starting to bug me. Ok, that came out wrong. Im surprised we dont have a standard procedure for dealing with these errors yet, as they seem to be popping up everywhere. Although I guess the tile rebuild is generally sufficient.. anyway.. im just tap tap tap-ing away until this refresh. Cmon now!

@Phantom - I see that, good catch! I obviously want to wait prior to deleting data as you pointed out, but if this isnt resolved by the refresh, I have no problem exploring the options you mentioned. In fact, I did take the liberty of doing basically what you advised at node A (which may be why that section is the "good one") after the first tile refresh didnt fix this. Didnt want to mess up node B yet being that there's a traffic signal there. Data accumulated to help drivers is IMHO deemed useless if a road is un-drivable. Thanks for your input. I will keep you posted on this one, could use expertise. Oh and here's the clients routing taken prior to my OP. Checked it just in case you'd ask for it [emoji1]


Sent from my Galaxy S4 via Tapatalk
Kobes1878
Map Raider
Map Raider
Posts: 675
Has thanked: 172 times
Been thanked: 296 times
Send a message
Attachments
[img]https:///P87dIo[/img][img]https:///nVuW1N[/img]
State Manager: NJ | Country Manager: USA

Post by Kobes1878
Yes, Please post the links - for myself and anyone else who may need them...

Thank you qwalatee!

@WAZE - Can we please get a tile refresh?? Whats happening? Did you all get Wazeted?! ;-)


Sent from my Galaxy S4 via Tapatalk
Kobes1878
Map Raider
Map Raider
Posts: 675
Has thanked: 172 times
Been thanked: 296 times
Send a message
[img]https:///P87dIo[/img][img]https:///nVuW1N[/img]
State Manager: NJ | Country Manager: USA

Post by Kobes1878
https://www.waze.com/livemap?lon=-74.43 ... 0809964894

...and its fixed. Don't know if it was the tile rebuild or submitting this to Waze but IDC, just happy its solved :D

(I cannot mark it solved until I regain access to my old account.)

Thanks all for your assistance!
Kobes1878
Map Raider
Map Raider
Posts: 675
Has thanked: 172 times
Been thanked: 296 times
Send a message
[img]https:///P87dIo[/img][img]https:///nVuW1N[/img]
State Manager: NJ | Country Manager: USA

Post by PhantomSoul
The problem seems to be at the B node at the west end of the segment. If you use the WME route checker and try routing to the segment in question from the west, you get this gigantic detour. If you try routing to the segment in question from the east, you get the expected route. Of course, trying to route through the segment produces a gigantic detour.

If the tile rebuild mentioned earlier doesn't help, we can try disconnecting W Veterans Hwy, dropping it disconnected, saving, and then reconnecting it, adjusting the turn arrows as needed, and saving again. This will reset the traffic statistics of entering and exiting that end of the W Veterans Hwy segment.

If that doesn't work, we can also try completely dissolving and rebuilding the junction at node B of that segment. This can be done by dragging all the approaching segments away from it and dropping them nearby, but not connected. Then, by saving, we dissolve the junction. Afterward, we can reconnect them in the correct spot to create a new junction, once again, of course, remembering to adjust the turn arrows as needed.

Also, Live Map can take much longer to reflect updates from WME than the Waze mobile clients, so this can take a while to debug if you want to try the less "nuclear" solutions first before dissolving the junction. I'd say that if you know for sure that the junction isn't prone to very bad congestion and the roads involved are just primary streets, let's just dissolve and rebuild the junction, but I'll leave that up to you since you seem to know the area better. ;)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
Posts: 1757
Has thanked: 311 times
Been thanked: 512 times
Send a message

Post by qwaletee
There is also a form where you can submit detour errors. If you want, I can post the URLs.

In this instance, I don't think I'd have many qualms about recreating everything, down to the segment level if need be.
qwaletee
EmeritusChamps
EmeritusChamps
Posts: 2939
Has thanked: 188 times
Been thanked: 958 times
Send a message
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues

Post by qwaletee
Small detours (routes around one segment, usually using 2-3 adjacent segments, typically a triangle): https://docs.google.com/forms/d/1WJzQEn ... w/viewform

Long routing issues (long unoptimized routes, mostly highway; not for detour off and back on road): https://docs.google.com/forms/d/1cC4Hd2 ... M/viewform

I have the "long detour" routes around a highway segment -- off ramp, short travel, on ramp to same highway) but I don't think it is very relevant anymore. There's another one for "alternative routes," not sure what it is for.
qwaletee
EmeritusChamps
EmeritusChamps
Posts: 2939
Has thanked: 188 times
Been thanked: 958 times
Send a message
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues