3 ms·
Usually happens due to very high uncertainty in localization estimates.
by cjhanks 8y ago
Usually happens due to very high uncertainty in localization estimates.
- btilly 8y agoI have it happen to me over and over again when Waze has my GPS coordinates. Its uncertainty is on the level of where I am in my house, and not which town I'm in.
- bpicolo 8y agoBy adding a distance measurement they've solidified a best-guess, though.
- cjhanks 8y agoYeah, often the guess you have is something you have no confidence in. Also, I am just speculating as someone who has had similar problems... I did not contribute to this app. Another common case is the history of your behavior is fully remote and your instantaneous connectivity is out-of-sync. So the map falls back to this kind of primitive state more similar to TomTom rather than being intuitive and catered.
- sharkbot 8y agoLooks like it prioritized historical locations over nearby locations. The little clock icon usually represents a prior location that was selected. Could be an interesting design approach to know which locations are "fungible". I.e., one Wawa is as good as another, but your parent's house isn't a replacement for mine [1]. [1] I'm sure your parents are very nice, of course :)
- jonknee 8y agoAnd ironically the OP was complaining that it didn't return him to the same WaWa: > Last time I asked for directions to a Wawa, it was to the one on Oak Lane, 5.9 miles away. Why doesn't it guess that I might be trying to go back to the same place?