Geoclue 2.1.1

I just rolled out Geoclue 2.1.1! Since my last post with Geoclue update, there has been lots of changes. You can find a list of all the changes here but here are the highlights:

  • Modem geolocation: If you got a 3GPP modem, geoclue will now be able to use that to locate you (with neighborhood-level accuracy) using opencellid.org. Additionally if your modem has GPS capability, geoclue can use that as well and as you know GPS is the most reliable geolocation source.

    One issue with GPS currently is that it takes a while before it can get a lock on and reason for that is that we currently have no support for A-GPS. I'll be talking with Aleksander Morgado during the weekend about how we can add that support but if I've understood correctly, it will need more work in ModemManager than geoclue now that it has all these other sources.

    Geoclue locating me using 3GPP source

  • WiFi geolocation: In my last relevant blog post, I mentioned that we'll be implementing this using Open WLAN Map project but around the same time Mozilla announced their own public geolocation API. After careful consideration, I decided to go for Mozilla Location Service. So geoclue now has a geolocation source that makes use of this public service.

    This service being very new, doesn't have a lot of data. If you want to help us (GNOME), Mozilla and all users of this service and geoclue, you can gather data using MozStumbler android application, which should work on most (if not all) android phones. I also implemented data gather in geoclue but it requires a GPS-enabled 3GPP modem and (at least for now) needs to be explicitly enabled in our configuration file.

    An advantage of using Mozilla Location Service is that it offers a Google geolocation compatible API as well. Geoclue uses this compatibility API and you can make it use Google's geolocation service instead by tweaking an option in our configuration file. Please note that geoclue is not responsible for any misuse of Google API. Please do read their ToS before use and you'll need to get yourself a key before you can use their API.

  • API to check if geolocation service is in use and next version of GNOME Shell will make use of it to show an icon in the panel to indicate to user that their location is being accessed.
GNOME Shell indicator for 'location services in use'

So keeping all this in mind, I'm pretty happy with our progress on geoclue2. I will be in Brussels this weekend. Unfortunately my submission about geo* to desktop devroom didn't make it to the shortlist (which I hear is half as short as last year's) but feel free to talk to me about geolocation and maps etc if you are around.

http://fosdem.org/

Comments

Post a Comment

Popular posts from this blog

Welcome to the virtual world!

Image
About two months ago I informed  the followers of this blog that I will now be working on SPICE project  for Red Hat . Judging from the questions I was asked after that, I realized that not many people know about SPICE so I thought I write at least one blog entry dedicated to explaining what SPICE is all about. Before I get to SPICE itself, let me first introduce you to the world SPICE lives in. Virtualization and Virtual Machines (VMs) For some reason, I feel that I should leave the definitions to wikipedia  and only quote it so that is what I am going to do: " Virtualization, in computing, is the creation of a virtual (rather than actual) version of something, such as a hardware platform, operating system, a storage device or network resources. " " A virtual machine (VM) is a "completely isolated operating system installation within your normal operating system".Today, this is implemented by either software emulation or hardware virtualization ". V
Read more

clutter-gst

After I was informed about the existence of ClutterGstVideoSink, I quickly modified my super-video application to make it use that. But as soon as i did that, i stopped getting even the static image. After careful analysis for days, I figured that I was supposed to call gst_bus_add_signal_watch() on the pipeline bus since ClutterGstVideoSink uses messages on the bus combined with signal handlers to render the frames in the application thread. This is obviously a 'dirty' hack; a hack because gst elements are supposed to do all the media processing in the pipeline thread, dirty because gst bus is not meant for media transport. After this realization, I had been working on it from time to time. First I tried to make the actual rendering happen in the gst pipeline thread by using the clutter's thread safety primitives and that worked quite nicely in the end except for one minor problem: The call to clutters rendering thread blocks if it happens after the clutter main loop has b
Read more

zbus and Implementing Async Rust API

Image
zbus As many of the readers already know, for the past (almost) 2 years, I've been developing a Rust-crate for D-Bus, called zbus . With this being my first big Rust project to start from scratch done almost entirely in my spare time, the progress was rather slow for many months. My perfectionism didn't help much with the progress either but also the fact that implementing a Serde API for the D-Bus format was quite challenging. Then along came my old friend and ex-colleague, Marc-André Lureau who sped up the progress 10 times and soon after we had the 1.0 release of zbus. While my original plan (perfectionism again) was for the API to be primarily async, with the synchronous API mostly just a wrapper around it, it was Marc-Andre who ended up doing most of the work and coming up with nice high-level API and his use case was primarily synchronous so we decided to go with synchronous API first. I still believe that was the right thing to do, since neither of us were fam
Read more