Part 2 - Maps API

PDF for offline use
Related Links:

Let us know how you feel about this


Using the Maps application is great, but sometimes you want to include maps directly in your application. In addition to the built-in maps application, Google also offers a native mapping API for Android. The Maps API is suitable for cases where you want to maintain more control over the mapping experience. Things that are possible with the Maps API include:

  • Programmatically changing the viewpoint of the map.
  • Adding and customizing markers.
  • Annotating a map with overlays.

Unlike the now deprecated Google Maps Android API v1, Google Maps Android API v2 was consolidated into Google Play Services. Therefore, it is necessary to meet some mandatory prerequisites before it is possible to use Google Maps Android API v2 in a Xamarin.Android application.

Google Maps API v2 Prerequisites

Several items need to be configured before you can use the Maps API, including:

  • Installing the Google Play Services SDK.
  • Creating an emulator with the Google APIs.
  • Obtaining a Maps API key.

Installing the Google Play Services SDK

Google Play Services is a technology from Google that allows Android applications to take advantage of various Google features such as Google+, In-App Billing, and Maps v2. These features are accessible on Android devices as background services which are contained in the Google Play Services APK.

Android applications interact with Google Play Services through Google Play Services client library. This library contains the interfaces and classes for the individual services such as Maps v2. The following diagram shows the relationship between an Android application and Google Play Services:

Android Maps API v2 is provided as a part of the Google Play Services. Before a Xamarin.Android application can use the Maps API v2, the Google Play Services SDK must be installed and bound. The Google Play Services SDK is installed through the Android SDK Manager. The following screenshot shows where in the Android SDK Manager the Google Play services client can be found:

Note: The Google Play services APK is a licensed product that may not be present on all devices. If it is not installed, then Google Maps v2 will not work on the device. For these devices, an alternative mapping library (such as OSMDroid) must be used.

Binding Google Play Services

Once the Google Play Services client library is installed, it must be bound by a Xamarin.Android Java binding library. There are two ways to accomplish this:

  • Use the Google Play Services component - This is the simplest approach and is only available starting with Xamarin.Android 4.8 or higher. Simply install the Google Play Services component . This document will focus on this approach.
  • Manually bind the Google Play Services client library - This is a more complex approach and is the only way for Xamarin.Android 4.4 or Xamarin.Android 4.6 to bind the Google Play Services SDK. Manually binding the Google Play Services client library is beyond the scope of this document, but an example of how to do so may be found in the Maps and Location Demo v2 sample on Github.

Adding the Google Play Services Component

To add the Google Play Services Component, right click on the Components folder of your project in the Solution Explorer. This will bring up an action menu as shown in the following screenshot:

Select the Get More Components menu option, and search for the component using the key words Google Play Services. You should see the search results similar to the following screenshot:

Notice there are two flavours of the component available in the Component store. Only one component should be installed:

  • Google Play Services - This component is for applications that target Android 4.0 (API level 14) or higher.
  • Google Play Services (Froyo) - This component is for applications that require backwards compatibility with Android 2.2 and Android 2.3. This component already contains a the Xamarin.Android.Support.v4 library. Projects using this component should not reference Mono.Android.Support.v4 .

The final step is to get a Google Maps v2 API key. An API key from Google Maps v1 will not work. For information about how to obtain and use the API key with Xamarin.Android, see the document Obtaining A Google Maps API Key.

Creating an Emulator with Google APIs

Although it is not recommended, it is possible to setup the emulator to support the Android Maps API v2. The emulator must be configured to target the Google API Level 17 (Android 4.2.2) or higher, as shown in the following screenshot:

Note:The AVD images with the Google Play services installed are running a very old version of Google Play Services. This is a known issue. This post on StackOverflow describes one work around. It is strongly recommended to use an actual Android device while developing a Android application with Google Maps Android API v2.

Specify the Required Permissions

The following permissions must be specified in the AndroidManifest.XML for the Google Maps Android API v2:

  • Access to the Network State - Maps API v2 must be able to check if it can download the map tiles.
  • Internet Access - Internet access is necessary to download the map tiles and communicate with the Google Play Servers for API access.
  • OpenGL ES v2 - The application must declare the requirement for OpenGL ES v2.
  • Google Maps API Key - The API key is used to confirm that the application is registered and authorized to use Google Play Services. See Obtaining a Google Maps API Key for details about this key.
  • Write to External Storage - Google Maps Android API v2 will cache downloaded tiles to external storage.
  • Access to the Google Web-based Services - The application needs permissions to access Google's web services that back the Android Maps API v2.
  • Permissions for Google Play Services Notifications - The application must be granted permission to receive remote notifications from Google Play Services.
  • Access to Location Providers - These are optional permissions. They will allow the GoogleMap class to display the location of the device on the map.

The following snippet is an example of the settings that must be added to AndroidManifest.XML:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="" android:versionName="4.5" package="" android:versionCode="6">
    <uses-sdk android:minSdkVersion="14" android:targetSdkVersion="17" />

    <!-- Google Maps for Android v2 requires OpenGL ES v2 -->
    <uses-feature android:glEsVersion="0x00020000" android:required="true" />

    <!-- We need to be able to download map tiles and access Google Play Services-->
    <uses-permission android:name="android.permission.INTERNET" />

    <!-- Allow the application to access Google web-based services. -->
    <uses-permission android:name="" />

    <!-- Google Maps for Android v2 will cache map tiles on external storage -->
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />

    <!-- Google Maps for Android v2 needs this permission so that it may check the connection state as it must download data -->
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

    <!-- Permission to receive remote notifications from Google Play Services -->
    <!-- Notice here that we have the package name of our application as a prefix on the permissions. -->
    <uses-permission android:name="<PACKAGE NAME>.permission.MAPS_RECEIVE" />
    <permission android:name="<PACKAGE NAME>.permission.MAPS_RECEIVE" android:protectionLevel="signature" />

    <!-- These are optional, but recommended. They will allow Maps to use the My Location provider. -->
    <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />

    <application android:label="@string/app_name">
        <!-- Put your Google Maps V2 API Key here. -->
        <meta-data android:name="" android:value="YOUR_API_KEY" />
        <meta-data android:name="" android:value="@integer/google_play_services_version" />

The GoogleMap Class

Once the prerequisites are taken care of, it is time to start developing the application and use Android Maps API v2. The GoogleMap class is the main API that a Xamarin.Android application will use to display and interact with a Google Maps for Android v2. This class has the following responsibilities:

  • Interacting with Google Play services to authorize the application with the Google web service.
  • Downloading, caching, and displaying the map tiles.
  • Displaying UI controls such as pan and zoom to the user.
  • Drawing markers and geometric shapes on maps.

The GoogleMap is added to an Activity in one of two ways:

  • MapFragment - The MapFragment is a specialized Fragment that acts as host for the GoogleMap object. The MapFragment requires Android API level 12 or higher. Older versions of Android use the SupportMapFragment .
  • MapView - The MapView is a specialized View subclass which can act as a host for a GoogleMap object. Users of this class must forward all of the Activity lifecycle methods to the MapView class.

Each of these containers expose a Map property that returns an instance of GoogleMap. Preference should be given to the MapFragment class as it is a simpler API that reduces the amount boilerplate code that a developer must manually implement.

Adding A MapFragment To An Activity

Similar to other Fragment classes, there are two ways to add the MapFragment to an Activity:

  1. Declaratively - The MapFragment can be added via the XML layout file for the Activity. The following XML snippet shows an example of how to use the <fragment> element:
  2. <?xml version="1.0" encoding="utf-8"?>
    <fragment xmlns:android=""
              class="" />
  3. Programatically - The following code snippet shows an example of programatically adding a MapFragment:
  4. _myMapFragment = MapFragment.NewInstance();
    FragmentTransaction tx = FragmentManager.BeginTransaction();
    tx.Add(Resource.Id.my_mapfragment_container, _myMapFragment);

The following screenshot is an example of this very simple MapFragment:

Although the code snippet above will automatically add the MapFragment to the Activity, the GoogleMap will not be ready until some indeterminate amount of time has passed. This is because the initialization for the GoogleMap object can take some time to complete as the API communicates with Google Play. While this initialization is happening, the MapFragment.Map property will return null. It is important to first perform a null check before attempting to use the instance of the GoogleMap object, as shown in the following code snippet:

MapFragment mapFrag = (MapFragment) FragmentManager.FindFragmentById(Resource.Id.my_mapfragment_container);
GoogleMap map = mapFrag.Map;
if (map != null) {
    // The GoogleMap object is ready to go.

Map Types

There are five different types of maps available from the Google Maps API v2:

  • Normal - This is the default map type. It shows roads and important natural features along with some man-made points of interest (such as buildings and bridges).
  • Satellite - This map shows satellite photography.
  • Hybrid - This map shows satellite photography and road maps.
  • Terrain - This primarily shows topographical features with some roads.
  • None - This map does not load any tiles, it is rendered as an empty grid.

The image below shows the different types of of maps, from left-to-right (normal, hybrid, terrain):

The GoogleMap.MapType property is used to set or change which type of map is displayed. The following code snippet shows how to display a satellite map.

MapFragment mapFrag = (MapFragment) FragmentManager.FindFragmentById(Resource.Id.my_mapfragment_container);
GoogleMap map = mapFrag.Map;
if (map != null) {
    map.MapType = GoogleMap.MapTypeSatellite;

GoogleMap Properties

GoogleMap defines several properties that can control the functionality and the appearance of the map. One way to configure the initial state of a GoogleMap is to pass a GoogleMapOptions object when creating a MapFragment. The following code snippet is one example of using a GoogleMapOptions object when creating a MapFragment:

GoogleMapOptions mapOptions = new GoogleMapOptions()

FragmentTransaction fragTx = FragmentManager.BeginTransaction();
_mapFragment = MapFragment.NewInstance(mapOptions);
fragTx.Add(, _mapFragment, "map");

The other way to configure a GoogleMap object is by setting values the UiSettings property of the map object. This code sample shows how to configure a GoogleMap to display the zoom controls and a compass:

MapFragment mapFrag = (MapFragment) FragmentManager.FindFragmentById(Resource.Id.my_mapfragment_container);
GoogleMap map = mapFrag.Map;
if (map != null) {
    map.UiSettings.ZoomControlsEnabled = true;
    map.UiSettings.CompassEnabled = true;

Note: The Java binding has changed some of the Java method names on the GoogleMapOptions class to InvokeXXX. This is done to keep the method names in line with .NET naming conventions.

Interacting with the Map

The Android Maps API v2 provides API's that allow an Activity to change the viewpoint, add markers, place custom overlays, or draw geometric shapes. This section will discuss how to accomplish some of these tasks in Xamarin.Android.

Changing the Viewpoint

Maps are modelled as a flat plane on the screen, based on the Mercator projection. The map view is that of a camera looking straight down on this plane. The position of the camera can be controlled by changing the location, zoom, tilt, and bearing. The CameraUpdate class is used to move the camera location. CameraUpdate objects are not directly instantiated, instead the Maps API provides the CameraUpdateFactory class.

Once a CameraUpdate object has been created, it is passed as a parameter to either the GoogleMap.MoveCamera or GoogleMap.AnimateCamera methods. The MoveCamera method updates the map instantly while the AnimateCamera method provides a smooth, animated transition.

This code snippet is a simple example of how to use the CameraUpdateFactory to create a CameraUpdate that will increment the zoom level of the map by one:

MapFragment mapFrag = (MapFragment) FragmentManager.FindFragmentById(Resource.Id.my_mapfragment_container);
GoogleMap map = mapFrag.Map;
if (map != null) {

The Maps API provides a CameraPosition which will aggregate all of the possible values for the camera position. An instance of this class can be provided to the CameraUpdateFactory.NewCameraPosition method which will return a CameraUpdate object. The Maps API also includes the CameraPosition.Builder class that provides a fluent API for creating CameraPosition objects. The following code snippet shows an example of creating a CameraUpdate from a CameraPosition and using that to change the camera position on a GoogleMap:

LatLng location = new LatLng(50.897778, 3.013333);
CameraPosition.Builder builder = CameraPosition.InvokeBuilder();
CameraPosition cameraPosition = builder.Build();
CameraUpdate cameraUpdate = CameraUpdateFactory.NewCameraPosition(cameraPosition);

MapFragment mapFrag = (MapFragment) FragmentManager.FindFragmentById(Resource.Id.my_mapfragment_container);
GoogleMap map = mapFrag.Map;
if (map != null) {

In the previous code snippet, a specific location on the map is represented by the a LatLng class. The zoom level is set to 18. The bearing is the compass measurement clockwise from North. The Tilt property controls the viewing angle and is specifies an angle of 25 degrees from the vertical. The following screenshot shows the GoogleMap after executing the preceding code:

Drawing on the Map

The Android Maps API v2 provides API's for drawing the following items on a map:

  • Markers - These are special icons that are used to identify a single location on a map.
  • Overlays - This is a image that can be used to identify a collection of locations or area on the map.
  • Lines, Polygons, and Circles - These are APIs that allow Activities to add shapes to a map.


The Maps API provides a Marker class which encapsulates all of the data about a single location on a map. By default they use a standard icon provided by Google Maps. It is possible to customize the appearance of a marker and to respond to user clicks.

Adding A Marker

To add a marker to a map, it is necessary create a new MarkerOptions object and then call the AddMarker method on a GoogleMap instance. This method will return a Marker object.

MapFragment mapFrag = (MapFragment) FragmentManager.FindFragmentById(Resource.Id.my_mapfragment_container);
GoogleMap map = mapFrag.Map;
if (map != null) {
    MarkerOptions markerOpt1 = new MarkerOptions();
    markerOpt1.SetPosition(new LatLng(50.379444, 2.773611));
    markerOpt1.SetTitle("Vimy Ridge");

The title of the marker will be displayed in an info window when the user taps on the marker. The following screenshot shows what this marker looks like:

Customizing A Marker

It is possible to customize the icon used by the marker by calling the MarkerOptions.InvokeIcon method when adding the marker to the map. This method takes a BitmapDescriptor object containing the data necessary to render the icon. The BitmapDescriptorFactory class provides some helper methods to simplify the creation of a BitmapDescriptor. The following table introduces some of these methods:

Method Description
DefaultMarker(float colour) Use the default Google Maps marker, but change the colour.
FromAsset(string assetName) Use a custom icon from the specified file in the Assets folder.
FromBitmap(Bitmap image) Use the specified bitmap as the icon.
FromFile(string fileName Create the custom icon from the file at the specified path.
FromResource(int resourceId) Create a custom icon from the specified resource.

The following code snippet shows an example of creating a cyan coloured default marker:

GoogleMap map = mapFrag.Map;
if (map != null)
    MarkerOptions markerOpt1 = new MarkerOptions();
    markerOpt1.SetPosition(new LatLng(50.379444, 2.773611));
    markerOpt1.SetTitle("Vimy Ridge");
    markerOpt1.InvokeIcon(BitmapDescriptorFactory.DefaultMarker (BitmapDescriptorFactory.HueCyan));

Info Windows

Info windows are special windows that popup to display information to the user when they tap a specific marker. By default the info window will display the contents of the marker's title. If the title has not been assigned, then no info window will appear. Only one info window may be shown at a time.

It is possible to customize the info window by implementing the GoogleMap.IInfoWindowAdapter interface. There are two important methods on this interface:

  • public View GetInfoWindow(Marker marker) - This method is called to get a custom info window for a marker. If it returns null , then the default window rendering will be used. If this method returns a View, then that View will be placed inside the info window frame.
  • public View GetInfoContents(Marker marker) - This method will only be called if GetInfoWindow returns null . This method can return a null value if the default rendering of the info window contents is to be used. Otherwise, this method should return a View with the contents of the info window.

An info window is not a live view - instead Android will convert the View to a static bitmap and display that on the image. This means that an info window cannot respond to any touch events or gestures, nor will it automatically update itself. To update an info window, it is necessary to call the GoogleMap.ShowInfoWindow method.

The following image shows some examples of some customized info windows. The image on the left has it's contents customized, while the image on the right has it's window and contents customized:

Ground Overlays

Unlike markers, which identify a specific location on a map, a GroundOverlay is an image that used to identify a collection of locations or an area on the map.

Adding A GroundOverlay

Adding a ground overlay to a map is very similar to adding a marker to a map. First, a GroundOverlayOptions object is created. This object is then passed as a parameter to the GoogleMap.AddGroundOverlay method, which will return a GroundOverlay object. This code snippet is an example of adding a ground overlay to a map:

BitmapDescriptor image = BitmapDescriptorFactory.FromResource(Resource.Drawable.polarbear);
GroundOverlayOptions groundOverlayOptions = new GroundOverlayOptions()
    .Position(position, 150, 200)
GroundOverlay myOverlay = _map.AddGroundOverlay(groundOverlayOptions);

The following screenshot shows this overlay on a map:

Lines, Circles, and Polygons

There are three simple types of geometric figures that can be added to a map:

  • Polyline - This is a series of connected line segments. It can mark a path on a map or form any shape required.
  • Polygon - This is an closed shape for marking areas on a map.
  • Circle - This will draw a circle on the map.


A Polyline is a list of consecutive LatLng objects which specify the vertices of each line segment. A polyline is created by first creating a PolylineOptions object and adding the points to it. The PolylineOption object is then passed to a GoogleMap object by calling the AddPolyline method.

PolylineOption rectOptions = new PolylineOption();
rectOptions.Add(new LatLng(37.35, -122.0));
rectOptions.Add(new LatLng(37.45, -122.0));
rectOptions.Add(new LatLng(37.45, -122.2));
rectOptions.Add(new LatLng(37.35, -122.2));
rectOptions.Add(new LatLng(37.35, -122.0)); // close the polyline - this makes a rectangle.


Polygons are very similar to Polylines, however they are not open ended. Polygons are a closed loop and have their interior filled in. Polygons are created in the exact same manner as a Polyline, except the GoogleMap.AddPolygon method invoked.

Unlike a Polyline, a Polygon is self closing. When AddPolygon is called, the method will automatically close off the polygon by drawing a line which connects the first and last points. The following code snippet will create a solid rectangle over the same area as the previous code snippet in the Polyline example.

PolygonOptions rectOptions = new PolygonOptions();
rectOptions.Add(new LatLng(37.35, -122.0));
rectOptions.Add(new LatLng(37.45, -122.0));
rectOptions.Add(new LatLng(37.45, -122.2));
rectOptions.Add(new LatLng(37.35, -122.2));
// notice we don't need to close off the polygon


Circles are created by first instantiating a CircleOption object which will specify the center and the radius of the circle in metres. The circle is drawn on the map by calling GoogleMap.AddCircle. The following code snippet shows how to draw a circle:

CircleOptions circleOptions = new CircleOptions ();
circleOptions.InvokeCenter (new LatLng(37.4, -122.1));
circleOptions.InvokeRadius (1000);
_map.AddCircle (CircleOptions);

Responding To Events

There are three types of interactions a user may have with a map:

  • Marker Click - The user clicks on a marker.
  • Marker Drag - The user has long-clicked on a mparger
  • Info Window Click - The user has clicked on an info window.

Each of these events will be discussed in more detail below.

Marker Click Events

When the user clicks on a marker the MarkerClick event will be raised, and a GoogleMap.MarkerClickEventArgs passed in. This class contains two properties:

  • GoogleMap.MarkerClickEventArgs.Handled - This property should be set to true to indicate that the event handler has consumed the event. If this is set to false then the default behaviour will occur in addition to the custom behaviour of the event handler.
  • P0 - This poorly name parameter is a reference to the marker that raised the MarkerClick event.

This code snippet shows an example of a MarkerClick that will change the camera position to a new location on the map:

private void MapOnMarkerClick(object sender, GoogleMap.MarkerClickEventArgs markerClickEventArgs)
    markerClickEventArgs.Handled = true;
    Marker marker = markerClickEventArgs.P0;
    if (marker.Id.Equals(MyMarkerId)) // The ID of a specific marker the user clicked on.
        _map.AnimateCamera(CameraUpdateFactory.NewLatLngZoom(new LatLng(20.72110, -156.44776), 13));
        Toast.MakeText(this, String.Format("You clicked on Marker ID {0}", marker.Id), ToastLength.Short).Show();

Marker Drag Events

This event is raised when the user wishes to drag the marker. By default, markers are not draggable. A marker can be set as draggable by setting the Marker.Draggable property to true or by invoking the MarkerOptions.Draggable method with true as a parameter.

To first drag the marker, the user must long-click on it and keep their finger on the map. When they drag their finger around the screen, the marker will move. When the user's finger lifts off the screen, the marker will remain in place.

The following table describes the various events that will be raised for a draggable marker:

Event Description
GoogleMap.MarkerDragStart(object sender, GoogleMap.MarkerDragStartEventArgs e) This event is raised when the user first drags the marker.
GoogleMap.MarkerDrag(object sender, GoogleMap.MarkerDragEventArgs e) This event is raised as the marker is being dragged.
GoogleMap.MarkerDragEnd(object sender, GoogleMap.MarkerDragEndEventArgs e) This event is raised when the when the user is finished dragging the marker.

Each of the EventArgs contains a single property called P0 that is a reference to the Marker object being dragged.

Info Window Click Events

Only one info window can be displayed at a time. When the user clicks on an info window in a map, the map object will raise an InfoWindowClick event. The following code snippet shows how to wire up a handler to the event:

private bool SetupMapIfNeeded()
    if (_map == null)
        _map = _mapFragment.Map;
        if (_map != null)
            _map.InfoWindowClick += MapOnInfoWindowClick;
            return true;
        return false;
    return true;

private void MapOnInfoWindowClick (object sender, GoogleMap.InfoWindowClickEventArgs e)
    Marker myMarker = e.P0;
    // Do something with marker.

Recall that an info window is a static View which is rendered as an image on the map. Any widgets such as buttons, check boxes, or text views that are placed inside the info window will be inert and cannot respond to any of their integral user events.

Xamarin Workbook

If it's not already installed, install the Xamarin Workbooks app first. The workbook file should download automatically, but if it doesn't, just click to start the workbook download manually.