AlanOfTheBerg wrote: I really can't fathom why Waze would want to route onto the ramps.
Talisker66 wrote:I would like to come back to my suggestion since I had the same Problem in my Area and it's now solved:
Look at the GPS-Tracks. Maybe the ramp and the road are too close together AND the GPS-Track is only slightly off the map AND since the Routing is now via the Ramp Waze does not recognize that you stay on the road and "allocates" the data to the road.
This was my observation: Everytime I stayed on the road Waze thought I used the off/on-ramps (at least this was what I saw on the client.
Only as I checked the GPS-Tracks and moved the Main Road more into the main GPS-Stream and increased the gap between the road and the ramp I've got this solved
moesterry wrote:Have you tried make a turn restriction for a few days, then routing along that point? With the turn restriction, navigation won't route you along the ramp. That way, when you go this road, it won't believe you are on the ramp and will be able to acquire a correct average speed on the segment.
I agree this is a very sad solution, but I think it's worth a try.
alexthelion wrote:But not only I find people driving this way very asocial, it also asked me to leave the main motorway to for the ramp on lots of occasion at night while I'm alone or as such on the road...
As far as I can remember I didn't experience this behaviour in the past and this started a couple of months ago.
Talisker66 wrote:Yeas, I actually separated the roads more than they really are. If I look at the GPS-Tracks you can easily move the ramps more to the north and they still will align with the tracks.
In addition you could move the node at the beginning of the ramp more to the east. This indicates the aerial to me.
Users browsing this forum: Google Feedfetcher