Gemini TrenchWorks¶

More accurate line definition (CL) for trench¶

As is known, the SFI model requires a line definition (CL), and for trenches this is normally generated based on a pipe. The result is a centerline with break points without roundings, which can lead to crossing cross sections and problems with the 3D model of the trench.

By smoothing the line definition, these challenges can be reduced. The new option Max. CL deviation ensures that the distance between the pipe and the line definition stays within specified tolerances. In previous versions, the deviation could in some cases become so large that it had a negative impact on the construction of the trench model.

Data type no. in list¶

Now also shows the data types' numbers in addition to names in the lists. This is partly because we sometimes need to know these, see point below.

Support for multiple parallel lines with the same code¶

In the function Create line definition data from application layer (when we use standard XREF table), it is S_FCODE that determines which data type the objects get.

Previously, all parallel lines with the same S_FCODE got the same data type. This was problematic because the centerline must be treated as a separate line – and therefore must have its own data type.

In the new version, we can now assign alternative data types when multiple parallel lines have the same S_FCODE.

This happens automatically for standard data types such as (but these can also be overridden in XREF tables):

101, 106: Stormwater
102, 107: Sewage
103, 108: Water
104, 109: Pump line

For others, and especially user-defined, data types, we must update the XREF table ourselves by adding S_FCODE_SIDE.

Example

All lines have the same S_FCODE=TEST in the application layer, and one is selected as centerline.

We create user-defined data type 10001 (for centerline).

Data type 10002 (for parallel lines with the same code as centerline).

We must then set up the XREF rule for transfer to line definition data in SFI model.