The Qt Location API provides mapping, navigation, and place search via QML and C++ interfaces.
The API has not been released yet but due to its platform-independent nature is available on all Qt platforms.
The Qt Location API gives developers the ability to determine a position by using a variety of possible sources, including satellite, or wifi, or text file, and so on. That information can then be used to determine a position in a map context with appropriate navigation and to embed, in the map, defined places with descriptive metadata. These three parts allow a device to know where it is and its location with respect to important features. Using features such as roads, destinations, routes, and other navigation attributes, applications can specify beginning and end-points for navigation and awareness of objects that may aid or hinder a journey.
To load the Qt Location module, add the following statement to your .qml files
import QtLocation 5.3
For C++ projects include the header appropriate for the current use case, for example applications using routes may use
The .pro file should have the location keyword added
QT += location
The API is split into sub-modules, which each have QML and C++ APIs. It focuses on Map and Place information. The required position data can be retrieved via the QtPositioning module.
Places is the natural complement to Positioning, providing a source of geographic data about places of interest (POIs). As well as providing the location, size and other vitals about a POI, the Places API can also retrieve images, reviews and other rich content related to the place.
|Places introduction:||for QML||for C++|
Maps and Navigation
Maps and Navigation provides Qt Quick user interface components for displaying geographic information on a map, as well as allowing user interaction with map objects and the display itself. It also contains utilities for geocoding (finding a geographic coordinate from a street address) and navigation (including driving and walking directions).
|Maps and Navigation introduction:||for QML||for C++|
API References and Examples
Alphabetized lists of all classes and user interface components in the API, as well as detailed example applications to demonstrate their usage.
|QML API Reference||Full list of QML components in the Qt Location API|
|C++ API Reference by domain||Full list of C++ classes and methods of the Qt Location APIs sorted by domain|
|C++ API Reference||Full list of C++ classes and methods of the Qt Location APIs|
|Example Apps||Examples demonstrating use of the Qt Location APIs|
|Maps and Navigation Tutorial||Tutorial introducing the QML Maps Types|
Plugin References and Parameters
Information about plugins, important notes on their usage, parameters that can be provided to influence their behavior.
Uses the relevant Nokia services provided by Nokia.
Uses Open Street Map and related services.
Implementing New Back-Ends and Porting
For systems integrators and distributors, information relating to making Qt Location available for a new platform.
|GeoServices||Information about the Qt Location GeoServices plugins|
|Places||Information for places backend implementors|
New Since Qt 4
In Qt 4 Qt Mobility provided some location functionality for Positioning and Maps with Landmarks support. The new Qt Location API has had an extensive reworking of Maps and Places (formerly Landmarks). Also both C++ and QML APIs have been reworked to be simpler to use.
New features of Qt Location includes
- Maps are now part of the Qt Quick scenegraph, and rendered using hardware-accelerated OpenGL
- Arbitrary Qt Quick items on the map are supported using MapQuickItem
- Now possible to create map overlays with a model
- Built-in support for pinch-to-zoom gestures, flicking , and panning (see MapGestureArea)
- Vast performance improvements over Qt Mobility 1.2, especially for large map polylines and objects in general
- Full QML API now available for routing and geocoding -- compatible with standard QML model-view design
- Service provider feature detection without having to open all the available plugins
- Unified Plugin QML type used by routing/geocoding/maps etc with easy-to-set PluginParameter
- Two plugins are supplied with Qt (a Nokia and an OSM plugin for GeoServices).
- Landmarks API is replaced by the Places API
- Place supports viewing of richer content such as reviews, images, and editorials
- Place supports locale handling, sponsored search results, and supplier attribution