1. Home
  2. Knowledge Base
  3. Mobile app
  4. Advanced Soarvo Mobile Functionality

Advanced Soarvo Mobile Functionality

Position Averaging for Feature Geometry

Prerequisites:
Basic knowledge of how to use the Soarvo mobile application.
Basic knowledge of how to use the Soarvo web portal.

App Version:
0.0.42+

When this feature is enabled and when the geometry of a point feature is updated to the current users position (or the current users device position is used as nodes for linear or area geometry) an average of the users position is taken over a configurable amount of time. That is then used instead of just the current users position. This feature is enabled on a per feature type basis.

To enable this functionality you should have two numerical attributes in a feature type with the name ‘_POSITION_AVERAGING_TIME_FRAME’ and ‘_POSITION_AVERAGING_MAX_ACC’. _POSITION_AVERAGING_TIME_FRAME controls how the time period that the average occurs over (in seconds). _POSITION_AVERAGING_MAX_ACC controls the minimum horizontal accuracy (in meters) that qualifies a users position to be used in the averaging calculation.

_POSITION_AVERAGING_MAX_ACC is an optional attribute, if it is not present in the feature type then the maximum accuracy for a position to be used in the average calculation is 9999m.

For example if _POSITION_AVERAGING_TIME_FRAME is set to 30 and _POSITION_AVERAGING_MAX_ACC is set to 5 then the averaging occurs over 30 seconds and will only use user positions where the accuracy is 5m or below.

Once the attributes have been added to the required feature type you will need to sync down the updated feature types on the Soarvo mobile application. You can do this either via ‘pull to refresh’ in the feature list for a given location, or via ‘pull to refresh’ in the feature type list which appears when you tap the green ‘add new feature’ floating action button. The below video shows how it functions on the Soarvo mobile application for a point feature – it also demonstrates how the position averaging only happens when the users position is used, it does not affect tapping on the map to manually change the features geometry.

Was this article helpful?

Need Support?

Can't find the answer you're looking for?
Contact Support