I’ve been told that streets with NO THRU TRAFFIC signs should be set to Private so that Waze doesn’t route anyone on them, unless their destination actually is on That Street.
Here in NE Ohio, there are several streets that have NO THRU TRAFFIC (NTT), but only at certain times of day. For example, I have a friend whose street has NTT signs, but it is only between 4-6pm. The other 22 hours per day, thru-traffic is legal.
There is currently no way I can figure out to change the class of the street to Private at specific times of day. Since streets like this exist, we need some way to make that distinction, so that Waze doesn’t route thru-traffic on those streets during restricted hours.
Which one of these will let people going to a destination ON the segment(s) turn onto it, but reject all others?
As far as I can tell, the options only offer route-around based on turning direction or type of vehicle, NOT based on destination. If I turn off turns from BOTH A and B junctions between 4-6pm, then ALL traffic gets blocked, INCLUDING drivers’ whose destination happens to be on that segment or group of segments.
Residents may of course know better, but visitors might be confused.
Restricting turns based on whether a driver is passing through or their destination is “local” to any segment(s) is NOT an option right now.
If I completely shut down a segment from 4-6pm, will drivers with destinations on the segments in question still get door to door directions, or will they ONLY get directions to the nearest end of the closed segment? Last time I tried to go to a destination that had a closure mid-segment, Waze treated the entire segment as closed, and only gave me directions to the nearest end of the segment. That was quite a while ago, so I have no personal experience to indicate if that has changed.
Here’s an example of a [NTT according to time] neighborhood that comes to mind:
If I turn off all turns into the neighborhood between 4-6pm, then inbound driving directions during that time would stop at either A or B. No one could actually get directions going into that neighborhood at that time. If the people who actually reside there are not Wazers, they would have no way of knowing that they need to give driving directions to a visitor who says they will use GPS.
If I had the option to set the road to private between 4-6pm, then drivers with non-thru destinations would still get accurately routed door to door without any undue ado.
There is a solution that may not many would like.
Make 2 Segments parallel. One as Private and one with the TBR.
Isn’t a great Solution and everything else than KISS, but it would work
But uncommon Problems needs uncommon Solutions when there is no other way
Best Way would be to ask a CM of your Country/State if this solution would be okay.
It is indeed a little un-elegant and might be seen as a mistake by some, but using both the TBR on a regular segment and a private road segment with no TBR on it in parallel apparently works.
Another one also suggested you set the TBR on a turn in the middle of the area so that there would be no routing thru but still possibility to be guided inside. But that depends on the layout of the streets there.
Might work with TBR only on the segments and not on the turns.
TBR will cause the segments somehow to work as private.
Anyways , if TBR will not solve the issue and will affect the locals , try my other suggestion that Vince mentioned , it’s fully working but it’s used for something a little different.
Anyways , you need to test it after adding any solution. IL routing server acts sometimes different then the ROW. so testing is needed
wow! Thanks for all of the ideas. Inelegant for certain, but I’ll check with my state crew this evening when more of them are available to see if any of these are preferred on the US/Can server.
For reference, because the parallel Private hack creates entirely new segments, would I need to recreate all of the house numbers too?
The southwest segment on my example PL has plenty of space with no houses to shoehorn in the Private parallel segment easily, but the northeast segment is fairly tight for that.
I stand corrected , I have just been informed that Waze fixed the bug with the TBR to a speccific number on the segment , so the solution will be overlapping segments with TBR on the main one
If there is a TBR on the segment, and the destination is that segment, won’t the routing engine still route all the way there since there is no other way to reach that destination? It will have a high penalty but should route correctly since there is no other alternative.
I’m waiting for a text message back from somebody who actually lives in the neighborhood that I used as an example. The SV is 6 years old. If there is no second sign on the opposite end, then only the one segment is affected according to my champ, which would mean that even if I use the parallel method, if a visitor were going the first house just past that segment, Waze would route them the entire way around the neighborhood. That’s a 2-mile loop to go 20 feet past a restricted segment.
The sign was never intended to block residents of the neighborhood or their guests, only thru traffic.
Still waiting for my friend to drive home from work.
Other than the fact that the Tile Update happens a few days behind the moment the edit actually happens, what about the tile update?
I have been told that if you put full TBR on a segment by turning off all of the inbound turns, that FUNCTIONALLY it’s no different than a closure : no traffic gets routed there during the time period that inbound turns are turned off.
Sorry, I don’t know if I get you right. English is not my native language.
As far as I know the TBR get’s online with the Tile Update, a Closure get’s immediately online.
And also I was teached, that it’s like a Closure - you cannot get through. But maybe the penalty is just set incredible high. Try it out.
The fact that some Informations are wrong given(pretty less Information but some… from higher ranked Editors - No Names), because some don’t know better, it would be helpful for me and maybe also others, when you are posting your results here
I would be very thankfull
The neighborhood doesn’t have a second [No Thru Traffic] sign anywhere to indicate where the private section ends, so I had to contact the city offices for clarification, hence the delay.
I created two parallels, one at each end of the neighborhood, and set the restrictions only for inbound traffic between 16:00-18:00, no restrictions on outbound traffic to make sure that residents and/or their guests who may be leaving the neighborhood during those hours are not at all affected by this.
I locked them up to L2 for now. Once the tile updates and I can verify the hack works as designed, then I will ask my AM/SM to lock them to L3 for protection.
I don’t really get it why you both made it that way… why not one with TBR and 2 Private Roads? Why 3 Segments (2 as Streets, 1 as Prvate)? Of course you need another Node. Could you maybe explain this?
Also there would may a Problem. The announcement could be keep left/right on a straight road. I don’t have a solution for this
I duplicated the triple segment group to match the Israeli fix. Since there is only a 1° difference, I’m not sure there will be instructions to keep right there. Usually, we have to set notable angle for way-finding segments to actually give instructions to keep right or left.
Because the restriction is only inbound, I have changed the parallel segments to one-way. Thus outbound drivers should never be affected by it.
It seemed simpler to create two inbound parallels, one on each end, instead of creating an entirely parallel neighborhood.
If you would make 2 Private Road Segments it would prevent one more announcement.
It will announce keep right/left because it wants to lead you one way and had to differentiate between two Segments. Also the Names play a role on the announcements. (You can also give Alternativenames which also affect these. But please use it only, when there is no other way. It’s undesirable - also it won’t work as wished in this case)
Nice Idea with the OneWay
