As per: http://article.gmane.org/gmane.comp.gnome.geoclue/246/ You want both most of the time and it avoids disconnects between the providers.
It's usefult to note that people who see geoclue as first and foremost a GPS wrapper with fallback methods (say, people developing for mobile phones) would like and api like this: 1. position, velocity, satellite data (which we currently don't have) all available in one callback/signal 2. the rest (addresses, geocoding) can be laid out however, but the unavailability of e.g. address data should not delay the position delivery Not sure how to reconcile this... Maybe just single Location interface with other ways to deal with capabilities: back when we designed the current api, separate interfaces sounded like a good enough way to do that but it seems that is incorrect.
See bug 29989 for the "combine position and velocity" issue.
Closing all bugs on old geoclue. If your bug still applies to new geoclue, please do re-open, I really don't have time to go through each and every bug and evaluate separately. :( Apologies for any inconvenience caused by this change.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.