Redlining

Areas planned in NET Design and realised with the help of NET Build can be used with the Redlining module for efficient documentation.

To do this, the redlining module must be activated in the infrastructure administrator.

If the redlining module has been selected and saved in the Explorer Manager, it is visible in the industry model explorer:

Industry Model Explorer	Object classes of the module

 

Synchronisation of the field reports

Synchronisation of the field reports is started in the Industry Model Explorer by right-clicking on the Industry Model and selecting the menu item "NET Build Field reports sync":

The NET Build login window opens:

The dialogue with the settings for project and measurement data opens. This is the connection to the NET Build instance.

The "Operators" (network operators) available in the list can be selected. There are "programmes" (projects) that can be selected for each available operator.
A programme (project) can be divided into different "segments" (sub-projects). Different "regions" can be managed within these segments. If possible, "Approved" should be selected in the "Status" field. The processing status of all other data/measures is not known.

A filter can be used to restrict the selection of regions. To do this, move the mouse pointer over the filter symbol and enter the relevant letters, numbers or characters in the field that appears. Then open the selection field and the corresponding entries will be displayed.

The date of submission can be selected in the fields "Submitted from", "to".

Click on the "Refresh" button to load the data.

The details of a data record can be opened by double-clicking. Another tab card then opens and the details of the data record are displayed.

If files (e.g. photos) have been loaded with the data, they can be viewed here. However, these are not transferred to NET Engineering.

Click on the "Load all measurements" button to load the measurement data. Another "Load measurements" tab opens.

The status of the work items to be transferred is defined in the "Status of work items" field.

If the NET Build object type, production reports or design elements have been selected, the additional option "Load completed planning objects without work" is displayed below the "Work items status" selection field.

This should be selected if there are design elements without work items in NET Build that are nevertheless required for complete network documentation and therefore need to be transferred to NET Engineering.

Before the data record can be selected for the measurement, it must be created in the corresponding form. The "Redlining Measurement" form is opened with the "Arrow button" in the dialogue and the new data record can be created.

The "Redlining measurement" form can also be opened in the "Redlining" group in the Industry Model Explorer.

The "Redlining measurement" form opened via the "Arrow button" is automatically opened in "Create dataset mode".

Once a new "Redlining measurement" has been created, this data record can be selected in the "Measurement" field.

The "Load all measurements" button is used to download the objects from NET Build and link them to the "Redlining measurement". Once the data transfer is complete, the data is displayed in the graphic.

The polygon shown in black represents the previously created "redlining measurement" and contains the transferred data.

The following illustration shows a detailed representation of lines and survey points.

The forms for the imported objects can be opened via the Industry Model Explorer or by double-clicking. The category, the link to the NET build object and the check status are displayed in each of these forms.

 

Redlining segment form

The check status of the objects is either set manually or adjusted automatically after certain work processes.

The measurements points are displayed with their respective accuracy (from the GPS measurement).

The imported segments may have gaps or overlaps. The errors are corrected semi-automatically. The "NET Redlining" function in the "Redlining Measurement" form supports data transfer to NET Engineering.

 

Data transfer

All measurements that have already been loaded into the project are displayed in the "Documentation data transfer" dialogue. The measurement whose data is to be transferred to NET Engineering can be selected in the sequence of actions.

The general snapping tolerance (m) is entered for synchronising the geometries. Only gaps that lie within this tolerance are closed.

Various validations can be carried out on the next tab. When the validation is mandatory in the Redlining data transfer then the checkbox cannot be deselected.

 

After clicking on "Search for problems", existing errors are listed. These can be searched for via the FID and then corrected.

It should be possible to carry out all validations without errors before the data transfer.

The following validations are available

• Blowing tabel validation: It is checked whether a record exists for all ducts in which a cable with a specific BLOWING_INFO is to run.
• Cable attribution: It is checked whether there is a type and that cables with the same name and the same ParentName have the same position number.
• Ducts routes with missing fittings: It is checked whether there are duct routes without fittings.
• Ducts with invalid start points: It is checked whether for ducts with a set name of a network node the network path of the associated paths leads to the specified network node.
• Ducts with connected geometry: It is checked whether there are identical ducts/duct types that do not have a connected geometry.
• Empty segments: It is checked whether ducts and/or cables are assigned to all segments.
• Fitting attribution: It is checked whether there is a type and an position number and that the connected ducts have a name.
• Not connected segments: It is checked whether there are segments that are not connected to any other segments.
• Not connected to the trail network structures: It is checked whether there are structures that are not connected to at least one segment.
• Objects without geometry:There is a new validation, which checks if there are any objects without geometry.This validation checks the following redlining classes for objects without geometry: terminator, closure, structure, segment, measurement line and measurement point
• Overlapping segments: It is checked whether segments overlap. Overlapping means that the segments have at least 1 non-common point (see identical geometries) and partially overlap.
• Parallel segments: It is checked whether there are parallel segments outside the set snapping tolerance. Segments that run parallel and cannot be combined by the tolerance and have exactly the same content.
• Redlining object classes validation: It is checked whether fittings only connect actually existing ducts and whether there are only segments to which a SOURCE_ID is assigned.
• Segment length less than tolerance: It is checked whether there are segments that have a shorter length than the snapping tolerance.
• Segments of structure with not connected geometry: It is checked whether there are network nodes whose segments do not have a connected geometry.
• Segments with identical geometries: It is checked whether there are geometries that fulfil the following condition: The geometries have at least one common point and no point of one geometry lies outside the other.

Various actions can be carried out during the subsequent transfer. These work according to a step-by-step concept (1).

1a) With "Snap redlining features" the geometries of the redlining paths are corrected within the set snapping tolerance.

The stylization of the blue segments indicates that the associated geometry was automatically corrected. The gaps and overlaps were thus eliminated if they were within the snapping tolerance (in the example: 0.5m). Geometries that lie outside the snapping tolerance are not automatically corrected. These must be reworked manually. The status is automatically adjusted and the stylization is done accordingly.

Gap outside tolerance	manual correction	Adjustment of test status and style

The assignment of the paths can be shown as a label via a view (TC_M_RL_SEGMENT) and the text on the line can be stylised.

1b) The "Link structures" action is used to transfer cabinets and manholes.

There must be no other structure with the same name in the tolerance area.
1c) With the action "Link distribution network" the main routes are taken over. The settings for the status can be retained.

1d) With the action "Link lead in trenches" the house connection segments are taken over and linked with the rest of the network.

Note:
It will be checked whether the segment type already exists. If this is not the case, a new type must be created. The name of the segment type is made up of the surface and construction method of the redlining segment:

• Surface / construction method
• Construction method, if no surface
• Surface, if no construction method

1e+f) The measured closures and terminators (devices) as well as cables (cable network) can also be adopted and linked to the segments/ducts.

1g) The connections of the fibres are taken over. In the process, a connector is assigned to the building unit.

2) With the "Snapping priority" it can be defined whether the correction should be made to the lead-in segment or main trench.

3) With the "Redlining transfer method" the network is completely rebuilt from the redlining data.

4) The status that the objects are to receive must be selected from: "Transfer status". When selecting the "Transfer status", the "Fixed feature status" is automatically ticked. The "Fixed feature status" are always ticked in addition. The "Fixed feature status" are saved as soon as a test run or data transfer is started. If you then close the form and open it again, all "Fixed feature status" with which a test run or data transfer was carried out are ticked.

5) The status of the fixed objects (these may not be moved and serve as a connecting point for the data from the redlining) can also be defined.

6) In the "Precision" field, select whether the location is calibrated, projected, located or unknown.

7) The debug messages provide information during the data transfer. If the function is activated, the error message can be displayed and saved. With a double click on the log entries, one is forwarded to the corresponding problem object.

8) The progress of editing is displayed.

9) The "Save as" dialogue opens and messages can be saved in a CSV file.

10) The selected function is executed without saving changes in the database.

11) With "Start" the objects are taken over.

12) The dialogue is closed.

As a result, the segments are equipped with ducts and have received the measured geometry and the set status.

The topological connections were created in such a way that the resulting network paths are correct.

At the bottom of the dialogue is an area with messages. Each message can be selected by double-clicking on it, and once an object has been saved, the corresponding form opens.

Meaning of the messages:

• black: Info message
• orange: Warning
• red: Data error/error
• grey: Debug message