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.

Example Video

The post Position Averaging for Feature Geometry appeared first on Soarvo.

Prerequisites:
Basic knowledge of how to use the Soarvo mobile application.
Basic knowledge of how to use the Soarvo web portal and setup feature types.
Knowledge of how to apply codes (previously called default codes in K-Capture) to attributes following the ‘App Codes for Attribute Settings Document’ below.

App Version:
0.0.98+

App Codes for Attribute Settings Document:
https://github.com/KorecGroup/soarvo-mobile-flutter-public-docs/blob/0.0.98/default-codes-doc.md

Manhole + pipe snapping refers to the functionality, previously available in K-Capture, for a linear feature (ie a pipe) to snap its start and end nodes to point features (ie manholes), and pull attribute values from the snapped point features into the linear feature for calculations – and more. When you also change the geometry or update one of the snapped point features, it should recalculate the attributes of the snapped linear feature and update its geometry to the new snapped point feature position.

The feature types for both the linear and point features requires a specific setup to activate this.

Point Feature Type Setup

If you want to activate the functionality which recalculates the snapped linear features geometry and attributes when you create / edit a given feature of this feature type then you need to add an attribute to the point feature type with a name of _recalc_snaps like in the below screenshot. You can hide this attribute from the feature type form via the attribute setting value of !MODIFIER-HIDE.

Linear Feature Type Setup

You can use the !SNAPPEDSTART(AttributeNameHere) and !SNAPPEDEND(AttributeNameHere) to pull out attribute values from the point features which are snapped to the respective start and end of the linear feature. Where ‘AttributeNameHere’ is the name of the attribute from the point feature. For example, if you wanted to pull out the value of the ‘COVER_LEV’ attribute from the manhole point features you would create attributes in the linear pipe feature type as below.

You can then calculate the difference between these values using the !CALC syntax for the attribute settings in an other attribute in the pipe feature type like below. The attribute names ‘DownstreamCoverLevel’ and ‘UpstreamCoverLevel’ are prefixed with a $ character to make them reactive, meaning whenever the ‘DownstreamCoverLevel’ or ‘UpstreamCoverLevel’ attributes are changed then this calculation is reran.

Example Video

With the feature types setup you should be able to follow the video below, in this two point features already exist with a ‘COVER_LEV’ attribute value. The video demonstrates creating a linear feature between them and then changing the position and COVER_LEV of one of the snapped point features.

The post Manhole + Pipe Snapping appeared first on Soarvo.

Prerequisites:
Basic knowledge of how to use the Soarvo mobile application.
Basic knowledge of how to use the Soarvo web portal and setup feature types.
Basic knowledge of operating and setting up an RD8K unit.

App Version:
0.0.112+

This functionality is available on ANDROID ONLY.

Soarvo Mobile has direct integration with Radio Detection’s RD8K Bluetooth units for cable and pipe based measurements.

Pairing the RD8K Unit to a Android Device

You will need to first follow the manual for whichever RD8K unit you have for pairing to your Android device first. The videos below show how this is done for a RD8200 unit, but should be similar for RD8100 units also.

In summary, the important aspects for pairing the RD8K unit are:

• Ensure Bluetooth communication is enabled via setting the ‘COM’ option to ‘on’
• Ensure the protocol (PROT in the RD8K UI) is ASCII. Where this is done can change depending on the unit version. The ASCII protocol version should also be set to ‘2’ if available
• If the ‘PHONE’ option is available, ensure it is set to ‘ANRD’
• Ensure the RD8K unit is paired to the android device via Bluetooth. The name of the bluetooth device is different depending on the unit and is separate from the RTK Locator built into some RD8K units. So consult the manual for your units Bluetooth name

The video below shows how to change the ‘COM’ option to ‘on’.

If Bluetooth communication has been successfully enabled, you should see a Bluetooth icon on the RD8K units display, which is highlighted in the below screenshot.

The video below shows how to change the ‘PROT’ option, which should be set to ASCII, ASCII version to ‘2’.

Setting up Soarvo Mobile to Receive RD8K Readings

Once the RD8K is paired and setup properly – you then need to configure Soarvo Mobile to receive readings from the unit. The below video shows how you can do this via the ‘External Devices’ section in the GPS management page.

In summary, the important aspects of the above video are:

• The feature type selected in the ‘RD8K Feature Type’ configuration field is the feature type that is used to auto start a feature when you’re in the location features overview page, and are not recording a feature. If no feature type is selected, then a feature type with a name of ‘RD8K’ is attempted to be used.
• Once the RD8K connection is enabled in the app, this connection is auto attempted on each boot up of the app. So you should not have to keep re-enabling it.

Recording RD8K Data in a Feature

You can take and send a measurement from the RD8K unit by clicking the button highlighted by the green circle in the image below. The Bluetooth icon on the RD8K units display panel will begin flashing, if an error does occur this will be displayed on the bottom left of the units display panel with an error code – which can be checked against the manual.

As you can see in the video in the above section, the full data string from the RD8K unit is auto added to the ‘FullData’ attribute. This is useful to see the raw data from the unit. You can get this by adding an attribute with a default code of ‘!RD8K’ to the feature type selected in the ‘RD8K Feature Type’, like in the below screenshot.

To instead just use a single value from the RD8K measurement (such as the depth) data you will need to know its index in the data which is comma separated. Then you can setup an attribute with a default code of ‘!RD8K(n)’ where n is the position of the value within the RD8K data (which is a 1 based index). For instance, if I want to pull out the 13th value from the data then I would setup an attribute like in the below screenshot.

RD8K Positions as Line/Polygon Nodes

If you’re recording a linear or area feature and record a measurement on the RD8K unit then your current position is added as a node to the linear or area feature. If the project contains a ‘RD8KNode’ point feature type then a point feature for each node measurement is also created. You can also use !RD8K default codes within the RD8KNode feature types attributes.

RD8K Bluetooth GPS Receiver as a Position Source

Some RD8K units come with a Bluetooth GPS receiver which can receive RTK corrections. The Bluetooth GPS receiver is usually a separate Bluetooth device from the RD8K locator. You will need to pair this Bluetooth GPS receiver with your android device, the manual for your RD8K unit will contain instructions for this.

After pairing – you should be able to follow the ‘Bluetooth GPS Receiver as a Position Source’ section in this page to then use this as a position source in Soarvo Mobile and send RTK corrections to the receiver (if required).

Please ensure you only use RTCM 3.x enabled mountpoints if your RD8K unit is the RD8200SG unit and want to use RTK corrections.

for the RD8200SG unit, there will be a flashing green light on the unit when the position is of RTK float quality. This changes to a solid green when the position is of RTK fixed quality.

The post RD8000+ Integration appeared first on Soarvo.

Radio Group Option with Default Codes

Radio group attributes can have default codes added as an option (you can also add default codes as a nested option). The default codes are processed when the attribute is opened and the processed value is added to the list of values the user can select. Not all default codes are supported in radio group options. The supported codes are:

• Feature Created Default Codes
• Calculation Based Default Codes

Radio Group and Checkbox Group Default Codes

For radio group and checkbox group attributes, you set the default code of the attribute by prefixing the first value in its list of options with 'DEFAULTCODE-', for example if the first option is DEFAULTCODE-!MODIFIER-SHOWWHEN $CATCompetency == 'No' then the default code for that attribute would set to !MODIFIER-SHOWWHEN $CATCompetency == 'No'.

Feature Type Metadata Settings

Feature Types can include metadata settings attributes which act like settings for that Feature Type and control specific pieces of functionality. These are typically attributes whose names are prefixed with an underscore (e.g. _ON_SAVE_ACTIONS).

This list is not comprehensive. The SOARVO knowledgebase contains dedicated pages for some functionality (for example, auto-recording linear/area nodes) which document the required metadata settings attributes for those workflows. The table below is only for metadata settings that don't require their own dedicated page.

Feature Type Metadata Settings

Feature Types can include metadata settings attributes which act like settings for that Feature Type and control specific pieces of functionality. These are typically attributes whose names are prefixed with an underscore (e.g. _ON_SAVE_ACTIONS).

This list is not comprehensive. The SOARVO knowledgebase contains dedicated pages for some functionality (for example, auto-recording linear/area nodes) which document the required metadata settings attributes for those workflows. The table below is only for metadata settings that don't require their own dedicated page.

Feature Created Default Codes

These default codes are calculated and set only when a feature is created.

Feature Saved Default Codes

These default codes are calculated and set only when a feature is saved.

Feature Opened Default Codes

These default codes are calculated and set when a feature is opened (so created/edited).

Geometry Based Default Codes

These default codes are calculated and set when the geometry of a feature is changed.

Calculation Based Default Codes

These default codes are for calculation based fields, They run when they are autonavigated over and when the form is opened.

Modifier Default Codes

These default codes modify properties of an attribute (mandatory, hidden, read only etc) depending on a condition.

Sketch Attribute Default Codes

These default codes are used specifically with sketch attributes (FileUpload attributes with a Drawing attribute setting) to load images into the sketch canvas. The PNG images must be uploaded to a location with the format like 'filename.png.system'. But can then be accessed across a project.

!CALC Expressions

!CALC uses Excel-like expressions to generate values from attributes and functions. You can reference attributes by name, and make expressions reactive by prefixing with a dollar sign (e.g. $field1). It's impossible to list all the different things you can do with !CALC expressions, if a !CALC expression fails to evaluate then an error should be present in the logs. Here are some examples of different things you can do with !CALC expressions:

Examples

• !CALC $Field1 + 10
• !CALC ($length * $width) / 2
• !CALC $status == 'active' ? 'Yes' : 'No'

Utility Functions

Utility functions are helpers you can call inside expressions to transform or combine values.

• join(parts, separator) — Join a list into a string.
  • Example: !CALC join([Field1, Field2], '-')
• number(value) — Parse a value to a number (returns 0 on failure).
  • Example: !CALC number($Field1) + 10
• numberOrNull(value) — Parse a value to a number (returns null on failure).
  • Example: !CALC numberOrNull($Field2)

Expressions in Modifier Default Codes

Modifier default codes use the same expression parser, so you can write boolean expressions there too.

Examples:

• !MODIFIER-SHOWWHEN $status == 'active'
• !MODIFIER-HIDEWHEN number($riskScore) > 10

The post Mobile App Data Entry Shortcuts appeared first on Soarvo.

App Version:
0.0.121+

Secondary features are automatically created and linked to a parent feature. They are recreated when the parent is edited and are deleted if the parent is also deleted.

You can create a secondary ‘GridLines’ linear feature which is a secondary feature with x amount of columns and rows, variable spacing, and different baselines. Optionally, you can also create ‘GridLineIntersections’ secondary point features, at the intersection of the GridLines secondary feature geometry – and ‘GridLineCentres’ secondary point features at the centre of the squares of the GridLines linear feature, which is used for annotating the squares.

‘GridLineCentres’ and ‘GridLineIntersections’ are optional, if you do not create these feature types then they won’t be generated – but the ‘GridLines’ secondary feature will and must be created.

Grid Generation – Parent Secondary Feature Type Setup

You must setup a parent feature type for all of the GridLines based secondary features. The parent should have a linear geometry type. This parent linear feature type must have the following setup on it:

A short text attribute of name ‘_secondary_feature’ with a default value of ‘GridLines’ like below:

A numerical attribute named ‘Rows’, a numerical attribute named ‘Cols’, and a numerical attribute named ‘Spacing’. It also needs a radio group attribute with the options ‘Centred’, ‘Left’, ‘Base’ for the baseline, as shown below:

At the end, your parent secondary feature, which when a feature of this type is created will create all of the GridLines based features, should look like below:

Grid Generation – ‘GridLines’ Feature Type Setup

You must setup a linear feature type of the name ‘GridLines’ in a given project. That should be all the setup that is required, you can optionally style this feature type how you wish.

Grid Generation – ‘GridLinesIntersections’ Feature Type Setup (OPTIONAL)

You must setup a point feature type of the name ‘GridLineIntersections’ in a given project. That should be all the setup that is required, you can optionally style this feature type how you wish.

Grid Generation ‘GridLinesCentres’ Feature Type Setup (OPTIONAL)

You must setup a point feature type of the name ‘GridLinesCentres’ in a given project. You then must create a short text attribute of the name ‘SQUARE_LABEL’, so your feature type should look like below:

If you want labels to appear (e.g ‘A1, A2, A3’ etc) you need to enable annotation for the ‘GridLineCentres’ feature type. You can do this by clicking the top right ‘feature type style’ button and then the bottom left ‘feature type annotation’ button to bring up the feature type annotation setup. As shown below:

Then, ensure the ‘Attribute’ textbox is filled with ‘SQUARE_LABEL’. The other options you can choose whatever you wish. A good starting point is shown below:

If you want to make the point icons themselves smaller, you can do this clicking the ‘feature type icon ‘ button – which is highlighted below:

Ensure that ‘Simplified icon’ is ticked, and then choose the largest or smallest circle styling option, like below:

Grid Generation – Mobile Demo

With all of the above setup done you should now be able to follow along with the video below, which shows the grid generation secondary feature workflow on the Soarvo Mobile app. In the video, the ‘GridLinesOrigin’ is the parent feature type which all of the grid based secondary features and linked to a feature of that type. So when you delete the ‘GridLinesOrigin’ feature then the grid based secondary features are deleted also.

The post Secondary Features – Grid Generation appeared first on Soarvo.

App Version:
0.0.126+

Secondary features are automatically created and linked to a parent feature. They are recreated when the parent is edited and are deleted if the parent is also deleted.

You can create n number of parallel line linear secondary features at an x offset from a parent linear feature. This is useful for automatically recording a set of cables that run parallel to each other.

Parallel Lines Generation – Parent Secondary Feature Type Setup

You must setup a parent feature type for all of the parallel line based secondary features. The parent should have a linear geometry type. This parent linear feature type must have the following setup on it:

A short text attribute of name ‘_secondary_feature’ with a default value of ‘ParallelLines’ like below:

A short text attribute of name ‘_parallel_line_feature_type_name’ with a default value that is the name of the feature type of the parallel lines you want to create. In the below screenshot the feature type of the parallel lines is ‘ParallelLine’:

A numerical attribute of name ‘ParallelLineSpacing’ and a numerical attribute of name ‘NumOfParallelLines’.

A radio attribute of name ‘CapturedLineSide’ with values ‘Left’, ‘Right, and ‘Middle’. Like below:

For the ‘CapturedLineSide’ the values are summarised below.

‘Left’ means the parent feature is the left most linear geometry, so all child parallel lines generated are on the right of the parents geometry. As shown in the below screenshot:

‘Right’ means the parent feature is the right most linear geometry, so all child parallel lines are on the left of the parents geometry. As shown in the below screenshot:

Middle means the parent feature is the middle geometry, and will alternate the behaviour from ‘Left’ to ‘Right’ to ‘Left’ to ‘Right’ etc. As shown in the below screen:

At the end, your parent secondary feature, which when a feature of this type is created will create the parallel line features, should look like below:

The ‘CustomText’ attribute is not required for the feature type setup – it is used later on in this documentation to show how you can copy over attribute values from the parent to its child parallel lines.

Parallel Lines Generation – Child Parallel Lines Feature Type Setup

The feature type name of the child parallel line feature type needs to be the same value as specified in the parents ‘_parallel_line_feature_type_name’ attribute and must be linear geometry.

You can automatically have the parallel line features copy over values from its parent. If an attribute in the parallel lines child feature type has the same name as an attribute in the parent, then the value is copied to the child. So for example, if you wanted to copy the ‘CustomText’ short text value from the parent to the child parallel line features then you would create a short text attribute with the name ‘CustomText’ in the child feature type, like below:

Parallel Lines – Mobile Demo

With all of the above setup done you should now be able to follow along with the video below, which shows the parallel line secondary feature workflow on the Soarvo Mobile app. In the video, the ‘ParallelLinesParent’ is the parent feature type which has secondary features with parallel linear geometry. So when you delete the ‘ParallelLinesParent’ feature then the ‘ParallelLine’ secondary features are deleted also.

The post Secondary Features – Parallel Lines appeared first on Soarvo.

App Version:
0.0.130+

Secondary features are automatically created and linked to a parent feature. They are recreated when the parent is edited and are deleted if the parent is also deleted.

You can create tree root protection zones and crown spreads as secondary features from a parent tree point, or hedge edge extents and centrelines from a parent hedge line. This is useful for automatically recording arboricultural survey data including the Root Protection Radius (RPR) (or alternatively known as Root Protection Area (RPA)) calculated from stem diameters, crown spreads (even or uneven), and hedge extents with configurable widths and surveyed sides.

Tree Inspection – Parent Secondary Feature Type Setup

You must setup a parent feature type for all tree inspection based secondary features. The parent should have a point geometry type for individual trees. This parent point feature type must have the following setup:

Required Attributes

1. Secondary Feature Identifier
   A short text attribute of name _secondary_feature with a default value of TreeInspection. Note, in the screenshots the default values are prefixed with !MODIFIER-HIDE;. This tells the app to hide this attribute from the UI and the semi-colon is a separator to chain ‘default values’ together:

2. Root Feature Type Name
   A short text attribute of name _root_feature_type_name with a modifier default code of !MODIFIER-HIDE;TreeInspTestRoot (replace TreeInspTestRoot with your actual root feature type name):

3. Crown Feature Type Name
   A short text attribute of name _crown_feature_type_name with a modifier default code of !MODIFIER-HIDE;TreeInspTestCrown (replace TreeInspTestCrown with your actual crown feature type name):

4. Stem Count
   A numerical attribute named StemCnt (no decimals allowed) to record the number of tree stems:

5. Stem Diameters
   Numerical attributes (with decimals allowed) for each stem diameter in millimeters:
   
   StemDia1 with modifier code:
   !MODIFIER-SHOWWHEN $StemCnt != null && $StemCnt>0
   
   StemDia2 with modifier code:
   !MODIFIER-SHOWWHEN $StemCnt != null && $StemCnt>1
   
   StemDia3 with modifier code:
   !MODIFIER-SHOWWHEN $StemCnt != null && $StemCnt>2
   
   StemDia4 with modifier code:
   !MODIFIER-SHOWWHEN $StemCnt != null && $StemCnt>3
   
   StemDia5 with modifier code:
   !MODIFIER-SHOWWHEN $StemCnt != null && $StemCnt>4
   
   StemDia6 with modifier code:
   !MODIFIER-SHOWWHEN $StemCnt != null && $StemCnt>5
   
   These attributes will only show when the stem count is greater than the corresponding number. The screenshot below shows the ‘SteamDia1’ attribute.

6. Root Protection Radius (RPR)
   A numerical attribute (with decimals allowed) named RootRadius with a default value of !CALCRPR:

The !CALCRPR calculation automatically computes the Root Protection Radius, in metres, based on the number of stems and their diameters:

For single stem trees: Uses StemDia1 * 12
For 2-5 stems: Calculates based on the square root of the sum of squared diameters * 12
For 6+ stems: Uses StemDia1 and StemCnt to calculate an average
The result is capped at a maximum of 15 metres

7. Crown Spread Type
   A radio group attribute named CrownSprd with two options:
   
   even
   uneven

8. Uneven Spread Measurements
   Numerical attributes (with decimals allowed) for directional crown spread measurements in metres, each with the modifier code !MODIFIER-SHOWWHEN $CrownSprd==’uneven’. The attribute names for these are:
   
   NorthSprd
   EastSprd
   SouthSprd
   WestSprd

These attributes will only show when “uneven” is selected for CrownSprd. The screenshot below shows the ‘NorthSprd’ attribute:

9. Even Spread Measurement
   A numerical attribute (with decimals allowed) named EvenSprd with the modifier code !MODIFIER-SHOWWHEN $CrownSprd==’even’

This attribute will only show when “even” is selected for CrownSprd.

At the end, your parent tree inspection feature type should look like below:

Tree Inspection – Child Root Feature Type Setup

You must setup a linear feature type with the name specified in your parent feature type’s _root_feature_type_name attribute (e.g., TreeInspTestRoot).

The root feature represents the root protection radius of the tree and is automatically generated as a circular line around the tree point based on the calculated RootRadius value.

1. Create a linear (LineString) feature type with your chosen name
2. Optionally add any attributes that you want to copy from the parent feature (e.g. species information)
3. Style the feature type as desired to represent the root protection zone

If the parent feature has matching attribute names, their values will be automatically copied to the root feature when it’s generated.

Tree Inspection – Child Crown Feature Type Setup

You must setup an area (polygon) feature type with the name specified in your parent feature type’s _crown_feature_type_name attribute (e.g., TreeInspTestCrown).

The crown feature represents the tree’s canopy spread and is automatically generated as either:

• A circular polygon (for even spread)
• An elliptical polygon (for uneven spread with directional measurements)

1. Create a polygon (Area) feature type with your chosen name
2. Optionally add any attributes that you want to copy from the parent feature (e.g species information, etc)
3. Style the feature type as desired to represent the tree canopy

If the parent feature has matching attribute names, their values will be automatically copied to the crown feature when it’s generated.

Tree Inspection – Parent Hedge Feature Type Setup

You must setup a parent feature type for hedge inspection based secondary features. The parent should have a linear geometry type for hedge lines. This parent linear feature type must have the following setup:

Required Attributes

1. Secondary Feature Identifier
   A short text attribute of name _secondary_feature with a default value of ‘!MODIFIER-HIDE;TreeInspection’:

2. Hedge Edge Feature Type Name
   A short text attribute of name _hedge_edge_feature_type_name with a modifier default code of !MODIFIER-HIDE;TreeInspTestHedgeEdge (replace with your actual hedge edge feature type name):

3. Hedge Centre Feature Type Name
   A short text attribute of name _hedge_centre_feature_type_name with a modifier default code of !MODIFIER-HIDE;TreeInspTestHedgeCentre (replace with your actual hedge centre feature type name):

4. Hedge Width
   A numerical attribute (with decimals allowed) named width to record the hedge width in metres:

5. Surveyed Side
   A radio group attribute named Surveyed with three options:|
   
   left
   right
   centre
   
   This determines which side of the drawn line represents the surveyed edge of the hedge.

At the end, your parent hedge inspection feature type should look like below:

Tree Inspection – Child Hedge Centre Feature Type Setup

You must setup a linear feature type with the name specified in your parent hedge feature type’s _hedge_centre_feature_type_name attribute (e.g., TreeInspTestHedgeCentre).

The hedge centre feature represents the centrelines of the hedge and is automatically generated based on the surveyed side and width:

For “left” surveyed: offset to the right by half the width
For “right” surveyed: offset to the left by half the width
For “centre” surveyed: uses the drawn line as-is

1. Create a linear (LineString) feature type with your chosen name
2. Optionally add any attributes that you want to copy from the parent feature (e.g species information)
3. Style the feature type as desired to represent the hedge centerline

If the parent feature has matching attribute names, their values will be automatically copied to the hedge centre feature when it’s generated.

Tree Inspection – Child Hedge Edge Feature Type Setup

You must setup an area (polygon) feature type with the name specified in your parent hedge feature type’s _hedge_edge_feature_type_name attribute (e.g., TreeInspTestHedgeEdge).

The hedge edge feature represents the full extent of the hedge and is automatically generated as a polygon buffer based on the surveyed side and width.

1. Create a polygon (Area) feature type with your chosen name
2. Optionally add any attributes that you want to copy from the parent feature (e.g. species information)
3. Style the feature type as desired to represent the hedge extent

If the parent feature has matching attribute names, their values will be automatically copied to the hedge edge feature when it’s generated.

Tree Inspection – Mobile Demo

With all of the above setup done you should now be able to create tree and hedge inspection features on the Soarvo Mobile app:

Tree Inspection Workflow

1. Create a new feature using your tree inspection parent feature type
2. Record the position of the tree on the map
3. Fill in the stem count and stem diameters
4. The Root Protection Radius will be automatically calculated
5. Select crown spread type (even or uneven) and enter the spread measurements
6. Save the feature
7. The root (circular line) and crown features will be automatically generated

Hedge Inspection Workflow

1. Create a new feature using your hedge inspection parent feature type
2. Record the linear geometry of the hedge on the map (from the surveyed side)
3. Fill in the hedge width
4. Select which side was surveyed (left, right, or centre)
5. Save the feature
6. The hedge edge and hedge centre features will be automatically generated

When you delete a parent tree or hedge inspection feature, all of its associated secondary features (root, crown, or hedge edge/centre) are automatically deleted as well.

The post Secondary Features – Tree Inspections appeared first on Soarvo.

App Version:
0.0.134+

There are three elements of alignment and chainage that are implemented in the Soarvo mobile application:

• UI widget at the bottom of the map that displays the chainage and offset from your current position to the linear feature selected as the ‘alignment’. This is referred to as the ‘maps chainage and offset display’ below
• Styling of the linear feature marked as the ‘alignment’ – it will have chainage markers along the length of the feature
• Chainage and offset based calculations that are activated by specific codes in the default value field of an attribute

For all three elements you must first select a linear feature, tap the three dots context menu on its sheet, and select ‘Use as Alignment’, like in the video below. You can also see how selecting a linear feature as the alignment enabled the the first two elements mentioned above.

If you want the units of the maps chainage and offset display, chainage markers, and chainage and offset based calculations to be in the ‘miles and yards’ format, e.g 1M 13Y, then you need to add a ‘Units’ attribute to the feature type of the linear feature selected as the alignment. Then set the value of this attribute to ‘MilesAndYards’. You can see in the image below this is setup as a radio group attribute. Metres is the default unit for all chainage and offset displays and calculations.

If the linear feature selected as alignment does not start at a chainage value of 0, then you can also specify this by creating a ‘StartChn’ numeric attribute to the feature type of the linear feature selected as the alignment. All chainage and offset calculations, including the UI displays, will then take this into account.

If you want to stop using the linear feature as the alignment then tap the feature, tap the three dots context menu button, then tap ‘Remove as Alignment’.

Chainage and Offset Calculations

The various default value codes to calculate chainages and offsets are summarized below.

The below default values are executed whenever the geometry of the feature is updated.

The below default values are executed whenever the feature is opened (so created/edited).

The post Alignment and Chainage appeared first on Soarvo.

App Version:
0.0.141+

By adding a ‘_AUTO_ADD_NODES’ numeric attribute to a feature type with linear or area geometry you can enable the ‘Auto Add Nodes’ functionality on the Soarvo Mobile App. The image belows shows an example. The value of the attribute is ‘1.23’ which is the minimum distance between the last node of the geometry and your current distance before a new node (at your current position) is added – in metres. If the feature has no nodes then your current position is added as the first node.

The full default value is ‘!MODIFIER-HIDE;1.23’ where the first part, before the semi-colon, tells the app to hide this attribute in the Soarvo Mobile App form UI.

Once the linear or area feature is setup like above, you should be able to follow along with the video below and use the same ‘start / stop’ button to enable / disable auto adding nodes to the current features geometry.

The post Auto Add Linear/Area Nodes appeared first on Soarvo.