| MapView.qml |
|
6201 |
- |
| qabstractgeotilecache.cpp |
|
3058 |
- |
| qabstractgeotilecache_p.h |
This is also used in the mapgeometry |
3032 |
- |
| qcache3q_p.h |
called just before a key/value pair is about to be _evicted_ |
13077 |
- |
| qgeocameracapabilities.cpp |
!
\class QGeoCameraCapabilities
\inmodule QtLocation
\ingroup QtLocation-impl
\since 5.6
\internal
\brief The QGeoCameraCapabilities class describes the limitations on camera settings imposed by a mapping plugin.
Different mapping plugins will support different ranges of zoom levels, and not all mapping plugins will
be able to support, bearing, tilting and rolling of the camera.
This class describes what the plugin supports, and is used to restrict changes to the camera information
associated with a \l QGeoMap such that the camera information stays within these limits.
|
10912 |
- |
| qgeocameracapabilities_p.h |
|
3358 |
- |
| qgeocameradata.cpp |
|
3706 |
- |
| qgeocameradata_p.h |
|
2232 |
- |
| qgeocameratiles.cpp |
|
27549 |
- |
| qgeocameratiles_p.h |
|
1555 |
- |
| qgeocameratiles_p_p.h |
|
3131 |
- |
| qgeocodereply.cpp |
!
\class QGeoCodeReply
\inmodule QtLocation
\ingroup QtLocation-geocoding
\since 5.6
\brief The QGeoCodeReply class manages an operation started by an
instance of QGeoCodingManager.
Instances of QGeoCodeReply manage the state and results of these
operations.
The isFinished(), error() and errorString() methods provide information
on whether the operation has completed and if it completed successfully.
The finished() and errorOccurred(QGeoCodeReply::Error,QString)
signals can be used to monitor the progress of the operation.
It is possible that a newly created QGeoCodeReply may be in a finished
state, most commonly because an error has occurred. Since such an instance
will never emit the finished() or
errorOccurred(QGeoCodeReply::Error,QString) signals, it is
important to check the result of isFinished() before making the connections
to the signals. The documentation for QGeoCodingManager demonstrates how
this might be carried out.
If the operation completes successfully the results will be able to be
accessed with locations().
|
8695 |
- |
| qgeocodereply.h |
|
1782 |
- |
| qgeocodereply_p.h |
|
1255 |
- |
| qgeocodingmanager.cpp |
!
\class QGeoCodingManager
\inmodule QtLocation
\ingroup QtLocation-geocoding
\since 5.6
\brief The QGeoCodingManager class provides support for geocoding
operations.
The geocode() and reverseGeocode() functions return
QGeoCodeReply objects, which manage these operations and report on the
result of the operations and any errors which may have occurred.
The geocode() and reverseGeocode() functions can be used to convert
QGeoAddress instances to QGeoCoordinate instances and vice-versa.
The geocode() function is also overloaded to allow a user to perform a free text
geocoding operation, if the string provided can be interpreted as
an address it can be geocoded to coordinate information.
Instances of QGeoCodingManager can be accessed with
QGeoServiceProvider::geocodingManager().
|
10243 |
- |
| qgeocodingmanager.h |
|
1672 |
- |
| qgeocodingmanager_p.h |
|
824 |
- |
| qgeocodingmanagerengine.cpp |
!
\class QGeoCodingManagerEngine
\inmodule QtLocation
\ingroup QtLocation-impl
\since 5.6
\brief The QGeoCodingManagerEngine class provides an interface and
convenience methods to implementers of QGeoServiceProvider plugins who want
to provide support for geocoding operations.
\note There are no source or binary compatibility guarantees for the
backend classes. The API is only guaranteed to work with the Qt version it
was developed against. API changes will however only be made in minor
releases. (6.6, 6.7, and so on.)
In the default implementation, supportsGeocoding() and
supportsReverseGeocoding() returns false while geocode() and
reverseGeocode() cause QGeoCodeReply::UnsupportedOptionError to occur.
If the service provider supports geocoding the subclass should provide an
implementation of geocode() and call setSupportsGeocoding(true) at
some point in time before geocode() is called.
Similarly, if the service provider supports reverse geocoding the subclass
should provide an implementation reverseGeocode() and call
setSupportsReverseGeocoding(true) at some point in time before
reverseGeocode() is called.
A subclass of QGeoCodingManagerEngine will often make use of a subclass
fo QGeoCodeReply internally, in order to add any engine-specific
data (such as a QNetworkReply object for network-based services) to the
QGeoCodeReply instances used by the engine.
\sa QGeoCodingManager
|
11356 |
- |
| qgeocodingmanagerengine.h |
|
1794 |
- |
| qgeocodingmanagerengine_p.h |
|
850 |
- |
| qgeofiletilecache.cpp |
|
18507 |
- |
| qgeofiletilecache_p.h |
This would be internal to qgeofiletilecache.cpp except that the eviction
policy can't be defined without it being concrete here |
4875 |
- |
| qgeojson.cpp |
!
\namespace QGeoJson
\inmodule QtLocation
\internal
From Qt 6.7, QGeoJson is a private API. The replacement API is the GeoJsonData QML type.
|
33067 |
- |
| qgeojson_p.h |
|
1189 |
- |
| qgeomaneuver.cpp |
!
\class QGeoManeuver
\inmodule QtLocation
\ingroup QtLocation-routing
\since 5.6
\brief The QGeoManeuver class represents the information relevant to the
point at which two QGeoRouteSegments meet.
QGeoRouteSegment instances can be thought of as edges on a routing
graph, with QGeoManeuver instances as optional labels attached to the
vertices of the graph.
The most interesting information help in a QGeoManeuver instance is
normally the textual navigation to provide and the position at which to
provide it, accessible by instructionText() and position() respectively.
It is also possible to determine if a routing waypoint has been passed by
checking if waypoint() returns a valid QGeoCoordinate.
|
13815 |
- |
| qgeomaneuver.h |
|
3195 |
- |
| qgeomaneuver_p.h |
|
1983 |
- |
| qgeomaneuverderived_p.h |
|
959 |
- |
| qgeomap.cpp |
|
9106 |
- |
| qgeomap_p.h |
|
4546 |
- |
| qgeomap_p_p.h |
Hooks into the actual map implementations |
3122 |
- |
| qgeomappingmanager.cpp |
!
\class QGeoMappingManager
\inmodule QtLocation
\ingroup QtLocation-maps
\since 5.6
\internal
\brief The QGeoMappingManager class provides support for displaying
and interacting with maps.
|
3948 |
- |
| qgeomappingmanager_p.h |
|
1551 |
- |
| qgeomappingmanager_p_p.h |
|
765 |
- |
| qgeomappingmanagerengine.cpp |
!
\class QGeoMappingManagerEngine
\inmodule QtLocation
\ingroup QtLocation-impl
\since 5.6
\internal
\brief Provides support functionality for map display with QGeoServiceProvider.
\note There are no source or binary compatibility guarantees for the
backend classes. The API is only guaranteed to work with the Qt version it
was developed against. API changes will however only be made in minor
releases. (6.6, 6.7, and so on.)
The QGeoMappingManagerEngine class provides an interface and convenience
methods to implementors of QGeoServiceProvider plugins who want to
provide support for displaying and interacting with maps.
|
5360 |
- |
| qgeomappingmanagerengine_p.h |
|
2119 |
- |
| qgeomappingmanagerengine_p_p.h |
|
1116 |
- |
| qgeomaptype.cpp |
!
\qmltype mapType
\inqmlmodule QtLocation
\ingroup qml-QtLocation5-maps
\since QtLocation 5.5
\brief The mapType type holds information about a map type.
This includes the map type's \l name and \l description, the \l style and
a flag to indicate if the map type is optimized for mobile devices (\l mobile).
|
5412 |
- |
| qgeomaptype_p.h |
|
3276 |
- |
| qgeomaptype_p_p.h |
|
1504 |
- |
| qgeoprojection.cpp |
QGeoProjectionWebMercator implementation
|
33922 |
- |
| qgeoprojection_p.h |
|
9506 |
- |
| qgeoroute.cpp |
!
\class QGeoRoute
\inmodule QtLocation
\ingroup QtLocation-routing
\since 5.6
\brief The QGeoRoute class represents a route between two points.
A QGeoRoute object contains high level information about a route, such
as the length the route, the estimated travel time for the route,
and enough information to render a basic image of the route on a map.
The QGeoRoute object also contains a list of QGeoRouteSegment objecs which
describe subsections of the route in greater detail.
Routing information is normally requested using
QGeoRoutingManager::calculateRoute(), which returns a QGeoRouteReply
instance. If the operation is completed successfully the routing
information can be accessed with QGeoRouteReply::routes()
\sa QGeoRoutingManager
|
14929 |
- |
| qgeoroute.h |
|
3487 |
- |
| qgeoroute_p.h |
|
3029 |
- |
| qgeorouteparser.cpp |
Private class implementations
|
1657 |
- |
| qgeorouteparser_p.h |
|
1610 |
- |
| qgeorouteparser_p_p.h |
|
1213 |
- |
| qgeorouteparserosrmv5.cpp |
: Always appended to one of the following strings:
- "Enter the roundabout"
- "Enter the rotary"
- "Enter the rotary <rotaryname>"
|
46090 |
- |
| qgeorouteparserosrmv5_p.h |
|
1413 |
- |
| qgeoroutereply.cpp |
!
\class QGeoRouteReply
\inmodule QtLocation
\ingroup QtLocation-routing
\since 5.6
\brief The QGeoRouteReply class manages an operation started by an instance
of QGeoRoutingManager.
Instances of QGeoRouteReply manage the state and results of these
operations.
The isFinished(), error() and errorString() methods provide information
on whether the operation has completed and if it completed successfully.
The finished() and errorOccurred(QGeoRouteReply::Error,QString)
signals can be used to monitor the progress of the operation.
It is possible that a newly created QGeoRouteReply may be in a finished
state, most commonly because an error has occurred. Since such an instance
will never emit the finished() or
errorOccurred(QGeoRouteReply::Error,QString) signals, it is
important to check the result of isFinished() before making the connections
to the signals. The documentation for QGeoRoutingManager demonstrates how
this might be carried out.
If the operation completes successfully the results will be able to be
accessed with routes().
|
7054 |
- |
| qgeoroutereply.h |
|
1546 |
- |
| qgeoroutereply_p.h |
|
1048 |
- |
| qgeorouterequest.cpp |
!
\class QGeoRouteRequest
\inmodule QtLocation
\ingroup QtLocation-routing
\since 5.6
\brief The QGeoRouteRequest class represents the parameters and restrictions
which define a request for routing information.
The default state of a QGeoRouteRequest instance will result in a request
for basic route segment and navigation maneuvers describing the fastest
route by car which covers the given waypoints.
There may be significant variation in the features supported by different
providers of routing information, or even in the features supported by
the same provider if different levels of authorization are used.
There are several functions in QGeoRoutingManager which can be used to
check which features are supported with the current provider and
authorization level.
\sa QGeoRoutingManager
|
14509 |
- |
| qgeorouterequest.h |
|
4855 |
- |
| qgeorouterequest_p.h |
|
1394 |
- |
| qgeoroutesegment.cpp |
!
\class QGeoRouteSegment
\inmodule QtLocation
\ingroup QtLocation-routing
\since 5.6
\brief The QGeoRouteSegment class represents a segment of a route.
A QGeoRouteSegment instance has information about the physical layout
of the route segment, the length of the route and estimated time required
to traverse the route segment and an optional QGeoManeuver associated with
the beginning of the route segment.
QGeoRouteSegment instances can be thought of as edges on a routing
graph, with QGeoManeuver instances as optional labels attached to the
vertices of the graph.
|
9577 |
- |
| qgeoroutesegment.h |
|
2412 |
- |
| qgeoroutesegment_p.h |
|
1929 |
- |
| qgeoroutingmanager.cpp |
!
\class QGeoRoutingManager
\inmodule QtLocation
\ingroup QtLocation-routing
\since 5.6
\brief The QGeoRoutingManager class provides support for geographic routing
operations.
The calculateRoute() and updateRoute() methods function QGeoRouteReply
objects, which manage these operations and report on the result of the
operations and any errors which may have occurred.
The calculateRoute() function is used to find a route (or routes) that
follows a set of waypoints and matches various other criteria. The
QGeoRouteRequest class is used to specify this information.
If supportsRouteUpdates() returns true then the QGeoRoutingManager
supports updating route information based on position updates. This
will cause the travel time and distance estimates to be updated, and
any QGeoRouteSegments already traversed to be removed from the route.
The updates can be triggered with the updateRoute() function, which makes
use of the QGeoPositionInfo instances emitted as position updates by
QGeoPositionInfoSource.
Instances of QGeoRoutingManager can be accessed with
QGeoServiceProvider::routingManager().
A small example of the usage of QGeoRoutingManager and QGeoRouteRequests
follows:
\snippet maps/routehandler.h RouteHandler
|
10012 |
- |
| qgeoroutingmanager.h |
|
1908 |
- |
| qgeoroutingmanager_p.h |
|
709 |
- |
| qgeoroutingmanagerengine.cpp |
!
\class QGeoRoutingManagerEngine
\inmodule QtLocation
\ingroup QtLocation-impl
\since 5.6
\brief The QGeoRoutingManagerEngine class provides an interface and
convenience methods to implementers of QGeoServiceProvider plugins who want
to provide access to geographic routing information.
\note There are no source or binary compatibility guarantees for the
backend classes. The API is only guaranteed to work with the Qt version it
was developed against. API changes will however only be made in minor
releases. (6.6, 6.7, and so on.)
Subclasses of QGeoRoutingManagerEngine need to provide an implementation of
calculateRoute().
In the default implementation, supportsRouteUpdates() returns false and
updateRoute() returns a QGeoRouteReply object containing a
QGeoRouteReply::UnsupportedOptionError.
If the routing service supports updating routes as they are being
traveled, the subclass should provide an implementation of updateRoute()
and call setSupportsRouteUpdates(true) at some point in time before
updateRoute() is called.
The function setSupportsRouteUpdates() is one of several functions which
configure the reported capabilities of the engine. If the capabilities
of an engine differ from the default values these functions should be
used so that the reported capabilities are accurate.
It is important that this is done before calculateRoute(), updateRoute()
or any of the capability reporting functions are used to prevent
incorrect or inconsistent behavior.
A subclass of QGeoRouteManagerEngine will often make use of a subclass
fo QGeoRouteReply internally, in order to add any engine-specific
data (such as a QNetworkReply object for network-based services) to the
QGeoRouteReply instances used by the engine.
\sa QGeoRoutingManager
|
13696 |
- |
| qgeoroutingmanagerengine.h |
|
2594 |
- |
| qgeoroutingmanagerengine_p.h |
|
1235 |
- |
| qgeoserviceprovider.cpp |
!
\class QGeoServiceProvider
\inmodule QtLocation
\ingroup QtLocation-common
\since 5.6
\brief The QGeoServiceProvider class aggregates access to services which provide
geographical information.
The Maps and Navigation API allows people to access various kinds of
geographical information, including functionality to perform geocoding,
routing and the display of maps. The QGeoServiceProvider aggregates the
access to a set of these services that are provided by a single vendor.
It is possible to mix and match service providers for the various domains,
so that a geocoding manager from one service provider can be used with
a geographic routing manager from another service provider.
This is not recommended unless the client is able to verify that the
data provided by the different services are compatible, as differences
in the underlying data sets could cause serious incongruences between
the services.
Subclasses of QGeoServiceProvider guarantee that the different services
that they provide are interoperable.
Each service provider must follow a naming convention for their service specific
parameter names/keys. They use the provider name as prefix for all their
parameter names. When a provider is loaded only those parameters are
passed on whose parameter names start with the provider name. This avoids the sharing
sensitive parameters such as confidential \c token or \c app_id parameters with other
plugins.
Please check the GeoServices plugin specific documentation to
obtain a complete list of the available parameter names/keys and values.
|
29608 |
- |
| qgeoserviceprovider.h |
|
5047 |
- |
| qgeoserviceprovider_p.h |
helper templates for generating the feature and manager accessors |
2628 |
- |
| qgeoserviceproviderfactory.cpp |
!
\class QGeoServiceProviderFactory
\inmodule QtLocation
\ingroup QtLocation-impl
\since 5.6
\deprecated
\brief The QGeoServiceProviderFactory class is a factory class used as the
plugin interface for services related to geographical information.
\note There are no source or binary compatibility guarantees for the
backend classes. The API is only guaranteed to work with the Qt version it
was developed against. API changes will however only be made in minor
releases. (6.6, 6.7, and so on.)
Implementers must provide a unique combination of providerName() and
providerVersion() per plugin.
The other functions should be overridden if the plugin supports the
associated set of functionality.
|
5152 |
- |
| qgeoserviceproviderfactory.h |
|
1473 |
- |
| qgeotiledmap.cpp |
|
13613 |
- |
| qgeotiledmap_p.h |
|
1982 |
- |
| qgeotiledmap_p_p.h |
|
2373 |
- |
| qgeotiledmappingmanagerengine.cpp |
!
\class QGeoTiledMappingManagerEngine
\internal
|
8034 |
- |
| qgeotiledmappingmanagerengine_p.h |
|
2587 |
- |
| qgeotiledmappingmanagerengine_p_p.h |
|
1147 |
- |
| qgeotiledmapreply.cpp |
!
\class QGeoTiledMapReply
\inmodule QtLocation
\ingroup QtLocation-impl
\since 5.6
\internal
\brief The QGeoTiledMapReply class manages a tile fetch operation started
by an instance of QGeoTiledManagerEngine.
Instances of QGeoTiledMapReply manage the state and results of these
operations.
The isFinished(), error() and errorString() methods provide information
on whether the operation has completed and if it completed successfully.
The finished() and errorOccurred(QGeoTiledMapReply::Error,QString)
signals can be used to monitor the progress of the operation.
It is possible that a newly created QGeoTiledMapReply may be in a finished
state, most commonly because an error has occurred. Since such an instance
will never emit the finished() or
errorOccurred(QGeoTiledMapReply::Error,QString) signals, it is
important to check the result of isFinished() before making the connections
to the signals.
If the operation completes successfully the results are accessed by
mapImageData() and mapImageFormat().
|
7201 |
- |
| qgeotiledmapreply_p.h |
|
1796 |
- |
| qgeotiledmapreply_p_p.h |
|
1026 |
- |
| qgeotiledmapscene.cpp |
|
21071 |
- |
| qgeotiledmapscene_p.h |
|
1706 |
- |
| qgeotiledmapscene_p_p.h |
|
5016 |
- |
| qgeotilefetcher.cpp |
|
4643 |
- |
| qgeotilefetcher_p.h |
|
1988 |
- |
| qgeotilefetcher_p_p.h |
|
1278 |
- |
| qgeotilerequestmanager.cpp |
|
7107 |
- |
| qgeotilerequestmanager_p.h |
|
1409 |
- |
| qgeotilespec.cpp |
|
2657 |
- |
| qgeotilespec_p.h |
|
2505 |
- |
| qgeotilespec_p_p.h |
|
1695 |
- |