Page 1 of 1

Somerset NJ: How can this be fixed?

Posted: Fri Jul 25, 2014 6:30 pm
by Nel101
https://www.waze.com/editor/?env=usa&lo ... s=32008922

You can see from the two UR's, Waze is routing onto Landing Lane, making a left and back onto Easton Ave. I have seen Waze route me this way before crossing this intersection. Obviously this is not a practical way to navigate through this intersection. Any ideas if there is a way to "fix" this?

Re: Somerset NJ: How can this be fixed?

Posted: Fri Aug 01, 2014 2:29 am
by Kobes1878
There were a lot of these errors previously but most of them seem to have been fixed in the backend.

If Phantoms method doesnt resolve this you can also use these forms to submit to Waze:

For small detours:
https://docs.google.com/forms/d/1WJzQEn ... w/viewform

For large detours:
https://docs.google.com/forms/d/1cC4Hd2 ... M/viewform

FYI - when I tested both routes just now I did not get any error.

Re: Somerset NJ: How can this be fixed?

Posted: Fri Aug 01, 2014 5:07 am
by Kobes1878
PhantomSoul wrote:
Kobes1878 wrote:FYI - when I tested both routes just now I did not get any error.
You gotta go on LiveMap and pick like 5 PM. And even then, sometimes you get it and sometimes you don't.
I tried almost every hour (not the half hours though :? ) LiveMap being that its estimating for the future with no Live data, can be scizo like that.
I would recommend filling out the form for short detours for both cases and let Waze fix it so we don't have to worry about future editors trying to "fix it back"
It was almost certainly traffic related though and the server suggested the ramp to save about 30 seconds. So as PS said, the Short Detours Form is the way to go.

NOTE: Thank you qwaletee for providing those forms here. I knew they'd come in handy someday!

Re: Somerset NJ: How can this be fixed?

Posted: Fri Jul 25, 2014 10:24 pm
by orbitc
Nel101 wrote:https://www.waze.com/editor/?env=usa&lo ... s=32008922

You can see from the two UR's, Waze is routing onto Landing Lane, making a left and back onto Easton Ave. I have seen Waze route me this way before crossing this intersection. Obviously this is not a practical way to navigate through this intersection. Any ideas if there is a way to "fix" this?
I'm on my phone but, didn't I restricted that left turn? I'll take a look again little later.

Re: Somerset NJ: How can this be fixed?

Posted: Fri Aug 01, 2014 1:55 am
by PhantomSoul
The detour prevention is failing in both cases because the road name, city, or both are different at the start of the detour and at the end of the detour, in both cases. Likely, Waze thinks it's marginally faster to take the jughandle, turn left at the stop sign, and then turn right to return to the highway than waiting to continue through at the signal - especially at intersections where there right turn is allowed on a red light.

In the first example, while taking that detour, you cross from New Brunswick into Franklin Twp, Somerset, causing the detour prevention to fail. You need that left enabled onto Franklin Blvd from that Landing Ln loop because it serves as a jughandle for traffic going from westbound Easton Ave to southbound Franklin Blvd.

In the second example, the highway becomes unsplit after mainline junction, so its name changes from US-206 S to just US-206, causing detour prevention to fail. On Freeways, we solved this by removing the city name; however, on surface highways like these, we need the city names and cardinal directions on split roads for navigation and other practical reasons.

The only way I know of preventing the detour is to ensure both primary road name and primary city name are the same thing for all segments along the highway from the segment before the start of the detour to the segment right after the end of it.

Re: Somerset NJ: How can this be fixed?

Posted: Fri Aug 01, 2014 3:54 am
by PhantomSoul
Kobes1878 wrote:FYI - when I tested both routes just now I did not get any error.
You gotta go on LiveMap and pick like 5 PM. And even then, sometimes you get it and sometimes you don't.
PleaseDriveFast wrote:Should it be considered that US-202/206 doesn't split until after River Rd, slightly North of the current location? While there is a median starting at Hills Dr. and Northward, the roads are essentially side-by-side, unlike some of the other highways in the area (US-22 most notably).
We could hack both instances several ways to pigeonhole the road into the detour prevention system, but there's nothing to keep another editor from not seeing that's what we did and request getting it unlocked to change it back; on the surface, the hack would be wrong according to the guidelines.

I would recommend filling out the form for short detours for both cases and let Waze fix it so we don't have to worry about future editors trying to "fix it back"

Re: Somerset NJ: How can this be fixed?

Posted: Fri Jul 25, 2014 6:46 pm
by PleaseDriveFast
Do you think there are turn restriction penalties being applied because of the split into 2 one-way segments? Would keeping this as a 1 segment, 2-way road until Franklin Blvd address this?

Re: Somerset NJ: How can this be fixed?

Posted: Fri Aug 01, 2014 1:23 am
by PleaseDriveFast
There's a similar routing behavior happening here based on the UR present there.

Waze routed the user off 202/206 and back on again using the ramps in that area. I do think the restricted turns for the 206 segment are adding penalties that makes Waze choose the ramp segment. Thoughts?

Re: Somerset NJ: How can this be fixed?

Posted: Fri Aug 01, 2014 2:20 am
by PleaseDriveFast
PhantomSoul wrote:The only way I know of preventing the detour is to ensure both primary road name and primary city name are the same thing for all segments along the highway from the segment before the start of the detour to the segment right after the end of it.
Should it be considered that US-202/206 doesn't split until after River Rd, slightly North of the current location? While there is a median starting at Hills Dr. and Northward, the roads are essentially side-by-side, unlike some of the other highways in the area (US-22 most notably).