Timbones wrote:The only thing I can find is the speed shown in Cartouche for this segment is NaN for one direction. Not sure which direction it is.
Timbones wrote:However, I can route from segment on to the Highway, but not too that segment from Bayside Beach Rd. Therefore, I suspect there's something wrong with the node on that fork. Delete and redo?
I agree. The direction towards Ft. Smallwood Rd is the native direction. If I recall correctly, that segment was set one way in that direction at some point. That would make sense from an autocorrection standpoint as few come southeast on Ft Smallwood to turn left on Bayside Beach, while many come out Bayside Beach to turn left on Ft Smallwood. Thus, the update request when waze decided not route this way.Timbones wrote:Yes, I believe that this is true, I just couldn't tell which way was native. I think this is a red herring anyway, as the problem is more likely to be at that node.
CBenson wrote:Timbones wrote:The only thing I can find is the speed shown in Cartouche for this segment is NaN for one direction. Not sure which direction it is.
I am under the impression that the first speed is for the native direction of the segment (the direction that the left to right one way selection gives) and the second speed is for the non-native direction. Is this not always the case?
Users browsing this forum: Bing [Bot]