Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Is that true even for the relatively new Android "raw GNSS" API? https://developer.android.com/develop/sensors-and-location/s...

I believe Google are using that themselves for their "urban canyon" GPS improvements: https://android-developers.googleblog.com/2020/12/improving-...



The API would provide pseudoranges and also the carrier phase on some phones, so it should be possible to calculate a solution with corrections.


Does this api improve on GPS drift?

Or is it up to the engineer to decide how to best to use these improvements?


The raw measurements API provides raw GNSS measurements so that somebody can implement their own position engine, and do things like RTK.

The corrections mentioned in the blog post are calculated by the phone (in Google Play Services, using Google's 3D building models) using the raw GNSS measurements, and provided back to the chipset to improve its position estimate (correcting for reflections and interference).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: