[SUPPORT] Android & iPhone app snap-to bug.

[bgodette]

It seems like the 3.xx clients are preferring to snap to farther away parallel roads to the right over the nearer road the driver is actually on. Example UR, gps trace is closer to W Bowles Ave but user is being snapped to S Julian St. This is fairly common and happens more often on predominately East/West roads in my experience.

It also happens to me personally every time heading westbound on E Hampden Ave, I'll always snap to E Hamilton Dr even while driving in the left lane, while my drives will always show my trace down the lane I was driving in. Same thing for heading East, except it'll snap me to E Hampden Pl.

[bgodette]

I've verified that this does NOT happen with the old 2.4.0.26 Android client, with or without a route set. I need to find a N/S road to test on for tomorrow. In the meantime if someone with an iPhone could check this as well.

[R4CLucky14]

I haven't seen this problem personally. I'll keep a better eye out for this.

[bgodette]

This may also be a rounding or conversion bug in the newer clients, so it may only happen in small sections.

[AlanOfTheBerg]

This may also be a rounding or conversion bug in the newer clients, so it may only happen in small sections.

Oh, good. Another rounding issue.

[MaliciousWolf]

I've verified that this does NOT happen with the old 2.4.0.26 Android client, with or without a route set. I need to find a N/S road to test on for tomorrow. In the meantime if someone with an iPhone could check this as well.

I can varify for the iPhone. I have had this issue occur daily on my normal commute to and from work. When driving N/S on my normal state route road I take, everything works fine. Eventually I have to get on a E/W Interstate and waze will keep trying to track me on back streets and residential roads to the right of the direction I'm traveling on the interstate in both the E/W directions.

[crazycomputingdotnet]

I have seen this issue before as well. I thought it was just roads too close together and an off ramp being in the mix so I pushed the roads apart a bit (so they were on the outer edges of the arial roads) and the update on 3/7 showed that fix, and it is now routing correctly and not pushing me on the side road, so I thought nothing of it.

(BTW you were mentioning roads that were close to places I lived/grew up and I got a little home sick...)

[MaliciousWolf]

I have seen this issue before as well. I thought it was just roads too close together and an off ramp being in the mix so I pushed the roads apart a bit (so they were on the outer edges of the arial roads) and the update on 3/7 showed that fix, and it is now routing correctly and not pushing me on the side road, so I thought nothing of it.

(BTW you were mentioning roads that were close to places I lived/grew up and I got a little home sick...)

I wish I could do a quick fix like that, though sadly I cannot for this is also occurring in a city I travel too twice a week with a lot of different streets and minimal space in between. To push one a little further away from another would cause it to become closer to yet another lol. Just will hope the developers work it out in the code and make it a bit more precise.

[bgodette]

Update: I'm plotting locations that this happens to me personally, and so far this looks more and more like a bug in the client's look-up table for converting GPS coordinates to internal map X/Y.

[nnote]

Most of my User Reports on the map for the last couple days is a wazer headed westbound and the client has the user GPS track about 1000 feet to the north and trying to route the wazer through those roads.