Yes, you can have a custom view for the user’s location. Unfortunately, it’s harder to implement than it should be because even though the documentation for the viewForAnnotation delegate method claims that you can just supply your own view if the annotation class is MKUserLocation, the custom view does not then continue to move with … Read more
I created a project based on your CalloutMapAnnotationView demonstrating a IB based solution. Arrow keys animate motion of the location annotation and it’s callout annotation. The callout now also automatically resizes based on the supplied contentView, and the view is loaded from a separate nib. Good luck! https://github.com/jacobjennings/JJMapCallout
In the viewForAnnotation method, you can access your ArtPiece properties but to avoid compiler errors and warnings, you’ll need to first cast the annotation parameter to your custom class. The annotation parameter in that method is just defined as a id<MKAnnotation> so the compiler won’t know about the ArtPiece-specific properties (until you tell it that … Read more
For some reason (possibly a bug), the path property returns NULL in the current release of iOS 7. A workaround is to construct your own CGPathRef from the points of the polygon. With this method, you don’t need a reference to the MKPolygonView or the MKPolygonRenderer. For example: CGMutablePathRef mpr = CGPathCreateMutable(); MKMapPoint *polygonPoints = … Read more
If you’re working with iOS 7+ only, there’s a new camera.altitude property that you can get/set to enforce a zoom level. Its equivalent to azdev’s solution, but no external code is required. In testing, I also discovered that it was possible to enter an infinite loop if you repeatedly tried to zoom in at detail, … Read more
After a lot of playing around and testing different ideas, some of which were mentioned here, the final solution that worked for me was as follows. Instead of creating new MKMapView’s as needed in the app, I added an mkMapView property to my AppDelegate and only created it when needed. Once it has been created, … Read more
There is an even easier solution. Create a custom UIView (for your callout). Then create a subclass of MKAnnotationView and override setSelected as follows: – (void)setSelected:(BOOL)selected animated:(BOOL)animated { [super setSelected:selected animated:animated]; if(selected) { //Add your custom view to self… } else { //Remove your custom view… } } Boom, job done.
In the viewForAnnotation delegate method, set the image based on which annotation the method is being called for. Be sure to do this after the view is dequeued or created (and not only in the if anView == nil part). Otherwise, annotations that use a dequeued view will show the image of the annotation that … Read more
The following converts the coordinate to a CGPoint in the polygon view and uses CGPathContainsPoint to test if that point is in the path (which may be non-rectangular): CLLocationCoordinate2D mapCoordinate = …; //user location or annot coord MKMapPoint mapPoint = MKMapPointForCoordinate(mapCoordinate); MKPolygonView *polygonView = (MKPolygonView *)[mapView viewForOverlay:polygonOverlay]; CGPoint polygonViewPoint = [polygonView pointForMapPoint:mapPoint]; BOOL mapCoordinateIsInPolygon = … Read more
When you want to use your own image for an annotation view, you should create an MKAnnotationView instead of an MKPinAnnotationView. MKPinAnnotationView is a subclass of MKAnnotationView so it has an image property but it generally overrides that and draws a pin image (that’s what it’s for). So change the code to: -(MKAnnotationView *)mapView:(MKMapView *)mV … Read more