Map Viewer (QML)▲
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.
Running the Example▲
To run the example from http://, open the Welcome mode and select the example from Examples. For more information, visit http://.
The example can work with any of the available geo services plugins. However, some plugins may require additional https:// in order to function correctly. https:// 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 default plugin used by this example is https://, which does not require any parameters.
Overview▲
QML types shown in this example:
-
Displaying a map
-
https://
-
https://
-
https://
-
-
Finding an address
-
https://
-
https://
-
https://
-
-
Directions and travel routes
-
https://
-
https://
-
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 {
// The Qt Company in Oslo
latitude: 59.9485
longitude: 10.7686
}
}In this example, we give the map an initial center https:// with a set latitude and longitude. We also set the initial zoom level to 50% (halfway between the maximum and minimum).
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 https://:
GeocodeModel {
id: geocodeModel
plugin: map.plugin
onStatusChanged: {
if ((status == GeocodeModel.Ready) || (status == GeocodeModel.Error))
map.geocodeFinished()
}
onLocationsChanged:
{
if (count == 1) {
map.center.latitude = get(0).coordinate.latitude
map.center.longitude = get(0).coordinate.longitude
}
}
}To display the contents of the https:// we use a https://:
MapItemView {
model: geocodeModel
delegate: pointDelegate
}https:// 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 https://:
Component {
id: pointDelegate
MapCircle {
id: point
radius: 1000
color: "#46a2da"
border.color: "#190a33"
border.width: 2
smooth: true
opacity: 0.25
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.
To send a geocode request, first we create an https:// object, and fill it in with the desired parameters.
Address {
id :fromAddress
street: "Sandakerveien 116"
city: "Oslo"
country: "Norway"
state : ""
postalCode: "0484"
}Then we set "geocodeModel.query" to the filled in https://, and call update() on the https://.
// send the geocode request
geocodeModel.query = fromAddress
geocodeModel.update()Directions and Travel Routes▲
Similar to the https://, Qt Location also features the https:// 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 https:// as a property of our Map:
RouteModel {
id: routeModel
plugin : map.plugin
query: RouteQuery {
id: routeQuery
}
onStatusChanged: {
if (status == RouteModel.Ready) {
switch (count) {
case 0:
// technically not an error
map.routeError()
break
case 1:
map.showRouteList()
break
}
} else if (status == RouteModel.Error) {
map.routeError()
}
}
}To display the contents of a model to the user, we need a view. Once again we will use a https://, to display the Routes as objects on the Map:
MapItemView {
model: routeModel
delegate: routeDelegate
}To act as a template for the objects we wish the view to create, we create a delegate component:
Component {
id: routeDelegate
MapRoute {
id: route
route: routeData
line.color: "#46a2da"
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 https://:
property variant fromCoordinate: QtPositioning.coordinate(59.9483, 10.7695)
property variant toCoordinate: QtPositioning.coordinate(59.9645, 10.671)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.
// clear away any old data in the query
routeQuery.clearWaypoints();
// add the start and end coords as waypoints on the route
routeQuery.addWaypoint(startCoordinate)
routeQuery.addWaypoint(endCoordinate)
routeQuery.travelModes = RouteQuery.CarTravel
routeQuery.routeOptimizations = RouteQuery.FastestRoute
routeModel.update();
// 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 a https:// element. To create this content, we use a standard https:// and https:// pair. The data in the https:// is built from the routeModel's output:
ListView {
interactive: true
model: ListModel { id: routeInfoModel }
header: RouteListHeader {}
delegate: RouteListDelegate{
routeIndex.text: index + 1
routeInstruction.text: instruction
routeDistance.text: distance
}
}Inside the https://, as you can see above, we add an https:// handler, which calls the showRouteList() which updates the routeInfoModel:
routeInfoModel.clear()
if (routeModel.count > 0) {
for (var i = 0; i < routeModel.get(0).segments.length; i++) {
routeInfoModel.append({
"instruction": routeModel.get(0).segments[i].maneuver.instructionText,
"distance": Helper.formatDistance(routeModel.get(0).segments[i].maneuver.distanceToNextInstruction)
});
}
}List of Files▲
Files:
List of Files▲
-
mapviewer/forms/Geocode.qml
-
mapviewer/forms/GeocodeForm.ui.qml
-
mapviewer/forms/Locale.qml
-
mapviewer/forms/LocaleForm.ui.qml
-
mapviewer/forms/Message.qml
-
mapviewer/forms/MessageForm.ui.qml
-
mapviewer/forms/ReverseGeocode.qml
-
mapviewer/forms/ReverseGeocodeForm.ui.qml
-
mapviewer/forms/RouteAddress.qml
-
mapviewer/forms/RouteAddressForm.ui.qml
-
mapviewer/forms/RouteCoordinate.qml
-
mapviewer/forms/RouteCoordinateForm.ui.qml
-
mapviewer/forms/RouteList.qml
-
mapviewer/forms/RouteListDelegate.qml
-
mapviewer/forms/RouteListHeader.qml
-
mapviewer/helper.js
-
mapviewer/main.cpp
-
mapviewer/map/CircleItem.qml
-
mapviewer/map/ImageItem.qml
-
mapviewer/map/MapComponent.qml
-
mapviewer/map/MapSliders.qml
-
mapviewer/map/Marker.qml
-
mapviewer/map/MiniMap.qml
-
mapviewer/map/PolygonItem.qml
-
mapviewer/map/PolylineItem.qml
-
mapviewer/map/RectangleItem.qml
-
mapviewer/mapviewer.pro
-
mapviewer/mapviewer.qml
-
mapviewer/mapviewer.qrc
-
mapviewer/menus/ItemPopupMenu.qml
-
mapviewer/menus/MainMenu.qml
-
mapviewer/menus/MapPopupMenu.qml
-
mapviewer/menus/MarkerPopupMenu.qml
List of Files▲
Images:
List of Files▲
-
mapviewer/resources/icon.png
-
mapviewer/resources/marker.png
-
mapviewer/resources/scale.png
-
mapviewer/resources/scale_end.png



