Geek Answers Handbook

How accurate are CoreLocation accuracy measurements?

I tested the accuracy of various aspects of CoreLocation and was surprised to find the accuracy value provided in the new and old places passed to the CLLocationMangerDelegate: (void) locationManager: didUpdateToLocation: fromLocation method is wildly inaccurate.

Walking along some sections of the sidewalk (along a stretch of road with buildings along one side), I found that although the CLLocationManager claims that the CLLocations he supplies have horizontal accuracy of 5 meters, in fact the position shown by MKUserAnnotation is something up 30 meters from the position that I know, I am (often showing as the opposite side of a row of buildings). This suggests that the accuracy reading itself is inaccurate. CLLocationManager informs me that its coordinates are accurate to within 5 meters, but are actually at a distance of 30 meters.

To clarify, this is not a cache / timestamp issue. It is repeatable in certain areas, not over time, which improves over time.

Has anyone else encountered this problem?

+5
source share
3 answers

CoreLocation is not human and does not know where you are "really", the essence of the answer to your question. It uses sensors on your device and gives you the best answer, and problems with its ability to know the accuracy of the stated answer reflect that the location problem is inherently very complex.

: CoreLocation , SSID , , GPS, . , , , , , . , , CoreLocation, , , , " ".

kCLLocationAccuracyBestForNavigation - , CoreLocation " , ", , , . , CoreLocation, , " " - , , , : " , ".

CoreLocation, , , , , , , . , , CoreLocation - , , , , . 10 , 100 , 1 3 . , CoreLocation , - - , , , .

, : CoreLocation , , , , , , , , , CoreLocation , , , CoreLocation , , , API . CoreLocation , , , , , , App Store .

+8

, . 65 2-3 . u 1414 .

+4

Set desiredAccuracy tokCLLocationAccuracyBestForNavigation

And this is the best you can get.

0
source

More articles:


All Articles