"Lorba Linda"

[ArchAbaddon]

This is still an issue; I observed it while navigating home yesterday on SR-91E between Gypsum Canyon and Green River.

[davielde]

Using WME LiveMap Alerts Overlay, I was very easily able to spot both "RRancho Cucamonga" for "Rancho Cucamonga" and "Fo" for "Fontana" along I-10. When I looked up the same alerts in the app, sure enough, the incorrect cities were there. I couldn't find any for "P" or "Lorba Linda", but that just means that there were no current alerts in the right spot at the right time. These are not WME "smudges".

"Fo": http://i.imgur.com/R3IP4Kf.png
"RRancho": http://i.imgur.com/OFxk66q.png

After seeing a few other anomalies in my local area as well, I am convinced that one of these things is happening when an actual smudge is not there in WME:
1) Waze uses a completely different city list for the app traffic and Livemap alerts versus the visual WME and app tile builds. In this case, it never would have been a smudge.
2) Waze uses the same city list, but in two different tables/databases/whatever. It was a smudge at some point, but the list for alerts is either out of sync or not refreshed often (over a year since there are cities available in the Ann Arbor, MI area that I know have not been existence since I started in Fall 2013...).
3) Waze uses the same list in the same database table, but cities that formerly had segment associations are which are now inactive in WME are still active for the alerts (i.e. it's "deleted" from our perspective in the sense that it is no longer in view, but it still appears in a table somewhere. It's common to maintain this history in databases and just flag something as active/inactive).

[davielde]

I think that's the most likely culprit. Someone puts in a city mistakenly as a typo, it gets a cityID and some kind of geometry, and then for whatever reason, Waze prefers it for alerts even though it is no longer an active city. Perhaps alphabetical order? Although that wouldn't explain how "RRancho" gets precedence over "Rancho", it fits with the other examples.

I found "P" just now at SR-57 and W Temple:
http://i.imgur.com/JV74g9d.png

[HandofMadness]

I see this too. It shows up on the status reports you see when stopped. "Object in Road near Lorba Linda".

I've been all over the city looking for wrong city name, and can't find any segments with the wrong city. This has been going on since I started using Waze.

[HandofMadness]

I'll try to pay more attention. Pretty sure its just about anywhere along the 91 between the 55 and Green River.

[HandofMadness]

Did some playing around. Looks like anything on the 91 between Gypsum Canyon and Green River is getting the "Lorba Linda" location.

UPDATE: Seems to start just east of Weir Canyon.

[HandofMadness]

[img]http://img.tapatalk.com/d/14/06/28/zu3ena9a.jpg[/img]

[img]http://img.tapatalk.com/d/14/06/28/jyhesuqy.jpg[/img]

[HandofMadness]

Bump

[HandofMadness]

shawndoc -

I'm curious how you managed to narrow it down so much; by looking at reports in the app?

Nothing on the 91W I take it....

Yes, I manually scrolled the app along the 91 during rush hour clicking each report to see which said Lorba Linda.

[jemay]

I have this request into Waze already. And we keep getting back they can not find Lorba...

I also brought it up in this forum.
https://www.waze.com/forum/viewtopic.php?f=129&t=78648

I have not let up on it yet... If you can, get screen captures and post them in the above forum to keep adding additional examples...