Can a Level 5 take a look at this area?
https://www.waze.com/editor/?zoom=4&lat=33.80928&lon=-96.53408&layers=BFTFFTTTTTTFTTTTTTTTTFT
There are three update requests that indicate the routing is directing people off of US Hwy 75 North, then immediately back on. Most of the segments in that area are locked, so I’m unable to make any changes if needed.
Thanks!
I don’t see anything wrong. I did unlock the segments for you. I’m not seeing anything jumping out at me. All connections are good, everything is connected correctly, there are no missing gaps. Keep an eye on it and see what happens.
I didn’t see anything obviously wrong that would cause the problem either. The only thing I noticed was that the cities were different on those segments of 75. The segment north of where the ramp enters is Denison, the segments to the south do not have a city. I know I’ve seen other threads where segment name differences would cause Waze to route to an exit and back on, but will the city name difference do the same thing?
Also, I noticed that most of the ramps in that area (except the two on this report) have reverse connectivity issues. Do those need to be cleaned up?
Si. Reverse connectivity needs to be corrected. Just disallow and allow the connection a couple of times to get it to disappear.
I fixed the ones that I could, but I still see quite a few along that section of highway that are on locked segments that I don’t have access to fix.
Also, this turn restriction needs to be updated:
The highlighted “N Hwy 75” road segment was previously set to 2-way traffic when it’s only a 1-way road. It needs to have the allowed turn to merge onto US Hwy 69 N. The segments of 69 are locked so I can update the turn.
I went ahead and connected it, and now I’m going to get on my soap box here for a second…
grabs soap box and stands on it
It irks the shit out of me when the service roads are labeled the same as the highway. The highway shields will actually move to the service roads (yes, I’ve seen the entire service road with the I-35 shield from Waco to Austin). I’ve been going around and adding “service rd” or “frontage rd” to the ends of the names of the those roads, so there won’t be two US-75 or two US-69s. It could also confuse a driver who’s not used to service roads. If the driver is instructed to “exit to Exit 74, Texas Travel Center, then stay to the left on US Hwy 75” after just getting off of 75, the driver could be confused as to what’s going on.
steps down
I just got an answer on whether the city name difference will cause this problem in another thread from WeeeZer14. He confirmed that different city names on the segments by the entry and exit are enough to make Waze think it’s a different road and use the exit/entry as a valid route.
txemt (or any other Level 5), can you update those segments of US Hwy 75 (both N and S) in that area to remove the Denison city information from them? Since that area is right on the Red River and Denison is further south, those segments shouldn’t be marked as Denison anyway. Hopefully this will resolve the exit/entry URs.
Also, it looks like there is one short segment of 75 S just across from the Exit 74 ramp that is labeled as US Hwy 69 S when the segments before and after it are US Hwy 75 S.
Once that’s done, this whole section of highway can be locked up again.
The city limits of Denison do go all the way up to the state line.
Then all of the segments to the south will need to be updated to reflect Denison so that there is consistency.
How’s that?
It looks like the issue of routing people off the highway at Exit 74 northbound and right back on has returned. I see there is a UR out there from yesterday for the issue, and I saw another UR last week in the same place noting the same problem.
I routed through there on Friday. When my route was initially generated, the route included using Exit 74 and getting right back on. But when I had reached that area (after a couple of re-calcs due to me going off-route), it did not give me that instruction in that area. Not sure why it was in the original path, but then not there when I reached the area.
Ideas on how to fix this one permanently?
Any chance you can post a permalink?
This is the area:
Don’t have the freeway name change at the junction at the end of the ramp.
Considering that the name does change there since US-69 merges with US-75 and is designated US-69 from that point north, how would this be handled? Those segments are all Level 5 locked anyway, so I’ll need someone else to make the update.
I don’t understand why the name change has anything to do with routing. The two ramps SHOULD be enough to keep Waze on the freeway.
Because that’s how waze decided to solve the problem.
http://www.waze.com/forum/viewtopic.php?f=10&t=11468&start=150#p108262
So…what about the ones that happen in the middle of nowhere where the name is the same, including the city name?
I haven’t seen any like that since this policy was implemented.
I don’t have time to read that thread right now. Thank you for that thread, and when I find an error like that, I’ll send it to you. 
EDIT:
Damn…not in Texas