Data transmission method based on single building data and general drawing data

Abstract

The invention relates to the technical field of engineering design, and discloses a data transmission method based on single building data and general drawing data, and the method comprises the steps: responding to an operation instruction of a user, and determining to-be-updated data based on the operation instruction; performing data updating according to the to-be-updated data and transmitting the to-be-updated data to corresponding associated data to obtain target monomer data and target general drawing data; and performing data verification according to the target monomer data and the target general drawing data to obtain a data transmission result. According to the method, the integrity, the consistency and the high efficiency of data between the monomers and the general graph can be effectively improved.

Description

Technical Field

[0001] The present application relates to the field of engineering design technology, and in particular to a data transmission method based on single building data and general drawing data. Background Art

[0002] The existing technical solution is a CAD collaborative design method based on semantic information exchange. By constructing a conceptual semantic model of CAD data and converting it into JSON data format, using version control technology to track the design process, and combining a CAD semantic capture plug-in and a CAD semantic information exchange center, real-time collaboration between design teams is achieved. However, although the efficiency of design collaboration is improved through semantic information exchange, the accuracy of semantic understanding is still limited by natural language processing technology, which can lead to misunderstanding of design intent or transmission deviation. Therefore, the integrity and consistency of design data transmission are poor, and the transmission efficiency is low.

[0003] Therefore, how to effectively improve the integrity, consistency and efficiency of data between monomers and the overall map is a problem that needs to be solved urgently.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a data transmission method based on single building data and general plan data, aiming to solve the technical problem of how to effectively improve the integrity, consistency and efficiency of data between single buildings and general plans.

[0006] To achieve the above-mentioned purpose, the present application proposes a data transmission method based on single building data and general plan data, the method comprising:

[0007] In response to an operation instruction of a user, determining data to be updated based on the operation instruction;

[0008] Update the data according to the data to be updated and transfer it to the corresponding associated data to obtain the target monomer data and the target overall map data;

[0009] Data verification is performed based on the target monomer data and the target overall map data to obtain a data transfer result.

[0010] In one embodiment, the data is updated according to the data to be updated and transmitted to the corresponding associated data to obtain the target monomer data and the target overall map data, including:

[0011] When the data to be updated is monomer data, data is updated according to the monomer data and transmitted to the corresponding associated data to obtain target monomer data and target overall map data;

[0012] When the data to be updated is the overall map data, data is updated according to the overall map data and transmitted to the corresponding associated data to obtain target monomer data and target overall map data.

[0013] In one embodiment, when the data to be updated is monomer data, data is updated according to the monomer data and transmitted to corresponding associated data to obtain target monomer data and target overall map data, including:

[0014] When the data to be updated is monomer data, obtaining a first monomer identifier of the monomer to be updated;

[0015] Constructing a monomer version identifier and a first monomer version number, and associating the monomer version identifier and the first monomer version number with the first monomer identifier to obtain a new monomer version;

[0016] Update the monomer version entity in the database according to the new monomer version to obtain a new monomer version entity;

[0017] The monomer contour entity and the monomer attached entity in the database are updated to obtain a new monomer contour entity and a new monomer base point entity;

[0018] Associating the new monomer version entity, the new monomer outline entity and the new monomer base point entity to obtain target monomer data;

[0019] The target monomer data is transferred to the corresponding overall map data to obtain the target overall map data.

[0020] In one embodiment, the updating of the monomer outline entity and the monomer attached entity in the database to obtain a new monomer outline entity and a new monomer base point entity includes:

[0021] Acquire a monomer contour entity and a monomer subsidiary entity in a database, and perform contour inspection and axis inspection on the monomer contour entity and the monomer subsidiary entity to obtain contour inspection results and axis inspection results;

[0022] When the contour check result is that the contour exists and the axis check result is that the axis intersection is unique, construct a new monomer contour and a new monomer base point;

[0023] Generate a contour identifier based on the new monomer contour, and generate a first monomer base point identifier and a monomer base point coordinate based on the new monomer base point;

[0024] The monomer contour entity is updated based on the contour identifier, the first monomer base point identifier, the first monomer identifier, and the first monomer version number to obtain a new monomer contour entity;

[0025] The monomer-affiliated entity is updated to obtain a first axis mark;

[0026] The overall drawing base point coordinates are obtained, and the monomer base point entity is updated according to the first axis identifier, the first monomer base point identifier, the monomer base point coordinates, the overall drawing base point coordinates and the first monomer version number to obtain a new monomer base point entity.

[0027] In one embodiment, when the data to be updated is the overall map data, data is updated according to the overall map data and transmitted to the corresponding associated data to obtain the target monomer data and the target overall map data, including:

[0028] When the data to be updated is general map data, obtaining a general map identifier of the general map to be updated;

[0029] Constructing a general map version identifier and a general map version number, and associating the general map version identifier and the general map version number with the general map identifier to obtain a new general map version;

[0030] Update the master map version entity in the database according to the new master map version to obtain a new master map version entity;

[0031] Construct new monomers and corresponding monomer dependencies, new general graphs and corresponding general graph dependencies;

[0032] Based on the new monomer, the monomer attachment, the new general map and the general map attachment, the monomer entity and the general map entity in the database are updated to obtain a new monomer entity and a new general map entity;

[0033] Associating the new master map version entity, the new monomer entity and the new master map entity to obtain target master map data;

[0034] The target overall map data is transferred to the corresponding monomer data to obtain the target monomer data.

[0035] In one embodiment, the updating of the monomer entity and the general diagram entity in the database based on the new monomer, the monomer attachment, the new general diagram and the general diagram attachment to obtain the new monomer entity and the new general diagram entity includes:

[0036] Generate a second monomer identifier and a second monomer version number according to the new monomer, and generate a second axis identifier according to the monomer attachment;

[0037] Determine a corresponding monomer base point according to the new monomer, and obtain coordinates of a second monomer base point corresponding to the monomer base point;

[0038] The monomer entity in the database is updated according to the second monomer identifier, the second monomer version number, the second axis identifier, the general drawing version number and the second monomer base point coordinates to obtain a new monomer entity;

[0039] Generating a general plan identification according to the new general plan, and generating a structure identification according to the general plan attachment;

[0040] The general plan entity in the database is updated according to the general plan identification, the structure identification and the general plan version number to obtain a new general plan entity.

[0041] In one embodiment, the data verification is performed according to the target monomer data and the target overall map data to obtain the data transfer result, including:

[0042] Determine a target monomer base point according to the target monomer data, and determine a target overall map base point according to the target overall map data;

[0043] Base point alignment is performed according to the target monomer base point and the target overall image base point to obtain aligned target monomer data and aligned target overall image data;

[0044] Integrate the aligned target monomer data into the aligned target overall image data and perform entity reconstruction to obtain the position and size of the monomer in the overall image;

[0045] The data transfer result is determined according to the position and size of the monomer in the overall diagram.

[0046] In addition, to achieve the above-mentioned purpose, the present application also proposes a data transmission device based on single building data and general plan data, and the data transmission device based on single building data and general plan data includes:

[0047] A determination module, configured to respond to an operation instruction of a user and determine data to be updated based on the operation instruction;

[0048] A transfer module, used for updating data according to the data to be updated and transferring it to the corresponding associated data to obtain target monomer data and target overall map data;

[0049] The verification module is used to perform data verification based on the target monomer data and the target overall map data to obtain a data transfer result.

[0050] In addition, to achieve the above-mentioned objectives, the present application also proposes a data transmission device based on single building data and general plan data, the device comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being configured to implement the steps of the data transmission method based on single building data and general plan data as described above.

[0051] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the data transmission method based on single building data and general plan data as described above are implemented.

[0052] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the data transmission method based on single building data and general plan data as described above.

[0053] The present application provides a data transmission method based on single building data and general plan data. The present application first responds to the user's operation instruction, determines the data to be updated based on the operation instruction; updates the data according to the data to be updated and transmits it to the corresponding associated data to obtain the target single building data and the target general plan data; performs data verification according to the target single building data and the target general plan data to obtain the data transmission result, which can effectively improve the integrity, consistency and efficiency of the data between the single building and the general plan.

[0054] In summary, the present application determines the data to be updated according to the user's operating instructions, quickly and efficiently updates the data according to the data to be updated and transmits it to the corresponding related data, thereby effectively improving the consistency of the data, and then performs data verification according to the target monomer data and the target overall drawing data, thereby effectively improving the integrity of the group data, overcoming the technical defects of poor integrity and consistency of design data transmission and low transmission efficiency, and can effectively improve the integrity, consistency and efficiency of the data between the monomer and the overall drawing. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0056] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0057] Figure 1 A flow chart of the first embodiment of the data transmission method based on single building data and general plan data provided in this application;

[0058] Figure 2 A flow chart of the second embodiment of the data transmission method based on single building data and general drawing data provided by the present application;

[0059] Figure 3 A data flow diagram of a data upload operation provided in Embodiment 2 of the data transmission method based on single building data and general plan data of the present application;

[0060] Figure 4 A data flow diagram of a single-unit data uploading operation provided in Embodiment 2 of the data transmission method based on single-unit building data and general plan data of the present application;

[0061] Figure 5 This is a schematic diagram of the module structure of a data transmission device based on single building data and general plan data in an embodiment of the present application;

[0062] Figure 6 This is a schematic diagram of the equipment structure of the hardware operating environment involved in the data transmission method based on single building data and general plan data in the embodiment of the present application.

[0063] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0064] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0065] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0066] The main solution of the embodiment of the present application is: in response to the user's operation instruction, determine the data to be updated based on the operation instruction; update the data according to the data to be updated and transfer it to the corresponding associated data to obtain target monomer data and target overall map data; perform data verification according to the target monomer data and the target overall map data to obtain the data transfer result.

[0067] The existing technical solution is a CAD collaborative design method based on semantic information exchange. By constructing a conceptual semantic model of CAD data and converting it into JSON data format, using version control technology to track the design process, and combining CAD semantic capture plug-ins and CAD semantic information exchange centers, real-time collaboration between design teams is achieved. However, although the efficiency of design collaboration is improved through semantic information exchange, the accuracy of semantic understanding is still limited by natural language processing technology, which will lead to misunderstandings or transmission deviations of design intent. Therefore, the integrity and consistency of design data transmission are poor, and the transmission efficiency is low. Therefore, how to effectively improve the integrity, consistency and efficiency of data between monomers and general drawings is a problem that needs to be solved urgently.

[0068] The present application determines the data to be updated according to the user's operating instructions, quickly and efficiently updates the data according to the data to be updated and transmits it to the corresponding related data, thereby effectively improving the consistency of the data, and then performs data verification according to the target monomer data and the target overall drawing data, thereby effectively improving the integrity of the group data, overcoming the technical defects of poor integrity and consistency of design data transmission and low transmission efficiency, and can effectively improve the integrity, consistency and efficiency of the data between the monomer and the overall drawing.

[0069] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a data transmission device based on single building data and general plan data, etc. The following takes a data transmission device based on single building data and general plan data as an example to illustrate this embodiment and the following embodiments.

[0070] Based on this, the embodiment of the present application provides a data transmission method based on single building data and general plan data, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the data transmission method based on single building data and general plan data of the present application.

[0071] In this embodiment, the data transmission method based on the single building data and the general plan data includes steps S10 to S30:

[0072] Step S10, in response to an operation instruction of a user, determining data to be updated based on the operation instruction.

[0073] It should be noted that the user's operation instruction refers to the user's upload of a single unit or overall operation instruction, such as adding, modifying or deleting certain data in a single building or general drawing. The operation instruction can be input through a graphical user interface (GUI) or provided through voice, gesture or other interactive methods.

[0074] It is understandable that when the user's operation instruction is to upload a single entity, the data to be updated is the single entity data, and when the user's operation instruction is to upload the overall map, the data to be updated is the overall map data. This embodiment does not make any specific restrictions on this.

[0075] Step S20, updating the data according to the data to be updated and transferring it to the corresponding associated data to obtain the target monomer data and the target overall map data.

[0076] It should be noted that when the data to be updated is single-body data, the data update may include single-body creation operations, single-body upload operations, and single-body version switching operations; when the data to be updated is general map data, the data update may include single-body pull operations, base point return operations, general map upload operations, general map version switching operations, and single-body association directory tree operations in the general map, etc. This embodiment does not impose specific restrictions on this.

[0077] It can be understood that the general plan is the general floor plan, which mainly represents the overall layout of the entire construction site, specifically expressing the location, orientation and basic conditions of the surrounding environment (original buildings, traffic roads, greening, terrain, etc.) of the new house. The single unit is the railway-affiliated production and living houses arranged in the general plan site, such as office buildings, dormitories, warehouses, etc. The single unit data usually contains detailed information about the single unit, such as size, location, material, etc., while the general plan data contains the layout and relationship of the entire building complex.

[0078] It is worth noting that the data update process is not limited to the simple update of monomer data and general map data, but also includes the synchronous update of related data. For example, when monomer data changes, the related general map data will also be adjusted accordingly to ensure data consistency. Similarly, when the general map data changes, all related monomer data will also be updated accordingly. This two-way synchronization mechanism ensures the integrity and consistency of the data.

[0079] It is worth noting that each update of the monomer and the general drawing will generate a new version record, regardless of whether the data has changed. This strict version control mechanism ensures the traceability of the data and the integrity of the historical version. When uploading a monomer or a general drawing, the system will automatically update the version information of the corresponding entity in the database and associate the new version number, which ensures the synchronization of the version information between the monomer and the general drawing and avoids the problem of data inconsistency. In addition, the version switching function of the monomer and the general drawing is supported, allowing users to view or restore to the historical version as needed.

[0080] In the specific implementation, the database table structure is designed to support the storage of version information, including single-body version tables and general map version tables, etc., to implement an automatic update mechanism for version information, automatically generate new version records when data is uploaded or modified, and provide a version switching user interface or API interface to facilitate users to perform version switching operations.

[0081] Step S30, performing data verification based on the target monomer data and the target overall map data to obtain a data transfer result.

[0082] It should be noted that the purpose of data verification is to ensure that the updated data is accurate and meets the predetermined rules and standards. Data verification can be performed by automatically aligning and reconstructing the target monomer data and the target overall map data to ensure data consistency and integrity.

[0083] It can be understood that the automatic alignment and reconstruction of the target monomer data and the target master map data includes base point alignment and entity reconstruction. Base point alignment refers to matching the base points in the monomer data with the corresponding base points in the master map data to ensure that the position of the monomer in the master map is accurate. Entity reconstruction refers to rebuilding the 3D model of the entire building complex based on the updated monomer data and master map data to check whether the geometry and topology of the data are correct.

[0084] It is worth mentioning that during the data verification process, the system automatically detects potential errors and inconsistencies in the data. For example, the system checks whether the size, position and material of the monomers match the layout in the general drawing, and whether there are overlapping or missing elements. If any errors or inconsistencies are found during the data verification process, the system will generate a detailed error report and provide corresponding modification suggestions so that users can quickly locate the problem and make corrections.

[0085] In a feasible implementation, step S30 may include: determining a target monomer base point according to the target monomer data, and determining a target overall map base point according to the target overall map data; performing base point alignment according to the target monomer base point and the target overall map base point to obtain aligned target monomer data and aligned target overall map data; integrating the aligned target monomer data into the aligned target overall map data and performing entity reconstruction to obtain the position and size of the monomer in the overall map; determining a data transfer result according to the position and size of the monomer in the overall map.

[0086] It should be noted that the base point is used to define the position of the monomer in the overall map. During the monomer creation process, the base point coordinates of the monomer will be set and associated with the base point coordinates of the overall map. By aligning the base point of the monomer with the base point of the overall map, the position of the monomer in the overall map can be ensured to be accurate. Base point alignment is a key step in the data verification process, which involves not only coordinate matching, but also verification of the relative position relationship between the monomer and the overall map.

[0087] It is understandable that during the entity reconstruction process, the system will reconstruct the three-dimensional model of the entire building complex based on the updated single-unit data and general plan data. This process not only checks the geometric and topological relationship of the data, but also ensures that the spatial relationship between the single unit and the general plan is correct. Entity reconstruction helps to discover potential design conflicts, such as spatial overlap between units or unreasonable layout.

[0088] It is worth mentioning that during the data verification process, the system will also perform logic verification to ensure that the single-unit data and general plan data comply with design specifications and building regulations. For example, the system will check whether the fire escape passages and evacuation paths of the single unit meet safety standards, and whether the distance between buildings meets the requirements of sunlight and ventilation. Through these comprehensive verifications, the rationality and compliance of the building design can be ensured.

[0089] In the specific implementation, the position and size of the monomer in the master plan can be used to determine whether the layout and size of the monomer meet the overall planning requirements. For example, the system will check whether the monomer exceeds the predetermined building red line, whether it maintains a reasonable distance from the adjacent buildings, and whether it meets the restrictions on building height and volume in the plan, and then obtain the data transfer result, such as a clear prompt of "data transfer successful" or "data transfer failed". If the data transfer is successful, the system will automatically update the relevant records in the database and synchronize the new monomer data and master plan data to various related modules and subsystems to ensure that the information of the entire building project remains consistent and real-time. In the case of data transfer failure, the system will provide detailed error reports and modification suggestions to help users quickly locate the problem and make corrections. For example, if the size of the monomer exceeds the predetermined building red line, the system will prompt the user to adjust the size of the monomer or modify the master plan layout to ensure that it meets the planning requirements. In addition, the system will also provide a historical version comparison function, allowing users to view the data differences between previous versions so that users can understand the specific content and reasons for the changes.

[0090] The present embodiment provides a data transmission method based on single building data and general plan data. The present embodiment first responds to the user's operation instruction, determines the data to be updated based on the operation instruction; updates the data according to the data to be updated and transmits it to the corresponding associated data to obtain the target single building data and the target general plan data; and performs data verification according to the target single building data and the target general plan data to obtain the data transmission result, which can effectively improve the integrity, consistency and efficiency of the data between the single building and the general plan.

[0091] In summary, this embodiment determines the data to be updated according to the user's operating instructions, quickly and efficiently updates the data according to the data to be updated and transmits it to the corresponding related data, thereby effectively improving the consistency of the data, and then performs data verification according to the target monomer data and the target overall drawing data, thereby effectively improving the integrity of the group data, overcoming the technical defects of poor integrity and consistency of design data transmission and low transmission efficiency, and can effectively improve the integrity, consistency and efficiency of the data between the monomer and the overall drawing.

[0092] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 3 , the step S20 further includes steps S201-S202:

[0093] Step S201, when the data to be updated is monomer data, data is updated according to the monomer data and transmitted to the corresponding associated data to obtain target monomer data and target overall map data.

[0094] It should be noted that when the data to be updated is single-body data, the data update may include a single-body creation operation, a single-body upload operation, and a single-body version switching operation, and this embodiment does not impose any specific restrictions on this.

[0095] It is understandable that when the data is updated to create a monomer operation, it specifically includes creating contours, creating axes and creating other entities. Creating contours includes drawing contour geometry, managing contour information and modifying contour information. Drawing the contour geometry of a monomer is usually completed through CAD (such as AutoCAD) or similar drawing software to form a part of the DWG file. When creating a contour, the contour's geometric information (such as coordinate points), monomer ID, contour ID, monomer version number, base point ID and other key information will be recorded in the database. This data will be stored in the "contour entity" of the database entity and is closely associated with the monomer ID. In addition to creating the contour itself, a series of initialization operations are required, including project tree initialization, monomer information initialization, contour table initialization, etc., to ensure that the records in the database are consistent with the entities in the DWG file.

[0096] After creating the outline, other entities related to the monomer are usually created, such as axes, structures, etc. These entities will also record their key information in the database, such as the axis number, monomer ID, axis ID, monomer version number, etc. For each created entity, a corresponding record will be added to the database. These records not only contain basic information about the entity, but may also include version-related metadata for subsequent version control and data tracking.

[0097] When the monomer data needs to be updated, a new version will be created. Each time a monomer is uploaded, a new version will be added, regardless of whether the data has actually changed. This ensures the traceability of the data and the independence between versions. Each new version will add a new record to the database, including version ID, version number, version information record, etc. This information allows users to easily view the historical versions of the monomer and perform necessary comparison and recovery operations.

[0098] In the monomer data, it is used to define the position of the monomer in the overall drawing. During the monomer creation process, the base point coordinates of the monomer will be set and associated with the base point coordinates of the overall drawing. The base point information of the monomer will be recorded in the "Single Base Point Entity" of the database entity, including 1-axis ID, A-axis ID, base point ID, monomer base point coordinates, overall drawing base point coordinates, monomer version number, etc. This information is crucial for the precise positioning of the monomer in the overall drawing.

[0099] After the monomer data is created and initialized, the data will be written back to the DWG file. In this way, the DWG file contains the latest monomer information and can be used by designers and engineers for subsequent design and construction work.

[0100] It is worth noting that when the data is updated to a single-body switching version operation, it includes selecting the version to be switched from the list, querying the database and creating the outline and its affiliated entities, and reconstructing the new entity in DWG. Specifically, it includes: selecting the version to be switched from the list includes checking the single-body version table through the CURD operation (the basic atomic operation for processing data) to obtain the single-table version number / ID, and then updating the single-body base point entity, outline entity, axis entity and other entities according to the single-table version number / ID and the created outline and its affiliated entities. Before reconstructing the new entity in DWG, you need to be prompted whether to clear the original entity. If you decide to clear the original entity, then New entities are reconstructed in DWG based on monomer base point entities, contour entities, axis entities and other entities, where monomer base point entities include information such as 1-axis ID, A-axis ID, base point ID, monomer base point coordinates, general drawing base point coordinates, monomer version number, etc.; contour entities include information such as monomer ID, contour ID, monomer version number, general drawing version number, base point ID, etc., and the general drawing version number in the contour entity is empty; axis entity includes information such as monomer ID, axis ID, axis number, monomer version number, base point ID, etc.; other entities include information such as monomer ID, monomer version number, general drawing version number, base point ID, etc., and the general drawing version number in the contour entity is empty. The above method can ensure smooth switching of monomer data between different versions while maintaining data integrity and consistency.

[0101] In a feasible implementation, step S201 may include: when the data to be updated is monomer data, obtaining the first monomer identifier of the monomer to be updated; constructing a monomer version identifier and a first monomer version number, and associating the monomer version identifier and the first monomer version number with the first monomer identifier to obtain a new monomer version; updating the monomer version entity in the database according to the new monomer version to obtain a new monomer version entity; updating the monomer outline entity and the monomer subsidiary entity in the database to obtain a new monomer outline entity and a new monomer base point entity; associating the new monomer version entity, the new monomer outline entity and the new monomer base point entity to obtain target monomer data; passing the target monomer data to the corresponding general map data to obtain target general map data.

[0102] It should be noted that in this embodiment, data update is a single upload operation, including selecting an upload target, creating a new version, adding a new base point record in the database, adding a new contour record in the database, filling the DWG contour information into the database, and writing each entity information in the database back to the DWG file, wherein DWG is a widely used computer-aided design (CAD) file format for storing two-dimensional and three-dimensional graphic data. In the process of uploading single data, the DWG file plays a vital role because it contains not only the geometric information of the single body, but also the attribute information related to it.

[0103] It can be understood that an entity refers to a data object in a database that represents a specific thing or concept. An entity is a basic unit for storing and managing data. A monomer identifier, or a monomer ID, is a unique identifier that is used to uniquely identify a monomer throughout its life cycle and to distinguish different monomer entities. A monomer version identifier, or a monomer version ID, is a unique identifier that identifies a specific version of a monomer. When any change occurs to a monomer, a new monomer version ID will be generated to distinguish different versions. A monomer version number is a number in the form of a number or string used to track the iteration of a monomer version. The version number is usually used to represent the change history of a monomer, so that users can understand the relationship between different versions. A monomer version entity refers to a data object that represents the monomer version information in a database. It contains a monomer ID, a monomer version ID, a monomer version number, and a monomer version information record. A monomer base point entity refers to a data object that represents the monomer base point information in a database. It contains information such as the 1-axis ID, the A-axis ID, the base point ID, the monomer base point coordinates, the general drawing base point coordinates, and the monomer version number. A monomer outline entity refers to a data object that represents the monomer outline information in a database. It contains the monomer ID, the outline ID, the monomer version number, the general drawing version number, the base point ID, and other information.

[0104] In the specific implementation, when performing a monomer upload operation, you first need to select the upload target, select a monomer (i.e., the monomer to be updated) name node to upload through the list, and query the monomer table through the CURD operation to obtain the monomer ID, i.e., the first monomer identifier. Create a new monomer version, generate the corresponding monomer version identifier and monomer version number, fill in the version information record and associate the monomer ID to obtain a new monomer version entity. Update the monomer outline entity and monomer base point entity in the database by adding new base point records and outline records to obtain a new monomer outline entity and a new monomer base point entity. Associate the new monomer version entity, the new monomer outline entity, and the new monomer base point entity to ensure that the logical relationship between them is correct, and obtain new monomer data, i.e., the target monomer data. Then, pass the updated entity information to the corresponding general map data to ensure the consistency of the monomer data with the general map data. In this process, it is necessary to ensure that the correspondence between the general map version number and the monomer version number is correct, so that the changes in the monomer data can be accurately reflected in the general map data.

[0105] During the process of uploading the monomer data, the DWG file also needs to be updated accordingly. First, the monomer geometry information in the DWG file is synchronized with the monomer base point information in the database to ensure the accuracy of the geometry data. Next, the attribute information in the DWG file is synchronized with the monomer attribute information in the database to ensure the accuracy of the attribute data. After completing these synchronization operations, the updated DWG file is saved and the new monomer data is written back to the DWG file to ensure that the data in the file is consistent with the data in the database. This process usually involves the use of CAD software to ensure the accuracy and completeness of the graphic data.

[0106] It is worth noting that each time an upload operation is performed, a new version will be added, and each time a new version is added, a new record will be added, regardless of whether the original data has changed. Each time a single upload is performed, only the single version number is recorded, and the overall map version number is empty.

[0107] In a feasible implementation manner, the updating of the monomer contour entity and the monomer subsidiary entity in the database to obtain a new monomer contour entity and a new monomer base point entity includes: obtaining the monomer contour entity and the monomer subsidiary entity in the database, and performing contour check and axis check on the monomer contour entity and the monomer subsidiary entity to obtain contour check results and axis check results; when the contour check result is that the contour exists and the axis check result is that the axis intersection is unique, constructing a new monomer contour and a new monomer base point; generating a contour identifier based on the new monomer contour, and generating a first monomer base point identifier and a monomer base point coordinate based on the new monomer base point; updating the monomer contour entity based on the contour identifier, the first monomer base point identifier, the first monomer identifier and the first monomer version number to obtain a new monomer contour entity; updating the monomer subsidiary entity to obtain a first axis identifier; obtaining the overall drawing base point coordinates, and updating the monomer base point entity according to the first axis identifier, the first monomer base point identifier, the monomer base point coordinates, the overall drawing base point coordinates and the first monomer version number to obtain a new monomer base point entity.

[0108] It should be noted that the monomer outline refers to the external boundary or shape of a monomer building, and the monomer outline entity refers to the data object representing the monomer outline information in the database, which includes the monomer ID, outline ID, monomer version number, master plan version number, base point ID and other information. Monomer attachment refers to other information or components related to the monomer, such as the axis. Monomer attachment entity refers to the data object representing the axis information in the database, including monomer ID, axis ID, axis number, monomer version number, base point ID and other information.

[0109] It is understandable that before performing contour checks and axis checks on the monomer contour entities and the monomer subsidiary entities, a project occupancy check is also required to ensure that the update of the monomer data will not conflict with other monomers in the project. Project occupancy check refers to analyzing the space occupancy within the entire project before updating the monomer data to ensure that the new monomer contours and subsidiary entities will not overlap or conflict with existing monomers or project plans. This inspection process usually involves spatial analysis algorithms to ensure the rationality of the monomer data and the coordination of the overall project layout. After the project occupancy check is completed, if the inspection results indicate that the update of the monomer contours and subsidiary entities will not cause conflicts, then the contour check and axis check can continue.

[0110] It is worth mentioning that the contour check is mainly to verify the integrity and accuracy of the monomer contour, ensuring that the contour segments are correctly connected and there is no overlap or omission. The axis check focuses on verifying whether the axis information in the monomer's attached entities is correct, including the length and angle of the axis and whether the intersection with other axes is unique. The axis includes axis 1 and axis A. When axis 1 or axis A does not exist, axis 1 or axis A is not unique, and axis 1 and axis A do not intersect, it is determined that the intersection of the axis is not unique. Otherwise, the intersection of the axis is unique.

[0111] In the specific implementation, when there is a contour and the axis intersection is unique, the absolute coordinates of the intersection are calculated based on the 1-axis and the A-axis, and the absolute coordinates of the intersection are used as the monomer base point coordinates, and the base point coordinates of the previous version of the overall drawing are copied. The monomer base point entity is updated according to the 1-axis ID, A-axis ID, base point ID, monomer base point coordinates, overall drawing base point coordinates, monomer version number and other information to obtain a new monomer base point entity. The monomer contour entity is updated according to the monomer ID, contour ID, monomer version number, overall drawing version number, base point ID and other information to obtain a new monomer contour entity.

[0112] like Figure 3 As shown, Figure 3 This is a data flow diagram for data upload operations. The data upload operations specifically include: the single-unit designer uploads the single-unit information to the general layout design system; the general layout designer uploads the general layout information to the general layout design system; the general layout design system obtains the project and single-unit information by querying five tables, generates single-unit version information and general layout version information based on the single-unit information, general layout information and project, feeds back the single-unit version information to the single-unit designer, and feeds back the single-unit information and general layout version information to the general layout designer.

[0113] like Figure 4 As shown, Figure 4The data flow diagram of the monomer data upload operation specifically includes: the monomer designer uploads the subsidiary entity information and the outline information, draws the outline according to the outline initialization information and the outline information uploaded by the monomer designer and associates the monomer ID to obtain the complete outline information, constructs the outline entity according to the complete outline information and generates the outline ID, draws the subsidiary entity according to the outline ID and the subsidiary entity information uploaded by the monomer designer to obtain the complete subsidiary entity information, constructs the subsidiary entity according to the complete subsidiary entity information, verifies the outline entity and the subsidiary entity respectively to obtain the verified outline information and the verified subsidiary entity information, uploads the monomer data according to the verified outline information, the verified subsidiary entity information and the base point information, receives the monomer version information after uploading, and feeds back the monomer version information to the outline entity and the subsidiary entity, the monomer data upload includes uploading the verified outline information to the database monomer outline data, uploading the verified subsidiary entity information and the base point information to the database monomer subsidiary data, after downloading the database monomer outline data and the database monomer subsidiary data, the monomer data is obtained and sent to the general drawing designer.

[0114] The data flow of the monomer data upload operation also includes determining the occupied project, obtaining the initialized contour data according to the contour entity in the database, drawing the monomer contour according to the initialized contour data and the monomer ID, constructing the monomer contour entity according to the shape information, drawing the axis line, entering and exiting the warehouse, drawing the steps, drawing the ramp and drawing the scattered water according to the contour object ID and the monomer contour, and then uploading the monomer data, selecting the contour and the subordinate entity, and performing the upload rule check, including the occupation check, the contour check and the axis line check, and filling in the version change information when the occupied project, the contour exist and the axis line intersection is unique. Filling in the version change information includes determining the monomer ID according to the monomer table record, and then creating a new version record according to the monomer ID, creating a new contour record, a new other subordinate entity record, a new axis line record and a new base point record according to the version ID, writing the DWG contour data into the database, writing the DWG subordinate entity data into the database, and writing the DWG axis line entity data into the database according to the monomer ID and the version ID, and calculating the intersection and direction of the 1-axis and the A-axis according to the monomer ID and the version ID, and then updating the DWG entity state and sending a database update message.

[0115] Step S202, when the data to be updated is the overall map data, data is updated according to the overall map data and transmitted to the corresponding associated data to obtain target monomer data and target overall map data.

[0116] It should be noted that when the data to be updated is the general map data, the data update may include pulling the individual unit operation, returning the base point operation, uploading the general map operation, switching the general map version operation, and the individual unit association directory tree operation in the general map, etc. This embodiment does not impose specific restrictions on this.

[0117] It can be understood that when the data is updated as a monomer pull operation, the monomer to be loaded is selected from the project tree list, the monomer version table is checked through the CURD operation, the latest monomer version number / ID is obtained, the database is queried and the contour and its affiliated entities are created, and the monomer base point entity, contour entity, axis entity and other entities in the database are updated according to the latest monomer version number / ID, the contour and its affiliated entities, and a prompt is given whether to clear the original entity. When it is determined to clear the original entity, it is determined whether to automatically align. When it is not automatically aligned, the user specifies the base point in DWG and reconstructs the new entity. When it is automatically aligned, the coordinates of the total drawing base point in the monomer base point table are read to determine whether to perform a non-empty check. If a non-empty check is performed, the user specifies the base point in DWG and reconstructs the new entity. If a non-empty check is not performed, the new entity is reconstructed according to the base point position. Among them, the monomer pull operation defaults to pulling the latest monomer version each time.

[0118] During the upload or update process of the general drawing, it may be necessary to update the base point coordinates of the general drawing according to the base point coordinates of the monomer. This usually involves querying the latest monomer version in the database and writing the base point coordinates of the corresponding version of the general drawing, which is also called the return base point operation. When the data is updated as the return base point operation, all axis entities in the DWG are retrieved, and all intersections of axis 1 and axis A are obtained, and then the validity is verified. The latest monomer version in the database is queried according to the monomer ID and the base point coordinates of the corresponding version of the general drawing are written to obtain the new monomer base point entity. Verify the validity of the axis in the DWG to ensure that the axis entities in the DWG file are valid and can be correctly mapped to the records in the database.

[0119] When the data is updated to switch the version of the general drawing, select the version to be switched from the list, check the general drawing version table through the CURD operation, get the general drawing version number / ID, query the database and create the single entity and the general drawing entity, update the single entity and the general drawing entity in the database according to the general drawing version number / ID, the single entity and the general drawing entity, and then prompt whether to clear the original entity. When it is determined to clear the original entity, reconstruct the new entity in DWG, that is, reconstruct the general drawing and its affiliated entities in the DWG file.

[0120] When the data is updated to the monomer association directory tree operation in the general diagram, select the entity to be associated (with filter), perform a validity check, query the monomer table through CURD operation, and write the monomer ID.

[0121] In a feasible implementation, step S202 may include: when the data to be updated is general map data, obtaining the general map identifier of the general map to be updated; constructing a general map version identifier and a general map version number, and associating the general map version identifier and the general map version number with the general map identifier to obtain a new general map version; updating the general map version entity in the database according to the new general map version to obtain a new general map version entity; constructing a new monomer and corresponding monomer attachments, a new general map and corresponding general map attachments; based on the new monomer, the monomer attachment, the new general map and the general map attachment, updating the monomer entities and general map entities in the database to obtain new monomer entities and new general map entities; associating the new general map version entity, the new monomer entity and the new general map entity to obtain target general map data; passing the target general map data to the corresponding monomer data to obtain target monomer data.

[0122] It should be noted that in this embodiment, data update is a general map upload operation. When uploading a general map, select a general map (i.e., the general map to be updated) name node through the list for uploading, query the general map through the CURD operation, and obtain the general map ID. Create a new version record for the general map in the database, including the general map ID, general map version ID, general map version number, and version information record. Each time an upload operation is performed, a new version will be added, and regardless of whether the data has changed, a new record will be added, thereby obtaining a new general map version entity. The general map version entity contains information such as the general map ID, general map version ID, general map version number, and version information record.

[0123] It is understandable that when the data is updated to the general drawing upload operation, the uploaded general drawing file needs to go through a series of verification and processing steps to ensure the accuracy and completeness of the data. The system will check the format and version of the uploaded DWG file to ensure that it meets the preset specifications. After the verification is passed, the system will build a new general drawing version entity based on the extracted information and associate it with the existing general drawing version. This process involves querying and updating existing records in the database to ensure that the new general drawing version entity can correctly reflect the current general drawing status. Subsequently, the system will update the monomer entities and general drawing entities in the database based on the new general drawing version entity, which includes creating new monomers and general drawing subsidiary entities and associating them with the corresponding monomers and general drawings. During this process, the system will perform a series of logical checks and data consistency checks to ensure that the updated data can correctly reflect the actual project status.

[0124] It is worth noting that a new master map version entity, a new single entity and a new master map entity will be generated and associated to form the target master map data. These data will then be passed to the corresponding single entity data to ensure that the single entity data can reflect the latest master map status.

[0125] During the entire data update process, the system will monitor and record all operations and changes in real time so that problems can be quickly located and repaired. In addition, the system will generate corresponding log files to record detailed information of each data update, including the operator, operation time, operation content, etc., for auditing and tracking.

[0126] In a feasible implementation manner, the monomer entities and general map entities in the database are updated based on the new monomer, the monomer attachment, the new general map and the general map attachment to obtain new monomer entities and new general map entities, including: generating a second monomer identifier and a second monomer version number according to the new monomer, and generating a second axis identifier according to the monomer attachment; determining the corresponding monomer base point according to the new monomer, and obtaining the second monomer base point coordinates corresponding to the monomer base point; updating the monomer entities in the database according to the second monomer identifier, the second monomer version number, the second axis identifier, the general map version number and the second monomer base point coordinates to obtain new monomer entities; generating a general map identifier according to the new general map, and generating a structure identifier according to the general map attachment; updating the general map entity in the database according to the general map identifier, the structure identifier and the general map version number to obtain a new general map entity.

[0127] It should be noted that when reading DWG monomer entity information, it is also necessary to obtain the monomer ID, outline ID, monomer version number and other information for the monomer in the general drawing. Then, add new monomers and their affiliated records in the database, that is, for the monomers in the general drawing, add new monomers and their affiliated records (such as outlines, axes, etc.) in the database. Then, according to the monomer ID, entity ID (including outline ID and axis ID), monomer version number, general drawing version number and base point ID, the new monomer entity and monomer affiliated entities can be obtained.

[0128] It can be understood that the DWG general plan entity information is read to obtain the general plan ID, entity ID (such as structure ID, road ID, site ID, etc.), general plan version number, base point ID and other information in the DWG single entity. Then, a new general plan entity record is added to the database, that is, a new record is added to the database for the general plan and its affiliated entities (such as structures, roads, sites, etc.), including their respective IDs, version numbers and other information, and then a new general plan entity can be obtained according to the general plan ID, structure ID and general plan version number.

[0129] In the specific implementation, in the data update process, in order to ensure data security, permission control should be performed on different versions of single data to restrict unauthorized personnel from accessing and modifying the data. When single data changes and a new version is created, the system should promptly notify relevant team members of the change information through emails, message notifications, etc.

[0130] In this embodiment, by quickly and efficiently updating data according to the data to be updated and transmitting it to the corresponding associated data, the consistency and efficiency of the data transmission process are effectively improved.

[0131] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the data transmission method of the present application based on single building data and general plan data. More forms of simple transformations based on this technical concept are all within the scope of protection of the present application.

[0132] This application also provides a data transmission device based on single building data and general plan data, please refer to Figure 5 The data transmission device based on the single building data and the general plan data includes:

[0133] The determination module 10 is used to respond to the user's operation instruction and determine the data to be updated based on the operation instruction.

[0134] The transmission module 20 is used to update the data according to the data to be updated and transmit it to the corresponding associated data to obtain the target monomer data and the target overall map data.

[0135] The verification module 30 is used to perform data verification based on the target monomer data and the target overall map data to obtain a data transfer result.

[0136] The present embodiment provides a data transmission device based on single building data and general plan data. The present embodiment responds to the user's operation instruction, determines the data to be updated based on the operation instruction; updates the data according to the data to be updated and transmits it to the corresponding associated data to obtain the target single building data and the target general plan data; performs data verification according to the target single building data and the target general plan data to obtain the data transmission result, which can effectively improve the integrity, consistency and efficiency of the data between the single building and the general plan.

[0137] In summary, this embodiment determines the data to be updated according to the user's operating instructions, quickly and efficiently updates the data according to the data to be updated and transmits it to the corresponding related data, thereby effectively improving the consistency of the data, and then performs data verification according to the target monomer data and the target overall drawing data, thereby effectively improving the integrity of the group data, overcoming the technical defects of poor integrity and consistency of design data transmission and low transmission efficiency, and can effectively improve the integrity, consistency and efficiency of the data between the monomer and the overall drawing.

[0138] Optionally, the transmission module 20 is also used to, when the data to be updated is monomer data, update the data according to the monomer data and transmit it to the corresponding associated data to obtain target monomer data and target overall map data; when the data to be updated is overall map data, update the data according to the overall map data and transmit it to the corresponding associated data to obtain target monomer data and target overall map data.

[0139] Optionally, the transmission module 20 is also used to obtain the first monomer identifier of the monomer to be updated when the data to be updated is monomer data; construct a monomer version identifier and a first monomer version number, and associate the monomer version identifier and the first monomer version number with the first monomer identifier to obtain a new monomer version; update the monomer version entity in the database according to the new monomer version to obtain a new monomer version entity; update the monomer outline entity and the monomer subsidiary entity in the database to obtain a new monomer outline entity and a new monomer base point entity; associate the new monomer version entity, the new monomer outline entity and the new monomer base point entity to obtain target monomer data; transfer the target monomer data to the corresponding general map data to obtain target general map data.

[0140] Optionally, the transmission module 20 is also used to obtain the monomer contour entity and the monomer affiliated entity in the database, and perform contour inspection and axis inspection on the monomer contour entity and the monomer affiliated entity to obtain contour inspection results and axis inspection results; when the contour inspection result is that the contour exists and the axis inspection result is that the axis intersection is unique, construct a new monomer contour and a new monomer base point; generate a contour identifier based on the new monomer contour, and generate a first monomer base point identifier and a monomer base point coordinate based on the new monomer base point; update the monomer contour entity based on the contour identifier, the first monomer base point identifier, the first monomer identifier and the first monomer version number to obtain a new monomer contour entity; update the monomer affiliated entity to obtain a first axis identifier; obtain the overall drawing base point coordinates, and update the monomer base point entity according to the first axis identifier, the first monomer base point identifier, the monomer base point coordinates, the overall drawing base point coordinates and the first monomer version number to obtain a new monomer base point entity.

[0141] Optionally, the transmission module 20 is also used to obtain the general map identifier of the general map to be updated when the data to be updated is the general map data; construct the general map version identifier and the general map version number, and associate the general map version identifier and the general map version number with the general map identifier to obtain a new general map version; update the general map version entity in the database according to the new general map version to obtain a new general map version entity; construct a new monomer and corresponding monomer attachments, a new general map and corresponding general map attachments; based on the new monomer, the monomer attachment, the new general map and the general map attachment, update the monomer entity and the general map entity in the database to obtain a new monomer entity and a new general map entity; associate the new general map version entity, the new monomer entity and the new general map entity to obtain the target general map data; transfer the target general map data to the corresponding monomer data to obtain the target monomer data.

[0142] Optionally, the transmission module 20 is also used to generate a second monomer identifier and a second monomer version number based on the new monomer, and generate a second axis identifier based on the monomer attachment; determine the corresponding monomer base point based on the new monomer, and obtain the second monomer base point coordinates corresponding to the monomer base point; update the monomer entity in the database according to the second monomer identifier, the second monomer version number, the second axis identifier, the general drawing version number and the second monomer base point coordinates to obtain a new monomer entity; generate a general drawing identifier based on the new general drawing, and generate a structure identifier based on the general drawing attachment; update the general drawing entity in the database according to the general drawing identifier, the structure identifier and the general drawing version number to obtain a new general drawing entity.

[0143] Optionally, the verification module 30 is also used to determine a target monomer base point based on the target monomer data, and to determine a target overall map base point based on the target overall map data; to perform base point alignment based on the target monomer base point and the target overall map base point to obtain aligned target monomer data and aligned target overall map data; to integrate the aligned target monomer data into the aligned target overall map data and perform entity reconstruction to obtain the position and size of the monomer in the overall map; and to determine a data transfer result based on the position and size of the monomer in the overall map.

[0144] The data transmission device based on single building data and general plan data provided by the present application adopts the data transmission method based on single building data and general plan data in the above-mentioned embodiment, which can solve the technical problem of how to effectively improve the integrity, consistency and efficiency of data between single buildings and general plans. Compared with the prior art, the beneficial effects of the data transmission device based on single building data and general plan data provided by the present application are the same as the beneficial effects of the data transmission method based on single building data and general plan data provided by the above-mentioned embodiment, and the other technical features of the data transmission device based on single building data and general plan data are the same as the features disclosed in the above-mentioned embodiment method, which will not be repeated here.

[0145] The present application provides a data transmission device based on single building data and general plan data, and the data transmission device based on single building data and general plan data includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the data transmission method based on single building data and general plan data in the above-mentioned embodiment one.

[0146] Reference below Figure 6 , which shows a schematic diagram of the structure of a data transmission device based on single building data and general plan data suitable for implementing the embodiment of the present application. The data transmission device based on single building data and general plan data in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The data transmission device based on the single building data and the general plan data shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0147] like Figure 6As shown, the data transmission device based on the single building data and the general plan data may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM: Read Only Memory) 1002 or the program loaded from the storage device 1003 to the random access memory (RAM: Random Access Memory) 1004. In the RAM 1004, various programs and data required for the operation of the data transmission device based on the single building data and the general plan data are also stored. The processing device 1001, the ROM 1002 and the RAM 1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems may be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 may allow the data transmission device based on the single building data and the general plan data to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a data transmission device based on the single building data and the general plan data with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have instead.

[0148] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0149] The data transmission device based on single building data and general plan data provided by the present application adopts the data transmission method based on single building data and general plan data in the above embodiment, which can solve the technical problem of how to effectively improve the integrity, consistency and efficiency of data between single buildings and general plans. Compared with the prior art, the beneficial effects of the data transmission device based on single building data and general plan data provided by the present application are the same as the beneficial effects of the data transmission method based on single building data and general plan data provided by the above embodiment, and the other technical features in the data transmission device based on single building data and general plan data are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0150] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0151] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0152] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the data transmission method based on the single building data and the general plan data in the above-mentioned embodiment.

[0153] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0154] The above-mentioned computer-readable storage medium may be included in the data transmission device based on the single building data and the general plan data; or it may exist independently without being assembled into the data transmission device based on the single building data and the general plan data.

[0155] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by a data transmission device based on single building data and general plan data, the data transmission device based on single building data and general plan data: responds to the user's operation instruction, determines the data to be updated based on the operation instruction; updates the data according to the data to be updated and transmits it to the corresponding associated data to obtain target single building data and target general plan data; and verifies the data according to the target single building data and target general plan data to obtain the data transmission result.

[0156] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0157] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0158] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0159] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned data transmission method based on single-unit building data and general plan data, and can solve the technical problem of how to effectively improve the integrity, consistency, and efficiency of data between single units and general plans. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the data transmission method based on single-unit building data and general plan data provided by the above-mentioned embodiment, and will not be repeated here.

[0160] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the data transmission method based on single building data and general plan data as described above.

[0161] The computer program product provided by the present application can solve the technical problem of how to effectively improve the integrity, consistency and efficiency of the data between the single building and the master plan. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the data transmission method based on the single building data and the master plan data provided by the above embodiment, which will not be elaborated here.

[0162] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A data transmission method based on single building data and general plan data, characterized in that: The method comprises: In response to an operation instruction of a user, determining data to be updated based on the operation instruction; Update the data according to the data to be updated and transfer it to the corresponding associated data to obtain the target monomer data and the target overall map data; Data verification is performed based on the target monomer data and the target overall map data to obtain a data transfer result.

2. The method according to claim 1, characterized in that The step of updating the data according to the data to be updated and transmitting the data to the corresponding associated data to obtain the target monomer data and the target overall map data includes: When the data to be updated is monomer data, data is updated according to the monomer data and transmitted to the corresponding associated data to obtain target monomer data and target overall map data; When the data to be updated is the overall map data, data is updated according to the overall map data and transmitted to the corresponding associated data to obtain target monomer data and target overall map data.

3. The method according to claim 2, characterized in that When the data to be updated is monomer data, data is updated according to the monomer data and transmitted to corresponding associated data to obtain target monomer data and target overall map data, including: When the data to be updated is monomer data, obtaining a first monomer identifier of the monomer to be updated; Constructing a monomer version identifier and a first monomer version number, and associating the monomer version identifier and the first monomer version number with the first monomer identifier to obtain a new monomer version; Update the monomer version entity in the database according to the new monomer version to obtain a new monomer version entity; The monomer contour entity and the monomer attached entity in the database are updated to obtain a new monomer contour entity and a new monomer base point entity; Associating the new monomer version entity, the new monomer outline entity and the new monomer base point entity to obtain target monomer data; The target monomer data is transferred to the corresponding overall map data to obtain the target overall map data.

4. The method according to claim 3, characterized in that The updating of the monomer contour entity and the monomer attached entity in the database to obtain a new monomer contour entity and a new monomer base point entity includes: Acquire a monomer contour entity and a monomer subsidiary entity in a database, and perform contour inspection and axis inspection on the monomer contour entity and the monomer subsidiary entity to obtain contour inspection results and axis inspection results; When the contour check result is that the contour exists and the axis check result is that the axis intersection is unique, construct a new monomer contour and a new monomer base point; Generate a contour identifier based on the new monomer contour, and generate a first monomer base point identifier and a monomer base point coordinate based on the new monomer base point; The monomer contour entity is updated based on the contour identifier, the first monomer base point identifier, the first monomer identifier, and the first monomer version number to obtain a new monomer contour entity; The monomer-affiliated entity is updated to obtain a first axis mark; The overall drawing base point coordinates are obtained, and the monomer base point entity is updated according to the first axis identifier, the first monomer base point identifier, the monomer base point coordinates, the overall drawing base point coordinates and the first monomer version number to obtain a new monomer base point entity.

5. The method according to claim 3, characterized in that When the data to be updated is the overall map data, data is updated according to the overall map data and transmitted to the corresponding associated data to obtain the target monomer data and the target overall map data, including: When the data to be updated is general map data, obtaining a general map identifier of the general map to be updated; Constructing a general map version identifier and a general map version number, and associating the general map version identifier and the general map version number with the general map identifier to obtain a new general map version; Update the master map version entity in the database according to the new master map version to obtain a new master map version entity; Construct new monomers and corresponding monomer dependencies, new general graphs and corresponding general graph dependencies; Based on the new monomer, the monomer attachment, the new general map and the general map attachment, the monomer entity and the general map entity in the database are updated to obtain a new monomer entity and a new general map entity; Associating the new master map version entity, the new monomer entity and the new master map entity to obtain target master map data; The target overall map data is transferred to the corresponding monomer data to obtain the target monomer data.

6. The method according to claim 5, characterized in that The updating of the monomer entity and the general diagram entity in the database based on the new monomer, the monomer attachment, the new general diagram and the general diagram attachment to obtain the new monomer entity and the new general diagram entity includes: Generate a second monomer identifier and a second monomer version number according to the new monomer, and generate a second axis identifier according to the monomer attachment; Determine a corresponding monomer base point according to the new monomer, and obtain coordinates of a second monomer base point corresponding to the monomer base point; The monomer entity in the database is updated according to the second monomer identifier, the second monomer version number, the second axis identifier, the general drawing version number and the second monomer base point coordinates to obtain a new monomer entity; Generating a general plan identification according to the new general plan, and generating a structure identification according to the general plan attachment; The general plan entity in the database is updated according to the general plan identifier, the structure identifier and the general plan version number to obtain a new general plan entity.

7. The method according to claim 1, characterized in that The data verification is performed according to the target monomer data and the target overall map data to obtain the data transfer result, including: Determine a target monomer base point according to the target monomer data, and determine a target overall map base point according to the target overall map data; Base point alignment is performed according to the target monomer base point and the target overall image base point to obtain aligned target monomer data and aligned target overall image data; Integrate the aligned target monomer data into the aligned target overall image data and perform entity reconstruction to obtain the position and size of the monomer in the overall image; The data transfer result is determined according to the position and size of the monomer in the overall diagram.

8. A data transmission device based on single building data and general plan data, characterized in that: The data transmission device based on the single building data and the general plan data comprises: A determination module, configured to respond to an operation instruction of a user and determine data to be updated based on the operation instruction; A transfer module, used for updating data according to the data to be updated and transferring it to the corresponding associated data to obtain target monomer data and target overall map data; The verification module is used to perform data verification based on the target monomer data and the target overall map data to obtain a data transfer result.

9. A data transmission device based on single building data and general plan data, characterized in that: The data transmission device based on single building data and general plan data comprises: a memory, a processor, and a data transmission program based on single building data and general plan data stored in the memory and executable on the processor, wherein the data transmission program based on single building data and general plan data is configured to implement the data transmission method based on single building data and general plan data as described in any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium stores a data transfer program based on single building data and general plan data, and when the data transfer program based on single building data and general plan data is executed by a processor, the data transfer method based on single building data and general plan data as described in any one of claims 1 to 7 is implemented.

Images