21–30 of 69 posts
L5 GPS will address the multipath-in-urban-canyon problem that Uber worked on.
Example: https://hikingguy.com/hiking-gear/garmin-gpsmap-66sr-review-...
Google explores these techniques as well. They're critical to improving accuracy in urban areas where you don't have line of sight to satellites (this is why your GNSS (AKA GPS) location is terrible whenever you're in a city). Here's [0] a cool gif visualizing the principle of GNSS ray tracing taken from one of Google's blog posts [1]. Here's an article with more information about Google's techniques [2]. [0] https:/…
Google explores these techniques as well. They're critical to improving accuracy in urban areas where you don't have line of sight to satellites (this is why your GNSS (AKA GPS) location is terrible whenever you're in a city). Here's [0] a cool gif visualizing the principle of GNSS ray tracing taken from one of Google's blog posts [1]. Here's an article with more information about Google's techniques [2]. [0] https:/…
That seems much more useful, since it applies to all Android apps, whereas Uber's solution would be limited to their app only.
If it were available to all android apps I don't know why Uber would go out of their way to reimplement it. So it must not be available to all apps and exclusive to Google maps and Waze
"2018" post.
I didn't even notice the date, thanks. The article presents it as if it was invented at Uber, but there's an identical family of techniques also called "shadow-matching" that have been known in the literature for like a decade. Many companies improve the raw GNSS fix with things like map-matching nowadays, but it was much less common even 5 years ago so this would have been fairly innovative back then.
Google explores these techniques as well. They're critical to improving accuracy in urban areas where you don't have line of sight to satellites (this is why your GNSS (AKA GPS) location is terrible whenever you're in a city). Here's [0] a cool gif visualizing the principle of GNSS ray tracing taken from one of Google's blog posts [1]. Here's an article with more information about Google's techniques [2]. [0] https:/…
I think it says that FLP (Fused Location Provider) is not built in to Android.
The Uber blog post is from 2018, and Google's implementation came in 2020.
Their internal app has ads for other Uber services? Oof.
Earlier quoted context omitted.
That seems much more useful, since it applies to all Android apps, whereas Uber's solution would be limited to their app only.
Almost like they wrote a blog article about it so others could learn from it. If it were available to all android apps I don't know why Uber would go out of their way to reimplement it. So it must not be available to all apps and exclusive to Google maps and Waze