ArcGIS Runtime SDK for iOS
100.15
|
A single maneuver in a series of driving direction.
Instances of this class represent an individual maneuver in a series of turn-by-turn driving directions.
Properties | |
NSArray< AGSDirectionEvent * > * | directionEvents |
NSString * | directionText |
double | duration |
double | estimatedArrivalTimeShift |
NSDate * | estimatedArriveTime |
NSInteger | fromLevel |
AGSGeometry * | geometry |
double | length |
NSArray< AGSDirectionMessage * > * | maneuverMessages |
AGSDirectionManeuverType | maneuverType |
NSInteger | toLevel |
|
readnonatomiccopy |
Events along the maneuver
|
readnonatomiccopy |
User-friendly text describing the maneuver
|
readnonatomicassign |
Duration (in minutes) of the maneuver
|
readnonatomicassign |
Time zone shift in minutes (based on the destination of this manuever) for the estimated arrival time.
|
readnonatomicstrong |
Estimated time of arrival at the destination of this manuever in the current locale of the device.
|
readnonatomicassign |
The logical level at the start of the maneuver. The fromLevel
and toLevel
properties are defined to provide a way to filter directions based on logical level division. For example, a 3D routing application might render a 2D map with route lines filtered by vertical level instead of displaying overlapping lines on different levels. The fromLevel
and toLevel
properties are populated from source data and not calculated by the directions engine. If the source data does not contain "LevelFrom" and "LevelTo" fields, the properties will be populated with -1 values
|
readnonatomicstrong |
Geometry representing the maneuver, be it a turn or travelling in a straight line.
|
readnonatomicassign |
Length (in meters) of the maneuver
|
readnonatomiccopy |
The detailed messages describing this manuever
|
readnonatomicassign |
The maneuver type
|
readnonatomicassign |
The logical level at the end of the maneuver. The fromLevel
and toLevel
properties are defined to provide a way to filter directions based on logical level division. For example, a 3D routing application might render a 2D map with route lines filtered by vertical level instead of displaying overlapping lines on different levels. The fromLevel
and toLevel
properties are populated from source data and not calculated by the directions engine. If the source data does not contain "LevelFrom" and "LevelTo" fields, the properties will be populated with -1 values