title: Using kCLLocationAccuracyBestForNavigation for non-navigation
body: <p>Apple's <a href="https://developer.apple.com/library/mac/documentation/CoreLocation/Reference/CoreLocationConstantsRef/index.html#//apple_ref/doc/constant_group/Accuracy_Constants" rel="nofollow">documentation</a> states that using <code>kCLLocationAccuracyBestForNavigation</code> is only recommended for navigation applications, and only when plugged in, due to the additional battery usage.</p>
  
  <p>I'm developing an application that only needs location periodically, perhaps even only once per app load, to find the user's location to display them some nearby places to choose from. So I don't need it often, but when I need it, it needs to be really accurate (and obviously as quick as possible). My desire is to try and get to 10m accuracy (or better) as quickly as possible.</p>
  
  <p>If I use <code>kCLLocationAccuracyBestForNavigation</code>:</p>
  
  <ol>
  <li><p>Will this have any meaningful impact on the battery when used for a short period of time (measured in seconds)? Or is Apple's conservative guidance aimed at people using this accuracy level for long periods of time?</p></li>
  <li><p>Perhaps of more importance, does this level of accuracy lead to longer wait times when the location manager first starts up? I.e. wait time before first reasonably accurate locations are reported?</p></li>
  <li><p>Is there any documentation of the technical differences between <code>kCLLocationAccuracyBestForNavigation</code> and <code>kCLLocationAccuracyBest</code>? I.e. what is happening exactly that allows the former to be more accurate? </p></li>
  </ol>