A distribution network overhead line branch line model distinguishing and generating method

Abstract

This invention discloses a method for identifying and generating branch line models of overhead distribution lines, belonging to the field of power system distribution network technology. This method addresses problems in existing technologies such as insufficient integration of ledger data, reliance on manual topology establishment, inconsistent branch coding, and weak support for automated modeling. It involves uploading on-site photos and marking branch points and attributes through a manual annotation process. Based on annotation rules, hierarchical branch codes are generated, constructing a tree-like topology structure. After conflict detection, a structured coding table is formed, driving parametric modeling tools to automatically generate 3D models of branch lines. This standardized process achieves structured association of ledger data, eliminating coding ambiguity and topology inconsistencies. It is adaptable to various scenarios, including urban areas, mountainous regions, and multi-level branches, providing a unified data foundation for the digital transformation of distribution networks, supporting intelligent operation and maintenance and cross-platform data integration, and promoting the intelligent upgrade of distribution network management.

Description

Technical Field

[0001] This invention relates to the field of power system distribution network technology, specifically to a method for identifying and generating branch line models of overhead distribution lines. Background Technology

[0002] As a crucial component of the power system, the accuracy and integrity of the distribution network's overhead lines directly impact power supply reliability, operation and maintenance efficiency, and the scientific nature of planning. With the accelerating digitalization of distribution networks, constructing accurate branch line models has become fundamental for achieving intelligent operation and maintenance, rapid fault location, and digital twins.

[0003] In existing technologies, the identification and modeling of branch lines of overhead distribution networks mainly rely on manual operation, which has the following significant problems:

[0004] 1. Insufficient integration of ledger data: The line ledger includes span attributes (such as span length and conductor type) and tower attributes (such as number and coordinates), but the two lack a structured relationship. Manual processing requires repeated cross-checking, resulting in low efficiency and easy errors in branch point identification.

[0005] 2. Topology creation relies on manual labor: Traditional methods require manual drawing of topology diagrams and labeling of branch relationships one by one. For routes with multiple branches and complex intersections, this is not only time-consuming, but also results in different topology diagrams drawn by different people. Figure 1 Poor consistency makes it difficult to meet the needs of digital management.

[0006] 3. Lack of standardized branch coding: There is a lack of unified branch coding rules, and different regions use different coding methods. For example, some use "main line number + branch line number", while others use "geographical area + number", which makes data sharing difficult and requires a lot of manual conversion for cross-platform model integration.

[0007] 4. Weak support for automated modeling: Existing codes are mostly unstructured descriptions (such as "XX line #5 pole branches off into a branch line"), which cannot be directly parsed by parametric modeling tools, and the connection relationships need to be manually adjusted to generate 3D models.

[0008] Although the industry has attempted related improvements, such as topology generation methods based on GIS data, these rely on complete GIS coordinates and are poorly applicable to older lines that have not been fully surveyed. Automatic branch point identification based on image recognition is limited by shooting conditions, resulting in insufficient accuracy and hindering engineering applications. Therefore, there is an urgent need for a method that combines manual annotation with automatic algorithms to achieve efficient branch line identification and accurate modeling. Summary of the Invention

[0009] The technical problem to be solved by this invention is to provide a method for identifying and generating branch line models of overhead distribution lines, thereby solving the problems of low utilization rate of ledger data, low efficiency of manual topology establishment, inconsistent coding, and insufficient support for automated modeling in the existing identification and generation of branch line models of overhead distribution lines.

[0010] To address the aforementioned technical problems, embodiments of the present invention provide the following technical solution: a method for identifying and generating branch line models of overhead distribution lines, comprising the following steps:

[0011] The manual annotation step involves uploading on-site photos of the overhead power distribution line through the photo annotation interface, selecting branch points in the photos using rectangular or circular selection tools, marking the branch direction using the arrow tool, and associating the tower number to which the branch point belongs.

[0012] The coding generation step, based on the annotation rules and combined with the manually marked branch point positions and tower numbers, generates hierarchical branch codes through a topology mapping algorithm. The hierarchical branch code format is "mainline ID-branch number", where the mainline ID is "1" by default, and the branch numbers are "2", "3"..."N" in the order of discovery, where N is a positive integer.

[0013] The topology mapping step involves establishing child node associations in the order of branch numbers, with the main line as the root node, based on the generated hierarchical branch codes, and automatically constructing a tree-like topology structure for the line. The tree-like topology structure includes the tower number, branch code, and parent node identifier of each node.

[0014] The conflict detection step checks whether there are multiple branch codes at the same branch point or whether there are the same branch codes at different branch points. If a conflict exists, the system displays the conflict location and associated code information and prompts for manual review and adjustment.

[0015] The model generation step involves forming a structured coding table from the conflict-detected tree topology and branch codes, which is then input into a parametric modeling tool to automatically generate a 3D model of the branch lines.

[0016] Preferably, in the manual annotation step, the photo annotation interface supports uploading JPG and PNG format photos, and automatically extracts the shooting time and GPS coordinate information of the photos, associates the branch point markings with GPS coordinates, and allows users to add branch line type, conductor specification and erection date attribute information to the marked branch points.

[0017] Preferably, in the encoding generation step, the specific implementation of the topology mapping algorithm includes:

[0018] Extract the pixel coordinates of manually marked branch points and their corresponding main line identifiers, and convert the pixel coordinates into actual geographic coordinates through perspective transformation;

[0019] Construct an empty adjacency list data structure with the main line as the root node. Each node in the adjacency list contains the tower number, geographical coordinates, branch code, and a list of child nodes.

[0020] Each branch point is added as a child node to its corresponding parent node in the order of branch number. The parent node is the main line or the superior branch line to which the branch point belongs.

[0021] Preferably, the specific process of the conflict detection step is as follows:

[0022] Compare the geographic coordinates of all branch points. If the same geographic coordinate corresponds to multiple branch codes, it is determined to be a conflict of multiple codes for the same point.

[0023] Perform uniqueness checks on all branch codes. If different geographic coordinates correspond to the same branch code, it is determined to be a code duplication conflict.

[0024] After a conflict is triggered, a manual adjustment interface is provided, which supports modifying branch numbers, merging duplicate branch points, and splitting incorrectly associated branch lines. After adjustment, the code generation and topology mapping steps are re-executed.

[0025] Preferably, in the model generation step, the structured coding table includes a branch coding table, a tower attribute table, and a topology table, wherein:

[0026] The branch coding table includes the coding value, line type, starting tower number, ending tower number, and conductor type;

[0027] The pole attribute table includes pole number, pole type, height, material, and geographic coordinates;

[0028] The topology table includes parent node code, child node code, span length, and connection method;

[0029] The line types include main lines and branches; the tower types include straight poles and tension poles; and the connection methods include T-joints and butt joints.

[0030] Preferably, in the adjacency list data structure, the root node corresponds to the main line code "1", the first-level branch nodes are coded as "1-2", "1-3"..."1-N", and the second-level branch nodes are coded as "1-2-1", "1-2-2"..."1-2-N". The level depth of the node is consistent with the level number of the branch code, and N is a positive integer.

[0031] Preferably, the method also includes a data verification step: performing connectivity verification on the generated tree topology, traversing all nodes, and if there are isolated nodes that are not connected to the root node or the parent node, prompting manual inspection of the branch point markers and parent node association information in the labeled data.

[0032] Preferably, the on-site photos are collected by a mobile terminal with positioning function. If the photos do not contain GPS coordinate information, the manual annotation step supports users to manually input the geographical coordinates of the branch points, or to select a tower with known coordinates in the photos as a reference point to calculate the relative coordinates of the branch points.

[0033] Preferably, the parametric modeling tool is Autodesk Civil 3D or Bentley OpenRoads. The model generation step imports the structured coding table into the tool through the API interface, automatically generates the three-dimensional model of the tower, the conductor path and connection relationship, and outputs a model verification report. The report includes information on unconnected towers and line segments with abnormal spans.

[0034] Preferably, in the labeling rules, when a branch line branches into a lower branch from an existing branch line, the numbering rule for the lower branch is to add branch numbers sequentially according to the discovery order based on the upper branch code, forming a multi-level hierarchical code; wherein, when the upper branch code is "main line ID - upper branch number", its first lower branch code is "main line ID - upper branch number - 1", the second is "main line ID - upper branch number - 2", and so on.

[0035] The beneficial effects of the above-described technical solution of the present invention are as follows:

[0036] 1. This invention effectively solves the core pain points in the existing modeling of branch lines of overhead distribution networks, and realizes the structured association between tower and span attributes; it replaces the traditional method of manually drawing topology, and eliminates coding ambiguity and topology inconsistency by using hierarchical coding rules and automatic mapping algorithms, making the identification of branch relationships more accurate and efficient, and providing a unified data foundation for digital modeling.

[0037] 2. This invention possesses strong scene adaptability and practical value. It can meet requirements in high-precision modeling of densely populated urban areas, adaptation to complex mountainous terrain, and complex topologies with multi-level branches through flexible coordinate processing and topology construction methods. Its ability to transform on-site information into structured data frees the modeling process from dependence on specific environments or equipment, adapting to different operation and maintenance scenarios.

[0038] 3. This invention provides key technical support for the digital transformation of power distribution networks. The standardized coding system and structured data format lay the foundation for the collaboration of power distribution network GIS, operation and maintenance platforms, and digital twin systems. Simultaneously, the automated modeling process reduces manual intervention, improves model consistency, and provides reliable data support for intelligent operation and maintenance, planning and design, and other business operations. Attached Figure Description

[0039] Figure 1 This is a flowchart of the distribution network overhead line branch model identification and generation method of the present invention;

[0040] Figure 2 This is a flowchart illustrating the specific implementation of the topology mapping algorithm in the method for identifying and generating branch line models of overhead distribution lines of the present invention.

[0041] Figure 3 This is a flowchart of the conflict detection steps in the method for identifying and generating branch line models of overhead distribution lines of the present invention.

[0042] Figure 4 This is a schematic diagram showing the distribution of conflict detection steps in the method for identifying and generating branch line models of overhead distribution lines of the present invention. Detailed Implementation

[0043] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments. Example 1

[0044] like Figure 1 As shown, this invention proposes a method for identifying and generating branch line models of overhead distribution lines, comprising the following steps:

[0045] S1. Manual labeling step: Upload on-site photos of the overhead distribution line through the photo labeling interface, select the branch points in the photos using the rectangular or circular selection tool, and mark the branch direction using the arrow tool, while associating the tower number to which the branch point belongs.

[0046] S2. Encoding generation step: Based on the annotation rules, combined with the manually marked branch point positions and tower numbers, a hierarchical branch code is generated through a topology mapping algorithm. The hierarchical branch code format is "mainline ID-branch number", where the mainline ID is "1" by default, and the branch number is "2", "3"..."N" in the order of discovery, where N is a positive integer.

[0047] S3. Topology mapping step: Based on the generated hierarchical branch codes, with the main line as the root node, establish child node associations in the order of branch numbers to automatically construct a tree-like topology structure of the line. The tree-like topology structure includes the tower number, branch code, and parent node identifier of each node.

[0048] S4. Conflict detection step: Detect whether there are multiple branch codes at the same branch point or whether there are the same branch codes at different branch points. If a conflict exists, the system displays the conflict location and associated code information and prompts for manual review and adjustment.

[0049] S5. Model generation step: The tree topology and branch codes that have undergone conflict detection are converted into a structured coding table, which is then input into the parametric modeling tool to automatically generate a 3D model of the branch lines.

[0050] In this embodiment, during the manual annotation step, the photo annotation interface supports uploading JPG and PNG format photos, and automatically extracts the photo's shooting time and GPS coordinate information, associates the branch point markings with GPS coordinates, and allows users to add branch line type, conductor specifications, and erection date attribute information to the marked branch points.

[0051] In this embodiment, the specific implementation of the topology mapping algorithm in the encoding generation step S2 includes:

[0052] S21. Extract the pixel coordinates of the manually marked branch points and their corresponding main line identifiers, and convert the pixel coordinates into actual geographic coordinates through perspective transformation. By extracting the pixel coordinates of the manually marked branch points and their corresponding main line identifiers, the core process involves spatial mapping using a perspective transformation algorithm. This transformation relies on two types of parameters:

[0053] Camera intrinsics: extracted from the drone / camera's metadata, or inferred from on-site targets (calibration boards with known coordinates);

[0054] Camera extrinsic parameters: These include the GPS coordinates of the shooting point, flight altitude, pitch / yaw angle, which are recorded in real time by the surveying equipment.

[0055] Based on the above parameters, the system constructs a projection transformation matrix to map pixels to the actual geographic coordinate system. Simultaneously, it uses the coordinates of the mainline towers associated with the mainline identifier, such as the known latitude and longitude of the mainline's start / end points, to perform error verification on the transformation results, ensuring that the spatial correlation between branch points and the mainline remains consistent.

[0056] S22. Construct an empty adjacency list data structure with the main line as the root node. Each node in the adjacency list contains the tower number, geographical coordinates, branch code, and a list of child nodes. Using the main line as the root node, construct an empty adjacency list using a key-value pair data structure. The key is a unique identifier for the node, and the value is a dictionary containing four main fields:

[0057] Tower number: The number of the first tower on the main line, serving as the physical identifier of the root node;

[0058] Geographic coordinates: The verified geographic coordinates of the starting point of the main line, corrected through step S21;

[0059] Branch code: Initialized to "1";

[0060] List of child nodes: An empty array, reserved for future branch mounting interfaces.

[0061] The adjacency list is designed to adapt to the "hierarchical expansion characteristics" of tree topologies: the parent node can quickly query the set of child nodes, providing an efficient data container for subsequent branches, while avoiding the traversal overhead of traditional linked list structures.

[0062] S23. Add each branch point as a child node to its corresponding parent node in order of branch number. The parent node is the main line or its superior branch to which the branch point belongs. Based on the spatial priority of the branch numbers, such as the order along the main line or the priority of manually marked hierarchical levels, attach the branch points as child nodes to their corresponding parent nodes. The core rules are as follows:

[0063] (1) Parent node determination:

[0064] If a branch directly branches off from the main line, the parent node is the main line tower node to which the branch point belongs. This is matched by the main line identifier and spatial location. For example, if the branch point is located on the main line #05 tower, then the parent node is #05.

[0065] If it is a multi-level branch, such as a branch of a branch, the parent node is the last tower node of the upper-level branch. For example, the parent node of a second-level branch is the last tower of the first-level branch.

[0066] (2) Encoding and Topology Maintenance:

[0067] Assign a hierarchical code to the new branch. For example, if the parent node is coded as "1-2", then the child branch is coded as "1-2-1".

[0068] Verify the existence of the parent node to avoid empty associations, and insert the identifier of the current branch point into the list of child nodes of the parent node to ensure "uniqueness of parent-child association", that is, each child node belongs to only one parent node, thus eliminating topological loops from the data structure level.

[0069] In this embodiment, the specific process of the collision detection step S4 is as follows:

[0070] S41. Compare the geographic coordinates of all branch points. If the same geographic coordinate corresponds to multiple branch codes, it is determined to be a conflict of multiple codes for the same point. Spatial fuzzy matching is used instead of absolute coordinate equality comparison: Set a geographic coordinate error threshold, such as latitude and longitude deviation ≤ 0.00001°, corresponding to an actual distance ≤ 1 meter. Using spatial grid indexing technology, quickly filter branch points within the same spatial neighborhood. If a branch point in this neighborhood is associated with two or more different branch codes, it is determined to be a conflict of multiple codes for the same point.

[0071] S42. Perform uniqueness checks on all branch codes. If different geographic coordinates correspond to the same branch code, it is determined to be a code duplication conflict. Construct a code-coordinate mapping hash table: using the branch code as the key (e.g., "1-2"), and storing the set of geographic coordinates corresponding to that code as the value. When traversing the hash table, if the distance between any two coordinates in the coordinate set of a certain code exceeds the conflict threshold, it is determined to be a code duplication conflict.

[0072] S43. After a conflict is triggered, a manual adjustment interface is provided, supporting operations such as modifying branch numbers, merging duplicate branch points, and splitting incorrectly associated branch lines. After adjustment, the coding generation and topology mapping steps are re-executed. After a conflict is triggered, the system presents the conflict with a "visual list + map highlighting": the list layer displays the conflict type (multiple codes for the same point / duplicate codes), the coordinates of the conflict point, the associated codes, and the tower thumbnail; the map layer highlights the conflict point and flashes dynamically, and the associated photo pop-up window assists in positioning.

[0073] Figure 4 It includes three types of line towers and their corresponding branch numbers: Main line towers: #1 to #5, all with branch numbers "1", conforming to the default coding rules of the main line; Branch line 1 towers: #1 and #2, both with branch numbers "2", indicating the first branch branching off from the main line; Branch line 2 towers: #1 and #2, both with branch numbers "3", indicating the second branch branching off from the main line.

[0074] In this embodiment, in the model generation step S5, the structured coding table includes a branch coding table, a tower attribute table, and a topology table, wherein:

[0075] The branch coding table includes the coding value, line type, starting tower number, ending tower number, and conductor type;

[0076] The pole attribute table includes pole number, pole type, height, material, and geographic coordinates;

[0077] The topology table includes parent node code, child node code, span length, and connection method;

[0078] The line types include main lines and branches; the tower types include straight poles and tension poles; and the connection methods include T-joints and butt joints.

[0079] In this embodiment, in the adjacency list data structure, the root node corresponds to the main line code "1", the first-level branch nodes are coded as "1-2", "1-3"..."1-N", and the second-level branch nodes are coded as "1-2-1", "1-2-2"..."1-2-N". The level depth of the node is consistent with the level number of the branch code, and N is a positive integer.

[0080] In this embodiment, a data verification step is also included: the connectivity of the generated tree topology is verified by traversing all nodes. If there are isolated nodes that are not connected to the root node or the parent node, the manual check of the branch point markers and parent node association information in the labeled data is prompted.

[0081] In this embodiment, the on-site photos are collected by a mobile terminal with positioning function. If the photos do not contain GPS coordinate information, the manual annotation step supports users to manually input the geographical coordinates of the branch points, or to select a tower with known coordinates in the photos as a reference point to calculate the relative coordinates of the branch points.

[0082] In this embodiment, the parametric modeling tool is Autodesk Civil 3D or Bentley OpenRoads. The model generation step imports the structured coding table into the tool through the API interface, automatically generates the three-dimensional model of the tower, the conductor path and connection relationship, and outputs a model verification report. The report includes information on unconnected towers and line segments with abnormal spans.

[0083] In this embodiment, the labeling rules stipulate that when a branch line branches off from an existing branch line (non-main line) to form a lower-level branch, the numbering rule for the lower-level branch is to add branch numbers sequentially based on the parent branch code in the order of discovery, forming a multi-level hierarchical code. Specifically, when the parent branch code is "main line ID - parent branch number", its first lower-level branch code is "main line ID - parent branch number - 1", the second is "main line ID - parent branch number - 2", and so on. For example, the first lower-level branch code of the branch "1-2" with main line code "1" is "1-2-1", and the second is "1-2-2". Example 2

[0084] Scene characteristics: A 10kV overhead power line is laid along a street in a city, including 6 towers (#01-#06). A branch line (including 3 towers #07-#09) is connected at tower #04 to a residential area. High-resolution photos were collected on-site using a GPS-equipped drone, and complete records of span, conductor type, and tower attributes were kept.

[0085] Step 1: Manual labeling

[0086] Photo Upload and Preprocessing: Upload a panoramic photo of tower #04 taken by a drone (PNG format, resolution 4096×2160). The system automatically extracts the GPS coordinates (X:116.4038°, Y:39.9147°) and shooting height. A distortion correction algorithm is used to eliminate the fisheye effect and enhance the edge contours of the conductors and tower, facilitating branch point identification.

[0087] Precisely mark the branch point: Use the circular selection tool to select the T-junction at the top of tower #04, and use the arrow tool to mark the branch direction, pointing towards the community. Select "#04" from the list of towers associated with the ledger, and add the following attributes: branch line type is "residential dedicated branch line", conductor specification is "JKLYJ-10 / 70", and installation date is "2024-01-15".

[0088] Coordinate association and verification: The system automatically binds the branch point markers to GPS coordinates and displays the ledger coordinates of tower #04 simultaneously to confirm coordinate consistency.

[0089] Step 2: Encoding Generation and Topology Mapping

[0090] Application of hierarchical coding rules:

[0091] The main line has a default code of "1". This branch is the first branch, numbered "2", and coded as "1-2". Branch lines #07-#09 all inherit this code, forming a "1-2" branch group.

[0092] Adjacency list construction details:

[0093] Root node (coded "1"): contains towers #01-#06, with geographic coordinates arranged in GPS order, and a list of child nodes ["1-2"].

[0094] Child nodes (coded "1-2"): contain #04 (branch point), #07-#09, with coordinates sequentially associated; the child node list is empty.

[0095] Node attributes: Each tower entry includes span information (e.g., #04 to #07 span 45 meters), conductor type and connection hardware type (T-terminal type "TL-10").

[0096] Topology visualization: The system generates a two-dimensional topology map, using different colors to distinguish between the main line (black) and branches (blue), and labels the tower number and span of each tower. It supports zooming and clicking on nodes to view details.

[0097] Step 3: Conflict Detection and Model Generation

[0098] No conflict verification: The coordinates of tower #04 correspond only to the code "1-2", and the codes "1" and "1-2" are unique, with no conflict prompts.

[0099] Refinement of the structured coding table:

[0100] Branch coding table: Add a "Branch function description" field (e.g., "#04-T connected to XX cell") to facilitate operation and maintenance identification;

[0101] Tower attribute table: Supplement operation and maintenance parameters such as "tower burial depth" and "maximum wind load";

[0102] Topology table: Add "traverse sag value" to provide accurate parameters for modeling.

[0103] 3D model generation results: After importing Autodesk Civil 3D, the system automatically matches the urban road BIM model to generate a 3D scene of the route with a street background. The tower model is scaled according to the actual height, the conductor is generated as a curve based on the sag value, and the T-junction automatically loads the 3D model of the hardware, which is consistent with the actual site conditions. Example 3

[0104] Scene characteristics: A 10kV power line, with main lines #01-#10 running along a hillside in a mountainous area. Branch A (#11-#13, to the village) branches off from tower #05, and branch B (#14-#16, to the mine) branches off from tower #08. Branch C (#17, to the irrigation station) branches off from tower #12 of branch A. Due to the complex terrain and GPS drift in some photos, branch B was mistakenly labeled as "2" during manual annotation (a duplicate of branch A).

[0105] Step 1: Conflict Triggering and Resolution

[0106] Conflict type identification: The system detected that #05 (coordinates X:117.234°, Y:35.678°) and #08 (coordinates X:117.256°, Y:35.691°) correspond to the same code "1-2", and determined it to be "code duplicate conflict". The two tower photos are highlighted on the interface and the coordinate deviation is marked.

[0107] Manual adjustment strategy: The operations and maintenance personnel use the system's "branch priority adjustment" function to keep branch A as "1-2", adjust the branch B's sequence number to "3", and update the code to "1-3". Simultaneously modify the attribute description of branch B, such as "Mining branch, priority lower than village branch".

[0108] Multi-level branch coding adaptation: Branch C branches out from branch A, with the sequence number "1" and the code "1-2-1". The system automatically verifies its association with the parent code "1-2" to confirm that the parent node is correct.

[0109] Step 2: Topology Mapping and Data Validation

[0110] The system verifies the integrity of the topology through depth-first traversal, confirming that all branches are derived from the main line or the superior branch, and there are no closed loops.

[0111] Isolated node detection, for example, if tower #17 is found to have no associated span information, triggers a data verification prompt: "Spans #17 and #12 are missing, please supplement." After manually entering a span of 25 meters, the verification passes.

[0112] Step 3: Adapt the model to mountainous terrain

[0113] Coordinate Correction: For tower #08 with GPS drift, the system combines the coordinates of adjacent towers #07 and #09 and corrects its coordinates through linear interpolation.

[0114] Terrain fusion modeling: Import mountain DEM elevation data, automatically adjust tower heights during model generation, and generate conductor paths along terrain undulations to avoid collisions with mountains.

[0115] The conflict report output, such as the model verification report, shows: "Branch B#14 crosses the main line #09 conductor at a distance of 3.5 meters (meeting the safety distance ≥ 3 meters)", without the need for manual adjustment. Example 4

[0116] Scenario characteristics: A 10kV line in an industrial park, main line #01-#20, branching from #06 into first-level branch A (#21-#25), branching from #23 of A into second-level branch B (#26-#28), branching from #27 of B into third-level branch C (#29-#30), and branching from #29 of C into fourth-level branch D (#31), forming a branch topology with a depth of 4.

[0117] Step 1: Encoding Generation and Topology Hierarchy

[0118] First-level branch A: "1-2"

[0119] Second-level branch B: "1-2-1"

[0120] Third-level branch C: "1-2-1-1"

[0121] Fourth-level branch D: "1-2-1-1-1"

[0122] The system automatically generates nested adjacency lists, and the list of child nodes for each node only contains direct subordinate branches, ensuring a clear data structure.

[0123] Step 2: Conflict Detection and Deep Adaptation

[0124] The uniqueness of the fourth-level branch code "1-2-1-1-1" was checked to confirm that there were no duplicates.

[0125] Topological traversal verifies that all nodes can be traced back to the root node "1", and there are no deeply isolated nodes;

[0126] When the model is generated, different line widths are used to display the layers. The main line width is 2mm, and the line width decreases by 0.3mm for each branch, making it easy to distinguish the layers.

[0127] In summary, this invention addresses the technical pain points in the field of branch line model identification and generation for overhead distribution networks by proposing a complete solution that integrates manual annotation and automated algorithms. It systematically solves problems such as insufficient integration of ledger data, reliance on manual topology establishment, inconsistent branch coding, and weak support for automated modeling in existing technologies.

[0128] This invention constructs a standardized and traceable branch line modeling system through a process of "manual annotation - code generation - topology mapping - conflict detection - model generation": The manual annotation module transforms field information into structured data through an intuitive interactive interface, ensuring the accuracy of branch point identification; the hierarchical coding rules and topology mapping algorithm realize the uniqueness of branch codes and the automated construction of topology structures, eliminating the ambiguity of traditional coding; the conflict detection and data verification mechanism further ensures data consistency and reduces the risk of modeling errors; the seamless integration of the structured coding table and parametric modeling tools enables efficient conversion from field data to 3D models.

[0129] This invention demonstrates strong adaptability to various scenarios and engineering value: in densely populated urban areas, it can combine high-precision GPS data to generate a 3D model that integrates with the geographic environment; in complex mountainous terrain, it can ensure the consistency between the model and the actual route through coordinate correction and terrain adaptation; for complex routes with multiple branches, its coding rules and topology algorithms can stably support branches up to level four and above, meeting the complex topology requirements of industrial parks and other similar locations.

[0130] This invention can significantly promote the digital transformation of power distribution networks: on the one hand, it greatly improves branch processing efficiency compared to traditional methods, reducing labor costs; on the other hand, the improved coding accuracy and model precision provide reliable data support for intelligent operation and maintenance, fault repair, planning and design, and other businesses. Furthermore, the standardized coding system and structured data format lay the foundation for cross-platform data fusion of power distribution network GIS systems, PMS operation and maintenance platforms, and digital twin systems.

[0131] In summary, this invention fills the gap in standardized modeling of distribution network branch lines, provides key support for the digital and intelligent management of distribution network lines, and has significant promotional value and application prospects.

[0132] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for identifying and generating branch line models of overhead distribution lines, characterized in that, Includes the following steps: The manual annotation step involves uploading on-site photos of the overhead power distribution line through the photo annotation interface, selecting branch points in the photos using rectangular or circular selection tools, marking the branch direction using the arrow tool, and associating the tower number to which the branch point belongs. The coding generation step, based on the annotation rules and combined with the manually marked branch point positions and tower numbers, generates hierarchical branch codes through a topology mapping algorithm. The hierarchical branch code format is "mainline ID-branch number", where the mainline ID is "1" by default, and the branch numbers are "2" "3" ... "N" in the order of discovery, where N is a positive integer. The topology mapping step involves establishing child node associations in the order of branch numbers, with the main line as the root node, based on the generated hierarchical branch codes, and automatically constructing a tree-like topology structure for the line. The tree-like topology structure includes the tower number, branch code, and parent node identifier of each node. The conflict detection step checks whether there are multiple branch codes at the same branch point or whether there are the same branch codes at different branch points. If a conflict exists, the system displays the conflict location and associated code information and prompts for manual review and adjustment. The model generation step involves forming a structured coding table from the conflict-detected tree topology and branch codes, which is then input into a parametric modeling tool to automatically generate a 3D model of the branch lines.

2. The method for identifying and generating branch line models of overhead distribution lines according to claim 1, characterized in that, In the manual annotation step, the photo annotation interface supports uploading JPG and PNG format photos, and automatically extracts the shooting time and GPS coordinate information of the photos, associates the branch point markings with GPS coordinates, and allows users to add branch line type, conductor specification and erection date attribute information to the marked branch points.

3. The method for identifying and generating branch line models of overhead distribution lines according to claim 1, characterized in that, The specific implementation of the topology mapping algorithm in the encoding generation step includes: Extract the pixel coordinates of manually marked branch points and their corresponding main line identifiers, and convert the pixel coordinates into actual geographic coordinates through perspective transformation; Construct an empty adjacency list data structure with the main line as the root node. Each node in the adjacency list contains the tower number, geographical coordinates, branch code, and a list of child nodes. Each branch point is added as a child node to its corresponding parent node in the order of branch number. The parent node is the main line or the superior branch line to which the branch point belongs.

4. The method for identifying and generating branch line models of overhead distribution lines according to claim 1, characterized in that, The specific process of the conflict detection step is as follows: Compare the geographic coordinates of all branch points. If the same geographic coordinate corresponds to multiple branch codes, it is determined to be a conflict of multiple codes for the same point. Perform uniqueness checks on all branch codes. If different geographic coordinates correspond to the same branch code, it is determined to be a code duplication conflict. After a conflict is triggered, a manual adjustment interface is provided, which supports modifying branch numbers, merging duplicate branch points, and splitting incorrectly associated branch lines. After adjustment, the code generation and topology mapping steps are re-executed.

5. The method for identifying and generating branch line models of overhead distribution lines according to claim 1, characterized in that, In the model generation step, the structured coding table includes a branch coding table, a tower attribute table, and a topology table, wherein: The branch coding table includes the coding value, line type, starting tower number, ending tower number, and conductor type; The pole attribute table includes pole number, pole type, height, material, and geographic coordinates; The topology table includes parent node code, child node code, span length, and connection method; The line types include main lines and branches; the tower types include straight poles and tension poles; and the connection methods include T-joints and butt joints.

6. The method for identifying and generating branch line models of overhead distribution lines according to claim 3, characterized in that, In the adjacency list data structure, the root node corresponds to the main line code "1", the first-level branch nodes are coded as "1-2", "1-3"..."1-N", and the second-level branch nodes are coded as "1-2-1", "1-2-2"..."1-2-N". The level depth of the node is consistent with the level number of the branch code, and N is a positive integer.

7. The method for identifying and generating branch line models of overhead distribution lines according to claim 1, characterized in that, It also includes a data verification step: performing connectivity verification on the generated tree topology, traversing all nodes, and if there are isolated nodes that are not connected to the root node or the parent node, prompting manual inspection of the branch point markers and parent node association information in the labeled data.

8. The method for identifying and generating branch line models of overhead distribution lines according to claim 2, characterized in that, The on-site photos were collected using a mobile terminal with positioning capabilities. If the photos do not contain GPS coordinate information, the manual annotation step allows users to manually input the geographical coordinates of the branch points, or to calculate the relative coordinates of the branch points by selecting a tower with known coordinates in the photos as a reference point.

9. The method for identifying and generating branch line models of overhead distribution lines according to claim 1, characterized in that, The parametric modeling tool is Autodesk Civil 3D or Bentley OpenRoads. The model generation step imports the structured coding table into the tool through the API interface, automatically generates the three-dimensional model of the tower, the conductor path and connection relationship, and outputs a model verification report. The report includes information on unconnected towers and line segments with abnormal spans.

10. The method for identifying and generating branch line models of overhead distribution lines according to claim 1, characterized in that, In the aforementioned labeling rules, when a branch line branches out into a lower-level branch from an existing branch line, the numbering rule for the lower-level branch is to add branch numbers sequentially based on the code of the upper-level branch in the order of discovery, forming a multi-level hierarchical code; wherein, when the code of the upper-level branch is "main line ID - upper-level branch number", its first lower-level branch code is "main line ID - upper-level branch number - 1", the second is "main line ID - upper-level branch number - 2", and so on.

Images