See section Autoconnect route tools for a step-by-step description of how to use the tools.
Background
The dpCom data model requires that nodes and routes are connected. While this connection is established automatically when routes are created within the user interface, it must be manually addressed for imported GIS or CAD data.
Input data can originate from multiple sources, and even when sourced from the same GIS or CAD tool, the representation of objects can vary based on the design patterns used. This variability necessitates flexibility in the tools used to create these connections. The tools in this group function like a toolbox, providing various utilities to handle different design patterns and their specific requirements. Each design pattern may require different tools and tool sequences to achieve the desired results.
Another requirement in dpCom is that a cable must be a child of one or more route objects, either directly or via pipes, ducts, or multiducts. This relationship is particularly relevant for customer drops, especially overhead (OH) customer drops. In some cases, the source data may not model this relationship, with drop cable lines being the only lines entering customer nodes.
A practical solution in dpCom is to import the layer with customer drops twice—first as cables and then as routes. This approach can create issues that the tools in Autoconnect route tools are designed to manage.
Some design patterns handled by the tools
|
The tools are designed to handle various design patterns, ensuring that imported data meets the connectivity requirements of the dpCom model. Please contact Digpro for assistance with specific configurations or if you need help addressing particular design patterns. |
Design pattern |
Tools to use |
|---|---|
Route lines ending (graphically) in a node in each end. |
1.Connect routes to nodes. |
Route lines with one or both end points having no node or other route at that point. |
1.Place nodes at vacant route ends.This will place an event node at the end(s). 2.Connect routes to nodes. 3.If applicable, Change type of node, or if the desired node is another subtype of event node, Change subtype of event node. |
Two route lines of the same characteristics with end points in a shared single point but without any node at that point. |
1.Decide between the following: oIf the lines are intended to be a multi-line object use Merge routes. oIf the lines are intended to be separate route objects, use Place nodes at vacant route ends. 2.Connect routes to nodes. |
Two route lines of different characteristics with end points in a shared single point but without any node at that point. |
1.Decide between the following: oIf the lines are intended to be a multi-line object the route objects must first be harmonized in terms of the subtype of the routes. Then use Merge routes. oIf the lines are intended to be separate route objects, use Place nodes at vacant route ends. 2.Connect routes to nodes. |
Three or more route lines with end points in a shared single point but without any node at that point. |
1.Place nodes at vacant route ends. This will place an event node at the shared point. 2.Connect routes to nodes. 3.If applicable, Change type of node, or if the desired node is another subtype of event node, Change subtype of event node. |
Two route lines crossing each other (forming an X) without any node at the crossing point. |
If this is intentional, for example, an OH (overhead) route crossing a UG (underground) route, do nothing. Otherwise: 1.Split routes and insert nodes. 2.Connect routes to nodes. |
Two route lines crossing each other (forming an X) with a node at the crossing point. |
1.Split route with node. 2.Connect routes to nodes. |
Two route lines, one ending in the middle of the other line (forming a T), without any node at the crossing point. |
1.Split routes and insert nodes. 2.Examine the T-crossing to check for possible short route if the T was not exact enough. This can cause a short route object to be created and that should be deleted. 3.Connect routes to nodes. |
Two route lines, one ending in the middle of the other line (forming a T), with a node at the crossing point |
1.Split route with node, possibly with just the passing route as input. 2.Connect routes to nodes. |
|
The tools listed below do not make any connection between route and node, they are just preparing the route and node data: •Split routes and insert nodes (interactive) •Place nodes at vacant route ends (interactive) •Split route with node (interactive) •Split routes and insert nodes •Place nodes at vacant route ends •Split route with node To connect, use the tool Connect routes to node. |
Input
With the exception of the tool Connect route to node based on matching field contents, all Autoconnect route tools require one or more route objects as input. While some tools interact with existing node objects, these nodes are identified automatically and do not need to be selected manually.
If the imported data includes a mix of route types, the Select with dialog 
tool can be used to focus on one route type at a time. For example, it is often beneficial to separate OH (overhead) routes from UG (underground) routes to prevent them from being split when they cross each other.
|
It is recommended to limit the number of routes input to the tools. Handling volumes over 100-200 routes can slow down the tools, as the underlying algorithms perform comparative analysis of the routes. |
Apply autoconnect route tools - interactive
The interactive variants of the tools provide a dialog interface that allows you to accept, skip, or abort the applicable action. This functionality is particularly useful in two scenarios:
•When first using the tool, the interactive variant helps you understand how it operates on the selected data. If the tool behaves as expected, subsequent runs can be done non-interactively.
•For input data that requires manual decisions, the interactive variant is essential.
1.Select the routes in the map where you want to use the function.
2.In the menu bar, select Edit > Autoconnect route tools (m) > [desired Autoconnect routes tool (interactive)]. Depending on what routes you have selected, a dialog opens where you can press:
oOK to accept.
oSkip to continue without changes.
oAbort to end the function.
|
For submenus Split routes and insert nodes (interactive) or Place nodes at vacant route ends (interactive): 1.In the drop-down menu in the dialog, select Event node or Joint manhole. |
|
For each action, the tool zooms in on the relevant point as follows: •Place nodes at vacant route ends (interactive) - The current route end is marked with a red cross on the map. •Merge routes (interactive) - The two routes being merged are highlighted. •Split routes and insert nodes (interactive) - The routes are highlighted, and the crossing point is marked with a red X. •Connect routes to nodes (interactive) - The route and the node being connected are highlighted. •Remove duplicate routes (interactive) - The routes are highlighted, since they are duplicates, they appear as a single highlighted line. |
Autoconnect route tools - Description
Customization of the Tools
Most of the tools interact with various types of nodes, either by creating nodes or analyzing relationships with existing nodes. By default, the created nodes are event nodes, and the interaction includes all types of nodes (manholes, cabinets, distribution nodes, customer nodes, poles, and event nodes).
|
This behavior can be modified in two ways: •Adjusting the existing tools to exclude certain types of nodes. •Adding a more specialized version of a tool. For assistance with customization, please contact Digpro. |
Submenu |
Extra info |
||
|---|---|---|---|
Autoconnect routes (interactive) |
Description: This run the tools Merge routes, Split routes and insert nodes, Place nodes at vacant route ends and Connect routes to node in sequence for the routes you select. Use case: When the imported data is appropriately structured, using the sequence of operations in this tool can be an effective method for making connections, potentially saving time.
|
||
Autoconnect routes |
|||
Merge routes (interactive) |
Description: Selected routes that have their end-point next to each other are merged into one single route. Use case: Certain settings in some GIS or CAD tools may create multiple individual segments for a line, rather than a multiline. When these segments are imported into dpCom as routes, each segment will be treated as a separate route object. |
||
Merge routes |
|||
Split routes and insert nodes (interactive) |
Description: Selected routes that intersect, meaning, form an X or a T will split at the crossning points and a node will be placed at that point. Use Case: When lines are manually drawn in a GIS or CAD tool, intersections or crossings forming an X or T may appear visually acceptable. However, when imported into dpCom, these routes will intersect or cross.
|
||
Split routes and insert nodes |
|||
Place nodes at vacant route ends (interactive) |
Description: For selected routes that do not have a nearby node at their endpoints, a node is created at each endpoint. Use Case: Lines may end without a node object at their endpoints. Lines may be drawn to form an X or T, but no node is placed at the crossing points.
|
||
Place nodes at vacant route ends |
|||
Connect routes to node (interactive) |
Description: For selected routes with nearby nodes at their endpoints that are not already connected, the routes will be connected to the nodes closest to their endpoints. Use Case: If the imported data does not include table-oriented data listing pairs of routes and nodes to document their connections, the connection of routes and nodes will be done in dpCom based on geographical proximity.
|
||
Connect routes to nodes |
|||
Remove duplicate routes (interactive) |
Description: For selected routes with identical layouts, one of the duplicate routes will be deleted. Use Case: In some cases, lines representing cables may not be suitable for creating route objects. A workaround is to import the cables twice into dpCom, first creating the cables and then creating routes. However, this may result in duplicate routes if there are multiple cable lines in the same location.
|
||
Remove duplicate routes |
|||
Split route with node (interactive) |
Description: For selected routes that pass over a node, the route is split at the node's location. Use Case: In the scenario described under Remove duplicate routes above, some cable lines may pass over nodes. For example, overhead (OH) cables may pass over one or more poles along their path. While this is acceptable for cable objects, when the same cable lines are imported as routes, they need to be split at the nodes they pass over.
|
||
Split route with node |
|||
Connect route to node based on matching field contents |
Description: Unlike the other tools in the Autoconnect route tools, this tool operates on a selection of both routes and nodes. The Select with dialog For the combination of routes and nodes in the selection, the routes that have a matching value to a customer node will be connected to the node. Use case: Some imported designs may have customer nodes positioned according to official registers, while the connecting cables, either stand-alone or with a route, are drawn to the nearest wall of the building. If the cable is stand-alone, it must be imported twice, both as a cable and as a route. The gap between the customer node and the route ending at the building makes it difficult for the Connect routes to nodes tool to make the necessary connections. However, if an attribute of the route, directly or inherited from the cable, matches an attribute of the customer node, the connection can be made based on these matching values.
|