LocationOperation issue with CLLocationAccuracy constants

[sirnacnud]

If you create a LocationOperation with accuracy set to kCLLocationAccuracyBestForNavigation, the location handler won't be called, as in didUpdateLocations, the horizontal accuracy of the current location is compared to the accuracy the user specified. The problem is that kCLLocationAccuracyBestForNavigation is defined as -2, so the only time the current location will have a negative horizontal accuracy is if it is invalid.

I'm not for sure if supplying kCLLocationAccuracyBestForNavigation, or any of the other constants that have a negative value, should be supported. It seems Apple's original code sample has this same issue.

[mcmurrym]

I'm open to solutions but am not an expert in this. If you feel you have an appropriate solution feel free to submit a pull request. Tests around this would be great too.