class QGeoRoutingManagerEngine

The QGeoRoutingManagerEngine class provides an interface and convenience methods to implementers of QGeoServiceProvider plugins who want to provide access to geographic routing information. More

Inheritance diagram of PySide6.QtLocation.QGeoRoutingManagerEngine

Synopsis

Methods

Virtual methods

Signals

Note

This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE

Detailed Description

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 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.

__init__(parameters[, parent=None])
Parameters:
  • parameters – Dictionary with keys of type .QString and values of type QVariant.

  • parentQObject

Constructs a new engine with the specified parent, using parameters to pass any implementation specific data to the engine.

abstract calculateRoute(request)
Parameters:

requestQGeoRouteRequest

Return type:

QGeoRouteReply

Begins the calculation of the route specified by request.

A QGeoRouteReply object will be returned, which can be used to manage the routing operation and to return the results of the operation.

This engine and the returned QGeoRouteReply object will emit signals indicating if the operation completes or if errors occur.

Once the operation has completed, routes can be used to retrieve the calculated route or routes.

If request includes features which are not supported by this engine, as reported by the methods in this engine, then a UnsupportedOptionError will occur.

The user is responsible for deleting the returned reply object, although this can be done in the slot connected to finished() , errorOccurred() , finished() or errorOccurred() with deleteLater().

errorOccurred(reply, error[, errorString=""])
Parameters:

This signal is emitted when an error has been detected in the processing of reply. The finished() signal will probably follow.

The error will be described by the error code error. If errorString is not empty it will contain a textual description of the error.

This signal and errorOccurred() will be emitted at the same time.

Note

Do not delete the reply object in the slot connected to this signal. Use deleteLater() instead.

finished(reply)
Parameters:

replyQGeoRouteReply

This signal is emitted when reply has finished processing.

If reply::error() equals NoError then the processing finished successfully.

This signal and finished() will be emitted at the same time.

Note

Do not delete the reply object in the slot connected to this signal. Use deleteLater() instead.

locale()
Return type:

QLocale

Returns the locale used to hint to this routing manager about what language to use for addresses and instructions.

See also

setLocale()

managerName()
Return type:

str

Returns the name which this engine implementation uses to distinguish itself from the implementations provided by other plugins.

The combination of managerName() and managerVersion() should be unique amongst plugin implementations.

managerVersion()
Return type:

int

Returns the version of this engine implementation.

The combination of managerName() and managerVersion() should be unique amongst plugin implementations.

measurementSystem()
Return type:

MeasurementSystem

Returns the measurement system used by this manager.

If setMeasurementSystem() has been called then the value returned by this function may be different to that returned by locale() .measurementSystem(). In which case the value returned by this function is what will be used by the manager.

setLocale(locale)
Parameters:

localeQLocale

Sets the locale to be used by this manager to locale.

If this routing manager supports returning addresses and instructions in different languages, they will be returned in the language of locale.

The locale used defaults to the system locale if this is not set.

See also

locale()

setMeasurementSystem(system)
Parameters:

systemMeasurementSystem

Sets the measurement system used by this manager to system.

The measurement system can be set independently of the locale. Both setLocale() and this function set the measurement system. The value set by the last function called will be used.

setSupportedFeatureTypes(featureTypes)
Parameters:

featureTypes – Combination of FeatureType

Sets the types of features that this engine can take into account during route planning to featureTypes.

It is important that subclasses use this method to ensure that the engine reports its capabilities correctly. If this function is not used the engine will report that it supports no feature types at all.

setSupportedFeatureWeights(featureWeights)
Parameters:

featureWeights – Combination of FeatureWeight

Sets the weightings which this engine can apply to different features during route planning to featureWeights.

It is important that subclasses use this method to ensure that the engine reports its capabilities correctly. If this function is not used the engine will report that it supports no feature weights at all.

setSupportedManeuverDetails(maneuverDetails)
Parameters:

maneuverDetails – Combination of ManeuverDetail

Sets the levels of detail for navigation maneuvers which can be requested by this engine to maneuverDetails.

It is important that subclasses use this method to ensure that the engine reports its capabilities correctly. If this function is not used the engine will report that it supports no maneuver details at all.

setSupportedRouteOptimizations(optimizations)
Parameters:

optimizations – Combination of RouteOptimization

Sets the route optimizations supported by this engine to optimizations.

It is important that subclasses use this method to ensure that the engine reports its capabilities correctly. If this function is not used the engine will report that it supports no route optimizations at all.

setSupportedSegmentDetails(segmentDetails)
Parameters:

segmentDetails – Combination of SegmentDetail

Sets the levels of detail for routing segments which can be requested by this engine to segmentDetails.

It is important that subclasses use this method to ensure that the engine reports its capabilities correctly. If this function is not used the engine will report that it supports no segment detail at all.

setSupportedTravelModes(travelModes)
Parameters:

travelModes – Combination of TravelMode

Sets the travel modes supported by this engine to travelModes.

It is important that subclasses use this method to ensure that the engine reports its capabilities correctly. If this function is not used the engine will report that it supports no travel modes at all.

supportedFeatureTypes()
Return type:

Combination of FeatureType

Returns the types of features that this engine can take into account during route planning.

supportedFeatureWeights()
Return type:

Combination of FeatureWeight

Returns the weightings which this engine can apply to different features during route planning.

supportedManeuverDetails()
Return type:

Combination of ManeuverDetail

Returns the levels of detail for navigation maneuvers which can be requested by this engine.

supportedRouteOptimizations()
Return type:

Combination of RouteOptimization

Returns the route optimizations supported by this engine.

supportedSegmentDetails()
Return type:

Combination of SegmentDetail

Returns the levels of detail for routing segments which can be requested by this engine.

supportedTravelModes()
Return type:

Combination of TravelMode

Returns the travel modes supported by this engine.

updateRoute(route, position)
Parameters:
Return type:

QGeoRouteReply

Begins the process of updating route based on the current position position.

A QGeoRouteReply object will be returned, which can be used to manage the routing operation and to return the results of the operation.

This engine and the returned QGeoRouteReply object will emit signals indicating if the operation completes or if errors occur.

If supportsRouteUpdates() returns false an UnsupportedOptionError will occur.

Once the operation has completed, routes can be used to retrieve the updated route.

The returned route could be entirely different to the original route, especially if position is far enough away from the initial route. Otherwise the route will be similar, although the remaining time and distance will be updated and any segments of the original route which have been traversed will be removed.

The user is responsible for deleting the returned reply object, although this can be done in the slot connected to finished() , errorOccurred() , finished() or errorOccurred() with deleteLater().