This is a large example covering many basic uses of maps, positioning, and navigation services in Qt Location. This page is divided into sections covering each of these areas of functionality with snippets from the code.

The Map Viewer example can work with any of the available geo services plugins. However, some plugins may require additional plugin parameters in order to function correctly. Plugin parameters can be passed on the command line using the --plugin argument, which takes the form:

--plugin.<parameter name> <parameter value>

Refer to the documentation for each of the geo services plugins for details on what plugin parameters they support. The Nokia services plugin supplied with Qt requires an app_id and token pair. See "Qt Location Nokia Plugin" for details.

QML types shown in this example:

src="https://assets.ubuntu.com/v1/34c7f226-example-mapviewer.png" alt="" />

Displaying a Map

Drawing a map on-screen is accomplished using the Map type, as shown below.

Map {
id: map
zoomLevel: (maximumZoomLevel - minimumZoomLevel)/2
center {
latitude: -27.5796
longitude: 153.1003
// Enable pinch gestures to zoom in and out
gesture.flickDeceleration: 3000
gesture.enabled: true
center {
latitude: -27.5796
longitude: 153.1003

In this example, we give the map an initial center coordinate with a set latitude and longitude. We also set the initial zoom level to 50% (halfway between the maximum and minimum).

The calls to "pinch" and "flick" are used to enable gestures on the map. The flick gesture is also sometimes known as "kinetic panning", and provides a more intuitive feel for panning the map both on touch screens and with a mouse.

As we do not specify a plugin for supplying map data, the platform default will be used. This is typically the "nokia" plugin, which provides data from Nokia services. Additional licensing conditions do apply to the use of this data, please see the documentation for further details.

Finding an Address (Geocoding)

To locate a certain address or place on the map uses a process called geocoding. In order to perform a geocode operation, we first need to adjust our Map object to be able to receive the result.

Receiving results of geocoding is done through a GeocodeModel, which is typically instantiated as a property of the Map component:

    property GeocodeModel geocodeModel: GeocodeModel {

Then, to display the contents of the GeocodeModel we use a MapItemView:

    MapItemView {
model: geocodeModel
delegate: pointDelegate

MapItemView uses an object called a "delegate" to act as a template for the items it creates. This can contain any map object desired, but in this case we show a MapCircle:

    Component {
id: pointDelegate
MapCircle {
radius: 1000
color: circleMouseArea.containsMouse ? "lime" : "red"
opacity: 0.6
center: locationData.coordinate

With these three objects, we have enough to receive Geocode responses and display them on our Map. The final piece is to send the actual Geocode request.

In this example, we have a utility component called Dialog which we use to display the user interface requesting geocoding parameters. You can create a similar component yourself using Dialog.qml in this example as a reference, or drive the process using any other UI you wish.

To send a geocode request, first we create an Address object, and fill it in with the desired parameters. Then we set "map.geocodeModel.query" to the filled in Address, and call update() on the GeocodeModel.

    InputDialog {
id: geocodeDialog
Address {
id: geocodeAddress
onGoButtonClicked: {
// manage the UI state transitions
page.state = ""
messageDialog.state = ""
// fill out the Address element
geocodeAddress.street = dialogModel.get(0).inputText
geocodeAddress.city = dialogModel.get(1).inputText
geocodeAddress.state = dialogModel.get(2).inputText
geocodeAddress.country = dialogModel.get(3).inputText
geocodeAddress.postalCode = dialogModel.get(4).inputText
// send the geocode request
map.geocodeModel.query = geocodeAddress

Directions and Travel Routes

Similar to the GeocodeModel, Qt Location also features the RouteModel type, which allows information about routes (for example driving directions) between two or more points, to be received and used with a Map.

Here again, we instantiate the RouteModel as a property of our Map:

    property RouteQuery routeQuery: RouteQuery {}
property RouteModel routeModel: RouteModel {
plugin : map.plugin
query: routeQuery

To display the contents of a model to the user, we need a view. Once again we will use a MapItemView, to display the Routes as objects on the Map:

    MapItemView {
model: routeModel
delegate: routeDelegate
autoFitViewport: true

To act as a template for the objects we wish the view to create, we create a delegate component:

    Component {
id: routeDelegate
MapRoute {
route: routeData
line.color: routeMouseArea.containsMouse ? "lime" : "red"
line.width: 5
smooth: true
opacity: 0.8

With the model, view and delegate now complete, the only missing component is some kind of control over the model to begin the Route request process. In the simplest case, we can fill out a Route request using two already available coordinates, which we store inside the RouteDialog component:

    RouteDialog {
id: routeDialog
property variant startCoordinate
property variant endCoordinate

In the next snippet, we show how to set up the request object and instruct the model to update. We also instruct the map to center on the start coordinate for our routing request.

        function calculateRoute() {
// clear away any old data in the query
// add the start and end coords as waypoints on the route
map.routeQuery.travelModes = routeDialog.travelMode
map.routeQuery.routeOptimizations = routeDialog.routeOptimization
// center the map on the start coord
map.center = startCoordinate;

This is all that is required to display a Route on the Map. However, it is also useful to be able to retrieve the written directions and explanation of the travel route. In the example, these are displayed in the pull-out on the left-hand side of the map. To create this pull-out's contents, we use a standard ListModel and ListView pair. The data in the ListModel is built from the routeModel's output:

    ListModel {
id: routeInfoModel
property string travelTime
property string distance
function update() {
if (routeModel.count > 0) {
for (var i = 0; i < routeModel.get(0).segments.length; i++) {
"instruction": routeModel.get(0).segments[i].maneuver.instructionText,
"distance": formatDistance(routeModel.get(0).segments[i].maneuver.distanceToNextInstruction)
travelTime = routeModel.count == 0 ? "" : formatTime(routeModel.get(0).travelTime)
distance = routeModel.count == 0 ? "" : formatDistance(routeModel.get(0).distance)

Inside the RouteModel, we add an onStatusChanged handler, which calls the update() function we defined on the model:

        onStatusChanged: {
if (status == RouteModel.Ready) {
switch (count) {
case 0:
clearAll() // technically not an error
case 1:
} else if (status == RouteModel.Error) {


  • mapviewer/mapviewer.qml
  • mapviewer/qmlmapviewerwrapper.cpp
  • mapviewer/content/dialogs/Message.qml
  • mapviewer/content/dialogs/RouteDialog.qml
  • mapviewer/content/map/3dItem.qml
  • mapviewer/content/map/CircleItem.qml
  • mapviewer/content/map/ImageItem.qml
  • mapviewer/content/map/MapComponent.qml
  • mapviewer/content/map/Marker.qml
  • mapviewer/content/map/MiniMap.qml
  • mapviewer/content/map/PolygonItem.qml
  • mapviewer/content/map/PolylineItem.qml
  • mapviewer/content/map/RectangleItem.qml
  • mapviewer/content/map/VideoItem.qml
  • mapviewer/mapviewer.pro
  • mapviewer/mapviewerwrapper.qrc