A graphic display device for fire control room and its automatic graphic import method and device.

Abstract

This application provides a graphic display device for a fire control room and its automatic graphic import method and apparatus, relating to the field of fire control, and solves the technical problems of low integration of graphics and data, poor visualization effect, and inconvenience in locating and retrieving fire component information. The method includes: receiving a building floor plan file in WMF or BMP format; generating a tree directory in a plane coordinate system through file naming rules and format verification; extracting icon points and text coordinates to construct an adjacency matrix; recursively traversing the adjacency matrix to associate the text of machine numbers, loops, and addresses with icon points to form an association information table; importing the component information tables of programmed fire alarm controllers and fire linkage controllers and comparing them with the association information table; filtering coordinate data from the component information table that matches the association information table; injecting the coordinate data into the association information table; and embedding the tree directory for displaying the fire control diagram. This application is used in fire control processes.

Description

Technical Field

[0001] This application relates to the field of fire control, and in particular to a graphic display device for a fire control room and a method and apparatus for automatically importing graphics. Background Technology

[0002] As the core equipment of the fire control room graphic display device (CRT), it plays a crucial role in centrally monitoring the distribution and real-time status of fire protection facilities within a building. Currently, before being put into use, existing fire control room graphic display devices and systems require manual programming operations such as importing building floor plans and installing fire component icons. This process is prone to problems such as chaotic file naming and incompatible formats due to a lack of unified file management and verification mechanisms, leading to difficulties in file retrieval. Furthermore, manual operation is inefficient and prone to import errors due to human error. When installing component icons on the building floor plan, it is necessary to manually identify the icon locations and textual coordinate information such as machine numbers, circuits, and addresses of fire components from CAD drawings. This not only relies on the experience of staff and has a high rate of human error, but also requires manually establishing the association between textual information and icon locations, which is time-consuming and labor-intensive. At the same time, manual operation makes it difficult to achieve accurate coordinate data conversion and spatial relationship modeling. Moreover, when matching the programmed component information of the controller with the icon information in the floor plan, data discrepancies are prone to occur, often requiring reprogramming, further increasing the workload and the probability of errors. Summary of the Invention

[0003] This application provides a graphic display device for a fire control room and its automatic graphic import method and apparatus, which solves the technical problems of low integration of graphics and data, poor visualization effect, and inconvenience in locating and retrieving fire component information in the prior art.

[0004] To achieve the above objectives, this application adopts the following technical solution: Firstly, a graphic display device for a fire control room and its automatic graphic import method include: receiving a building floor plan file in WMF or BMP format; generating a tree directory in a plane coordinate system by passing file naming rules and format verification; parsing the DXF file in the building floor plan file to extract icon points and text coordinates, and constructing an adjacency matrix; recursively traversing the adjacency matrix to associate the text of machine numbers, loops, and addresses with icon points to form an association information table; importing the component information tables of programmed fire alarm controllers and fire linkage controllers and comparing them with the association information table; filtering coordinate data from the component information table that matches the association information table and injecting it into the association information table; discarding any remaining information that does not match the association information table; the component information table contains machine number, loop, and address information; and embedding the association information table containing the injected coordinate data into the tree directory for displaying the fire control diagram.

[0005] Based on the above technical solution, in the fire control room graphic display device and its automatic graphic import method provided in this application, compliant files are automatically filtered through file naming rules and format verification mechanisms, and a tree-like directory structure is generated with the project name as the root node and the building and building floor plan as secondary nodes. This allows for intelligent organization and rapid retrieval of floor plan files, solving the problems of chaotic file management, low efficiency, and error-prone manual import in the prior art. Simultaneously, by parsing the DXF file to extract icon points and text coordinates (including machine number, loop, and address), and performing a dual-scale coordinate transformation to convert vector coordinates into screen pixel coordinates, a normalized weighted adjacency matrix is ​​constructed based on Euclidean distance calculation, enabling accurate extraction of coordinate data and spatial relationship modeling. This reduces reliance on manual coordinate identification, lowers the error rate, and improves efficiency. Finally, intelligent association is performed through recursive traversal of the adjacency matrix (including weight calculation, sparsification, and iterative matching) to form an association information table containing machine number, loop, address, and coordinates. This table is then compared and matched with a pre-programmed component information table (based on item-by-item verification of machine number, loop, and address). Matching coordinate data is injected, and mismatched information is discarded, enabling automatic integration and autonomous consistency maintenance of fire protection component data, solving the problems of secondary programming and data disconnect. Furthermore, by embedding the association information table into a tree directory, automatic display of the fire control diagram is achieved, allowing for seamless overlay of graphics and data and rapid location, improving visualization and reducing retrieval difficulties.

[0006] In conjunction with the first aspect mentioned above, in one possible implementation, a tree directory is generated in a planar coordinate system through file naming rules and format validation. This includes: for WMF format files, verifying whether the key feature word in the PLACEABLEMETAHEADER structure of the file header is 9AC6CDD7h, and calculating the graphic width n based on the Left, Top, Right, Bottom, and Inch parameters in the PLACEABLEMETAHEADER structure. Width And graphic height n Height , make the graphic width n Width And graphic height n Height Verify against the preset range of the screen's graphic display area. For BMP format files, verify that the feature word in the tagBITMAPINFOHEADER structure at the file header is 424Dh, and read the graphic width bi from the tagBITMAPINFOHEADER structure. Width and graphic height bi Height Get the screen pixel width h width and screen pixel height h Height ,pass and Calculate the pixel deviation C between the BMP file and the screen pixels.x and C y The deviation value C x and C y The file is validated against a preset range. If the graphic size and pixel count are within the preset range, no processing is performed; otherwise, it is discarded or replaced to obtain a compliant file. The compliant file's filename is then validated using regular expressions. If the filename conforms to the rules, no processing is performed; otherwise, it is renamed. The filename format is [Building Number, Floor Number, Attribute Identifier], where the building number ranges from [0, 4000], the floor number ranges from [-9, -1] or [1, 300], and the attribute identifier includes standard floor b, ground floor d, or mezzanine j. The compliant filenames are sorted using a bubble sort algorithm to generate a tree-like directory structure with the project name as the root node and buildings and building plans as secondary nodes.

[0007] In conjunction with the first aspect mentioned above, one possible implementation involves extracting icon points and text coordinates to construct an adjacency matrix, including: This process parses the location information and text coordinates of all fire-fighting component icons in the DXF file. The text coordinates include the machine number, circuit, and address. The parsed coordinates are deduplicated to remove duplicate coordinate data, reducing matching errors. Based on the width and height information of the DXF file and the graphic dimensions of the corresponding WMF or BMP format plan view, a two-scale coordinate transformation is performed to convert the original vector coordinates of the DXF file into pixel coordinates on the current computer screen. The Euclidean distance between the text coordinates and the fire-fighting icon locations is calculated, generating an adjacency matrix of distance relationships.

[0008] In conjunction with the first aspect mentioned above, one possible implementation involves performing a dual-scale coordinate transformation, which includes extracting the coordinate data X of each point in the dxf file. dxf and Y dxf Filter by minimum and maximum coordinate values ​​to determine the four corner coordinates, with minimum and maximum coordinate values ​​being MinX, MinY, MaxX, and MaxY, respectively. Based on these four corner coordinates, calculate the length of the DXF file. and width Based on the length of the dxf file and width The pixel size of the target screen area (screenwidth) pixe By horizontal scaling and vertical scaling ratio Establish mapping conversion rules between the DXF file coordinate system and the screen pixel coordinate system. Based on these rules, convert each original vector coordinate X in the DXF file... dxf and Y dxf pass and Convert to screen pixel coordinates X screen and Y screen This will be converted to screen pixel coordinates X. screen and Y screen Associated with the corresponding fire-fighting component icons and text information.

[0009] In conjunction with the first aspect mentioned above, one possible implementation involves calculating the Euclidean distance between text coordinates and fire icon locations to generate an adjacency matrix of distance relationships. This includes: calculating the Euclidean distance between all text coordinates and fire component icon locations, generating an initial adjacency matrix containing all distance relationships, where text coordinates include machine number, loop, and address. The Euclidean distance values ​​are mapped to the range [0,1] using minimum and maximum scaling methods, and the adjacency matrix is ​​normalized. Based on the normalized distance values, a weighted adjacency matrix is ​​constructed with text coordinates as rows and icon locations as columns, where the weight is the reciprocal of the Euclidean distance, with closer distances resulting in higher weights. Edges with weights below a preset threshold are removed, retaining only the associated text-to-icon location relationships. The weighted adjacency matrix is ​​then sparsified to obtain an adjacency matrix where each text coordinate is associated only with its closest icon location.

[0010] In conjunction with the first aspect mentioned above, one possible implementation involves recursively traversing the adjacency matrix to associate the text of the machine number, loop, and address with the icon points, forming an association information table. This includes: based on a weighted adjacency matrix after normalization and sparsification, recursively searching for the associated icon point with the highest weight, starting with the text coordinates, to establish a preliminary matching relationship. If the same icon point is associated with multiple text coordinates, the normalized distance weight between each text coordinate and the icon point is calculated, retaining only the association with the highest weight and dissolving other associations. For unmatched text coordinates and icon points, the Euclidean distance between them and the remaining points is recalculated, the adjacency matrix is ​​updated, and the recursive matching process is iteratively executed until all text coordinates are associated with a unique icon point or no further matching is possible. Based on the final matching results, an association information table containing the machine number, loop, address, and corresponding icon point coordinates is generated. The association information table also includes a matching confidence index and a flag indicating whether manual intervention is required.

[0011] In conjunction with the first aspect mentioned above, one possible implementation involves filtering coordinate data from the component information table that matches the associated data table and injecting it into the associated information table. This includes: traversing the component information tables of the programmed fire alarm controllers and fire linkage controllers to extract the machine number, circuit, and address information. The extracted machine number, circuit, and address information are then matched item by item with the corresponding fields in the associated information table. If a record in the component information table completely matches the machine number, circuit, and address in the associated information table, the coordinate data corresponding to that record is injected into the corresponding field of the associated information table. If a record in the component information table has no matching entry in the associated information table, it is considered invalid data and discarded, generating the final associated information table after the coordinate data has been injected.

[0012] In conjunction with the first aspect mentioned above, one possible implementation involves embedding the associated information table (after injecting coordinate data) into a tree directory. This includes: associating the coordinate data in the associated information table with the corresponding building floor plan nodes in the tree directory based on the node structure of the tree directory; creating an independent layer storage space for each floor plan node, and storing the coordinate data in the associated information table hierarchically according to machine number, circuit, and address information; establishing a fast index relationship between the machine number, circuit, and address combination in the associated information table and the tree directory nodes through hash mapping; converting the screen pixel coordinates in the associated information table into the relative coordinate system corresponding to the tree directory nodes and injecting them into the layer storage space; dynamically loading the coordinate data of the corresponding layer in the graphical display interface based on the selection status of the tree directory node, and rendering the fire protection component icons to the specified positions on the building floor plan; and supporting the display of multiple layers of fire protection component icons within the tree directory after embedding the associated information table, and overlaying the icons with the floor plan through coordinate mapping, enabling quick location and retrieval of associated fire protection component information by the tree directory nodes.

[0013] In conjunction with the first aspect mentioned above, in one possible implementation, after the associated information table with injected coordinate data is embedded in the tree directory, it also includes: real-time calculation of the screen pixel coordinates (X, Y, X) of each fire-fighting component icon in the associated information table. screen ,Y screen） The offset error (ΔX, ΔY) between the corresponding theoretical position in the architectural floor plan WMF or BMP file and its actual position, where ΔX = |X screen X 理论 |,ΔY=|Y screen Y 理论| If the offset error (ΔX, ΔY) exceeds the preset tolerance threshold, an offset warning is generated, and the offset fire component icon is highlighted in the graphical display interface. If multiple offset warnings exist, the offset fire component icons are highlighted sequentially in the graphical display interface via scrolling. A graphical fine-tuning interface is provided, which receives drag-and-drop adjustment commands from the user based on the offset warning to adjust the coordinates of the fire component icon, and updates the adjusted coordinate data to the associated information table and the corresponding tree directory layer storage space.

[0014] Based on the final matching results, a success rate report is automatically generated. The report includes the total number of parts, the number of automatically matched parts, the number of matched parts that failed, the number of parts that require manual adjustments, and the overall matching success rate percentage.

[0015] Secondly, a graphic display device for a fire control room and its automatic graphic import device are provided, comprising: a communication unit and a processing unit; the communication unit is used to receive architectural floor plan files in WMF or BMP format; the processing unit is used to generate a tree directory in a plane coordinate system by verifying file naming rules and format. The DXF file in the architectural floor plan file is parsed to extract icon points and text coordinates, and an adjacency matrix is ​​constructed. By recursively traversing the adjacency matrix, the text of machine number, loop, and address is associated with the icon points to form an association information table. The component information tables of the programmed fire alarm controller and fire linkage controller are imported and compared with the association information table. Coordinate data matching the association information table is selected from the component information table and injected into the association information table; the remaining information that does not match the association information table is discarded. The component information table contains machine number, loop, and address information. The association information table with injected coordinate data is embedded in the tree directory for displaying the fire control diagram.

[0016] Thirdly, this application provides a graphic display device for a fire control room and an automatic graphic import device thereof, comprising: a processor and a storage medium; the storage medium includes instructions, and the processor is used to execute the instructions to implement the method described in the first aspect and any possible implementation thereof. The graphic display device for the fire control room and its automatic graphic import device may be an electronic device or a chip within an electronic device.

[0017] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on the fire control room graphic display device and its automatic graphic import device, cause the fire control room graphic display device and its automatic graphic import device to perform the methods described in the first aspect and any possible implementation thereof.

[0018] Fifthly, this application provides a computer program product containing instructions that, when the computer program product is run on the fire control room graphic display device and its automatic graphic import device, cause the fire control room graphic display device and its automatic graphic import device to perform the methods described in the first aspect and any possible implementation of the first aspect.

[0019] This application provides a graphic display device for a fire control room and its automatic graphic import method and apparatus. It can automatically filter compliant files through file naming rules and format verification mechanisms, and generate a tree-like directory structure with the project name as the root node and buildings and building floor plans as secondary nodes. This allows for intelligent organization and rapid retrieval of floor plan files, solving the problems of chaotic file management, low efficiency, and error-prone manual import in existing technologies. Simultaneously, it extracts icon points and text coordinates (including machine number, loop, and address) from DXF files, performs a dual-scale coordinate transformation to convert vector coordinates to screen pixel coordinates, and then constructs a normalized weighted adjacency matrix based on Euclidean distance calculation. This enables accurate extraction of coordinate data and spatial relationship modeling, thereby reducing... This approach reduces reliance on manual coordinate identification, lowers error rates, and improves efficiency. Finally, intelligent association is achieved through recursive traversal of the adjacency matrix (including weight calculation, sparsity processing, and iterative matching), forming an association information table containing machine number, loop, address, and coordinates. This table is then compared and matched with a pre-programmed component information table (based on item-by-item verification of machine number, loop, and address). Matching coordinate data is injected, and mismatched information is discarded, enabling automatic integration and autonomous consistency maintenance of fire protection component data, resolving issues of secondary programming and data disconnect. Furthermore, by embedding the association information table into a tree directory, automatic display of fire control diagrams is achieved, allowing for seamless overlay of graphics and data and rapid location, improving visualization and reducing retrieval difficulties.

[0020] It should be understood that the descriptions of technical features, technical solutions, beneficial effects, or similar language in this application do not imply that all features and advantages can be achieved in any single embodiment. Rather, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution, or beneficial effect is included in at least one embodiment. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions, and beneficial effects described in this embodiment can be combined in any suitable manner. Those skilled in the art will understand that embodiments can be implemented without one or more specific technical features, technical solutions, or beneficial effects of a particular embodiment. In other embodiments, additional technical features and beneficial effects may be identified in specific embodiments that do not embody all embodiments. Attached Figure Description

[0021] Figure 1A system architecture diagram of a fire control room graphic display device and its automatic graphic import system provided in this application embodiment; Figure 2 A flowchart illustrating a graphic display device for a fire control room and its automatic graphic import method, provided as an embodiment of this application; Figure 3 A flowchart illustrating another fire control room graphic display device and its automatic graphic import method provided in this application embodiment; Figure 4 A flowchart illustrating another fire control room graphic display device and its automatic graphic import method provided in this application embodiment; Figure 5 A flowchart illustrating another fire control room graphic display device and its automatic graphic import method provided in this application embodiment; Figure 6 A flowchart illustrating another fire control room graphic display device and its automatic graphic import method provided in this application embodiment; Figure 7 This is a schematic diagram of the structure of a graphic display device for a fire control room and its automatic graphic import device, provided in an embodiment of this application. Detailed Implementation

[0022] In the description of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences.

[0023] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0024] To address the shortcomings of existing technologies in importing and managing building floor plans, such as the lack of unified and standardized file naming rules and format verification mechanisms, manual import of floor plans often suffers from inefficiencies and errors. These problems include filenames that do not conform to the actual building numbers, floor numbers, and attribute identifiers, mismatched key features in file formats (e.g., WMF, BMP), and poor compatibility of graphic sizes with screen display areas. Secondly, in the extraction and processing of fire protection component information, the lack of data processing methods when extracting icon locations, machine numbers, circuits, addresses, and other textual coordinate information from the DXF files associated with the building floor plans leads to duplicate coordinate data causing subsequent matching errors. Furthermore, the absence of standardized coordinate transformation methods makes it difficult to accurately convert the original vector coordinates of the DXF files into pixel coordinates on the computer screen, relying solely on manual identification and conversion, resulting in a high error rate and significantly reduced work efficiency. Furthermore, in terms of text and icon point association and data matching, the association is mostly established manually, which is time-consuming, labor-intensive, and prone to errors. Simultaneously, when matching the component information of programmed fire alarm controllers and fire linkage controllers with the component information in the floor plan, there is a lack of automated comparison and verification and data integration mechanisms, leading to data discrepancies and often requiring reprogramming. Finally, in terms of graphic display and information interaction, the effective integration of component coordinate data and tree directory cannot be achieved, making seamless overlay of graphics and data difficult and resulting in poor visualization of fire control diagrams. This application provides a fire control room graphic display device and its automatic graphic import method. This method automatically filters compliant files through file naming rules and format verification mechanisms, and generates a tree directory structure with the project name as the root node and buildings and building floor plans as secondary nodes. This allows floor plan files to be intelligently organized and quickly retrieved, solving the problems of chaotic file management, low efficiency, and error-prone manual import in the prior art. Simultaneously, it extracts icon point and text coordinates (including machine number, loop, and address) by parsing DXF files, performs dual-scale coordinate transformation to convert vector coordinates into screen pixel coordinates, and then calculates based on Euclidean distance. A normalized weighted adjacency matrix is ​​constructed to enable accurate extraction of coordinate data and spatial relationship modeling, thereby reducing reliance on manual coordinate identification, lowering the error rate, and improving efficiency. Finally, intelligent association is performed through recursive traversal of the adjacency matrix (including weight calculation, sparsity processing, and iterative matching) to form an association information table containing machine number, loop, address, and coordinates. This table is then compared and matched with a pre-programmed component information table (based on item-by-item verification of machine number, loop, and address). Matching coordinate data is injected, and mismatched information is discarded, enabling automatic integration and autonomous consistency maintenance of fire protection component data, solving the problems of secondary programming and data disconnect. Furthermore, by embedding the association information table into a tree directory, automatic display of fire control diagrams is achieved, allowing seamless overlay of graphics and data and rapid location, improving visualization and reducing retrieval difficulties.

[0025] like Figure 1 As shown in the embodiment of this application, a graphic display device for a fire control room and its automatic graphic import method are provided, including: Step 101: Receive architectural floor plan files in WMF or BMP format, and generate a tree directory in the plane coordinate system by passing the file naming rules and format verification.

[0026] WMF is a Windows metafile format used to store vector graphics. BMP is a bitmap image file format that supports lossless storage. Architectural floor plan files are graphic files containing architectural layout information. File naming rules specify the format that filenames must follow, such as a combination of building number, floor number, and attribute identifiers. Format validation is the process of verifying whether the file type and size conform to preset standards. A plane coordinate system is a two-dimensional coordinate system used to locate graphic elements. A tree directory is a hierarchical structure used to organize files based on project and architectural information.

[0027] In some implementations, the system first receives architectural floor plan files in WMF or BMP format, verifies the WMF and BMP files, and removes or replaces files whose size or pixel deviation exceeds a preset range to obtain format-compliant files. Then, regular expressions are used to verify the compliance of the file names. Non-compliant files are renamed. Finally, the compliant file names are sorted using a bubble sort algorithm to generate a tree-like directory structure with the project name as the root node and the buildings and architectural floor plans as secondary nodes.

[0028] It should be noted that file naming rules and format verification ensure the standardization and compatibility of floor plan files, avoiding import failures due to file format or naming errors. Furthermore, during the verification process, the preset ranges for graphic dimensions and pixel deviations need to be adjusted according to the actual screen resolution to ensure optimal display quality.

[0029] Step 102: Parse the dxf file in the building floor plan, extract the icon points and text coordinates, and construct the adjacency matrix.

[0030] DXF files are a CAD data exchange format used to store graphic information. Icon points are the coordinates of the fire protection component icons on the floor plan. Text coordinates are the coordinates of text elements labeling machine numbers, circuits, and addresses. The adjacency matrix is ​​a matrix representing the Euclidean distance relationship between text coordinates and icon points.

[0031] In some implementations, the system first parses the DXF file in the building floor plan file, extracting the point information and text coordinate information of all fire-fighting component icons. The extracted coordinate information is then deduplicated to remove duplicate coordinate data and reduce matching errors. Next, based on the length and width information of the DXF file and the graphic size of the corresponding WMF or BMP format floor plan, a dual-scale coordinate transformation is performed to convert the original vector coordinates of the DXF file into pixel coordinates on the current computer screen. Finally, the Euclidean distance between all text coordinates and fire-fighting icon points is calculated, generating an initial adjacency matrix containing all distance relationships. The Euclidean distance values ​​are then normalized to the range [0,1] using minimum and maximum scaling methods. Based on the normalized distance values, a weighted adjacency matrix is ​​constructed with text coordinates as rows and icon points as columns. Edges with weights below a preset threshold are then removed, and the weighted adjacency matrix is ​​sparsified to obtain an adjacency matrix where each text coordinate is associated only with its closest icon point.

[0032] It should be noted that deduplication is performed to avoid matching errors caused by duplicate coordinate data in the drawings and to ensure data accuracy. The construction of the adjacency matrix relies on Euclidean distance calculation, normalization and sparsification to improve matching efficiency, but the preset threshold setting needs to be adjusted according to the actual application to avoid over-matching or under-matching.

[0033] Step 103: By recursively traversing the adjacency matrix, associate the text of the machine number, loop, and address with the icon points to form an association information table. Recursive traversal is an algorithmic technique that iterates through data structures such as matrices by repeatedly calling itself. The machine number is a unique identifier for the fire alarm controller. A loop is a numbered internal circuit path within the controller. An address is the location of a component within a specific loop. Text refers to the textual information of the machine number, loop, and address labeled in the DXF file. The association information table is a data structure used to store the matching relationships between machine numbers, loops, addresses, and corresponding icon locations, along with additional information.

[0034] In some implementations, based on a weighted adjacency matrix after normalization and sparsification, the system recursively searches for the associated icon point with the highest weight, starting with the text coordinates, to establish a preliminary matching relationship. If the same icon point is associated with multiple text coordinates, the normalized distance weight between each text coordinate and the icon point is calculated, and only the association with the text coordinate with the highest weight is retained, while other associations are removed. Then, for the text coordinates and icon points that have not been successfully matched, the Euclidean distance between them and the remaining points is recalculated, the adjacency matrix is ​​updated, and the recursive matching process is iteratively executed until all text coordinates are associated with a unique icon point or no further matching is possible. Finally, based on the final matching results, an association information table containing the machine number, loop, address, and corresponding icon point coordinates is generated.

[0035] Step 104: Import the component information table of the programmed fire alarm controller and fire linkage controller and compare it with the associated information table. Filter the coordinate data that matches the associated data table from the component information table and inject it into the associated information table. Discard the remaining information that does not match the associated information table. The component information table contains machine number, circuit and address information.

[0036] Among them, a programmed fire alarm controller is a fire alarm control device whose components have been programmed. A fire linkage controller is a control device that controls the linkage of fire-fighting equipment. A component information table is a table that stores programming information for all components in the controller, including data such as machine number, circuit, and address. Coordinate data refers to the specific location information of the component in the graphic. Injection refers to the operation of adding successfully matched coordinate data to the associated information table. Discard refers to the direct deletion of data that cannot be matched.

[0037] In some implementations, the component information tables of pre-programmed fire alarm controllers and fire-fighting linkage controllers are imported. These tables contain complete component programming information such as component number, circuit, and address. Then, coordinate data matching the associated data table can be filtered from the component information table and injected into the associated information table, including: Iterate through the component information tables of the programmed fire alarm controllers and fire linkage controllers to extract the machine number, circuit, and address information.

[0038] The extracted machine number, circuit, and address information are matched item by item with the corresponding fields in the associated information table.

[0039] If a record in the component information table is completely consistent with the machine number, circuit, and address in the associated information table, then the coordinate data corresponding to that record will be injected into the corresponding field of the associated information table.

[0040] If a record in the component information table has no matching item in the associated information table, it is determined to be invalid data and discarded directly, and the final associated information table after injecting coordinate data is generated.

[0041] It should be noted that the matching process requires the machine number, loop, and address to be completely consistent to ensure the accuracy of data association.

[0042] Step 105: Embed the associated information table of the injected coordinate data into the tree directory for displaying the fire control diagram.

[0043] Embedding refers to the operation of integrating data from the associated information table into the tree directory node. Displaying the fire control diagram refers to rendering fire component icons onto the building floor plan in the graphical interface for monitoring and display.

[0044] In some implementations, based on the node structure of a tree directory, the coordinate data in the associated information table after the coordinate data is injected is associated with the corresponding building floor plan nodes in the tree directory. Then, an independent layer storage space is created for each floor plan node, and the coordinate data in the associated information table is stored hierarchically according to the machine number, circuit, and address information. Next, a fast index relationship between the machine number, circuit, and address combination in the associated information table and the tree directory node is established through hash mapping. Then, the screen pixel coordinates in the associated information table are converted into the relative coordinate system corresponding to the tree directory node and injected into the layer storage space. Finally, in the graphical display interface, the coordinate data of the corresponding layer is dynamically loaded according to the selection status of the tree directory node, and the fire protection component icons are rendered to the specified positions on the building floor plan to realize the display of the fire control diagram. Moreover, each floor plan node in the tree directory after embedding the associated information table supports the display of multiple layers of fire protection component icons, and the icons are superimposed on the floor plan through the coordinate mapping relationship, which supports the quick location and retrieval of associated fire protection component information by the tree directory node.

[0045] Based on the above technical solution, compliant files are automatically filtered through file naming rules and format verification mechanisms, and a tree-like directory structure is generated with the project name as the root node and buildings and building floor plans as secondary nodes. This allows for intelligent organization and rapid retrieval of floor plan files, solving the problems of chaotic file management, low efficiency, and error-prone manual import in existing technologies. Simultaneously, icon points and text coordinates (including machine number, loop, and address) are extracted by parsing DXF files, and a dual-scale coordinate transformation is performed to convert vector coordinates to screen pixel coordinates. Then, a normalized weighted adjacency matrix is ​​constructed based on Euclidean distance calculation, enabling accurate extraction of coordinate data and spatial relationship modeling. This reduces the reliance on manual coordinate identification and lowers costs. Low error rate improves efficiency; finally, intelligent association is performed by recursively traversing the adjacency matrix (including weight calculation, sparsification, and iterative matching) to form an association information table containing machine number, loop, address, and coordinates. This table is then compared and matched with the pre-programmed component information table (based on item-by-item verification of machine number, loop, and address). Matching coordinate data is injected, and mismatched information is discarded, enabling automatic integration and autonomous consistency maintenance of fire protection component data, thus solving the problems of secondary programming and data disconnect. In addition, by embedding the association information table into the tree directory, the automatic display of the fire control diagram is achieved, allowing for seamless overlay of graphics and data and rapid location, improving the problem of poor visualization and reducing the inconvenience of retrieval.

[0046] In one possible implementation of the embodiments of this application, combined with Figure 1 ,like Figure 2 As shown, generating a tree directory in a planar coordinate system by passing file naming rules and format validation can be achieved through the following steps 201 to 206, which are explained in detail below: Step 201: For WMF format files, verify whether the key feature word in the PLACEABLEMETAHEADER structure in the file header is 9AC6CDD7h, and calculate the graphic width n based on the Left, Top, Right, Bottom, and Inch parameters in the PLACEABLEMETAHEADER structure. Width And graphic height n Height , make the graphic width n Width And graphic height n Height Verify with the preset range of the screen's graphic display area.

[0047] The PLACEABLEMETAHEADER structure is the Windows metafile header structure, used to store metafile metadata, including fields such as Key, Handle, Left, Top, Right, Bottom, and Inch. The key identifier 9AC6CDD7h is the identifier for the WMF file, represented in hexadecimal, used to verify the file type. Left, Top, Right, and Bottom are the coordinate values ​​in metafile units, representing the left, top, right, and bottom boundaries of the graphic, respectively. The Inch parameter represents the metafile unit per inch, used for unit conversion. The graphic width n... Width And graphic height n Height The physical size (in millimeters) is calculated to represent the actual size of the graphic. The preset range of the screen graphic display area is a limitation of the display area of ​​the CRT screen, used to ensure that the graphic size fits the display effect and avoids exceeding a reasonable range.

[0048] In some implementations, the PLACEABLEMETAHEADER structure at the beginning of the WMF file is first read. The Key field is extracted and its value is checked to see if it is 9AC6CDD7h (hexadecimal). If it matches, the file format is correct, and no further processing is performed; otherwise, the file is considered invalid and discarded. Then, based on the Left, Top, Right, Bottom, and Inch parameters in the PLACEABLEMETAHEADER structure, the formula n is used... Width =(Right-Left) 25.4 / Inch and n Height =(Bottom-Top) 25.4 / Inch calculates the width and height of the graphic. Then, the calculated n... Width and n HeightThe value is compared with the preset range of the screen's graphic display area. If the graphic size is within the preset range (not exceeding twice the screen display area), the file is qualified and no further processing is required. If it exceeds the preset range, it is rejected or replaced. This ensures that the graphic will not be difficult to recognize or display abnormally due to scaling when displayed on the CRT screen.

[0049] Step 202: For BMP format files, verify whether the feature word in the tagBITMAPINFOHEADER structure at the file header is 424Dh, and read the graphic width bi from the tagBITMAPINFOHEADER structure. Width and graphic height bi Height .

[0050] The tagBITMAPINFOHEADER structure is a bitmap header structure used to store metadata for BMP format files, including bi Size bi Width bi Height Fields such as 424Dh. The feature word 424Dh is the identifier for the BMP file, represented in hexadecimal, located at the file header, used to verify the correct file type. The image width is determined by bi. Width The field indicates that the image width is defined as `inpixels`. The image height is defined by `bi`. Height The field indicates that the image height is inpixels.

[0051] In some implementations, the BMP file is opened and its header data is read. The feature word field in the `tagBITMAPINFOHEADER` structure is extracted, and its value is checked to see if it is 424Dh (hexadecimal). If it matches, the file is considered a valid BMP file and can proceed with further processing; otherwise, the file is invalid and must be discarded. Then, the `bi` keyword is read from the `tagBITMAPINFOHEADER` structure. Width andbi Height The values ​​of the fields are used to obtain the width and height of the graphic, which in turn represent the size of the image and are used for graphic display and coordinate transformation processing.

[0052] Step 203: Obtain the screen pixel width h width and screen pixel height h Height ,pass and Calculate the pixel deviation C between the BMP file and the screen pixels. x and C y The deviation value C x and C y Verify against the preset range.

[0053] Screen pixel width refers to the horizontal resolution of the computer screen, expressed in pixels as the width of the screen. Screen pixel height refers to the vertical resolution of the computer screen, expressed in pixels as the height of the screen. Deviation value C x and C y The scaling ratio is calculated by taking the ratio of the image pixel size of the BMP file to the screen pixel size. It is used to measure the degree of adaptation between the file pixels and the screen pixels. The preset range refers to a pre-set allowable deviation threshold range, used to determine whether the deviation value is within an acceptable range, to ensure that there are no distortion or mismatch issues when displaying graphics.

[0054] In some implementations, the pixel width h of the current computer screen is first read directly from the screen display settings or system parameters. width and pixel height h Height This is used as the baseline size. Then, based on the graphic width bi of the read BMP format file... width and graphic height bi height Through formula and Calculate the horizontal deviation value C x and vertical deviation value C y This represents the scaling ratio of the BMP file's pixel dimensions relative to the screen's pixel dimensions. Next, the calculated C... x and C y The value is checked against the preset range. If C x and C y If all values ​​are within the preset range (for example, the preset range might be defined as between 0.5 and 2.0), it indicates that the file pixels and screen pixels are well adapted, and no processing is required; if C x Or C y If the file exceeds the preset range, it will be removed or replaced to prevent the image from becoming blurry, distorted, or exceeding the screen boundary due to improper scaling.

[0055] Step 204: If the graphic size and pixels are within the preset range, no processing is performed; if they exceed the preset range, they are removed or replaced to obtain a compliant file.

[0056] The graphic dimensions refer to the calculated width and height of the graphic, expressed in millimeters for WMF files and in pixels for BMP files, representing the physical or logical size of the graphic. A pixel is the basic unit of digital images, used to quantify image resolution. The preset range is a pre-defined threshold interval based on screen display capabilities, used to determine whether graphic size or pixel deviation is within acceptable limits. A format-compliant file refers to a graphic file that meets system requirements after passing all verification steps and can be safely imported and used for subsequent processing.

[0057] Step 205: Perform compliance checks on the filenames of compliant files using regular expressions. If the filenames comply with the rules, no processing is performed. If the filenames do not comply with the rules, they should be renamed. The filename format is [building number, floor number, attribute identifier], where the building number ranges from [0, 4000], the floor number ranges from [-9, -1] or [1, 300], and the attribute identifier includes standard floor b, ground floor d, or mezzanine j.

[0058] Regular expressions are pattern tools used for string matching and validation, checking whether filenames conform to a predetermined format through specific syntax rules. Filename compliance verification refers to the programmatic process of verifying whether a filename meets specified naming conventions. Attribute identifiers are letter codes representing floor characteristics, including three types: standard floor (b), ground floor (d), and mezzanine floor (j). Renaming refers to the system automatically generating a new filename and replacing the original filename when the filename does not conform to the naming conventions.

[0059] In some implementations, the system parses the filenames of format-compliant files that have passed size verification. It uses a pre-designed regular expression pattern to match and verify the complete filename, strictly adhering to the format requirements of [building number, floor number, attribute identifier]. This allows the system to extract the three components of the filename: building number, floor number, and attribute identifier. It verifies whether the building number is an integer between 0 and 4000, whether the floor number is an integer between -9 and -1 or 1 and 300, and whether the attribute identifier is any character from b, d, or j. If all verification conditions are met, the filename is deemed compliant, and the system retains the original filename without any further processing. If any verification condition is not met, the system automatically performs a renaming operation, generating a new filename according to the actual file attributes and naming rules (e.g., correcting "1-5-c" to "1-5-b"), ensuring the filename fully complies with the specifications.

[0060] Step 206: Sort compliant file names using the bubble sort algorithm to generate a tree-like directory structure with the project name as the root node and buildings and building floor plans as secondary nodes.

[0061] The bubble sort algorithm is a simple sorting algorithm that sorts elements by repeatedly comparing adjacent elements and swapping their order. A compliant filename refers to a filename that passes format validation and conforms to naming rules, with the format [building number, floor number, attribute identifier]. The project name refers to the name of the fire protection project, serving as the top-level node in the tree-like directory. A building refers to a specific individual building, identified by its building number, serving as a second-level node in the tree-like directory. A building floor plan refers to a specific floor plan file, serving as the bottom-level node in the tree-like directory. The tree-like directory structure is a hierarchical data structure that starts with a root node and connects nodes through parent-child relationships to form a tree-like hierarchy.

[0062] In some implementations, after obtaining all valid filenames, a bubble sort algorithm is used to sort these filenames. The sorting rules are based on the priority of building number, floor number, and attribute identifiers. First, files are sorted by building number in ascending order. For files with the same building number, they are then sorted by floor number (negative floors take precedence over positive floors, and the numbers are sorted in ascending order). Finally, they are sorted by the order of attribute identifiers (b, d, j). After sorting, a directory structure can be created using the project name as the root node. Then, the building number information is extracted from the sorted filenames, and a building child node is created for each unique building number and attached to the root node. Finally, under each building node, a corresponding building floor plan child node is created according to the sorting results. The node name is the original filename, thus generating a hierarchical and ordered tree-like directory structure, which facilitates users to browse and search according to the logical hierarchy of projects, buildings, and floor plans.

[0063] Based on the above technical solution, by verifying the file header structure and calculating the graphic size, deviations from the preset screen range can be checked to ensure that the graphic size is adapted to the display device, thereby automatically filtering out compliant files. Secondly, regular expressions are used to verify the compliance of filenames, and non-compliant files are automatically renamed to achieve standardization of file naming. Finally, a bubble sort algorithm is used to sort compliant filenames and generate a tree-like directory structure with the project name as the root node and buildings and building floor plans as secondary nodes, thus achieving intelligent organization and rapid retrieval of files. This allows the entire process to work together to automate file processing, reducing manual intervention, improving data accuracy and integration, and solving the problems of chaotic file management, low efficiency of manual import, susceptibility to errors, and high errors in manual coordinate identification in existing technologies.

[0064] In one possible implementation of this application embodiment, extracting icon points and text coordinates and constructing an adjacency matrix can be achieved through the following steps 301 to 304, which are described in detail below: Step 301: Parse the location information and text coordinate information of all fire-fighting component icons in the DXF file. The text coordinate information includes the machine number, circuit, and address.

[0065] Among them, fire protection component icons refer to graphic elements representing fire protection equipment such as heat detectors and smoke detectors. Location information refers to the coordinates of the icon on the floor plan. Text coordinate information refers to the coordinates of text labels such as serial number, circuit, and address. The serial number is the unique identifier of the fire alarm controller, the circuit is the number of the internal circuit path of the controller, and the address is the location identifier of the component within a specific circuit.

[0066] Step 302: Deduplicate the parsed coordinate information to remove duplicate coordinate data in order to reduce matching errors.

[0067] Deduplication refers to the process of removing duplicate coordinate values ​​from the data, thereby eliminating redundancy. Duplicate coordinate data refers to the occurrence of the same coordinate value multiple times in the parsing results due to technical errors or export mistakes. Matching error refers to the errors or decrease in accuracy caused by duplicate data in subsequent steps such as constructing the adjacency matrix or association matching.

[0068] In some implementations, duplicate coordinate points can be identified through algorithms, such as using hash tables or direct value comparisons to detect and remove identical coordinate entries; this ensures that only one instance of each unique coordinate is retained, reducing errors in subsequent adjacency matrix construction and icon association processes, and improving the accuracy and efficiency of data processing.

[0069] Step 303: Based on the width and height information of the DXF file and the graphic dimensions of the corresponding WMF or BMP format planar image, perform a dual-scale coordinate transformation to convert the original vector coordinates of the DXF file into pixel coordinates of the current computer screen.

[0070] Dual-scale coordinate transformation refers to the process of mapping and transforming coordinates based on two different scales (the vector coordinate scale of the DXF file and the pixel scale of the WMF and BMP planar images). Vector coordinates are point data represented in graphic units in the DXF file. Pixel coordinates are point data represented in pixels on the computer screen.

[0071] Performing a two-scale coordinate transformation includes: Extract the coordinate data X of each point in the dxf file dxf and Y dxf Filter the minimum and maximum coordinate values ​​to determine the coordinates of the four corners. The minimum and maximum coordinate values ​​are MinX, MinY, MaxX, and MaxY, respectively.

[0072] Calculate the length of a DXF file based on its four corner coordinates. and width .

[0073] Based on the length of the dxf file and width The pixel size of the target screen area (screenwidth) pixe By horizontal scaling and vertical scaling ratio Establish mapping and conversion rules between the DXF file coordinate system and the screen pixel coordinate system.

[0074] Based on the mapping conversion rules, each original vector coordinate X in the dxf file is... dxf and Y dxf pass and Convert to screen pixel coordinates X screen and Y screen .

[0075] This will be converted to screen pixel coordinates X. screen and Y screen Associated with the corresponding fire-fighting component icons and text information.

[0076] It should be noted that the dual-scale coordinate transformation relies heavily on the dimensional consistency between the DXF file and the plan view file. Inconsistencies may lead to coordinate shifts, requiring manual fine-tuning. If the DXF header file lacks the four corner coordinates, approximate calculations using all points are necessary, potentially introducing errors. For WMF files, the PLACEABLEMETAHEADER structure must be verified to ensure file validity. The transformed pixel coordinates must be associated with the fire-fighting component icons and text information to ensure the accuracy of subsequent steps.

[0077] Step 304: Calculate the Euclidean distance between the text coordinates and the fire icon locations, and generate an adjacency matrix of the distance relationships.

[0078] In this context, Euclidean distance refers to the straight-line distance between two points in a two-dimensional coordinate system. An adjacency matrix is ​​a matrix data structure where rows represent text coordinates (including machine number, circuit, and address information), columns represent fire icon locations, and matrix element values ​​represent the distance or weight relationship between them. Normalization is achieved by linearly transforming the original values ​​to the [0,1] interval using minimum and maximum scaling methods, thereby eliminating scale differences. A weighted adjacency matrix is ​​a form of adjacency matrix where element values ​​are not simple distances but weights, typically the reciprocal of the distance, with closer distances resulting in higher weights. Sparsity processing involves removing elements with weights below a preset threshold from the matrix, retaining only strongly related edges, making the matrix sparse and ensuring that each text coordinate is associated with only the single closest icon location.

[0079] Calculate the Euclidean distance between the text coordinates and the fire icon locations, and generate an adjacency matrix of distance relationships, including: Calculate the Euclidean distance between all text coordinates and fire component icon locations, and generate an initial adjacency matrix containing all distance relationships. The text coordinates include machine number, circuit, and address.

[0080] The adjacency matrix is ​​normalized by mapping the Euclidean distance values ​​to the range [0,1] using minimum and maximum scaling methods.

[0081] Based on the normalized distance values, a weighted adjacency matrix is ​​constructed with text coordinates as rows and icon positions as columns, where the weight is the reciprocal of the Euclidean distance, and the closer the distance, the higher the weight.

[0082] Edges with weights below a preset threshold are removed, and only the relationships between associated text and icon points are retained. The weighted adjacency matrix is ​​then sparsified to obtain an adjacency matrix in which each text coordinate is associated with only the closest icon point.

[0083] It should be noted that normalization is used to ensure that distance values ​​are compared within the same range, thus avoiding bias caused by different coordinate scales. Since closer distances indicate stronger discrimination, the weight is set to the reciprocal of the distance. However, it's important to note that the weight is infinite when the distance is 0, so extreme values ​​need to be handled beforehand. Furthermore, the choice of the preset threshold should be based on the actual data distribution. A threshold that is too high may result in too many associations being rejected, leading to insufficient matching; a threshold that is too low may retain weak associations, introducing errors.

[0084] Based on the above technical solution, the point information and text coordinate information (including machine number, circuit, and address) of fire component icons are automatically extracted by parsing DXF files, replacing the traditional method of relying on manual identification and input, thus alleviating the problems of low efficiency and high recognition error caused by manual operation. Secondly, by deduplicating the parsed coordinate information, duplicate coordinate data is automatically eliminated, reducing matching errors caused by drawing errors or export redundancy, and overcoming the unreliability of data redundancy and manual cleanup. Next, based on the length and width information of the DXF file and the graphic size of the corresponding WMF or BMP format plan, a dual-scale coordinate transformation is performed to automatically convert the original vector coordinates into screen pixel coordinates, ensuring coordinate system consistency and accurate mapping, solving the display misalignment caused by inconsistency in coordinate systems and the tediousness of manual calibration. Finally, by calculating the Euclidean distance between the text coordinates and the fire icon points and generating an adjacency matrix of distance relationships, data-driven intelligent association matching is achieved, avoiding the time-consuming and laborious problems of relying on experience judgment and manual association, thereby improving the overall integration of graphics and data, visualization effect, and retrieval convenience.

[0085] In one possible implementation of this application embodiment, the association of the text of the machine number, loop, and address with the icon points by recursively traversing the adjacency matrix to form an association information table can be achieved through the following steps 401 to 404, which are described in detail below: Step 401: Based on the weighted adjacency matrix after normalization and sparsification, starting with the text coordinates, recursively search for the associated icon points with the highest weight to establish a preliminary matching relationship.

[0086] Sparsity reduction involves removing edges with weights below a preset threshold, retaining only the positional relationships between related text and icons. Recursive search is the process of traversing the adjacency matrix using a recursive algorithm to find the optimal match.

[0087] In some implementations, based on a weighted adjacency matrix after normalization and sparsification, each text coordinate is used as a starting node to recursively search for the associated icon point with the highest weight, thereby establishing a preliminary matching relationship. If the same icon point is associated with multiple text coordinates, the normalized distance weight between each text coordinate and the icon point is calculated, and only the association of the text coordinate with the highest weight is retained while other associations are removed. For text coordinates and icon points that fail to match, the Euclidean distance between them and the remaining points is recalculated, the adjacency matrix is ​​updated, and the recursive matching process is iteratively executed until all text coordinates are associated with a unique icon point or no further matching is possible, thus forming a preliminary matching result.

[0088] Step 402: If the same icon location is associated with multiple text coordinates, calculate the normalized distance weight between each text coordinate and the icon location, retain only the text coordinate association with the highest weight, and remove the other associations.

[0089] In this context, "same icon location" refers to multiple text coordinates that are associated with the same fire-fighting component icon location in the adjacency matrix. The association relationship refers to the matching correspondence between text coordinates and icon locations.

[0090] In some implementations, when the same icon point is detected to be associated with multiple text coordinates, the normalized distance weight between each text coordinate and the icon point is first calculated; then all weight values ​​are compared, and only the text coordinate association with the highest weight is retained; at the same time, the association between other text coordinates with lower weights and the icon point is removed; the unassociated text coordinates will enter the subsequent rematching process, and new icon point associations will be found by updating the adjacency matrix and iterative matching process.

[0091] Step 403: For text coordinates and icon points that failed to match, recalculate the Euclidean distance between them and the remaining points, update the adjacency matrix, and iteratively execute the recursive matching process until all text coordinates are associated with a unique icon point or no further matching is possible.

[0092] Among them, unmatched text coordinates refer to text coordinates that failed to be associated with any icon points during the initial matching process, including machine number, circuit and address information.

[0093] In some implementations, after identifying text coordinates and icon points that failed to match after the initial matching, the Euclidean distance between the unmatched text coordinates and the remaining icon points can be recalculated to generate new distance data. The adjacency matrix can then be updated based on the recalculated distance, and the weight values ​​can be adjusted to reflect the current point relationships. During the iterative execution of recursive matching, the process repeatedly searches for the associated icon point with the highest weight, starting with the text coordinates, to establish a matching relationship. This process is continuously looped until all text coordinates are successfully associated with a unique icon point or no further matches can be found, thus completing the matching process.

[0094] Step 404: Based on the final matching results, generate an association information table containing the machine number, loop, address and corresponding icon coordinates. The association information table also includes a matching confidence index and a flag indicating whether manual intervention is required.

[0095] Among them, the serial number is the unique identifier of the fire alarm controller. The loop is the number of the internal circuit path of the controller. The address is the location identifier of the component in a specific loop. The icon point coordinates are the location coordinates of the fire alarm component icon on the floor plan. The association information table is a data structure that stores the matching relationship between the serial number, loop, address, and corresponding icon point coordinates.

[0096] In some implementations, the system collects data on the serial numbers, loops, addresses, and corresponding icon coordinates of all successfully matched devices based on the final matching results. A matching confidence index is then calculated for each matching item based on the normalized distance weight. A flag indicating manual intervention can be set based on a preset confidence threshold; when the confidence level is below the threshold, the flag indicates that intervention is required. Finally, all data is integrated to generate a structured association information table containing complete fields such as serial number, loop, address, coordinates, confidence index, and intervention flag.

[0097] Based on the above technical solution, a spatial relationship model between text coordinates and icon positions is established using a normalized weighted adjacency matrix structure. A recursive search algorithm is employed to achieve efficient optimal matching, and an iterative update mechanism ensures continuous processing of unmatched points, ultimately generating a related information table with quality assessment indicators. This improves matching efficiency, reducing manual operations that previously took hours to minutes of automated processing. Furthermore, Euclidean distance calculation and weighting reduce human error and improve matching accuracy. Finally, confidence indicators and intervention markers enable precise human intervention guidance, forming a quantifiable quality assessment system.

[0098] In one possible implementation of this application embodiment, embedding the associated information table after injecting coordinate data into the tree directory can be achieved through the following steps 501 to 506, which are described in detail below: Step 501: Based on the node structure of the tree directory, associate the coordinate data in the associated information table with the corresponding building floor plan nodes in the tree directory.

[0099] It should be noted that by accurately associating coordinate data with tree directory nodes, indexing efficiency can be improved through hash mapping, and display performance can be optimized through dynamic loading mechanism. However, attention should be paid to the accuracy of coordinate transformation to avoid icon offset. Furthermore, the hierarchical structure of layer storage helps manage a large amount of component data and supports fast retrieval and visual interaction.

[0100] Step 502: Create an independent layer storage space for each planar diagram node, and store the coordinate data in the associated information table in layers according to machine number, circuit and address information.

[0101] The layer storage space is an independent data storage area allocated to each floor plan node, used to store fire protection component data related to that floor plan.

[0102] In some implementations, an independent layer storage space is created for each planar diagram node. This means that an independent storage area is allocated to each node based on the planar diagram nodes already generated in the tree directory. Then, the coordinate data is classified according to the machine number, circuit, and address information in the association information table. Component coordinate data with the same machine number are stored together to form the first level. Under the same machine number, the second level is divided by circuit. Finally, under the same circuit, the third level is divided by address, realizing hierarchical storage of coordinate data. This ensures that the layer storage space of each planar diagram node contains complete and ordered component coordinate information, providing a data foundation for subsequent fast retrieval and display.

[0103] It should be noted that by creating an independent layer storage space for each floor plan node, the isolation and independence between different floor plan data are ensured, avoiding data confusion; at the same time, the hierarchical storage according to machine number, circuit and address information not only conforms to the actual organizational logic of fire protection components, but also greatly improves the efficiency of data retrieval and access.

[0104] Step 503: Establish a fast index relationship between the machine number, loop, and address combination in the association information table and the tree directory node through hash mapping.

[0105] Hash mapping is a data structure that uses a hash function to quickly map keys to values, enabling efficient data retrieval.

[0106] In some implementations, the machine number, loop, and address fields are extracted from the associated information table and combined into a unique key (e.g., concatenating the machine number, loop, and address into a string). Then, a hash function is used to calculate the hash value of this key, generating a numeric index. Next, a mapping relationship is established between the hash value and tree directory nodes (based on filenames such as building number-floor number-attribute identifier), and stored in a hash table. When it is necessary to retrieve a specific combination of machine number, loop, and address, the corresponding tree directory node is quickly located by calculating its hash value, thereby accessing the coordinate data under that node. This effectively avoids the inefficient operation of traversing the entire tree directory, achieving instant data access and indexing.

[0107] Step 504: Convert the screen pixel coordinates in the association information table into the relative coordinate system corresponding to the tree directory node, and inject them into the layer storage space.

[0108] The relative coordinate system is the local coordinate system corresponding to the tree directory node. It is based on the size and position definition of the planar map and is used to locate icons within the node.

[0109] In some implementations, screen pixel coordinate data is extracted from the associated information table. Based on the building plan dimensions corresponding to the tree directory nodes (such as the width and height parameters obtained from WMF or BMP files), the scaling ratio and offset are calculated, converting the screen pixel coordinates into the node's local relative coordinate system. Then, according to the hierarchical structure of the tree directory nodes, the converted relative coordinate data is organized hierarchically by machine number, circuit, and address information. Finally, this hierarchical coordinate data is injected into the corresponding layer storage space, completing data integration. This ensures that the coordinate data matches the local coordinate system of the tree directory nodes, improving the accuracy and adaptability of icon display.

[0110] Step 505: In the graphical display interface, dynamically load the coordinate data of the corresponding layer according to the selection status of the tree directory node, and render the fire protection component icon to the specified position on the building floor plan.

[0111] The graphical display interface refers to the visual interface in the fire control room's graphic display device (CRT) used to display building floor plans and fire component icons.

[0112] In some implementations, the system monitors changes in the user's selection status of tree directory nodes. When a user selects a specific floor plan node, it immediately locates the corresponding layer storage space through a pre-established hash mapping relationship. Then, it dynamically loads all coordinate data stored hierarchically under that node by machine number, circuit, and address. Next, it matches the loaded coordinate data with the building floor plan using the coordinate system to ensure accurate data location. Finally, it uses a graphics rendering engine to draw various fire protection component icons onto the corresponding coordinate positions on the building floor plan, completing the visualization display.

[0113] Step 506: Each floor plan node in the tree directory after embedding the associated information table supports the display of multi-level fire protection component icons, and the icons are superimposed on the floor plan through coordinate mapping, supporting the quick location and retrieval of associated fire protection component information by the tree directory node.

[0114] The multi-level fire protection component icon display refers to the ability to display multiple fire protection component icons layered by unit number, circuit, and address under the same floor plan node. Icon overlay on the floor plan refers to the visualization effect of accurately overlaying fire protection component icons onto their corresponding locations on the building floor plan. Quick location and retrieval refers to the function of directly accessing related fire protection component information through tree directory nodes.

[0115] In some implementations, the associated information table is fully embedded in the tree directory structure, so that each floor plan node contains complete fire protection component data. Then, a multi-layer display mechanism is established for each floor plan node, and the fire protection component icons are organized hierarchically according to machine number, circuit, and address information. Next, the coordinates of the icons are precisely matched with the coordinate system of the building floor plan through coordinate mapping, so as to achieve pixel-level overlay of icons and floor plans. Finally, based on the hierarchical structure of the tree directory nodes, a fast indexing mechanism is built. When the user selects a specific node, the system immediately locates and displays all associated fire protection component information under that node, including detailed data such as icon position, machine number, circuit, and address.

[0116] Based on the above technical solution, a hierarchical data management framework is established by associating the related information table with the floor plan nodes through the node structure of the tree directory. This solves the problems of chaotic file management and low efficiency of manual import. Simultaneously, an independent layer storage space is created for each floor plan node, and data is stored hierarchically by machine number, circuit, and address, achieving orderly organization and isolated management of data, overcoming retrieval difficulties caused by data redundancy and lack of classification. A fast index relationship between machine number, circuit, and address combinations and tree directory nodes can be established through hash mapping, allowing for rapid data location and improving the efficiency of traditional traversal retrieval. Furthermore, screen pixel coordinates are converted to a relative coordinate system of nodes and injected into the layer storage, ensuring the consistency of the coordinate system and eliminating icon misalignment caused by coordinate mismatch. Data is dynamically loaded and icons are rendered based on the selection status of the tree directory nodes, achieving on-demand loading and real-time display, solving the problems of high memory pressure and slow response caused by traditional one-time loading. Finally, through multi-layer icon display and coordinate mapping overlay, it supports rapid location and retrieval of fire protection component information from tree directory nodes, achieving deep integration of graphics and data, and overcoming the drawbacks of existing technologies where graphics and data are disconnected and require secondary programming.

[0117] In one possible implementation of this application embodiment, after the associated information table with injected coordinate data is embedded in the tree directory, it can also be implemented through the following steps 601 to 605, which are described in detail below: Step 601: Calculate the screen pixel coordinates (X, X, Y) of each fire-fighting component icon in the associated information table in real time. screen ,Y screen） The offset error (ΔX, ΔY) between the corresponding theoretical position in the architectural floor plan WMF or BMP file and its actual position, where ΔX = |X screen X 理论 |,ΔY=|Y screen Y 理论 |

[0118] The theoretical position is the coordinates derived from parsing the DXF file, representing the original position in the architectural floor plan file. The offset error (ΔX, ΔY) is the difference between the actual screen coordinates and the theoretical position.

[0119] In some implementations, the screen pixel coordinates obtained by converting the icon points from the DXF file through a dual-scale coordinate transformation can be obtained first. Then, the original vector coordinates of the DXF file can be extracted. The theoretical position is derived from this. The offset errors ΔX and ΔY of each fire component icon are calculated.

[0120] Step 602: If the offset error (ΔX, ΔY) exceeds the preset tolerance threshold, an offset warning is generated, and the offset fire-fighting component icon is highlighted in the graphical display interface.

[0121] The preset tolerance threshold is the maximum allowable error range for deviation, used to determine whether an early warning should be triggered. The deviation warning is a visual alarm signal automatically generated by the system when the error exceeds the threshold. The graphical display interface is the visual area in the fire control room's graphical display device used to display building floor plans and fire component icons. Highlighting is a technical means of making specific icons stand out in the interface by changing icon colors, adding flashing effects, or adding borders.

[0122] In some implementations, when the real-time calculated offset error (ΔX, ΔY) exceeds the preset tolerance threshold, an offset warning signal containing the specific component identifier and error value will be generated, and the corresponding fire component icon will be located in the graphical display interface. The icon will be highlighted by changing its display attributes (such as setting it to a red flashing state or adding a yellow border).

[0123] It should be noted that the tolerance threshold needs to be set according to the actual engineering accuracy requirements, and a value of 3-5 pixels is usually recommended; the highlight display adopts a non-blocking warning mode, which does not affect the normal monitoring function.

[0124] Step 603: If there are multiple offset warnings, the icons of the fire-fighting components with the multiple offsets will be highlighted sequentially in the graphical display interface by scrolling.

[0125] The scrolling method refers to the process by which the system sequentially switches between displaying multiple warning icons in a specific order and at specific time intervals, ensuring that each offset icon is displayed in turn.

[0126] In some implementations, when multiple offset warnings are detected, the system first extracts the corresponding fire component icons and coordinate data from the associated information table. Then, it initializes a scrolling display queue in the graphical interface, sorting the icons according to their generation time or spatial position. Next, a scrolling timer is started, highlighting each offset icon sequentially at preset time intervals (e.g., 2-3 seconds). The highlighting is achieved by changing the icon color to red and adding a flashing effect. After the current icon is finished being highlighted, the system automatically switches to the next icon in the queue, repeating this process until all warning icons have been processed. Simultaneously, a scrolling progress indicator, such as "Warning 1 / 5," is displayed at the bottom of the interface for easy tracking by operators. The entire process requires no manual intervention; the system automatically maintains the scrolling status and automatically stops scrolling and returns to normal display mode after all warnings have been processed.

[0127] Step 604: Provide a graphical fine-tuning interface to receive user commands to drag and adjust the coordinates of fire component icons based on offset warnings, and update the adjusted coordinate data to the associated information table and the corresponding tree directory layer storage space.

[0128] The graphical user interface (GUI) is an interactive interface that allows users to adjust the coordinates of fire protection component icons through visual operations. It is typically integrated into a graphical display device. Fire protection component icons are graphic elements representing fire protection equipment (such as heat detectors and smoke detectors), and their positions are displayed on the building floor plan. The drag-and-drop adjustment command is a command that allows users to move the icon's position by dragging it using a mouse or touch operation.

[0129] In some implementations, when an offset warning is detected in the graphical display interface, a graphical fine-tuning interface is activated, displayed as an overlay on the building floor plan, and the icons of the fire protection components that need adjustment are highlighted. At this time, the user can drag and drop the icons to the correct position, and the interface displays the coordinate changes and offset error values ​​in real time. After dragging is complete, the system captures the adjusted screen pixel coordinates (X...). screen ,Y screen）The system calculates the offset error between the original theoretical position and the actual position to verify if it is below the tolerance threshold. Then, it traverses the associated information table, locates the corresponding record based on the icon identifier (such as machine number, circuit, or address combination), and updates the coordinate field of the associated information table with the new coordinate data. Simultaneously, it accesses the layer storage space of the corresponding building floor plan node in the fast index tree directory using hash mapping, converts the adjusted coordinates to a node-relative coordinate system, and injects them into the storage space. Finally, it automatically refreshes the graphic display, renders the updated icon position, and records the adjustment log to the intervention flag in the associated information table to ensure data consistency.

[0130] Step 605: Based on the final matching results, automatically generate a success rate report. The report includes the total number of parts, the number of automatically matched parts, the number of matched parts that failed, the number of parts that require manual adjustment, and the overall matching success rate percentage.

[0131] The total number of components refers to the total number of component records extracted from the component information tables of the programmed fire alarm controllers and fire linkage controllers, representing the total number of fire-fighting components that need to be processed in the system. The number of successfully matched components refers to the number of components whose records in the component information table completely match the machine number, circuit, and address in the associated information table, and whose coordinate data is successfully injected. The number of failed matches refers to the number of invalid data records in the component information table that have no matching entries in the associated information table and are directly discarded. The number requiring manual fine-tuning refers to the number of components in the associated information table whose offset error exceeds the preset tolerance threshold and requires user adjustment via a graphical interface. The overall matching success rate percentage is the percentage obtained by multiplying the ratio of the number of successfully matched components to the total number of components by 100%, used to measure the overall effectiveness of automatic matching.

[0132] In some implementations, based on the final matching results, the total number of parts can be counted from the imported part information table. Then, the association information table is traversed to count the number of parts that were automatically matched successfully. The number of failed matches is counted by comparing the part information table and the association information table, and counting the number of records in the part information table that had no matching items and were discarded. The number of parts requiring manual fine-tuning is determined by checking the intervention flag in the association information table or by calculating the number of parts whose offset error exceeds the tolerance threshold in real time. Finally, the system calculates the overall matching success rate percentage as (number of automatically matched parts / total number of parts). It achieves 100% accuracy and automatically generates a structured report, outputting in text or table format fields such as total number of parts, number of successful automatic matches, number of failed matches, number requiring manual adjustments, and overall match success rate percentage.

[0133] Based on the above technical solution, the intelligent early warning queue and scrolling highlight display structure overcome the visual confusion and missed detection problems caused by the simultaneous display of multiple abnormal points in traditional interfaces. The combination of graphical drag-and-drop adjustment and automatic data synchronization eliminates data inconsistencies and secondary errors that may occur when manually modifying multiple data sources. Furthermore, the multi-dimensional success rate report generation structure fills the gap in the lack of quantitative evaluation indicators in traditional methods. This collectively addresses the problems of low efficiency and error-proneness of manual operation in existing fire control room graphic display devices, difficulty in effectively highlighting multiple abnormal points, lack of consistency in data modification, and lack of quantifiable evaluation standards for system performance.

[0134] The above mainly describes the solutions of the embodiments of this application from the perspective of device implementation. It is understood that each device, such as a fire control room graphic display device and its automatic graphic import device, includes at least one of the hardware structure and software module corresponding to each function in order to achieve the above functions. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. The embodiments of this application can divide the fire control room graphic display device and its automatic graphic import device into functional units according to the above method examples. For example, each function can be divided into separate functional units, or two or more functions can be integrated into the same processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in the embodiments of this application is illustrative and only represents a logical functional division; other division methods may exist in actual implementation.

[0135] When using integrated units, Figure 7 A possible structural schematic diagram of a fire control room graphic display device and its automatic graphic import device (referred to as a fire control room graphic display device and its automatic graphic import device 70) involved in the above embodiments is shown. The fire control room graphic display device and its automatic graphic import device 70 includes a processing unit 701 and a communication unit 702, and may also include a storage unit 703. Figure 7 The structural diagram shown can be used to illustrate the structure of the fire control room graphic display device and its automatic graphic import device involved in the above embodiments.

[0136] when Figure 7The structural diagram shown is used to illustrate the structure of the fire control room graphic display device and its automatic graphic import device involved in the above embodiments. The processing unit 701 is used to control and manage the operation of the fire control room graphic display device and its automatic graphic import device. The communication unit 702 is used for the fire control room graphic display device and its automatic graphic import device to communicate with other devices. The storage unit 703 is used to store the program code and data of the fire control room graphic display device and its automatic graphic import device.

[0137] For example, communication unit 702 is used to receive architectural floor plan files in WMF or BMP format; Processing unit 701 generates a tree directory in a planar coordinate system by verifying file naming rules and formats. It parses the DXF file in the building floor plan, extracts icon points and text coordinates, and constructs an adjacency matrix. By recursively traversing the adjacency matrix, it associates the text of machine numbers, loops, and addresses with icon points, forming an association information table. It imports the component information tables of the programmed fire alarm controllers and fire linkage controllers and compares them with the association information table. It filters coordinate data from the component information table that matches the association information table and injects it into the association information table; any remaining information that does not match is discarded. The component information table contains machine number, loop, and address information. The association information table with injected coordinate data is embedded in the tree directory for displaying the fire control diagram.

[0138] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and variations.

Claims

1. A graphic display device for a fire control room and its automatic graphic import method, characterized in that, include: Receive architectural floor plan files in WMF or BMP format, and generate a tree directory in a plane coordinate system by passing the file naming rules and format validation. Parse the DXF file in the architectural floor plan, extract the icon points and text coordinates, and construct an adjacency matrix; The extraction of icon points and text coordinates, and the construction of an adjacency matrix, includes: Parse the location information and text coordinate information of all fire-fighting component icons in the DXF file. The text coordinate information includes the machine number, circuit, and address. The parsed coordinate information is deduplicated to remove duplicate coordinate data, thereby reducing matching errors; Based on the width and height information of the DXF file and the graphic size of the corresponding WMF or BMP format planar image, a dual-scale coordinate transformation is performed to convert the original vector coordinates of the DXF file into pixel coordinates of the current computer screen. Calculate the Euclidean distance between the text coordinates and the fire icon locations, and generate an adjacency matrix of the distance relationships; The calculation of the Euclidean distance between the text coordinates and the fire icon location, generating an adjacency matrix of distance relationships, includes: Calculate the Euclidean distance between all text coordinates and fire component icon locations, and generate an initial adjacency matrix containing all distance relationships. The text coordinates include machine number, circuit, and address. The Euclidean distance values ​​are mapped to the range [0,1] using minimum and maximum scaling methods, and the adjacency matrix is ​​normalized. Based on the normalized distance values, a weighted adjacency matrix is ​​constructed with text coordinates as rows and icon positions as columns, where the weight is the reciprocal of the Euclidean distance, and the closer the distance, the higher the weight. Edges with weights below a preset threshold are removed, and only the relationships between associated text and icon points are retained. The weighted adjacency matrix is ​​then sparsified to obtain an adjacency matrix in which each text coordinate is associated with only the one closest icon point. By recursively traversing the adjacency matrix, the text of the machine number, loop, and address is associated with the icon points to form an association information table. The process involves recursively traversing the adjacency matrix to associate the text of the machine number, loop, and address with the icon points, forming an association information table, including: Based on the weighted adjacency matrix after normalization and sparsification, starting with the text coordinates, we recursively search for the associated icon points with the highest weight to establish a preliminary matching relationship. If the same icon location is associated with multiple text coordinates, calculate the normalized distance weight between each text coordinate and the icon location, retain only the text coordinate association with the highest weight, and remove the other associations; For text coordinates and icon points that fail to match, recalculate the Euclidean distance between them and the remaining points, update the adjacency matrix, and iteratively execute the recursive matching process until all text coordinates are associated with a unique icon point or no further matching is possible. Based on the final matching results, an association information table is generated, which includes the machine number, loop, address and corresponding icon point coordinates. The association information table also includes a matching confidence index and a flag indicating whether manual intervention is required. Import the component information table of the programmed fire alarm controller and fire linkage controller and compare it with the associated information table. Filter the coordinate data that matches the associated data table from the component information table and inject it into the associated information table. Discard the remaining information that does not match the associated information table. The component information table contains machine number, circuit, and address information. The associated information table containing the injected coordinate data is embedded in the tree directory for displaying the fire control diagram.

2. The graphic display device for a fire control room and its automatic graphic import method according to claim 1, characterized in that, The process of generating a tree directory in a planar coordinate system through file naming rules and format validation includes: For WMF format files, verify that the key feature word in the PLACEABLEMETAHEADER structure in the file header is 9AC6CDD7h, and calculate the graphic width n based on the Left, Top, Right, Bottom, and Inch parameters in the PLACEABLEMETAHEADER structure. Width And graphic height n Height , make the graphic width n Width And graphic height n Height Verify with the preset range of the screen's graphic display area; For BMP format files, verify that the feature word in the tagBITMAPINFOHEADER structure at the file header is 424Dh, and read the graphic width bi from the tagBITMAPINFOHEADER structure. Width and graphic height bi Height ; Get screen pixel width h width and screen pixel height h Height ,pass and Calculate the pixel deviation C between the BMP file and the screen pixels. x and C y The deviation value C x and C y Verify against the preset range; If the graphic size and pixels are within the preset range, no processing is performed; if they exceed the preset range, they are removed or replaced to obtain a compliant file. The file name of the compliant file is validated using regular expressions. If the file name is compliant, no action is taken. If the file name is not compliant, it is renamed. The file name format is [building number, floor number, attribute identifier], where the building number ranges from [0, 4000], the floor number ranges from [-9, -1] or [1, 300], and the attribute identifier includes standard floor b, ground floor d, or mezzanine j. The compliant file names are sorted using a bubble sort algorithm to generate a tree-like directory structure with the project name as the root node and buildings and building floor plans as secondary nodes.

3. The graphic display device for a fire control room and its automatic graphic import method according to claim 2, characterized in that, The dual-scale coordinate transformation includes: Extract the coordinate data X of each point in the dxf file dxf and Y dxf The minimum and maximum coordinate values ​​are filtered to determine the coordinates of the four corners, where the minimum and maximum coordinate values ​​are MinX, MinY, MaxX, and MaxY, respectively. Calculate the length of the DXF file based on the four corner coordinates. and width ; Based on the length of the dxf file and width ScreenWidth (pixel size of the target screen area) pixe By horizontal scaling and vertical scaling ratio Establish mapping and conversion rules between the DXF file coordinate system and the screen pixel coordinate system; Based on the aforementioned mapping conversion rules, each original vector coordinate X in the dxf file will be converted... dxf and Y dxf pass and Convert to screen pixel coordinates X screen and Y screen ; Converted to screen pixel coordinates X screen and Y screen Associated with the corresponding fire-fighting component icons and text information.

4. The graphic display device for a fire control room and its automatic graphic import method according to claim 3, characterized in that, The step of filtering coordinate data that matches the associated data table from the component information table and injecting it into the associated information table includes: Traverse the component information tables of the programmed fire alarm controllers and fire linkage controllers to extract the machine number, circuit and address information; The extracted machine number, circuit, and address information are matched item by item with the corresponding fields in the associated information table; If a record in the component information table is completely consistent with the machine number, circuit, and address in the associated information table, then the coordinate data corresponding to that record will be injected into the corresponding field of the associated information table. If a record in the component information table has no matching item in the associated information table, it is determined to be invalid data and discarded directly, and the final associated information table after injecting coordinate data is generated.

5. The graphic display device for a fire control room and its automatic graphic import method according to claim 4, characterized in that, The step of embedding the associated information table after injecting coordinate data into the tree directory includes: Based on the node structure of the tree directory, the coordinate data in the association information table is associated with the corresponding building floor plan nodes in the tree directory; Create an independent layer storage space for each plan node, and store the coordinate data in the associated information table in layers according to machine number, circuit and address information; A fast index relationship between the machine number, loop, and address combination in the associated information table and the tree directory node is established through hash mapping; Convert the screen pixel coordinates in the associated information table into the relative coordinate system corresponding to the tree directory nodes, and inject them into the layer storage space; In the graphical display interface, the coordinate data of the corresponding layer is dynamically loaded according to the selection status of the tree directory node, and the fire protection component icons are rendered to the specified positions on the building floor plan. Each floor plan node in the tree directory after embedding the associated information table supports multi-level display of fire protection component icons, and the icons are superimposed on the floor plan through coordinate mapping, enabling quick location and retrieval of associated fire protection component information by the tree directory node.

6. The graphic display device for a fire control room and its automatic graphic import method according to claim 5, characterized in that, After the associated information table is embedded in the tree directory following the injected coordinate data, it also includes: Real-time calculation of the screen pixel coordinates (X) of each fire-fighting component icon in the associated information table. screen ,Y screen） The offset error (ΔX, ΔY) between the corresponding theoretical position in the architectural floor plan WMF or BMP file and its actual position, where ΔX = |X screen X 理论 |,ΔY=|Y screen Y 理论 |; If the offset error (ΔX, ΔY) exceeds the preset tolerance threshold, an offset warning is generated, and the fire-fighting component icon of the offset is highlighted in the graphical display interface. If multiple offset warnings exist, the icons of the fire-fighting components corresponding to the offsets will be highlighted sequentially in the graphical display interface by scrolling. A graphical fine-tuning interface is provided to receive user commands to drag and adjust the coordinates of the fire component icons based on the offset warning, and to update the adjusted coordinate data to the associated information table and the corresponding tree directory layer storage space. Based on the final matching results, a success rate report is automatically generated. The report includes the total number of parts, the number of automatically matched successfully, the number of matched unsuccessfully, the number of parts requiring manual adjustments, and the overall matching success rate percentage.

7. A graphic display device for a fire control room and its automatic graphic import device, characterized in that, The device includes: a communication unit and a processing unit; The communication unit is used to receive architectural floor plan files in WMF or BMP format; The processing unit is used to generate a tree directory in a planar coordinate system by verifying file naming rules and format. Parse the DXF file in the architectural floor plan, extract the icon points and text coordinates, and construct an adjacency matrix; The extraction of icon points and text coordinates, and the construction of an adjacency matrix, includes: Parse the location information and text coordinate information of all fire-fighting component icons in the DXF file. The text coordinate information includes the machine number, circuit, and address. The parsed coordinate information is deduplicated to remove duplicate coordinate data, thereby reducing matching errors; Based on the width and height information of the DXF file and the graphic size of the corresponding WMF or BMP format planar image, a dual-scale coordinate transformation is performed to convert the original vector coordinates of the DXF file into pixel coordinates of the current computer screen. Calculate the Euclidean distance between the text coordinates and the fire icon locations, and generate an adjacency matrix of the distance relationships; The calculation of the Euclidean distance between the text coordinates and the fire icon location, generating an adjacency matrix of distance relationships, includes: Calculate the Euclidean distance between all text coordinates and fire component icon locations, and generate an initial adjacency matrix containing all distance relationships. The text coordinates include machine number, circuit, and address. The Euclidean distance values ​​are mapped to the range [0,1] using minimum and maximum scaling methods, and the adjacency matrix is ​​normalized. Based on the normalized distance values, a weighted adjacency matrix is ​​constructed with text coordinates as rows and icon positions as columns, where the weight is the reciprocal of the Euclidean distance, and the closer the distance, the higher the weight. Edges with weights below a preset threshold are removed, and only the relationships between associated text and icon points are retained. The weighted adjacency matrix is ​​then sparsified to obtain an adjacency matrix in which each text coordinate is associated with only the one closest icon point. By recursively traversing the adjacency matrix, the text of the machine number, loop, and address is associated with the icon points to form an association information table. The process involves recursively traversing the adjacency matrix to associate the text of the machine number, loop, and address with the icon points, forming an association information table, including: Based on the weighted adjacency matrix after normalization and sparsification, starting with the text coordinates, we recursively search for the associated icon points with the highest weight to establish a preliminary matching relationship. If the same icon location is associated with multiple text coordinates, calculate the normalized distance weight between each text coordinate and the icon location, retain only the text coordinate association with the highest weight, and remove the other associations; For text coordinates and icon points that fail to match, recalculate the Euclidean distance between them and the remaining points, update the adjacency matrix, and iteratively execute the recursive matching process until all text coordinates are associated with a unique icon point or no further matching is possible. Based on the final matching results, an association information table is generated, which includes the machine number, loop, address and corresponding icon point coordinates. The association information table also includes a matching confidence index and a flag indicating whether manual intervention is required. Import the component information table of the programmed fire alarm controller and fire linkage controller and compare it with the associated information table. Filter the coordinate data that matches the associated data table from the component information table and inject it into the associated information table. Discard the remaining information that does not match the associated information table. The component information table contains machine number, circuit, and address information. The associated information table containing the injected coordinate data is embedded in the tree directory for displaying the fire control diagram.

Images