@aaronpk we're currently looking at geoloqi but would you mind clarifying the benefits of using your service over iOS CLLocationManager calls? Specifically, hav

@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? Thanks!