A method, device and medium for generating a schematic diagram of a fire hydrant system of a three-dimensional model

Abstract

The embodiment of the specification discloses a fire hydrant system schematic diagram generation method and device of a three-dimensional model, relating to the fire protection technical field, the method comprising: obtaining the target schematic diagram generation parameters triggered by the user through the preset graphical user interface, the target schematic diagram generation parameters including the target fire hydrant system, the connection mode and the labeling setting parameters; according to the target fire hydrant system, performing instance extraction in the pre-acquired building three-dimensional model, determining multiple target fire hydrant instances and the fire hydrant attribute information corresponding to each target fire hydrant instance; based on the connection pipe set, traversing each connection pipe in the building three-dimensional model, performing the pipe merging and connecting operation based on the target fire hydrant entity, and determining multiple functional pipe sets; generating the pipeline topology graph through the multiple functional pipe sets, the connection mode and the preset drawing rule, setting the pipeline topology graph based on the labeling setting parameters, and generating the corresponding fire hydrant system schematic diagram.

Description

Technical Field

[0001] This specification relates to the field of fire protection technology, and in particular to a method, equipment and medium for generating a three-dimensional model of a fire hydrant system schematic diagram. Background Technology

[0002] In the field of building water supply and drainage design, the schematic diagram of a fire hydrant system is a key design document that expresses the water supply topology. Currently, the generation of such drawings mainly relies on two technical solutions: one is completely manual drawing, where designers need to construct elements such as elevation lines, risers, and fire hydrants based on experience in 2D drawing tools; the other is semi-automatic generation, where a simplified algorithm is used to output the schematic diagram framework, and then the pipe routing is manually adjusted and annotations are added.

[0003] However, manual drawing involves frequent repetitive operations and significant time consumption due to the need for manual analysis of complex pipe connections in the 3D model, resulting in a substantial extension of the design cycle. Building Information Modeling (BIM) provides the actual spatial coordinates and topological connections of the fire hydrant system; generating orthogonal projection schematics based on this eliminates human interpretation bias. In semi-automatic generation, the lack of a precise mapping from the BIM to the 2D schematic leads to inconsistencies between the generated drawings and the 3D spatial layout, increasing the design error rate and requiring additional manual verification. Furthermore, the reliance on designers' subjective experience to set rules in annotation and attachment processes results in inconsistent drawing output formats, hindering cross-project collaboration and the reuse of deliverables.

[0004] In summary, existing technologies, due to their heavy reliance on manual processes and lack of automated mapping, suffer from core problems such as low design efficiency, insufficient drawing consistency, and lack of standardization in the generation of fire hydrant system schematic diagrams. This leads to risks of project cycle loss and accumulation of quality risks. Summary of the Invention

[0005] This specification provides one or more embodiments of a method, device, and medium for generating a three-dimensional model of a fire hydrant system schematic diagram, which addresses the following technical problems: Existing technologies, due to their high reliance on manual processes and lack of automated mapping, suffer from low design efficiency, insufficient drawing consistency, and a lack of standardization in the generation of fire hydrant system schematic diagrams, leading to risks of project cycle loss and accumulated quality risks.

[0006] One or more embodiments of this specification employ the following technical solutions:

[0007] This specification provides one or more embodiments of a method for generating a schematic diagram of a fire hydrant system from a three-dimensional model. The method includes: acquiring target schematic diagram generation parameters triggered by a user through a preset graphical user interface, wherein the target schematic diagram generation parameters include at least one target fire hydrant system corresponding to the target schematic diagram, a connection method, and annotation setting parameters; extracting instances from a pre-acquired three-dimensional building model based on the at least one target fire hydrant system corresponding to the target schematic diagram, determining multiple target fire hydrant instances and fire hydrant attribute information corresponding to each target fire hydrant instance, wherein the fire hydrant attribute information includes spatial location information, fire hydrant height information, and a set of connecting pipes; traversing each connecting pipe in the three-dimensional building model based on the set of connecting pipes, and performing a pipe merging and connection operation based on the target fire hydrant entity to determine multiple sets of functional pipes, wherein the functional pipes include risers, horizontal main pipes, and appliance branch pipes; generating a pipeline topology diagram through the multiple sets of functional pipes, the connection method, and preset drawing rules, and setting the pipeline topology diagram based on the annotation setting parameters to generate a schematic diagram of the fire hydrant system corresponding to the three-dimensional building model.

[0008] This specification provides one or more embodiments of a device for generating a three-dimensional model of a fire hydrant system schematic diagram, comprising:

[0009] At least one processor; and,

[0010] A memory communicatively connected to the at least one processor; wherein,

[0011] The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the above-described method.

[0012] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions configured to perform the above-described method.

[0013] The above-mentioned technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects: an automated and lossless mapping of three-dimensional engineering semantics to two-dimensional drawing specifications is constructed. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0015] Figure 1 A flowchart illustrating a method for generating a three-dimensional model of a fire hydrant system schematic diagram, as provided in the embodiments of this specification.

[0016] Figure 2 A schematic diagram illustrating a graphical user interface provided in an embodiment of this specification;

[0017] Figure 3 This is a structural example diagram of a riser provided in the embodiments of this specification;

[0018] Figure 4 A structural example diagram of a horizontal trunking pipe provided in the embodiments of this specification;

[0019] Figure 5 A structural example diagram of an appliance branch pipe provided in the embodiments of this specification;

[0020] Figure 6 A schematic diagram of a fire hydrant system provided for an embodiment of this specification;

[0021] Figure 7 This is a structural schematic diagram of a three-dimensional model fire hydrant system schematic diagram generation device provided in the embodiments of this specification. Detailed Implementation

[0022] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0023] This specification provides a method for generating a three-dimensional model of a fire hydrant system schematic diagram. It should be noted that the execution entity in this specification embodiment can be a server or any device with data processing capabilities. Figure 1 This specification provides a flowchart illustrating a method for generating a three-dimensional model of a fire hydrant system schematic diagram, as shown in the embodiments below. Figure 1 As shown, the main steps include the following:

[0024] Step S101: Obtain the target schematic generation parameters triggered by the user through a preset graphical user interface.

[0025] In one embodiment of this specification, a target schematic diagram generation parameter is received from the user through a preset graphical user interface. This parameter includes at least one target fire hydrant system, piping method, and annotation settings corresponding to the target schematic diagram. It should be noted that the purpose of these target schematic diagram generation parameters is to allow the user to customize the schematic diagram generation rules, ensuring that the output meets specific design requirements. Figure 2 This is a schematic diagram illustrating a graphical user interface provided in an embodiment of this specification, such as... Figure 2 As shown, the graphical user interface (UI) provides checkboxes and drop-down menus for users to set parameters. These parameters include system selection parameters, allowing users to select multiple fire hydrant systems, such as low-zone, high-zone, and underground garage connection systems, supporting the merging of multiple systems to generate the schematic diagram. Additionally, there are connection method parameters, with a drop-down menu selecting the fire hydrant connection method (flat connection or top connection), affecting the geometry of subsequent appliance branch pipes; for example, top connections require the branch pipe to bend downwards. The target schematic diagram generation parameters also include elevation line control parameters, with checkboxes determining whether elevation lines are drawn, and pipe diameter labeling control parameters, controlling whether branch pipe diameters are labeled. Furthermore, there are attachment leader-out labeling control parameters and leader-out labeling content. The checkbox for attachment leader-out labeling control parameters determines whether attachments, such as air valves and pressure gauges, are labeled; the input box for leader-out labeling content specifies the labeling text for various components (such as test fire hydrants). After UI interaction, the system retrieves the target schematic diagram generation parameters triggered by the user.

[0026] Step S102: Based on at least one target fire hydrant system corresponding to the target schematic diagram, extract instances from the pre-acquired 3D building model to determine multiple target fire hydrant instances and the fire hydrant attribute information corresponding to each target fire hydrant instance.

[0027] The fire hydrant's attribute information includes spatial location information, fire hydrant height information, and a set of connecting pipes;

[0028] Existing technologies rely on manual identification of fire hydrants and their connections in 3D models, resulting in low design efficiency and a high risk of errors. Fire hydrant systems in 3D building models contain dozens to hundreds of scattered instances, which are easily missed during manual screening. The set of connecting pipes for fire hydrants determines the merging logic of subsequent risers and horizontal mains, and manual recording makes it difficult to ensure accuracy. In addition, spatial location and height information are the basis for coordinate calculations when mapped to a 2D orthogonal view, and their absence will lead to distortion of the schematic diagram.

[0029] In one embodiment of this specification, firstly, a family type filter is activated in the building's 3D model based on the target fire hydrant system identifier (e.g., "low-zone fire hydrant system") selected by the user through a graphical interface. The family type filter is based on preset fire hydrant family category keywords (e.g., ... " Hydrant” Alternatively, for "fire hydrant" (or "fire hydrant"), the system scans all family instances in the model that meet the criteria. During the scan, the application programming interface of the building information model is called to traverse the family instance table in the model database and filter out the set of fire hydrant instances whose "belonging to system" attribute exactly matches the target system identifier, forming the initial target instance pool.

[0030] Next, spatial location information, hydrant height information, and various structured attributes of the connecting pipe set are extracted for each target fire hydrant instance. By reading the insertion point coordinates of the fire hydrant family instance, its X, Y, and Z coordinates in the 3D model space are obtained. These coordinates represent the absolute position in the model's global coordinate system, directly provided by the underlying database of the Building Information Modeling (BIM) system, thus acquiring spatial location information. Based on the relative relationship between the insertion point's Z-coordinate value and the structural elevation of the floor to which it belongs, the vertical installation height of the fire hydrant's bottom from the finished floor surface is calculated. This calculation process requires associating with the floor elevation objects in the model and is achieved through coordinate difference conversion. The model's pipe connection relationship API is called to obtain all physically connected pipe objects to the fire hydrant instance; each connected pipe is traversed, and its unique identifier, pipe diameter, material type, and endpoint coordinates are extracted; a pipe topology linked list is dynamically constructed to record the connection order and direction between pipes.

[0031] Finally, the aforementioned attribute information is encapsulated into structured data objects. Each target fire hydrant instance corresponds to a data entity, containing an array of spatial locations, a height value, a list of connecting pipe identifiers, and their associated attribute sets. All instance data is stored in groups according to the floor to which they belong, forming a standardized input dataset that can be called by the subsequent pipe merging module.

[0032] It should be noted that in the above process, the "belonging system" attribute of the target system identifier and the model instance must use an exact string matching algorithm to avoid omissions due to naming differences. When fire hydrants are indirectly connected to pipelines through accessories such as flanges and valves, the connection points of the accessories must be searched recursively until the directly connected pipeline entity is located. Furthermore, spatial location information must be uniformly converted to the model's global coordinate system to ensure consistency in the calculation benchmark for subsequent steps.

[0033] Regarding data completeness, conventional methods rely on designers visually identifying fire hydrant locations in the model and manually recording attributes. In complex projects, instances in hidden locations (such as fire hydrants in manholes) are easily overlooked. The technical solution in this specification, however, uses a programmed filtering mechanism to ensure that all fire hydrant instances within the target system are extracted without omission, and that attribute information is directly derived from the model database, eliminating human error at its source. Regarding topological accuracy, conventional processes require designers to manually trace each pipe connection path, which is time-consuming and difficult to handle complex topologies such as ring networks. The technical solution in this specification automates the acquisition of connecting pipe sets and dynamically constructs a topological linked list, accurately recording the connection relationships between fire hydrants and pipes, and between pipes, providing unambiguous input data for subsequent riser merging and loop detection. Regarding process efficiency, large commercial complex projects often contain hundreds of fire hydrant instances; manual extraction takes several hours and requires repeated verification. The technical solutions in this specification complete instance screening and attribute extraction on the server side within milliseconds, compressing data preparation time to a negligible level, allowing design resources to focus on creative decisions rather than repetitive operations. More importantly, the structured attribute dataset becomes the core driving force for subsequent end-to-end automation; spatial location and height information support coordinate calculations for two-dimensional mapping, and the set of connecting pipelines determines the merging rules for functional pipelines. This direct transfer from model data to algorithm input eliminates information attenuation caused by manual translation, ensuring strict consistency between the final generated schematic diagram and the 3D model.

[0034] Step S103: Based on the connection pipe set, traverse each connection pipe in the building 3D model to perform a pipe merging and connection operation based on the target fire hydrant entity, and determine multiple functional pipe sets.

[0035] This functional pipeline includes risers, horizontal mains, and appliance branch pipes;

[0036] Based on this set of connecting pipes, each connecting pipe is traversed in the 3D building model to perform a pipe merging and connection operation based on the target fire hydrant entity, identifying multiple functional pipes. Specifically, this includes: traversing each connecting pipe in the set of connecting pipes in the 3D building model, extracting pipe segments with an angle less than a preset angle threshold and a length greater than a preset length threshold, merging continuous pipe segments with coincident geometric axes, and outputting a target riser set. This target riser set includes multiple target risers and the corresponding end connection relationships and riser spatial height data for each target riser; based on the end connection relationships of each target riser... Identify the connecting pipes at the end of each target riser, and search for continuous pipe segments horizontally until the next target riser or pipe end is found. Merge these segments to determine the target horizontal pipe set, which includes multiple target horizontal pipes and the connection relationships between the two ends of each target horizontal pipe, as well as the horizontal pipe's spatial height data. Based on the connecting pipe set corresponding to the target fire hydrant entity, traverse the connecting pipes of the target fire hydrant instance to determine the target appliance branch set, which includes multiple target appliance branch pipes and the fire hydrant instance identifier at the end of each target appliance branch pipe, as well as the appliance branch's spatial height data. Based on the set of connecting pipes corresponding to the target fire hydrant entity, traverse the connecting pipes of the target fire hydrant instance to determine the set of target appliance branch pipes. Specifically, this includes: starting from the connecting pipe of the target fire hydrant instance, searching segment by segment along the pipe topology path to determine the search path; terminating when the search path encounters the endpoint of the target riser or the endpoint of the target horizontal main pipe, and merging all pipe segments corresponding to the search path into a single appliance branch pipe, recording the fire hydrant instance identifier and appliance branch pipe spatial height data at the endpoint of each single appliance branch pipe.

[0037] In Building Information Modeling (BIM), the physical piping of a fire hydrant system consists of numerous independent pipe segments, such as horizontal sections, elbows, and valve partitions. Pipe merging is the core conversion logic for generating readable schematic diagrams. Schematic diagrams need to use single line segments to represent logical components such as risers / horizontal trunks, while the physical piping in the model is composed of multiple segments spliced ​​together. For example, horizontal trunks may contain bends and avoidance structures. If not merged, the output will be chaotic and lose the meaning of the schematic diagram's logical abstraction. The connection relationships between physical pipe segments, such as riser connections across floors, need to be reorganized into continuous functional piping; otherwise, it is impossible to establish a basis for loop detection. Furthermore, merged functional piping, such as a single horizontal trunk, only needs to be labeled once, avoiding the bloated drawings caused by labeling each segment individually.

[0038] In one embodiment of this specification, a set of risers is first generated. It should be noted that in this embodiment, vertical pipes connecting fire hydrant networks on different floors are defined as risers. All connecting pipes of the target fire hydrant instance are traversed, and spatial attitude analysis is performed on each pipe. The angle between the pipe axis direction vector and the vertical direction (Z-axis) is calculated, and pipe segments with an angle less than a first preset angle threshold are selected, i.e., nearly vertical. Alternatively, the angle between the pipe axis direction vector and the horizontal direction (X-axis) can be calculated, and pipe segments with an angle not less than a second preset angle threshold are selected, i.e., nearly vertical. For example, the first preset angle threshold can be set to 5 degrees, and the second preset angle threshold can be set to 85 degrees. Short pipes with a length less than a preset length threshold are excluded to avoid misclassification of branch pipes. The preset length threshold can be set to 1 meter, or can be set according to requirements.

[0039] Geometric collinearity detection is performed on candidate pipe segments that meet the conditions. The axial projections of adjacent pipe segments are calculated to see if they overlap and if their elevations are continuous. If they overlap, they are recursively merged into a single riser. Figure 3 This is a structural example diagram of a riser provided in the embodiments of this specification, such as... Figure 3 As shown, three risers with overlapping axis projections and continuous elevations of adjacent pipe segments are merged into one merged riser. After merging, key riser attributes are extracted, including the starting end height (Z-coordinate of the lowest point of the merged segment), the ending end height (Z-coordinate of the highest point of the merged segment), the identifier of the connecting pipe at the starting end (the non-riser pipe connected at the bottom), and the identifier of the connecting pipe at the ending end (the non-riser pipe connected at the top), forming a structured riser data entity and storing it in the target riser set.

[0040] This is followed by the generation of a set of horizontal main pipes. Here, a horizontal main pipe is defined as a pipe connecting two risers, or one end connected to a riser and the other end free, with horizontal pipes on both sides. It should be noted that in a Revit model, a true horizontal main pipe is often composed of several pipe segments joined together. For example, horizontal segments, slightly inclined segments, elbows, and riser segments may be mixed together; there may be sleeves, valves, or tees in between, geometrically "breaking" the connection; the elevation may also have slight variations (slope or avoidance). However, the schematic diagram in the embodiment of the instruction manual does not need to address these issues; it only requires mapping multiple pipe segments on the same floor, in the same loop, with the same direction, and of the same system type into a single horizontal two-dimensional line segment.

[0041] The algorithm iterates through the endpoint connections of each riser in the target riser set. Starting from the connecting pipe at the bottom or top of the riser, it searches horizontally along the pipe topology path, with the angle between the direction vector and the horizontal plane less than a preset angle threshold. During the search, three types of pipe segments are dynamically merged: continuous horizontal straight pipe segments, slightly inclined pipe segments created to avoid obstacles, and pipe segments interrupted by valves, sleeves, or other accessories but with collinear axis projections. The search terminates in one of two situations: encountering the endpoint of another target riser, or when the pipe end is unconnected. The merged pipe segment is defined as a horizontal trunk pipe, and its starting end height (search start point Z coordinate), ending end height (search end point Z coordinate), and the connection relationship between the two ends (left end riser identifier / right end riser identifier or free end marker) are extracted to form a horizontal trunk pipe data entity and stored in the target horizontal trunk pipe set. Figure 4 This is a structural example diagram of a horizontal trunking pipe provided in the embodiments of this specification, such as... Figure 4 As shown, iterate through all the pipes connected to the top and bottom of the riser, and obtain the other pipes connected to it in turn until a riser or an unconnected pipe is encountered. Merge each obtained pipe into a horizontal trunk pipe and extract the horizontal trunk pipe attribute information.

[0042] Finally, a set of appliance branch pipes is generated. Here, an appliance branch pipe is defined as a pipe that is directly connected to a fire hydrant at one end and to a riser or horizontal main pipe at the other end. The connection points of each target fire hydrant instance are traversed, starting from the directly connected pipe and searching segment by segment along the pipe topology path. The search process ignores geometric interruptions caused by pipe fittings (such as valves and tees), only detecting changes in the pipe axis direction. The search terminates when a target riser endpoint or target horizontal main pipe endpoint is encountered, indicating access to the main network. All pipe segments along this path are merged into a single appliance branch pipe, and key attributes are extracted. These key attributes include the starting end height (Z-coordinate of the fire hydrant connection point), the ending end height (Z-coordinate of the point accessing the main network), and the identifier of the connected fire hydrant instance (associated with the fire hydrant data extracted in the previous steps). All appliance branch pipe entities are stored in the target appliance branch pipe set. Figure 5 This is a structural example diagram of an appliance branch pipe provided in the embodiments of this specification, such as... Figure 5 As shown, iterate through all the pipes connected to the fire hydrants, and obtain the other pipes connected to them in turn until a horizontal pipe is encountered. Then, merge the pipes obtained each time into a single appliance branch pipe and extract its information.

[0043] When manually drawing schematic diagrams, designers rely on experience to determine which pipe segments should be merged into risers or horizontal trunks. This is prone to errors due to insufficient spatial imagination, such as mistakenly classifying inclined pipes as risers. The technical solution in this specification's embodiments ensures that the merging results strictly conform to engineering definitions through preset angle thresholds and collinearity detection physical rules. Risers are defined as near-vertical long pipes, and horizontal trunks as horizontally connected pipes, eliminating the risk of subjective misjudgment at the algorithmic level. Regarding topological integrity, traditional semi-automatic tools only extract isolated pipe segments, ignoring the functional relationships between pipes. The technical solution in this specification's embodiments dynamically reconstructs the complete topological network of the fire hydrant system through recursive search of endpoint connection relationships: risers serve as vertical trunks, horizontal trunks as horizontal loops, and appliance branch pipes as terminal access paths. This connection-based merging mechanism ensures that the generated two-dimensional schematic diagram accurately reflects the water supply logic of the three-dimensional model. Through axial projection merging and accessory penetration, non-functional geometric deformations are intelligently ignored, retaining only key topological features affecting the water supply path, resulting in a concise schematic diagram that still meets engineering rigor requirements. Crucially, the merged single riser corresponds to a vertical line segment in the schematic diagram, the horizontal main pipe corresponds to a horizontal connection, and the appliance branch pipe determines the connection method of the fire hydrant. This transformation from physical pipes to logical components enables the server to generate standardized drawings based on unified rules, solving the problem of expression differences caused by manual drawing.

[0044] Step S104: Generate a pipeline topology diagram by using multiple functional pipeline sets, connection methods and preset drawing rules. Based on the annotation setting parameters, set the pipeline topology diagram to generate a fire hydrant system schematic diagram corresponding to the building 3D model.

[0045] Using the set of multiple functional pipes, the connection method, and preset drawing rules, a pipeline topology map is generated. Specifically, this includes: extracting the floor elevation value and floor identifier for each floor in the 3D building model; determining the total length of the elevation line based on the total number of risers in the target riser set, and generating equally spaced parallel lines according to the floor sequence corresponding to the floor identifier and labeling the floor elevation identifier to generate a floor elevation line layer; locating the fire hydrant instance based on each target riser and the floor elevation identifier in the target riser set, and determining the coordinates of the fire hydrant's center position; and determining the pipeline connection layer between the multiple functional pipes using the set of multiple functional pipes and the connection method, so as to generate a pipeline topology map based on the floor elevation line layer, the fire hydrant's center position coordinates, and the pipeline connection layer. By using the multiple functional pipe sets and the connection method, the pipe connection layers between the multiple functional pipes are determined, specifically including: detecting the closed loop formed by the target riser set and the target horizontal trunk set; arranging risers belonging to the same closed loop horizontally at a preset first spacing, and arranging riser groups belonging to different closed loops horizontally at a preset second spacing; determining the connection line between each target appliance branch and the target fire hydrant according to the connection method and the appliance branch set, so as to connect the target appliance branch and the target fire hydrant, and connecting the corresponding riser axis endpoints at both ends of the horizontal trunk in the target horizontal trunk set through a horizontal straight line. Detecting the closed loop formed by the target riser set and the target horizontal pipe set specifically includes: obtaining the riser space height data of each target riser in the target riser set and the horizontal pipe space height data of each target horizontal pipe in the target horizontal pipe set; based on the riser space height data or the horizontal pipe space height data, taking the specified target riser or specified target horizontal pipe with the lowest space height as the starting node; recursively traversing adjacent pipe nodes along the endpoint connection relationship of the specified target riser or specified target horizontal pipe to generate a loop traversal path and marking visited nodes; when the loop traversal path returns to any visited node, the loop traversal path is marked as a closed loop.

[0046] In the automatic generation process of fire hydrant system schematic diagram, the pipeline topology diagram construction step is the core spatial mapping method to realize the conversion of three-dimensional functional pipelines into two-dimensional visual diagrams. The merged functional pipeline set (rises, horizontal mains, and appliance branch pipes) only retains the topological relationship and needs to be converted into a visual diagram in combination with the building floor structure and connection rules.

[0047] In one embodiment of this specification, a floor elevation line layer is first constructed. Elevation values ​​and identifiers (such as...) for all floors are extracted from the 3D building model. " F1 ” , " B1 ”Sort the elevation values ​​in ascending order. Then, calculate the total length of the elevation lines. This is done by multiplying the total number of risers in the target riser set by a preset spacing coefficient, avoiding direct numerical calculations. In one embodiment, the length of the elevation line = (total number of risers / 2) * 9000 mm. When multiple systems are selected, the total number of risers should be the sum of all riser numbers. In a two-dimensional coordinate system, parallel straight lines are generated in floor order, with equal vertical spacing and a uniform length equal to the calculated total length, using the horizontal direction as the reference. Each elevation line is labeled with its corresponding floor identifier at both ends, forming a vertical spatial reference system.

[0048] Next, the center point of the fire hydrant is located. For each target fire hydrant instance, the corresponding elevation line is matched based on its floor level. Using the elevation line as the vertical reference, the Y-coordinate of the fire hydrant's center point is determined by a preset vertical offset (vertical direction in the schematic coordinate system). Simultaneously, the X-coordinate of the center point is determined by a preset horizontal offset based on the axis position of the target riser into which the appliance branch pipe connected to the fire hydrant is located. Finally, a set of two-dimensional coordinates for all fire hydrants is output. In one embodiment, the preset vertical offset can be set to 1100mm, and the preset horizontal offset can be set to 500mm.

[0049] Next, a pipe connection layer is generated. The spatial height data of the target riser set and the target horizontal pipe set are obtained, including the starting and ending heights. Starting with the riser or horizontal pipe with the lowest spatial height as the starting node, adjacent pipe nodes are recursively traversed along their endpoint connections, and visited nodes are marked. When the traversal path returns to a visited node, all pipes contained in that path are marked as a closed loop. Riseres within the same loop are arranged equidistantly in the horizontal direction according to a preset first spacing. Riser groups in different loops are isolated and arranged according to a preset second spacing, forming a riser axis position matrix. It should be noted that the first spacing between risers within the same loop can be set to 3000mm, and the second spacing between risers in different loops can be set to 6000mm. Riseres are drawn sequentially, and the riser height is determined based on the actual height.

[0050] Based on the vertical pipe markings at both ends of each horizontal main pipe in the target horizontal main pipe set, locate the coordinates of the two ends in the vertical pipe axis position matrix, and connect the two ends with a horizontal straight line. If one end is a free end (without a connected vertical pipe), extend the line horizontally from the connection point for a predetermined length. When connecting appliance branch pipes to fire hydrants, the pipe connection method needs to be considered. If the connection method is "top connection," extend a line segment vertically downwards from the center point of the fire hydrant to a predetermined turning height, and then extend horizontally to the target vertical pipe axis position. If the connection method is "side connection," extend a straight line horizontally from the center point of the fire hydrant directly to the target vertical pipe axis position.

[0051] The final composite pipeline topology map overlays the elevation line layer, fire hydrant location points, riser axis (vertical segment), horizontal main pipe connection line (horizontal segment), and appliance branch pipe polyline onto the same two-dimensional coordinate system, eliminating redundant information in three-dimensional space and outputting an orthogonal projection map that retains only the topological connection relationship.

[0052] The above technical solutions require conventional design to manually draw elevation lines and estimate lengths based on experience, which can easily lead to floor misalignment or disproportionate layout. The technical solution in this specification dynamically calculates elevation line lengths based on the total number of risers and generates equidistant parallel lines strictly according to the model's floor data, ensuring that the vertical scale perfectly matches the actual building's layering and avoiding basic errors such as a fire hydrant crossing multiple elevation lines on a single floor. Furthermore, manual riser arrangement often results in pipe intersections or uneven spacing due to difficulties in loop identification. The technical solution in this specification automatically detects closed loops using a recursive traversal algorithm and groups them according to loop relationships. Risers within the same loop are arranged compactly, while isolation zones are maintained between different loops. This intelligent layout based on topology relationships allows complex pipe networks to clearly display the water supply loop logic in a two-dimensional plane, avoiding the trial-and-error costs of repeated layout adjustments by designers. The pipeline topology diagram, as a structured data layer, provides precise anchor points for subsequent annotation modules. The riser axis position determines the pipe diameter annotation coordinates, the midpoint of the horizontal main pipe positions the attached legend, and the fire hydrant connection points are associated with and annotated. This layered generation mechanism, which prioritizes topology over annotation, solves the problem of misalignment between annotations and pipelines in conventional processes, enabling one-click drawing generation with zero manual adjustments.

[0053] Based on the annotation settings parameters, the pipeline topology diagram is configured to generate a fire hydrant system schematic diagram corresponding to the building's 3D model. Specifically, this includes: extracting the floor elevation line layer and pipe connection layer from the pipeline topology diagram to determine the current floor elevation line corresponding to each target riser; when the annotation settings parameters include a riser diameter annotation instruction, the riser diameter text corresponding to the target riser is added at the midpoint of each current floor elevation line, offset by a preset radial distance in the vertical direction; when the annotation settings parameters include a horizontal main pipe diameter annotation instruction, the horizontal main pipe diameter text corresponding to the target horizontal main pipe is added at the midpoint of each target horizontal main pipe segment, offset by a preset distance in the vertical positive direction; when the annotation settings parameters include an appliance branch pipe diameter annotation instruction, the branch pipe diameter text is added at the midpoint of each target appliance branch horizontal segment, offset by a preset distance in the vertical negative direction.

[0054] In one embodiment of this specification, the annotation setting parameters are first parsed, and the set of instructions configured by the user through the graphical interface is read, including Boolean control signals such as the enable flags for riser diameter annotation, horizontal main pipe diameter annotation, and appliance branch pipe diameter annotation. Simultaneously, preset annotation style rules (such as text font, font size, and color) and offset parameters (such as radial distance and vertical positive / negative direction distance) are extracted. Next, the annotation anchor point is located, and each target riser in the pipeline topology diagram is traversed. The floor to which the riser belongs is determined based on its spatial height. It should be noted that the floor to which the riser belongs can be determined by matching its height range with the elevation line height; for example, a riser height of 12.3m can be matched... " F3@12.0m ” Elevation Line. Locate the elevation line segment in the elevation line layer corresponding to the floor and calculate its midpoint coordinates. Using the midpoint coordinates as a reference, offset the midpoint by a preset radial distance perpendicular to the elevation line to generate a label text insertion point, thus determining the anchor point for the riser pipe diameter label. In one example, the preset radial distance is 200mm. Traverse each horizontal line segment in the target horizontal pipe set and calculate its geometric midpoint coordinates. Using the midpoint coordinates as a reference, offset the midpoint by a preset distance vertically upward to generate a label text insertion point, thus determining the anchor point for the horizontal pipe diameter label. In one example, the preset distance is 200mm. Identify the horizontal pipe segment in the appliance branch pipe connection line (for flat connections, it's the entire segment; for top connections, it's the horizontal segment after a bend). Calculate the midpoint coordinates of the horizontal pipe segment. Using the midpoint coordinates as a reference, offset the midpoint by a preset distance vertically downward to generate a label text insertion point, thus determining the anchor point for the appliance branch pipe diameter label. In one example, the preset distance here is 200mm. It should be noted that the positive vertical direction is the positive Y-axis of the two-dimensional coordinate system, and the negative direction is the negative Y-axis, to ensure that the annotation is always located on the outside of the pipe.

[0055] Extract pipe diameter attribute values ​​(e.g., DN150) from the target riser, horizontal main, and appliance branch pipe data entities, and convert them according to a preset text format (e.g., add "DN"). ” (Prefix, unit symbol), dynamically binds annotation text to anchor point coordinates, ensuring the text center point coincides with the anchor point. It should be noted that when adjacent annotations overlap, their positions are automatically fine-tuned along the pipe axis to maintain text readability, and the pipe diameter text content directly originates from the original attributes of the functional pipe set, avoiding manual input errors. Finally, an annotation layer is synthesized, selectively adding three types of pipe diameter text to the annotation layer based on the annotation enable flag status; the annotation layer is then overlaid on the pipeline topology diagram to form a complete fire hydrant system schematic, outputting a vector graphics file (such as DWG format), preserving the editability and association between text and pipelines.

[0056] The above technical solution automatically extracts pipe diameter attributes from the functional pipeline set and binds them to annotation text, ensuring strict consistency between each annotation and the 3D model data, eliminating the risk of human transcription errors at the source. It transforms specifications into preset offset rules, locking the anchor point of riser annotations to the midpoint of the floor elevation line, fixing horizontal main pipe annotations directly above the pipe section, and placing appliance branch pipe annotations below the horizontal section. This mechanical execution mechanism ensures a uniform and neat annotation layout for all projects, meeting the standardization requirements of review agencies. It batch-generates all specified annotations according to user-selected annotation instructions, compressing annotation time to the second level. Annotation positions automatically avoid pipes and other text, avoiding the tedious repeated adjustments in traditional processes. Users can freely choose to annotate only main risers to reduce drawing redundancy, or annotate all branch pipes to meet detailed construction needs. This on-demand annotation capability allows the same algorithm to adapt to different granularity requirements in both schematic design drawings and construction details, changing the traditional binary dilemma of full annotation or no annotation, and improving user choice.

[0057] After generating the pipeline topology map, the method further includes: identifying the vent valve instance connected to the top of the target riser in the 3D model of the building, and drawing the vent valve symbol at the top coordinate position of the corresponding target riser; identifying the pressure gauge and / or butterfly valve instance associated with the target horizontal main pipe or appliance branch pipe, and drawing the pressure gauge legend and / or butterfly valve legend at the midpoint coordinate position of the corresponding target horizontal main pipe or appliance branch pipe.

[0058] In the process of generating fire hydrant system schematic diagrams, the creation of accessory legends is a crucial step in ensuring the integrity of the engineering drawings. Accessory devices such as exhaust valves, pressure gauges, and butterfly valves directly affect system operation and maintenance safety. However, they are scattered and small in size in the 3D model. If they are not explicitly marked in the 2D schematic diagram, the construction team will be unable to confirm their installation locations, potentially overlooking critical equipment. Furthermore, the lack of visual references during later maintenance increases the difficulty of troubleshooting. By programmatically identifying and locating accessory instances, this addresses the core shortcomings of existing technologies, such as the tendency to overlook hidden accessories due to manual annotation and the arbitrary placement of legends, ensuring that the schematic diagram fully reflects the information of all functional components of the system.

[0059] In one embodiment of this specification, the first step is to identify attachment instances. The data entity of each riser in the target riser set is traversed, and the coordinates of its top connection point are extracted. Using the equipment connection relationship API of the building 3D model, a recursive search is performed for equipment family instances directly physically associated with that connection point. If the equipment family category attribute contains a preset exhaust valve keyword (such as...), the process is repeated. " AirReleaseValve ”If a pipe is identified as an exhaust valve instance, its corresponding riser identifier and 3D coordinates are recorded. The unique identifier of each pipe in the target horizontal main pipe set and appliance branch pipe set is traversed, and the model pipe accessory association interface is called to obtain all equipment instances installed along the pipe length. Equipment family category attributes are then matched to pressure gauges (e.g., "PressureGauge"). ” ) or butterfly valve (such as " ButterflyValve ” For each instance of the keyword, record its installation pipe identifier, offset along the pipe (percentage of the position from the pipe start point), and three-dimensional coordinates.

[0060] Next, calculate the coordinates of the two-dimensional legend. Based on the target riser identifier to which the air vent valve example belongs, locate the two-dimensional coordinates of the top endpoint of the riser (i.e., the upper endpoint of the vertical line segment of the riser) in the pipeline topology diagram. Draw the air vent valve symbol using this coordinate as the center point. Based on the installation pipe identifier in the attached example, locate the corresponding pipe segment in the pipeline topology diagram (horizontal main pipes are horizontal line segments, and appliance branch pipes are horizontal / broken line segments); calculate the legend position using the offset rate along the pipe. If the pipe is a straight line, calculate the coordinates of the point on the line segment by interpolation according to the offset rate; if it is a broken line, such as an upper-connected appliance branch pipe, first map it to the total length of the broken line, and then locate it according to the offset rate; draw the pressure gauge or butterfly valve legend with the calculation point as the center.

[0061] Finally, a legend layer is generated, and a preset symbol library (SVG vector graphics set) is called. The corresponding legend is selected according to the attachment type. In one example, the exhaust valve uses a "hollow triangle + exhaust arrow" symbol; the pressure gauge uses a "circular dial + pointer" symbol; and the butterfly valve uses a "diamond valve body" symbol. In addition to the above methods, other legends can also be selected for display. The legend is scaled to a preset size, and with the calculated coordinates as the center, the legend is overlaid on the pipeline topology diagram to establish the topological association data between the legend and the pipeline / riser, which facilitates subsequent labeling. Figure 6 This is a schematic diagram of a fire hydrant system provided in the embodiments of this specification. The final fire hydrant system schematic diagram is as follows: Figure 6 As shown.

[0062] By programmatically traversing pipe connections, the system indiscriminately identifies all accessory equipment conforming to the engineering definition, accurately locating even components hidden in ceilings or pipe racks, ensuring that drawings completely cover critical equipment. Strictly mapping the offset rate along the pipes in the 3D model to the 2D view ensures that the legend position accurately reflects the actual spatial relationships. When multiple accessories exist in densely packed pipe areas, the program can automatically fine-tune the legend position to avoid overlap, while maintaining its topological association with the pipes without intersecting. This dynamic layout capability makes the output drawings both information-rich and clearly readable.

[0063] The above technical solution constructs an automated data channel, realizing the automated and lossless mapping of 3D engineering semantics to 2D drawing specifications. The input end directly reads the geometric attributes (coordinates, angles) and engineering attributes (pipe diameter, equipment type) of the 3D model. The processing end generates functional pipelines through merging rules, outputs topology diagrams through mapping rules, and adds semantics through annotation rules. The output end is a vectorized schematic diagram, retaining the parametric association of all elements. When the model is modified, the drawings can be updated synchronously simply by re-executing the process, forming a positive cycle of model changes and automatic drawing updates, effectively improving efficiency. More importantly, it eliminates information attenuation caused by cross-stage translation, enabling the design intent to be transmitted to the construction stage without loss.

[0064] This specification also provides an embodiment of a device for generating a three-dimensional model of a fire hydrant system schematic diagram, such as... Figure 7 As shown, the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the above-described method.

[0065] This specification also provides a non-volatile computer storage medium storing computer-executable instructions configured to perform the above-described method.

[0066] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0067] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0068] The devices, media, and methods provided in the embodiments of this specification are one-to-one correspondences. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0069] Those skilled in the art will understand that embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0070] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0071] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0072] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0073] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0074] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0075] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0076] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Without further limitation, the phrase "comprising a…" … ” The definition of a specific element does not preclude the presence of other identical elements in the process, method, product, or apparatus that includes the element.

[0077] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A method for generating a schematic diagram of a three-dimensional fire hydrant system, characterized in that, The method includes: The system obtains the target schematic diagram generation parameters triggered by the user through a preset graphical user interface. The target schematic diagram generation parameters include at least one target fire hydrant system, connection method, and labeling setting parameters corresponding to the target schematic diagram. Based on at least one target fire hydrant system corresponding to the target schematic diagram, instances are extracted in a pre-acquired 3D building model to determine multiple target fire hydrant instances and fire hydrant attribute information corresponding to each target fire hydrant instance, wherein the fire hydrant attribute information includes spatial location information, fire hydrant height information, and a set of connecting pipes; Based on the set of connecting pipes, each connecting pipe is traversed in the three-dimensional building model to perform a pipe merging and connection operation based on the target fire hydrant instance, thereby determining multiple sets of functional pipes, wherein the functional pipes include risers, horizontal main pipes and appliance branch pipes. By using the multiple functional pipe sets, the connection method, and the preset drawing rules, a pipeline topology diagram is generated. Based on the annotation setting parameters, the pipeline topology diagram is set to generate a fire hydrant system schematic diagram corresponding to the building 3D model. A pipeline topology diagram is generated using the multiple functional pipeline sets, the pipe connection methods, and preset drawing rules, specifically including: Extract the floor elevation value and floor identifier for each floor from the 3D building model; Based on the total number of risers in the target riser set, the total length of the elevation line is determined, and parallel lines with equal spacing are generated according to the floor order corresponding to the floor identifiers and floor elevation identifiers are marked to generate a floor elevation line layer. Based on each target riser in the target riser set and the floor elevation marker, the fire hydrant instance is located, and the coordinates of the fire hydrant's center position are determined. By using the multiple functional pipe sets and the pipe connection method, a pipe connection layer between the multiple functional pipes is determined, so as to generate a pipeline topology map based on the floor elevation line layer, the fire hydrant center position coordinates and the pipe connection layer. By using the multiple functional pipeline sets and the pipe connection method, the pipeline connection layers between the multiple functional pipelines are determined, specifically including: The closed loop formed by the target riser assembly and the target horizontal trunk assembly is detected. Risers belonging to the same closed loop are arranged horizontally at a preset first spacing, and riser groups belonging to different closed loops are arranged horizontally at a preset second spacing. Based on the aforementioned pipe connection method and equipment branch pipe set, determine the connection line between each target equipment branch pipe and the target fire hydrant to connect the target equipment branch pipe and the target fire hydrant, and connect the corresponding riser axis endpoints at both ends of the horizontal main pipe in the target horizontal main pipe set through a horizontal straight line.

2. The method for generating a schematic diagram of a three-dimensional fire hydrant system according to claim 1, characterized in that, Based on the set of connecting pipes, each connecting pipe is traversed in the 3D building model to perform a pipe merging and connection operation based on the target fire hydrant instance, thereby determining multiple functional pipes, specifically including: In the building 3D model, each connecting pipe in the connecting pipe set is traversed, pipe segments with an angle less than a preset angle threshold and a length greater than a preset length threshold are extracted, continuous pipe segments with coincident geometric axes are merged, and a target riser set is output. The target riser set includes multiple target risers and the end connection relationship and riser spatial height data corresponding to each target riser. Based on the end connection relationship of each target riser, the riser end connection pipe corresponding to each target riser is determined, and continuous pipe segments are searched along the horizontal direction until the next target riser or pipe end is found. After merging, the target horizontal pipe set is determined. The target horizontal pipe set includes multiple target horizontal pipes and the end connection relationship and horizontal pipe spatial height data corresponding to each target horizontal pipe. Based on the set of connecting pipes corresponding to the target fire hydrant instance, the connecting pipes of the target fire hydrant instance are traversed to determine the set of target appliance branch pipes. The set of target appliance branch pipes includes multiple target appliance branch pipes and the endpoint connection fire hydrant instance identifier and appliance branch pipe spatial height data corresponding to each target appliance branch pipe.

3. The method for generating a schematic diagram of a three-dimensional fire hydrant system according to claim 2, characterized in that, Based on the set of connecting pipes corresponding to the target fire hydrant instance, the set of target appliance branch pipes is determined by traversing the connecting pipes of the target fire hydrant instance, specifically including: Starting from the connecting pipe of the target fire hydrant instance, the search path is determined by searching segment by segment along the pipe topology path; The search path terminates when it encounters the endpoint of the target riser or the endpoint of the target horizontal main pipe, and all pipe segments corresponding to the search path are merged into a single appliance branch pipe. The endpoint connection of each single appliance branch pipe to the fire hydrant instance and the spatial height data of the appliance branch pipe are recorded.

4. The method for generating a schematic diagram of a three-dimensional fire hydrant system according to claim 1, characterized in that, Detecting the closed loop formed by the target riser assembly and the target horizontal trunk assembly specifically includes: Obtain the riser space height data of each target riser in the target riser set and the horizontal pipe space height data of each target horizontal pipe in the target horizontal pipe set; Based on the riser space height data or the horizontal trunk space height data, the designated target riser or designated target horizontal trunk with the lowest space height is taken as the starting node. Recursively traverse adjacent pipe nodes along the endpoint connection relationship of the specified target riser or the specified target horizontal trunk, generate a loop traversal path, and mark the visited nodes; When the loop traversal path returns to any visited node, the loop traversal path is marked as a closed loop.

5. The method for generating a schematic diagram of a three-dimensional fire hydrant system according to claim 1, characterized in that, After generating the pipeline topology diagram, the method further includes: Identify the instance of the exhaust valve connected to the top of the target riser in the 3D model of the building, and draw the exhaust valve symbol at the corresponding top coordinate position of the target riser; Identify pressure gauge and / or butterfly valve instances associated with the target horizontal main pipe or appliance branch pipe, and draw pressure gauge and / or butterfly valve legends at the midpoint coordinates of the corresponding target horizontal main pipe or appliance branch pipe.

6. The method for generating a schematic diagram of a three-dimensional fire hydrant system according to claim 1, characterized in that, Based on the annotation settings parameters, the pipeline topology diagram is set to generate a fire hydrant system schematic diagram corresponding to the building's 3D model, specifically including: Extract the floor elevation line layer and pipe connection layer from the pipeline topology diagram to determine the current floor elevation line corresponding to each target riser; When the annotation setting parameters include the riser diameter annotation instruction, the riser diameter text corresponding to the target riser is added at the midpoint of each current floor elevation line, offset by a preset radial distance in the vertical direction. When the annotation setting parameters include the horizontal trunk pipe diameter annotation instruction, the horizontal trunk pipe diameter text corresponding to the target horizontal trunk pipe is added at a preset distance offset from the midpoint of the line segment of each target horizontal trunk pipe along the vertical positive direction. When the annotation setting parameters include the instrument branch pipe diameter annotation instruction, the branch pipe diameter text is added at a preset distance offset in the vertical negative direction from the midpoint of the horizontal segment of each target instrument branch pipe.

7. A device for generating a schematic diagram of a three-dimensional fire hydrant system, characterized in that, The device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method as described in any one of claims 1-6.

8. A non-volatile computer storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are configured to perform the method as described in any one of claims 1-6.

Images