ottonomy wrote:I'm not sure if you gathered from my post that I was the one who submitted the UR. I drive through this intersection from various angles frequently, and the routing there is almost always odd.
AlanOfTheBerg wrote:If Waze doesn't have the data from drivers taking this route, then it doesn't have the information required to make the correct mathematical decision. Waze needs all the data for all segments/speeds/time of day to ensure the fastest route is selected. If all the roads are correct and turns/restricted turns are correct, mark it solved and move on.
shawndoc wrote:Does this always happen, or was this a one time deal?
CBenson wrote:Waze does keep distinct speed data for each segment for each exit path from the segment. Thus, the question becomes have you actually driven through the intersection taking waze's proposed turns. My experience is that if you do this a few times the odd routing stops.
jemay wrote:So I tried Live map and could not reproduce the route in the direction you was heading, but reverse, it will travel the path you pictured. Nothing stands out.
The path travels from no city to city to no city and the street name change from Garfield to N Garfield (but that should not cause any issues) and on the dog leg there is a "node has 1 U-Turns." at Oak St & Avonrea Rd (so why would it route that way?)
So the next thing is it must be traffic???...
shawndoc wrote:I looked at it and couldn't find anything wrong. I know a lot of the Sr editors hate deleting segments, but I think it might be a good idea to delete and redraw that section of roadway and see if that fixes things. Since that's a pretty heavily trafficed area, the speed data should be reset fairly quickly. And besides, its not routing right anyway.
We've seen before that some segments/junctions appear fine in the editor, but are corrupted in the back end.
Users browsing this forum: glomp, Google Feedfetcher