Hello all developers,
We've made our asset tracking application based on the Nordic SDK. From working with this for a while now, I have some observations I would like to discuss here.
From SDK 2.2.0, these has been several improvements to the Location library. This handles almost everything, but we're not so "hands on" the code when using this. I feel like it provides less feedback on getting a fix (like satellite stats, timeout, assistance data handling, location methods etc). Its quite the black box.
Alternatively, we can use "the rest", like nrf_cloud lib extensions with multicell, agps etc to achieve the same result. This is a bit more work, but we have better control and more flexibility in adapting the system as we want to. I.e, The callback functions supported by the nrf_modem_gnss is a lot better than the one made available through he location lib.
The location library also has a great new feature in selecting accuracy of gnss fix. There seems to be no way in getting this without using this approach.
I have not been able to combine the location library with other approaches, like using location lib only for gnss, but handling fallback to cell location by multicell_location (Some config options couldn't be combined, cant remember which ones right now), or using the nrf_modem_gnss CB in combination with location lib (Would have to start gnss twice - seems like nonsense)
I guess what I'm wondering, is my understanding here correct? If someone would like to elaborate on my assumptions, this would be very welcomed.
Thank you all for any insight provided!
Kind regards,
Torje
