Areas planned in NET Design and realised with the help of NET Build can be used with the Redlining module for efficient documentation.
The Redlining module must be activated in the Infrastructure Administrator.
If the Redlining group has been ticked and saved in the Industry Model Explorer, it is visible in the Industry Model Explorer:
|Industry Model Explorer||Object classes of the module|
Synchronisation of the field reports
The synchronisation of the field reports is started in the Industry Model Explorer by right-clicking on the Industry Model and selecting "NET Build Field reports sync":
The dialogue for the NET BUILD registration opens:
The dialogue with the settings for project and survey data opens. This is the connection to the NET Build instance.
The "operators" (network operators) available in the list can be selected.
For each available operator there are "programmes" (projects) that can be selected.
A programme (project) can be divided into different "segments" (sub-projects). Within these segments, different "regions" can be managed.
If possible, "approved" should be selected in the "Status" field. For all other data/measurements it is not known in which processing status they are.
The refresh button loads the data.
Double-click on one of the loaded data sets to open it.
The details of the record are displayed.
If files (e.g. photos) were loaded with the data, they can be viewed here. However, these are not transferred to NET Engineering.
With the button "load all surveys" the data of the survey are loaded.
The status of the work elements can be defined.
Before the record for the survey can be selected, it must be created in the corresponding form. The form "Redlining Measurement" is opened with the "Arrow Button" in the dialogue box
or in the "Redlining" group in the Industry Model Explorer.
The record can then be selected.
The button "Load all measurements" downloads the objects from NET Build and links them to the measurement.
This data is displayed in the graphic.
The black outline is the polygon for measurement.
Detailed representation of lines and points
Forms can be opened for the imported objects. The category, the link to the NET Build object and the test status are displayed in these forms.
The checked state of the objects can be set manually or is automatically adjusted according to certain workflows.
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 function "NET Redlining" in the form "Redlining Measurement" supports the data transfer into NET Engineering.
All measurements that have already been loaded into the project are displayed. The measurement can be selected.
The general snapping tolerance applies to the alignment of the geometries. Only gaps that lie within this tolerance are closed.
Different validations can be carried out.
After starting with "Scan for problems", existing errors are displayed and can be searched for and corrected via the FID.
Before data transfer, all validations should be possible without errors.
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 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.
- 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 following transmission. These work according to a 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 occupancy of the paths can be shown as a label via a view (TC_M_RL_SEGMENT) and the text on the line can be stylized.
1b) With the action "Link structures" cabinets and manholes are transferred.
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.
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) 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.
7) The progress of editing is displayed.
8) The "Save as" dialogue opens and messages can be saved in a CSV file.
9) The selected function is executed without saving changes in the database.
10) With "Start" the objects are taken over.
11) 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 links have been created so that the resulting network paths are correct.
In the lower part of the window there is an area with messages. Each message can be selected by double-clicking and if an object has been stored, the corresponding form opens:
Meaning of the messages:
- black: Info message
- orange: Warning
- red: Data error/error
- grey: Debug message