title: Decoding the CLLocationAccuracy const's
body: <p>the following are listed in CLLocation.h but from my experience they are deceiving names- possibly originally thought up to serve two purposes, 1. to test the accuracy of the location returned, but also 2. to set how hard the location manager works, specifically what is enabled (gps (how many sat channels), how hard the wifi works, triangulation etc.</p>
  
  <pre><code>extern const CLLocationAccuracy kCLLocationAccuracyBestForNavigation; // (raw value: -2)
  extern const CLLocationAccuracy kCLLocationAccuracyBest; // (raw value: -1)
  extern const CLLocationAccuracy kCLLocationAccuracyNearestTenMeters; // (raw value: 10)
  extern const CLLocationAccuracy kCLLocationAccuracyHundredMeters; // (raw value: 100)
  extern const CLLocationAccuracy kCLLocationAccuracyKilometer; // (raw value: 1000)
  extern const CLLocationAccuracy kCLLocationAccuracyThreeKilometers; // (raw value: 3000)
  </code></pre>
  
  <p>I would love to take a look at CLLocation.m, but as that is not likely to happen any time soon- does anyone have any field testing showing what they think is going on with these different modes.</p>
  
  <p>ie, kCLLocationAccuracyBest = 10 satellite (channels/trunks?), 100% power to wifi etc..</p>
  
  <p>I'm kind of guessing at straws here- I think this is the type of information apple should have provided-</p>
  
  <p>what I really want to know is, what is actually happening with <code>kCLLocationAccuracyThreeKilometers</code> in relation to battery draw- is the gps on? 1 sat trunk? wifi enabled? wifi on a timer? who knows? I know I'd like to</p>