A bunch of requests... NY/NJ area

Wajo357 · January 23, 2013, 5:44pm

orbitc:

CBenson:

Wajo357:

-I just navigated to my parents from Wayne, NJ to Brooklyn, NY and it told me to go through the Lincoln, even though I had avoid tolls on. Interesting. Although I did clean it up a few days ago by removing the segments after the toll booth from having the ‘toll’ option on. Maybe the fact that there were only 2 small toll segments associated with this drive that had to do with something.

The current problem with avoid toll roads is that when you have avoid toll roads set, waze prefers to route you the wrong way through non-toll one-way outbound segments, rather than toll inbound segments. This is what is happening at the Lincoln Tunnel. Waze is routing through non-toll segments the wrong way into Manhattan over segments like these.

I think, this needs to addressed. That would be very dangerous, in most other circumstances. I’m guessing that something needs to be change in the algorithm that forces waze to choose the wrong way when no toll road option is enabled.

On Sunday I decided to take the Brookly Battery Tunnel even though I had ‘No Toll Roads’ on Waze and when I got to the segment with the toll, it had me just go backwards so it wouldn’t go through the segment… lol. It is behavior like this that you want to minimize.

Wajo357 · January 23, 2013, 5:45pm

orbitc:

Wajo357:

orbitc:

I would agree that one time penalty for the toll road rather than adding them up. I too cannot back that up. Perhaps. there could be other factors that made Waze chose that route.

Ok… so I figured out a way to play around with this behavior - but it means screwing around with my block. Since my block isn’t a thru street at either end, I figure there isn’t much risk in it.

My plan:

Test 1 - Flag both segments on my street (broken up by my waze voice test segment) as a Toll. Typically the shortest route directs me up the block with the longer of the 2 segments. So this will test to see if the length of a toll segment affects the system - if it routes me to go around the block through the shorter segment.

Test 2 - If it doesn’t route thru the shorter segment, I’ll break up the longer one into 3 smaller segments and see if that forces me to go around the block to only drive through the 1 toll segment instead of 3.

How does that sound?

Yet, another test…sounds good by me. Please let me know your findings.

Ok… Test 1 set. Will let you know over the weekend.

I also locked the segments for good measure. I don’t want someone ruining my test before I can even drive through it.

CBenson · January 23, 2013, 5:46pm

I totally agree. The issue was presented to waze almost as soon as the avoid toll roads option went live. But as you can see, it hasn’t been solved yet.

Wajo357 · January 23, 2013, 5:48pm

Well… this can be mitigated by reducing the number of toll segments. Who has the guts to change the wiki?

CBenson · January 23, 2013, 5:53pm

I’m not seeing how the reducing the number of toll segments mitigates the wrong-way over one-way segments problem.

Wajo357 · January 23, 2013, 5:56pm

Because once you pass the toll road segment, Waze won’t give the restriction to the other segments thus trying to make you go the wrong way.

Wajo357 · January 23, 2013, 6:03pm

I PMed Weeezer14 earlier.

After looking at this thread: http://www.waze.com/forum/viewtopic.php?f=249&t=30299&p=288229

I decided to look at the Garden State Pkwy

The one section I looked at only has the segment under the toll marked as a toll, NOT the segments leading to it:
https://www.waze.com/editor/?zoom=6&lat=40.99926&lon=-74.0714&layers=BFTFFTTTTTTFTTTTTTTTTFT

Maybe getting this changed will be easier than I thought? lol.

CBenson · January 23, 2013, 6:10pm

But the problem, like at the Linclon Tunne,l is that waze is finding a route without any segments marked as toll. As there is only a toll eastbound through the tunnel, waze will route eastward over the non-toll westbound lanes. As there will always be at least one toll segment for the proper eastbound routes, waze will continue to route eastward over the westbound lanes if you have avoid toll roads selected.

Wajo357 · January 23, 2013, 6:15pm

Ahh… I see your problem now. Interesting. Wow. Anyway, I think the consensus though is that it would be best if we can minimize this occurrence.

orbitc · January 23, 2013, 6:33pm

Great idea…

orbitc · January 23, 2013, 6:42pm

Let’s wait until your tests end. Once we confirm that, one of the issue is due to marking segments near by the actual toll roads as toll roads. We’ll update the wiki accordingly.

jasonh300 · January 23, 2013, 7:44pm

In this case, the Toll checkbox should be removed if there’s a chance that Waze will route someone on that ramp and then off the other before the tolls.

It’s for purposes of marking the roads, if someone is reading the client like a map…this feature has not yet been implemented.

Probably not as big of an issue, but you could remove the toll checkbox there too. There’s no legitimate routing that would take someone there. They might do that if they’re just running Waze with Navigation off.

Yes, that needs to be marked Toll because there’s no way to get to it without paying a toll.

Wajo357 · January 25, 2013, 2:00pm

Connect parking lot roads to highway and allow turns:
https://www.waze.com/editor/?zoom=7&lat=40.89376&lon=-74.2316&layers=BFTFFTTTTTTFTTTTTTTTTFT&segments=70910555,70910556,70910729,70910735
Allow turn to parking lot road…
https://www.waze.com/editor/?zoom=7&lat=40.86275&lon=-74.38629&layers=BFTFFTTTTTTFTTTTTTTTTFT&segments=67705610
Connect segment to ramp and allow turn:
https://www.waze.com/editor/?zoom=8&lat=40.77464&lon=-74.03607&layers=BFTFFTTTTTTFTTTTTTTTTFT&segments=70474804

FYI - Maps updated with the toll segments on my block:

A) When leaving my block to work, Waze would not navigate on my block. The purple wasn’t even showing. It just started at the end of my block, even though it saw me on my block. Weird action.

B) When navigating back home from work, it did not route my around the corner. It DID route my up the block the same way.

Now I’ll split up the long segment and we’ll see.

I didn’t test the voice yet.

orbitc · January 25, 2013, 2:47pm

171: Done

172: Done

173: Done

That’s interesting, but I kind of understand the idea behind it. You are already in a toll road so the navigation would start when you reach the highlighted road. Kind of like the traditional Navigation systems.

Wajo357 · January 25, 2013, 2:58pm

thanks!

What is weird is that when navigation thru a toll is the only option, it will navigate through it. So why have this behavior when you are starting on a toll segment.

orbitc · January 25, 2013, 3:13pm

I would imagine that your toll segment isn’t as long as if you were in one. Therefore, the highlighted starting road point is for you to navigate without the navigation.

orbitc · January 25, 2013, 5:04pm

Here is my Voice Test for the following:

Exit 70 N-S / Exit 80 N - S / Ave “S” / Ave ‘S’

Exit 70 N-S: Exit 70 enn ess
Exit 80 N - S: Exit 80 North South
Ave “S”: Avenue ess
Ave ‘S’: Avenue ess (same as above)

Wajo357 · January 25, 2013, 5:11pm

lol… beating me to the punch.

Question, is the first one “enn ess” or “enness” where the voice is blurring the words together…

Also, how do we want to handle the Brooklyn letter avenues now? Should we speak to a few of the champs if all of the avenues should be changed to ‘?’ or “?”?

orbitc · January 25, 2013, 5:19pm

Personally, I would prefer to use single ’ ’ quotes.

In addition, let’s get Jason’s opinion as well.

As for as the test result I think it was enness. Let me double check. I’ll let you know soon.

orbitc · January 25, 2013, 5:47pm

:!: CORRECTION: :!:

Exit 70 N-S / Exit 80 N - S / Ave “S” / Ave ‘S’

Exit 70 N-S: Exit 70 North ess
Exit 80 N - S: Exit 80 North ess
Ave “S”: Avenue ess
Ave ‘S’: Avenue ess (same as above)