Allow your users to display the map in either raster or vector format:

Sample use case 1: Your app is designed to use raster tiles for map display. You want to update the app with TomTom Maps API raster tiles.

Sample use case 2: You want to take advantages of vector tiles features such as map 2.5 D perspective, custom map styles, etc.

Sample use case 3: Your app runs on devices with different capabilities. You want to use vector tiles for map display on powerful devices and raster tiles on devices with less processing power.

Use the code snippets below in your app to display the map with raster or vector tiles.

Additionally, you can get details about the specific traffic flow or incident of the road fragment (e.g. current speed, travel times, etc)
from Flow Segment Data
service which is integrated in Maps SDK. This service is designed to work alongside the traffic to support clickable
flow and incidents data visualizations. This is handled for you in the Maps SDK. SDK provides default implementation of trafficDelegate which is
TTMapTrafficDelegateDefault.

By default implementation, when you click on the specific traffic incident, a balloon with details is shown for incident flows:

The default implementation of incident click listener zoom the map when traffic cluster is clicked:

Traffic API flow tiles style types are represented in the SDK as an enum.
The available traffic flow styles are the following:

Allow your user to see the map in different languages to make your app international.
The language parameter determines the language of labels on the map.
It does not affect any proper nouns, like the names of streets, plazas, etc.
List of the supported languages can be found
here.

Sample use case: You want to have all labels only in British English

To change language for the map:

Allow your user to see the map boundaries based on international or local country views.
The local view is available for a particular area of the world that is considered
as disputed by two or more countries. As a result, each country can show this area as
a part of his country. List of the supported views can be found
here.

Sample use case: You want to display local map view for Israel.

To change geopolitical view for the map:

Allow your user to create and provide the map with one or more custom styles for vector map tiles.

Modify default TomTom style

The best way to create a custom style is to modify the default TomTom style for vector maps using the Maputnik editor.
You can find the json map style in the resources directory.
The tutorial on how to modify the style is available for all Maps SDKs (for Android, iOS and Web) here link.
Note, that after step 9 of the linked tutorial, you need to save the json file and place it in resources directory of your app project.

Provide your style
You can provide an external map style file on the server and provide the URL. Sprites and fonts
should be stored locally in the application. Currently, we don’t support loading resources and fonts
from a server.

Sample use case: You want to display a night styled map at night or in a tunnel.

To change the style of the map:

Allow your users to dynamically toggle the visibility of map entities. You can hide map layers to get
the level of detail you need and highlight the layers that are important for your use case.

Sample use case: You want to provide a clear map view for driving that focuses on the road network
in your app. You can achieve that by switching off some map layers e.g. woodland, build-up areas, etc.
You can turn these layers back on at run time to bring back the details for a better map viewing experience.

The following articles provide more information on map layer visibility and map layers available in
the default style: Map layers, Default style.

You can retrieve all layers available in the style or only those that match provided regex.
To filter, you can use layer ID or source layer ID properties, as shown below:

Unresolved directive in index.adoc - include::7MapLayersVisibility.adoc[]

Unresolved directive in index.adoc - include::8DynamicMapSources.adoc[]

Developers are not limited to attaching only a single map. You can put as many map objects as you want on the same page without any issues.

Sample use case: You want to display two independent maps in your app.

Center the map in your mobile app either at the current coordinates or any other location, at the zoom level of your choice.

Sample use case: You want to display the maps for selected cities in specific zoom levels.
Your users should be able to easily to switch between different locations.

Use the code snippets below in your app to display maps of different locations (in this case, the current location and the TomTom offices in Amsterdam and Berlin).

The example shows how to center the map on Amsterdam:

Set either 2D map perspective for typical map view mode, or 2.5D map perspective for custom scenarios such as moving the map.

Sample use case: You want to switch from 2D to 2.5D modes to support following the moving location in your app.
Use the code snippets below in your app to switch between perspectived.

Note, that switching between 2D and 3D mode only changes the perspective.
The zoom level and map orientation are set with the methods described in the "Map centering" example.

Perspective ratio can be changed fluent in value - false to true.

Implement any action you need to be triggered on one of the following map events:

To receive events you need to register id<TTMapViewDelegate> on map

Sample use case: In your app, users invoke one behavior with a single press and another with a long press.

Use the code snippets below in your app to catch map events. In this example,
the action is simply to display a toast with latitude and longitude on each map event.
Of course, you can implement other cool features instead.

In this example you will see a Toast with latitude and longitude of a
point that was clicked on the map, but you can utilize these information
in your own manner.

Enable and disable gestures

You can disable gestures such as zooming, scrolling and rotating in your application by setting up an integer mask on properties like below:

Disable zooming gesture

Disable the rotating gesture

Disable the scrolling gesture

You can turn off more than one gesture by setting up the mask on properties like below:

If you want to enable gestures, setup the integer mask on a property like below:

You can place custom images on the map using TTAnnotation.
You can do that with a TTAnnotationManager which can be obtained from TTMapView.
Use a one of factory method from TTAnnotation to create an annotation, then pass it to manager.

You can display icons using a two of different types:

Mixing icons of focal and decal modes is generally unsupported and advised against, as there are unresolvable depth-sorting issues and the results
will not always look correct. It is safe to mix some modes, however, such as either of the decal modes with any of the standing modes.
For performance purposes, it is recommended to use the same tag for same images so they can be reused from cache.

Sample use case: In your app, you want to display a number of annotations, to mark places on the map.
Use the code snippet below to display a single annotation at specific coordinates on the map

Thanks to this feature you can use GIFs as marker icons. For this purpose, you need to place your images
in the assets folder and then use them in the following way:

You have a possibility to change the anchoring point for your icon. The anchor specifies which point of an annotation image is attached to the map.
The annotation will rotate around this anchoring point when rotating the map.
You can use the default image representation of an annotation which is attached to the bottom height center width.
You can change this behavior by TTAnnotationAnchor enumeration.
E.g. if you want to use a crosshair annotation image, you should set the anchor to TTAnnotationAnchorCenter

You can implement an observable of annotation selected event. You can do that with the global delegate TTAnnotationDelegate
for all annotations that has to be registered on TTAnnotationManager as following

Maps SDK allows to observe annotation selected event.
There is one global delegate TTAnnotationDelegate for all annotations that has to be registered on TTAnnotationManager as followed.

Allow your users to cluster annotations for better visualization. By default, annotations clustering is disabled.
You can decide per each marker, if it should be included in the clustering process or not (e.g. you want to have a few
annotations that are never clustered). To manipulate marker clustering, use TTAnnotationManager obtained
from TTMapView.

Sample use case: You want to display the distribution of parking spots across the city. Individual parking spots are
shown only at higher zoom levels, otherwise data is clustered for better visualization.

To enable annotations clustering:

To flag a marker that it should be clustered:

Examples are shown below:

Allow your users to display and customize balloons in a few lines of code.

Sample use case: You would like to learn more about a place on the map. Depending on the
selected location, the app displays a balloon containing either text or additional information such
as icons or pictures.

To display a balloon, attach a callout to a TTAnnotation. The map can display only one annotation
at a time

A callout can be triggered in two ways:

There can be only one selected annotation on the map at a time.

A callout can be closed in the following ways:

A callout is an instance of UIView that implements the TTCalloutView protocol. You can use one of the built-in callout views, such as the default TTCalloutViewSimple, or make your own custom balloon.

The default behavior for an annotation is to display an instance of TTCalloutViewSimple containing the annotation’s coordinates. You can change the following properties:

To change the default text of a simple callout, register your delegate on the annotation manager and override the viewForSelectedAnnotation method

Although you can use default callouts, SDK also allows you to create fully customizable ones.
A callout is nothing more than a Cocoa UIView implementing the TTCalloutView protocol. Callouts can be built by either Interface Builder or programmatically.

This is an example of a custom callout:

Allow your users to draw shapes like circles, polygons and polylines on your map to mark different areas on the map.

Sample use case: You are developing an app for a delivery company and need to illustrate ranges of the transportation area around different cities.
What you need to do is e.g. to render circles round cities with radiuses indicating zones of deliveries.
The details on the example implementation of shapes rendering are described below.

A TTMapView supports several shape overlays. These are:

Shape overlays are immutable i.e. once they have been created, their shapes cannot be changed (although you may change their visibility and color).
If you want to change a shape, you must remove the existing shape and replace it with a new one.

It is the responsibility of the framework user to be conscientious about performance and how many shape overlays they are using.
You should use as few shapes as possible, and hide or dispose of ones that are not being displayed.

Code examples are below:

You can display a route on the map and customize its origin and destination icons.
It is also possible to specify the fill color, outline color and width of the route.

Sample use case: when you add the route, you would like to highlight the starting and
the destination points. Also you would like to plan several routes simultaneously
with different origin and destination points and use different icons.

Prerequisites:

TTMapView *mapView object was created and configured. Route coordinates are prepared.