Remarks

This method can be used to move a feature smoothly from its current position to a new one. The animation will run until the new position is reached, after duration seconds, and then stop.

Every time the feature is updated, RefreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode Dynamic and DynamicAsync. View.UpdateRequired events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method will start an animation of the feature, using 2D parameters bearing and speed. Every time the view is updated, the speed and direction will be updated and a new position calculated, depending on how long time has elapsed since the previous update (see Time and TimeFactor). The current bearing and speed values will be set as attributes #memdsBearing and #memdsSpeed, and can be used when visualizing the feature. The animation will continue until another animation is specified, or until StopFeatureAnimation is called explicitly by the application.

Every time the feature is updated, RefreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode Dynamic and DynamicAsync. View.UpdateRequired events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Even though this animation is done in only two dimensions, the animated feature can still be displayed in a 3D globe view. There is another overload of this method that can be used to do more complex 3D animations.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method will start an animation of the feature, in three dimensions. The feature position and the bearing, pitch and roll parameters specify the current orientation of the feature in 3D space. The speed parameter specifies the current feature speed, in a local feature coordinate system: the x coordinate is the speed in the forward direction, the y coordinate is side-ways speed (positive to the left), and z is the upward speed. The delta* parameters specify the corresponding change rate of these parameters. Every time the view is updated, the current bearing, pitch, roll and speed will be updated, and a new position calculated, depending on how long time has elapsed since the previous update (see Time and TimeFactor). The current feature state values will be set as attributes #memdsBearing, #memdsPitch, #memdsRoll, and #memdsSpeed, and can be used when visualizing the feature. The animation will continue until another animation is specified, or until StopFeatureAnimation is called explicitly by the application.

Every time the feature is updated, RefreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode Dynamic and DynamicAsync. View.UpdateRequired events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Even though this animation is done in three dimensions, the animated feature can still be displayed in a 2D view. There is another overload of this method that can be used to do a simpler 2D animation just using direction and speed.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method can be used to move a feature smoothly from its current position to a new one. The animation will run until the new position is reached, after duration seconds, and then stop.

Every time the feature is updated, refreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode OrdinaryLayerCacheModeDynamic and OrdinaryLayerCacheModeDynamicAsync. View::updateRequired events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method will start an animation of the feature, using 2D parameters bearing and speed. Every time the view is updated, the speed and direction will be updated and a new position calculated, depending on how long time has elapsed since the previous update (see time and timeFactor). The current bearing and speed values will be set as attributes #memdsBearing and #memdsSpeed, and can be used when visualizing the feature. The animation will continue until another animation is specified, or until stopFeatureAnimation is called explicitly by the application.

Every time the feature is updated, refreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode OrdinaryLayerCacheModeDynamic and OrdinaryLayerCacheModeDynamicAsync. View::updateRequired events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Even though this animation is done in only two dimensions, the animated feature can still be displayed in a 3D globe view. There is another overload of this method that can be used to do more complex 3D animations.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method will start an animation of the feature, in three dimensions. The feature position and the bearing, pitch and roll parameters specify the current orientation of the feature in 3D space. The speed parameter specifies the current feature speed, in a local feature coordinate system: the x coordinate is the speed in the forward direction, the y coordinate is side-ways speed (positive to the left), and z is the upward speed. The delta* parameters specify the corresponding change rate of these parameters. Every time the view is updated, the current bearing, pitch, roll and speed will be updated, and a new position calculated, depending on how long time has elapsed since the previous update (see time and timeFactor). The current feature state values will be set as attributes #memdsBearing, #memdsPitch, #memdsRoll, and #memdsSpeed, and can be used when visualizing the feature. The animation will continue until another animation is specified, or until stopFeatureAnimation is called explicitly by the application.

Every time the feature is updated, refreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode OrdinaryLayerCacheModeDynamic and OrdinaryLayerCacheModeDynamicAsync. View::updateRequired events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Even though this animation is done in three dimensions, the animated feature can still be displayed in a 2D view. There is another overload of this method that can be used to do a simpler 2D animation just using direction and speed.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method can be used to move a feature smoothly from its current position to a new one. The animation will run until the new position is reached, after duration seconds, and then stop.

Every time the feature is updated, refreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode DYNAMIC and DYNAMICASYNC. View.updateRequired events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method will start an animation of the feature, using 2D parameters bearing and speed. Every time the view is updated, the speed and direction will be updated and a new position calculated, depending on how long time has elapsed since the previous update (see time and timeFactor). The current bearing and speed values will be set as attributes #memdsBearing and #memdsSpeed, and can be used when visualizing the feature. The animation will continue until another animation is specified, or until stopFeatureAnimation is called explicitly by the application.

Every time the feature is updated, refreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode DYNAMIC and DYNAMICASYNC. View.updateRequired events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Even though this animation is done in only two dimensions, the animated feature can still be displayed in a 3D globe view. There is another overload of this method that can be used to do more complex 3D animations.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method will start an animation of the feature, in three dimensions. The feature position and the bearing, pitch and roll parameters specify the current orientation of the feature in 3D space. The speed parameter specifies the current feature speed, in a local feature coordinate system: the x coordinate is the speed in the forward direction, the y coordinate is side-ways speed (positive to the left), and z is the upward speed. The delta* parameters specify the corresponding change rate of these parameters. Every time the view is updated, the current bearing, pitch, roll and speed will be updated, and a new position calculated, depending on how long time has elapsed since the previous update (see time and timeFactor). The current feature state values will be set as attributes #memdsBearing, #memdsPitch, #memdsRoll, and #memdsSpeed, and can be used when visualizing the feature. The animation will continue until another animation is specified, or until stopFeatureAnimation is called explicitly by the application.

Every time the feature is updated, refreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode DYNAMIC and DYNAMICASYNC. View.updateRequired events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Even though this animation is done in three dimensions, the animated feature can still be displayed in a 2D view. There is another overload of this method that can be used to do a simpler 2D animation just using direction and speed.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method can be used to move a feature smoothly from its current position to a new one. The animation will run until the new position is reached, after duration seconds, and then stop.

Every time the feature is updated, refreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode OrdinaryLayerCacheMode.Dynamic and OrdinaryLayerCacheMode.DynamicAsync. View.updateRequired (not available in Python) events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method will start an animation of the feature, using 2D parameters bearing and speed. Every time the view is updated, the speed and direction will be updated and a new position calculated, depending on how long time has elapsed since the previous update (see time and timeFactor). The current bearing and speed values will be set as attributes #memdsBearing and #memdsSpeed, and can be used when visualizing the feature. The animation will continue until another animation is specified, or until stopFeatureAnimation is called explicitly by the application.

Every time the feature is updated, refreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode OrdinaryLayerCacheMode.Dynamic and OrdinaryLayerCacheMode.DynamicAsync. View.updateRequired (not available in Python) events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Even though this animation is done in only two dimensions, the animated feature can still be displayed in a 3D globe view. There is another overload of this method that can be used to do more complex 3D animations.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.

Remarks

This method will start an animation of the feature, in three dimensions. The feature position and the bearing, pitch and roll parameters specify the current orientation of the feature in 3D space. The speed parameter specifies the current feature speed, in a local feature coordinate system: the x coordinate is the speed in the forward direction, the y coordinate is side-ways speed (positive to the left), and z is the upward speed. The delta* parameters specify the corresponding change rate of these parameters. Every time the view is updated, the current bearing, pitch, roll and speed will be updated, and a new position calculated, depending on how long time has elapsed since the previous update (see time and timeFactor). The current feature state values will be set as attributes #memdsBearing, #memdsPitch, #memdsRoll, and #memdsSpeed, and can be used when visualizing the feature. The animation will continue until another animation is specified, or until stopFeatureAnimation is called explicitly by the application.

Every time the feature is updated, refreshFeaturePresentation will be called automatically, with the value passed in moveOnly, so animation will also work in ordinary layers with cache mode OrdinaryLayerCacheMode.Dynamic and OrdinaryLayerCacheMode.DynamicAsync. View.updateRequired (not available in Python) events will also be generated, so in most cases the application only needs to update the view once after this method is called; after that the view will be updated automatically until the animation stops.

Even though this animation is done in three dimensions, the animated feature can still be displayed in a 2D view. There is another overload of this method that can be used to do a simpler 2D animation just using direction and speed.

Note that this type of animation is different from animated visualization. This method actually modifies the feature instead of just animating visualization parameters. For more information see Animated Visualization.