On the Distribution tab, you specify the rules that apply during the distribution of the calculated points to their target industry models. See also Transferring Coordinates.
You can distribute one new point to multiple feature classes and target industry models.
Each distribution rule distributes the point once, that means that for each industry model and feature class, a separate distribution rule is required. For each field code you can define no, one or more distribution rules.
When you distribute a point, you can either update the coordinates and move the point, or you can update the precision, and keep the location of the existing point.
Field Code settings in the Distribution tab |
Description |
---|---|
FC |
Specifies the field code. |
Tolerance Statement |
Specifies a query that returns the maximum tolerance values for reliable and precise points. The unit for the tolerances is the industry model length unit. See also Reliability Tolerance Statement. |
Rule Name |
Specifies a name for the distribution rule. Enter a name that describes the distribution. |
Industry Model Placeholder |
Specifies a placeholder for the name of the industry model where the point is stored. See Fill Industry Model. |
Feature Class |
Specifies the feature class. |
Keep Identifier |
Specifies whether the identifier of the Survey industry model is stored in the point number attribute of the target feature class TB_POINTNUMBER. Default is Yes. Clear this option, if you do not want to store the Identifier in the point number attribute. For example, if you use other methods of point numbering. |
Update Position |
Specifies whether the position of the point shall be updated. Only for existing and moveable points. Clear this option, if you do not want to update the coordinates of the point. Then only the reliability attributes will be updated. For example, if a point lies on a straight line, or if a dimensioning has been applied. |
Attr.1 Value 1 |
Specifies a feature class attribute and a value to be stored in the database. You can specify up to 10 pairs of attribute/value to be stored. For example, you specify that a point with field code 41 is a manhole (feature class = WW_MANHOLE) with the following properties: Attribute 1 = ID_FUNCTION Value 1 = 2 (Control Manhole) Attribute 2 = ID_OWNERSHIP Value 2 = 3 (Public) Attribute 3 = ID_LAYING_TYPE Value 3 = 4 (Underground). |