The Location API provides a library for mapping, navigation and place information.
The Qt Location API provides the developer with a set of functions to interact with maps, navigational data and places of interest. This is particularly useful when associated with current position information which can be retrieved via the QtPositioning module.
With the Maps API we can associate a position with a map in various formats supplied by a backend. Then the Places API could be used to populate places on the Map or even specify the current position as a place of interest and associate it with an icon, contact details and other information.
The following table provides links to more detailed information on sections of the Qt Location C++ API.
Maps and Navigation | Displaying maps and finding routes. |
Places | Searching for and managing points of interest. |
Geoservices Plugin Implementation | Implement new geoservices and positioning plugins. |
Aggregates access to services which provide geographical information |
Currently it is not possible to interact with maps data via C++. The only available interface is the Maps and Navigation (QML) API.
Represents the information relevant to the point at which two QGeoRouteSegments meet |
|
Represents a route between two points |
|
Manages an operation started by an instance of QGeoRoutingManager |
|
Represents a segment of a route |
|
Represents the parameters and restrictions which define a request for routing information |
|
Support for geographic routing operations |
Manages an operation started by an instance of QGeoCodingManager |
|
Support for geocoding operations |
Represents a set of data about a place |
|
Manages a content retrieval operation started by an instance of QPlaceManager |
|
Manages a place details fetch operation started by an instance of QPlaceManager |
|
Represents an icon |
|
Manages operations which return an identifier such as saving and removal operations of places and categories |
|
The interface which allows clients to access places stored in a particular backend |
|
Represents an individual user |
|
Represents an address of a QGeoLocation |
|
Represents basic information about a location |
|
Represents generic attribute information about a place |
|
Represents a category that a QPlace can be associated with |
|
Represents a contact detail such as a phone number or website url |
|
Serves as the base class for rich content types |
|
Represents the parameters of a content request |
|
Represents a publisher's article describing a place |
|
Represents a reference to an image |
|
Interface for implementers of QGeoServiceProvider plugins who want to provide access to place functionality |
|
Manages a place matching operation started by an instance of QPlaceManager |
|
Used to find places from one manager that match those from another. It represents a set of request parameters |
|
Represents a search result containing a proposed search |
|
Holds rating information about a place |
|
Manages an operation started by an instance of QPlaceManager and serves as a base class for more specialized replies |
|
Represents a search result containing a place |
|
Represents a review of a place |
|
Manages a place search operation started by an instance of QPlaceManager |
|
Represents the set of parameters for a search request |
|
The base class for search results |
|
Manages a search suggestion operation started by an instance of QPlaceManager |
|
Represents a supplier of a place or content associated with a place |
Interface and convenience methods to implementers of QGeoServiceProvider plugins who want to provide support for geocoding operations |
|
Interface and convenience methods to implementers of QGeoServiceProvider plugins who want to provide access to geographic routing information |
|
Factory class used as the plugin interface for services related to geographical information |
|
Interface for implementers of QGeoServiceProvider plugins who want to provide access to place functionality |