CODEWITHSUNDEEP
ioscllocationmanagerios10cllocation
ganka
ganka

Reputation: 309

Location timestamp accuracy in ios

After analysing location services in iOS 10, found that some inconsistency is in the caching behaviour.

Fetching locations in a periodic time (in my case every 20 secs) returns locations but their timestamps are not in chronologically ordered. This indicates that the caching locations might have issues. So if you are checking accuracy through location-timestamp better to save the previous timestamps also. So that you could decide that the location fetched can be used or not.

Below image is taken from my console log. Here I used the format "Lat Long : latitude_longitude | location_timestamp | Now : current_timestamp"

highlighted rows have older timestamps

Upvotes: 3

Views: 4870

Answers (3)

Chirag Shah
Chirag Shah

Reputation: 3016

Yes some time in best accuracy ios take the location from the cache so you need to avoid that location here is the code for accurate locationtion.

Update : "Because it can take several seconds to return an initial location, the location manager typically delivers the previously cached location data immediately and then delivers more up-to-date location data as it becomes available. Therefore it is always a good idea to check the timestamp of any location object before taking any actions."

Reference :

https://developer.apple.com/reference/corelocation/cllocationmanager

Note: you can vary the accuracy for the device like ipod and ipad 

//MARK: Location delgates
    func locationManager(_ manager: CLLocationManager, didUpdateLocations locations: [CLLocation])
    {
        if locations.count > 0
        {
            let location = locations[locations.count-1]

            let maxAge:TimeInterval = 60;
            let requiredAccuracy:CLLocationAccuracy = 100;

            let locationIsValid:Bool = Date().timeIntervalSince(location.timestamp) < maxAge && location.horizontalAccuracy <= requiredAccuracy;
            if locationIsValid
            {
                NSLog(",,, location : %@",location);
                NSLog("valid locations.....");

            }
        }
    }

Upvotes: 4

netshark1000
netshark1000

Reputation: 7403

The problem behind this is that sometimes the timestamps do not match to the location! E.g. while traveling you suddenly records speeds > 300km/h and best accuracy.

I would sort the locations and only would take the last one if not too old:

func locationManager(_ manager: CLLocationManager, didUpdateLocations locations: [CLLocation]) {

        let sortedLocations = locations.sorted { (l1, l2) -> Bool in
            return l1.timestamp.compare(l2.timestamp) != .orderedDescending
        }

        if let newestLocation = sortedLocations.last{

            if Date().timeIntervalSince(newestLocation.timestamp) < 60{
                //TODO: Use the location
            }
        }
    }

Upvotes: 1

ganka
ganka

Reputation: 309

Yes like @chirag shah commented we definitely need to do that check. My suggestion is we should know about that the caching technique has been modified. And also it is not enough only checking the timestamp, we have to focus on the failure case. Here is the objective C code

-(void)locationManager:(CLLocationManager *)manager didUpdateLocations:(NSArray *)locations{

    CLLocation* location = [locations lastObject];
    NSDate* locationTimestamp = location.timestamp;
    NSTimeInterval cachedBefore = [locationTimestamp timeIntervalSinceNow];
    if (fabs(cachedBefore) < 60.0) {
        // Implement your code here
    }else{
        // Try again or wait for fetching location
    }
}

Upvotes: 0

Related Questions