coldblaze wrote:This problem presents itself in another way. When driving into DC on I-395 N, there are times that the 4/5 lane highway splits right in front of you. Waze looks at the fork ahead as an exit/offramp, and assumes you know this and are on the correct side of the split. For those not familiar with the highway itself, it is a bit disconcerting to be in the left most lane, when you needed to be in the right most to continue going straight, and Waze never mentioned a thing to you, assuming you were on what is considered the main part of the highway.
coldblaze wrote: I know that most of this can be handled by renaming roads with exits appropriately, and I am trying to flag area managers to do so, so that the road split is mentioned in Waze ahead of time. I am not sure any other way, and often times area managers have taken upwards of 3 months to implement changes, which is sad as well.
CBenson wrote:I haven't had the occassion to come into to DC on 395 often. But when I have, I haven't noticed much of an issue. I just follow the I-395 signs until waze tells me to use another road.
CBenson wrote:The other way is to learn to edit the maps yourself (and then become an area manager). However, I must say that the area manangers in Northern Virginia have really stepped it up recently. I'm surprised that you have an 3 month delay in responding to update requests inside the Beltway in Virginia at this point.
coldblaze wrote:Yeah, there were two issues on 395 that I don't have permission to modify, I assume because its a major highway, otherwise I would have. For example, the first is when you are heading to the Capitol, Waze tells you to stay left and take exit 9. The problem is that you need to stay right and take exit 6 first. I have missed that exit 3 or 4 times in the last few months because of this. Anyway, I made a comment on the regular map and hope someone can fix it.
coldblaze wrote:Yeah, I do edit the map myself quite a lot. There are areas though that I think require escalated privilages to modify, so I usually go into the regular map mode and make a comment. It is those comments that take a long time to fix. To be fair, the last comment I left was for up near George Mason area, which took about 3 months to resolve. It was an on-ramp that was moved.
CBenson wrote:I really think that waze used to give turn instructions in both directions here.
AlanOfTheBerg wrote:Bases on previous testing on similar splits in other areas, Waze did give instructions at splits between same road type and all three segments have different names, which is the case here. If it doesn't give "stay left" and "stay right" instructions here, then something has changed in the routing/turn instructions code on the server.
Yeah, there is some debate over what these roads should be called even outside the waze community. The construction of the new 11th Street Bridge has caused the signs to change a bunch. I will also admit that I don't fully understand the "/" guidance in the wiki at this point. But I need to get the instructions to display at all, before I worry too much about making them more clear.AlanOfTheBerg wrote:There's some non-standard namings in there. Missing slash or : at least. And an extra / on the other.
AlanOfTheBerg wrote:EDIT: It looks like the angle may not be extreme enough at the split, which floors me. It looks just fine. But even the livemap navigation instructions extension shows a "continue" move rather than a "stay" or "turn." Maybe try increasing the angle a bit more?
Users browsing this forum: No registered users