title: Understanding MKCoordinateFromMapPoint behaviour
body: <p>In a location based app we use MKMapPoints to store locations, for example the current user location.</p>
  
  <p>When we try use this location on a MKMapView, to set the region that is initially displayed (zoomed in on the user) we convert this to a CLLocationCoordinate2D</p>
  
  <p>There's a convernience method for that: namenly: MKCoordinateForMapPoint, but during testing this gives strange results.</p>
  
  <pre><code>  MKMapPoint mapPoint = MKMapPointMake(51.96, 6.3); // My area ;)
    CLLocationCoordinate2D automagicCoordinate = MKCoordinateForMapPoint(mapPoint);
    CLLocationCoordinate2D manualCoordinate = CLLocationCoordinate2DMake(mapPoint.x, mapPoint.y);
  </code></pre>
  
  <p>I would expect both the automagicCoordinate and the manualCoordinate to be exactply the same.
  but when I inspect it in the debugger I get the following result:</p>
  
  <pre><code>automagicCoordinate.latitude = (CLLocationDegrees) 85.05
  automagicCoordinate.longitude = (CLLocationDegrees) -179.99
  
  manualCoordinate.latitude = (CLLocationDegrees) 51.96
  manualCoordinate.longitude = (CLLocationDegrees) 6.3
  </code></pre>
  
  <p>How come the coordinate created with the method is incorrect? </p>