#mkannotation

[antonio081014]

How to Customize Map Annotation and Map Annotation View

Many developers might have seen iOS app like yelp, foursquare, they have their own very customized Annotation View providing very specific information.

While, in this demo, it will show you how to make your own map annotation and annotation view. 

1st, create a new project, name it "Tracker 286s".

2nd, Add MapKit framework to your project. (It's under Build Phases of your project target).

3rd, Go to your storyboard, drag a toolbar and MKMapView to the your controller's view. The clear button will clear all the annotation from the map.

4th, Ctrl + drag your MapView outlet to the ViewController.m, also ctrl + drag the clear(Bar Button Item) to add the IBAction to the ViewController.m

5th, Add 

@import MapKit;

in the ViewController.m file.

6th, Add <MKMapViewDelegate> right after 

@interface ViewController ()

To create an Annotation to be added to the MapView, we need to create a class conforms MKAnnotation Protocol.

7th, Create a new file names MAnnotation subclass of NSObject, conforms <MKAnnotation>.

// // MAnnotation.h // Tracke 286s // // Created by Antonio081014 on 4/7/14. // Copyright (c) 2014 Antonio081014.com. All rights reserved. // #import <Foundation/Foundation.h> @import MapKit; @interface MAnnotation : NSObject <MKAnnotation> @property (nonatomic, strong) NSNumber *angle; - (id)initWithLocation:(CLLocationCoordinate2D)coord andAngle:(CGFloat) angle; @end

In this code, we have a public property angle, which will be used and explained later. Also a public designate initializer is declared, which contains a coordinate tells where in the map the annotation will be, and the angle.

8th, Implement the function in MAnnotation File. 

// // MAnnotation.m // Tracke 286s // // Created by Antonio081014 on 4/7/14. // Copyright (c) 2014 Antonio081014.com. All rights reserved. // #import "MAnnotation.h" @implementation MAnnotation @synthesize coordinate = _coordinate; @synthesize title = _title; @synthesize subtitle = _subtitle; - (id)initWithLocation:(CLLocationCoordinate2D)coord andAngle:(CGFloat)angle { self = [super init]; if (self) { self.coordinate = coord; self.angle = [NSNumber numberWithDouble:angle]; } return self; } #define epsilon 0.005f - (void)setCoordinate:(CLLocationCoordinate2D)newCoordinate { if ((fabs(_coordinate.latitude - newCoordinate.latitude) > epsilon || fabs(_coordinate.longitude - newCoordinate.longitude) > epsilon)) { [self willChangeValueForKey:@"coordinate"]; _coordinate = newCoordinate; [self didChangeValueForKey:@"coordinate"]; } } - (CLLocationCoordinate2D)coordinate { return _coordinate; } - (void)setTitle:(NSString *)title { if (_title != title) { [self willChangeValueForKey:@"title"]; _title = title; [self didChangeValueForKey:@"title"]; } } - (NSString *)title { if (_title) { return _title; } return _title = [NSString stringWithFormat:@"%.6f", [self.angle doubleValue]]; } - (NSString *)subtitle { if (_subtitle) { return _subtitle; } return _subtitle = [NSString stringWithFormat:@"(%.5f, %.5f)", self.coordinate.longitude, self.coordinate.latitude]; } - (void)setSubtitle:(NSString *)subtitle { if (_subtitle != subtitle) { [self willChangeValueForKey:@"subtitle"]; _subtitle = subtitle; [self didChangeValueForKey:@"subtitle"]; } } @end

Here, implement all the properties of the MKAnnotation, since the Map-Kit uses KVO(Key-Value-Observation) to detect any change of property in MKAnnotation, so when we custom implemented these setters, we need to notify the observers(the one who is interested in these changes) in these setters. Any manual change in your change will require you implementing the corresponding setter. For more reference, check out this link. The title and subtitle are used to display callout, which will be displayed when you click on the annotation on the map.

9th, Display annotation on the Map.

// // ViewController.m // Tracke 286s // // Created by Antonio081014 on 4/7/14. // Copyright (c) 2014 Antonio081014.com. All rights reserved. // #import "ViewController.h" @import MapKit; #import "MAnnotation.h" @interface ViewController () <MKMapViewDelegate> @property (weak, nonatomic) IBOutlet MKMapView *mapView; @end @implementation ViewController #define METERS_PER_MILE 1609.344 - (void)viewWillAppear:(BOOL)animated { [super viewWillAppear:animated]; // Set the center of the map. // This is the Park near Los Angeles City Hall. CLLocationCoordinate2D centerLocation; centerLocation.latitude = 34.0528873; centerLocation.longitude = -118.2434255; // Create a Map Region based on the Center Location created above and the size defined below. MKCoordinateRegion viewRegion = MKCoordinateRegionMakeWithDistance(centerLocation, 0.5*METERS_PER_MILE, 0.5*METERS_PER_MILE); // Set the Map Region to display. [self.mapView setRegion:viewRegion animated:YES]; // Create the coordinate for the Annotation. // This is the location of Los Angeles City Hall, which could be fetched from Google Map. CLLocationCoordinate2D coordinateOfLACityHall; coordinateOfLACityHall.latitude = 34.053714; coordinateOfLACityHall.longitude = -118.242653; // Create the Annotation with our designate initializer. MAnnotation *annotation = [[MAnnotation alloc] initWithLocation:coordinateOfLACityHall andAngle:90.f]; // Add the annotation to the Map. [self.mapView addAnnotation:annotation]; } - (IBAction)clearAllAnnotations:(UIBarButtonItem *)sender { } @end

Most of the code are already explained in the comment around the code. You should get something like this:

When click on the red pin point, you should see:

Which displays the angle as the title, coordinate as the subtitle as we defined in our MAnnotation class.

10th, Custom Annotation View. Adding this snippet to your ViewController.m file.

- (MKAnnotationView *)mapView:(MKMapView *)mapView viewForAnnotation:(id<MKAnnotation>)annotation { return nil; }

This function will be like this even you don't write it here. It's a default delegate function.

11th, Create a new file MAnnotationView subclass MKAnnotationView. So the MAnnotationView.h file will look like:

// // MAnnotationView.h // Tracke 286s // // Created by Antonio081014 on 4/7/14. // Copyright (c) 2014 Antonio081014.com. All rights reserved. // #import <MapKit/MapKit.h> @interface MAnnotationView : MKAnnotationView @end

12th, Implement the designate initializer which will be called in the 

- (MKAnnotationView *)mapView:(MKMapView *)mapView viewForAnnotation:(id<MKAnnotation>)annotation;

So with other function.

// // MAnnotationView.m // Tracke 286s // // Created by Antonio081014 on 4/7/14. // Copyright (c) 2014 Antonio081014.com. All rights reserved. // #import "MAnnotationView.h" #import "MAnnotation.h" @implementation MAnnotationView - (instancetype)initWithAnnotation:(id<MKAnnotation>)annotation reuseIdentifier:(NSString *)reuseIdentifier { self = [super initWithAnnotation:annotation reuseIdentifier:reuseIdentifier]; if (self) { // Set the frame size to the appropriate values. CGRect cFrame = self.frame; cFrame.size.width = 40; cFrame.size.height = 40; self.frame = cFrame; self.contentMode = UIViewContentModeRedraw; // The opaque property is YES by default. Setting it to // NO allows map content to show through any unrendered parts of your view. self.opaque = NO; } return self; } // This function is critical, the comment is very important. // Whenever you assign an annotation to this view, the view will be redraw. - (void)setAnnotation:(id <MKAnnotation>)annotation { [super setAnnotation:annotation]; // this annotation view has custom drawing code. So when we reuse an annotation view // (through MapView's delegate "dequeueReusableAnnoationViewWithIdentifier" which returns non-nil) // we need to have it redraw the new annotation data. // // for any other custom annotation view which has just contains a simple image, this won't be needed // [self setNeedsDisplay]; } // Only override drawRect: if you perform custom drawing. // An empty implementation adversely affects performance during animation. // This function simply draw a triangle, then rotate in proper angle. - (void)drawRect:(CGRect)rect { CGFloat angle = 0.f; if ([self.annotation isKindOfClass:[MAnnotation class]]) { MAnnotation *annotation = (MAnnotation *)self.annotation; angle = [annotation.angle doubleValue]; } CGFloat size = MIN(self.bounds.size.width, self.bounds.size.height) / 2.f; CGPoint center = CGPointMake(self.bounds.size.width / 2.f, self.bounds.size.height / 2.f); // Draw the Path. UIBezierPath *path = [[UIBezierPath alloc] init]; [path moveToPoint:CGPointMake(center.x + 0.f, center.y - size)]; [path addLineToPoint:CGPointMake(center.x - size / 2.f, center.y + size / 2.f * sqrt(3.f))]; [path addLineToPoint:CGPointMake(center.x + size / 2.f, center.y + size / 2.f * sqrt(3.f))]; [path closePath]; // Rotate to the right angle. CGAffineTransform transform = CGAffineTransformIdentity; [path applyTransform:transform]; transform = CGAffineTransformTranslate(transform, center.x, center.y); transform = CGAffineTransformRotate(transform, angle / 180.f * M_PI); transform = CGAffineTransformTranslate(transform, -center.x, -center.y); [path applyTransform:transform]; // Fill and Stroke with right color. [[UIColor redColor] setFill]; [[UIColor blackColor] setStroke]; [path fill]; [path stroke]; } @end

Most of the code are explained with the comment.

13, Back to the ViewController.m file, Add the following code right after [super viewWillAppear:animated];

self.mapView.delegate = self;

14, Add the following code to the ViewController.m file.

- (MKAnnotationView *)mapView:(MKMapView *)mapView viewForAnnotation:(id<MKAnnotation>)annotation { // If this annotation is our custom define annotation, we'll display it in our custom annotation view. if ([annotation isKindOfClass:[MAnnotation class]]) { static NSString *annotationViewIdentifier = @"Custom Annotation View"; // We retrieve this annotation view. MKAnnotationView *annotationView = [self.mapView dequeueReusableAnnotationViewWithIdentifier:annotationViewIdentifier]; // If it has been used before, we update the annotation information, so the view could be redraw. if (annotationView) { annotationView.annotation = (MAnnotation *)annotation; } // Otherwise, let's create it. else { annotationView = [[MAnnotationView alloc] initWithAnnotation:(MAnnotation *)annotation reuseIdentifier:annotationViewIdentifier]; annotationView.opaque = NO; } return annotationView; } // Otherwise, will use annotation's default annotation view to display it. // For user current location, it will be a blue twinkle ball. // For other location, it will be a red point pin. return nil; }

Build and Run this code, you will see:

15th, For last, we'll remove the annotations from the Map by implement 

- (IBAction)clearAllAnnotations:(UIBarButtonItem *)sender

Adding this snippet in this function: 

[self.mapView removeAnnotations:self.mapView.annotations];

If you have more question about removing annotations from MapView, check out another post.

For the full code, check out the github.

[antonio081014]

How to Remove All the Map Annotations except Current User Location Annotation

Today, working on the project focused on Location and Map View Programming. I need to update the Map Annotation Display when user zoom in and out the map. This would totally make sense here the Annotation will not be resizable and too many of the Annotations displayed in a very small area on the Map. It's like this April Fool's Day, Google Map on mobile device gave people the fun of being a Pokemon Master by finding all the Pokemon, which is displayed as an Annotation on the map. It could be seen only when certain zoom level you are in. So, to find all the Pokemon, you have to zoom to certain level, then search it manually like a tank. So, the question here is how can we remove these MKAnnotations. This task is very easy by using one line code:

[self.mapView removeAnnotations:self.mapView.annotations];

The mapView is the outlet connected with MKMapView in the storyboard. But this line of code would remove all of the annotations on the map. While my app intentionally need to keep the current user location's annotation to constantly display the current location of the user. How can we do that? We need to iterate through all the annotations, find out which one is not the Current User Location Annotation.

for (id<MKAnnotation> annotation in self.mapView.annotations) { if (![annotation isKindOfClass:[MKUserLocation class]]) { [self.mapView removeAnnotation:annotation]; } }

Simple solution. Good luck with your own project.

[flatironschool]

Creating Custom Map Annotations using MKAnnotation Protocol

The following is a guest post by Basar Akyelli and originally appeared on his blog. Basar is currently in the iOS-000 class at The Flatiron School. You can follow him on Twitter here.

This week at Flatiron School, we learned how to create custom UIMapView annotations using the MKAnnotation protocol. Even though at first I found it to be more complicated than it should be, it started to make more sense after I used it a few times.

Let’s build a single view application that shows our custom MKAnnotation object on a map.

On Xcode, let’s create a new Single View application:

  Since we’ll be using Map Kit methods and objects, we should add the Map Kit framework to our project.

Onto our main View, let’s drag and drop a Map View and check its “Shows User Location” behavior:

If we run our application now, this is what we get:

Let’s zoom to our location. Not that hard. We need to create an outlet to our Map first. Just Control-drag your map to the ViewController.h file and create an IBOutlet. Let’s name our outlet mapView:

  Don’t forget to import  <MapKit/MapKit.h> in your header file. Now we’re ready to zoom. We will need to implement the Map View’s didUpdateUserLocation method. In order for the Map View to call this method once it finds the user’s location, we need to set its delegate property to our ViewController.

Now let’s run the application again:

 Much better. Now that we’re done with our basic set up. Let’s create a custom annotation for Bryant Park. For this, we’ll need to create a new NSObject class which adheres to the MKAnnotation delegate. Let’s go ahead and create this class, called “MyCustomAnnotation” and set its protocol:

The MKAnnotation protocol asks us to create two properties: an title property which is an NSString, and a coordinate property which is a CLLocationCoordinate2D. We also need to create a new initializer as well as a method which will return an instance of MKAnnotationView: 

title is the text that is displayed inside the Callout box which is shown once you tap on a pin. coordinate is the 2D coordinate of the pin. Let’s go ahead and implement our initializer and our  MKAnnotationView method.

We’re basically returning a MKAnnotationView object that has a custom image (park_icon) and it is able to show a Callout dialogue. It will also have an Detail Disclosure accessory on its right side.

Let’s go ahead and add our custom MKAnnotationView to our map. Let’s not forget to import MyCustomAnnotation.h to our ViewController.m file. We will need to add an annotation to our map, and we’ll also need to implement the viewForAnnotation method of the MapView protocol to set our annotation’s view to our newly built method.

We’re asking the mapView if there are any unused MyCustomAnimation annotations that we can re-use (this is to prevent creating unnecessary annotations — we only need what we see on our screen.) Then we set it to our annotationView method which we built into our MyCustomAnnotation object.

We’re done! Let’s see what our app looks like now:

That’s it! Not that bad, is it?

[bjmiller22]

Using NSFetchedResultsController with an MKMapView

If you're familiar with Core Data, you've most likely encountered an NSFetchedResultsController at some point, and if so, you've doubtless linked it to a UITableView. A challenge I ran across recently was to not only list data from Core Data in a UITableView, but to list that same data in an MKMapView. One thing I quickly remembered: MKMapView's don't use index paths (NSIndexPath) like UITableViews do. 

While looking around for examples of others who have done this, I came across a wonderful article on just the subject. My implementation was a little different, so I felt compelled to write about it, but I did not want to pass on linking to the original article: http://flowandgo.blogspot.com/2011/08/having-fun-with-nsfetchedresultscontrol.html.

Let me start with the MKAnnotation. MKAnnotation is a protocol used by MKMapView to guarantee that any object adhering to it will provide the proper information for the map to display the annotations with proper titles, subtitles, and on the proper coordinate. In my app I already had a Core Data entity with properties for latitude and longitude, so I simply made my human-editable NSManagedObject subclass (in this case, "FamilyMember". Hint: use MOGenerator. You're welcome) adhere to the MKAnnotation protocol, and provided the following three methods in its private implementation:

@implementation FamilyMember - (NSString)title {     return self.name; } - (NSString *)subtitle {     return self.address; } - (CLLocationCoordinate2D)coordinate {     CLLocationCoordinate2D coord;     coord.latitude = [self.latitude doubleValue]; // or self.latitudeValue à la MOGen     coord.longitude = [self.longitude doubleValue];     return coord; } @end

I like doing the whole annotation bit this way, as it saves creating another class just to strictly be the annotation, and then alloc/init'ing a bunch of them throughout the app lifecycle. Having it directly in the entity saves time as the entities are already in an array inside the NSFetchedResultsController, and also reduces code.

OK. Now that your entity is officially also an MKAnnotation object, it will be easier to work with the MKMapView delegate methods. But first, let's add the NSFetchedResultsController. Open your view controller's .m file which has your mapView in it, import <CoreData/CoreData.h>, and add this code:

#import <CoreData/CoreData.h> @interface your_class () <MKMapViewDelegate, NSFetchedResultsControllerDelegate> @property (nonatomic, strong) NSFetchedResultsController *fetchedResultsController; ...any others... @end @implementation your_class - (void)controllerWillChangeContent:(NSFetchedResultsController *)controller { [[UIApplication sharedApplication] setNetworkActivityIndicatorVisible:YES]; } - (void)controllerDidChangeContent:(NSFetchedResultsController *)controller { [[UIApplication sharedApplication] setNetworkActivityIndicatorVisible:NO]; } - (void)controller:(NSFetchedResultsController *)controller didChangeObject:(id)anObject atIndexPath:(NSIndexPath *)indexPath forChangeType:(NSFetchedResultsChangeType)type newIndexPath:(NSIndexPath *)newIndexPath { switch (type) { case NSFetchedResultsChangeInsert: [self fetchedResultsChangeInsert:anObject]; break; case NSFetchedResultsChangeDelete: [self fetchedResultsChangeDelete:anObject]; break; case NSFetchedResultsChangeUpdate: [self fetchedResultsChangeUpdate:anObject]; break; case NSFetchedResultsChangeMove: // do nothing break; default: break; } } - (void)fetchedResultsChangeInsert:(FamilyMember *)familyMember { [self.mapView addAnnotation:familyMember]; } - (void)fetchedResultsChangeDelete:(FamilyMember *)familyMember { [self.mapView removeAnnotation:familyMember]; } - (void)fetchedResultsChangeUpdate:(FamilyMember *)familyMember { [self fetchedResultsChangeDelete:familyMember]; [self fetchedResultsChangeInsert:familyMember]; } @end

The first two methods just simply start the activity indicator in the status bar to show something is happening; they are not necessary. The last three methods are convenience methods. The controller:didChangeObject:atIndexPath:forChangeType:newIndexPath: is called to let you handle how you want to handle the object in question. We simply use a switch() command to check what the change type was, and then handle it accordingly. As you can see, with just one line of code per operation (okay, two for Update), you're altering the map with whatever familyMember object was updated/inserted/deleted (Move doesn't really apply). These methods are called when the NSFetchedResultsController observes changes in the entities you specify, which we'll do here. Still in the same file, add the following:

- (NSFetchedResultsController *)fetchedResultsController { if (_fetchedResultsController) return _fetchedResultsController; NSFetchedResultsController *frc = nil; if (self.managedDocument) { // using UIManagedDocument for Core Data storage NSFetchRequest *request = [NSFetchRequest fetchRequestWithEntityName:@"FamilyMember"]; NSSortDescriptor *sortDescriptor = [NSSortDescriptor sortDescriptorWithKey:@"name" ascending:YES]; [request setSortDescriptors:@[sortDescriptor]]; NSManagedObjectContext *moc = self.managedDocument.managedObjectContext; frc = [[NSFetchedResultsController alloc] initWithFetchRequest:request managedObjectContext:moc sectionNameKeyPath:nil cacheName:nil]; [frc setDelegate:self]; _fetchedResultsController = frc; NSError *error = nil; [_fetchedResultsController performFetch:&error]; [self configureAnnotations]; } return _fetchedResultsController; } - (void)configureAnnotations { [self.mapView removeAnnotations:self.mapView.annotations]; [self.mapView addAnnotations:[self.fetchedResultsController fetchedObjects]]; } // called from AppDelegate, to set the UIMD, and set up the NSFRC - (void)setManagedDocument:(UIManagedDocument *)managedDocument { _managedDocument = managedDocument; [self fetchedResultsController]; }

Breaking this down, we have a custom getter for our _fetchedResultsController property, which returns it immediately if it already exists, or creates one with a fetch request and performs a fetch. The -configureAnnotations method just removes and re-adds the annotations from the _fetchedResultsController's "fetchedObjects" property, which is an NSArray of the entity you specified (in our case, FamilyMember). The -setManagedDocument: method is there so I can immediately call the getter for the NSFetchedResultsController, since now it has an NSManagedObjectContext from which to fetch objects.

Almost there.  That should be it for the NSFetchedResultsController. Now, for the MKMapView delegate methods. Still in the same file, enter the following:

- (MKAnnotationView *)mapView:(MKMapView *)mapView viewForAnnotation:(id)annotation { MKPinAnnotationView *annotationView = (MKPinAnnotationView *)[mapView dequeueReusableAnnotationViewWithIdentifier:@"MyPin"]; if (!annotationView) { annotationView = [[MKPinAnnotationView alloc] initWithAnnotation:annotation reuseIdentifier:@"MyPin"]; annotationView.canShowCallout = YES; annotationView.animatesDrop = YES; } annotationView.annotation = annotation; return annotationView; }

That's it! Because we set the FamilyMember entity to be a conformer of the MKAnnotation protocol, the "annotation" in this method is the FamilyMember object itself, and it will now place a pin on the map where the .coordinate property tells it to go. 

I hope this helps you, and you find it helpful for any project you're working on!

Twitter: @bjmillerltd

App.net: @bjmiller