@aaronpk we're currently looking at geoloqi but would you mind clarifying the benefits of using your service over iOS CLLocationManager calls? Specifically, have you analyzed the relative power consumption & accuracy of various CLLocationManager settings?
For example, we found the best power consumption when the desiredAccuracy value is set to kCLLocationAccuracyThreeKilometers, and we trigger the startMonitoringSignificantLocationChanges method before entering into the background. Surprisingly, the accuracy was much better than 3km but varied depending on device & OS. Similarly, the power consumption was affected by the background network access schemes & buffering we used, of course.
Anyway, we stopped our studies after sampling just a few devices (3GS, 4) and one or two OS releases (iOS 4.2 and 5.0). Don't mean to pry your secret sauce, but what type of calibration are you offering?
Sounds like you've been doing a good amount of experimenting as well! If you use the default startMonitoringSignificantLocationChanges method you'll get updates sporadically depending on things like what other apps are using location services, so it looks pretty crazy in the wild. It will also skip over many geofences if they are smaller than a kilometer or so. Our SDK manages this intelligently and can trigger the smaller geofences more reliably without the phone being in super-accurate mode the entire time. If you send your contact info through our site we'd be happy to talk about this further! https://developers.geoloqi.com/enterprise
This is fantastic! I've been ephemerally plotting my GPS tracks for a few years (though I'm only up to about 1.6M points), but the thought of publishing my tracks on the open internet has always seemed just a little too creepy, even by internet standards.
Good question. The movement is all natural. I tried as much as possible to avoid changing my behavior because I was recording my location. I wanted to get an objective picture of where I had been.
For example, we found the best power consumption when the desiredAccuracy value is set to kCLLocationAccuracyThreeKilometers, and we trigger the startMonitoringSignificantLocationChanges method before entering into the background. Surprisingly, the accuracy was much better than 3km but varied depending on device & OS. Similarly, the power consumption was affected by the background network access schemes & buffering we used, of course.
Anyway, we stopped our studies after sampling just a few devices (3GS, 4) and one or two OS releases (iOS 4.2 and 5.0). Don't mean to pry your secret sauce, but what type of calibration are you offering?
Thanks!