Comment 10 for bug 1481240

I'm not convinced that location-service is causing issues here. We do not switch on positioning unless someone explicitly asks us to do so. In that case, it will take ~30 seconds until network-based positioning kicks in and likely another 2 - 3 minutes until the GPS hands us a position. With that, we are likely seeing a race on startup here.

For Pete's statement: The location service deals in numeric values on purpose. Geocoding and reverse geocoding is consciously left out and we assume other layers of the system to do a better job of the encoding/decoding task (we also want to avoid calling "home" to a geoip service from a central system service).