Highway design data version control method

Abstract

The invention discloses a highway design data version control method. The method comprises the following steps: constructing a local library, an intra-group library, a professional library and a project library; determining each design line and project group of the project; a designer designs the corresponding stake number paragraph data of the corresponding design line; the designer submits the project file to the intra-group library and updates the project version number of the project file; the project group leader pulls the project file in the intra-group library to the local library for auditing, submits the project file to the professional library and updates the project version number of the project file; and the total project manager pulls the project file of each specialty in the specialty library for auditing, submits the project file to the project library and updates the project version number. According to the method, the time and energy of a designer are not additionally occupied for version control; the accuracy of design data is improved; and design collaboration is promoted.

Description

Technical Field

[0001] The present invention relates to the field of information technology application and data management technology in the field of highway design, and in particular to a highway design data version control method. Background Art

[0002] In the field of highway design, the design process usually involves the collaborative work of multiple designers. However, in the traditional design model, each designer is often only responsible for designing their designated highway section or professional part. The non-digital collaborative design method will lead to the following problems:

[0003] First, designers lack experience in digital collaboration. In the traditional highway design process, designers usually rely on paper documents for professional exchanges and communication. This approach has obvious limitations, especially in terms of data consistency and real-time performance. Due to the cumbersomeness of modifying and transmitting paper documents, it is easy to cause inconsistencies in data between different disciplines or different design stages, such as data mismatches between the plane, longitudinal and cross-section of the highway, or changes in the plane design are not reflected in the relevant designs such as the bridge alignment in a timely manner, resulting in displacement and other problems. This data inconsistency not only affects the accuracy of the design, but may also lead to errors and delays in the construction phase.

[0004] Secondly, regarding the version control of design data. Currently, many designers use the "Save As" function on their local computers to save multiple versions of design data. This method lacks a unified version management mechanism, making version control confusing and difficult to track. At the same time, designers can usually only rely on file names or simple text descriptions to annotate version changes. This method is not only not intuitive, but also difficult to accurately reflect the differences and changes between versions. This non-standard version control method greatly reduces the effectiveness of collaborative design, makes data sharing and collaboration between different designers difficult, and increases communication costs and the possibility of errors.

[0005] Therefore, in order to solve the above problems, the present invention proposes a highway design data version control method. The method realizes centralized management, unified version control and collaborative design of design data by introducing the concepts of version control and collaborative design. Through this method, the consistency and accuracy of design data can be ensured, the design efficiency and quality can be improved, the communication cost and error rate can be reduced, and the digital transformation and upgrading of the highway design industry can be promoted. Summary of the invention

[0006] The purpose of the present invention is to provide a highway design data version control method to solve the problems of chaotic data version management and low efficiency of collaborative work in the highway design process. Through the application of this method, unified management and version control of design data can be achieved, the efficiency of collaborative work between design teams can be improved, the accuracy and consistency of design files can be ensured, and the overall quality and efficiency of highway design can be improved.

[0007] Solving data consistency issues

[0008] In view of the data consistency problem caused by the lack of digital collaboration experience of designers and their reliance on traditional paper documents for professional exchanges, this patent aims to achieve centralized management and sharing of design data by introducing a digital version control method to ensure that the data between various parts of highway design (such as plane, longitudinal, cross section, etc.) remains highly consistent. This helps to reduce design errors and construction problems caused by inconsistent data and improve the accuracy and reliability of the design.

[0009] Standard version management

[0010] In response to the problem that designers rely on the local "Save As" function to save multiple versions and the version description is unclear, this patent proposes a unified version control method for tracking and managing the change history of design data. Through clear version identification and change records, designers can clearly understand the source, modification content and differences of each version, thereby improving the effectiveness of collaborative design.

[0011] Improve the reliability and accuracy of design data

[0012] Through digital collaborative design and version control methods, it is possible to ensure that design data is accurately transmitted and updated between various links and professional fields. This helps to reduce errors and omissions in the information transmission process and improve the reliability and accuracy of design data. At the same time, through automated data verification and inspection mechanisms, errors and inconsistencies in the data can be discovered and corrected in a timely manner, further ensuring the accuracy of design data.

[0013] The above-mentioned purpose of the present invention is achieved by the following technical means:

[0014] A highway design data version control method adopts the following technical scheme to realize unified management and version control of design data, as well as collaborative work and data sharing among design teams, and includes the following steps.

[0015] Step 1: Build the designer's local library, the server's group library, professional library, and project library;

[0016] Step 2: Determine the various design lines and project groups of the project;

[0017] Step 3: For each project group, the project leader creates a new project file corresponding to the project group in the local library. The version number of the project file is the project version number, and submits the project file to the group library, or the designer pulls other professional project files from the professional library to the group library;

[0018] The project file includes multiple design line data. The attributes of the design line data include the design line ID and the design line name. In the entire project, the design line ID remains unchanged, and the design line name may be different due to different designer notes.

[0019] Each design line data includes data of each pile number section. Different pile number sections may involve different specialties, such as routes, bridges, tunnels, etc. The attributes of the pile number section data include the starting pile number, the ending pile number, the effective time, and the expiration time.

[0020] The data of each pile number section include plane data, longitudinal data, cross-section data, intersection data, earthwork data, and structure data.

[0021] Step 4: The designer pulls the project file from the group library and designs the corresponding pile number segment data of the corresponding design line.

[0022] Step 5: The designer submits the project file containing the designed pile number segment data to the group library. The group library performs design line consistency check and data conflict check, publishes the pile number segment data, updates the effective time and expiration time of the pile number segment data, and updates the project version number of the project file.

[0023] For newly created and updated pile number paragraph data, the effective time is usually set to the time when the pile number paragraph data is published, and the expiration time is "9999-12-31 23:59:59", which means that the pile number paragraph data will never be invalid in theory unless the pile number paragraph data is updated. Before publishing a new version of the pile number paragraph data, the expiration time of the last version of the pile number paragraph data updated this time is updated to one second before the time when the new version of the pile number paragraph data is published. Set the effective time of the new version of the pile number paragraph data to the current time, and the expiration time to "9999-12-31 23:59:59".

[0024] Step 6: The project leader pulls the project files in the group library to the local library for review, and submits them to the professional library after review. The professional library performs design line consistency check and data conflict check, publishes pile number segment data, updates the effective time and expiration time of the pile number segment data, and updates the project version number of the project file. The professional library feeds back the updated project files to the group library.

[0025] The professional library is used to store project files of various project groups (different majors can correspond to different project groups, including routes, bridges, tunnels, etc.). The project files of a project group can be used by designers of project groups of other majors, but cannot be modified by designers of project groups of other majors.

[0026] Step 7: The general project manager pulls the project files of each discipline from the professional library for review, and submits them to the project library after review. The project library performs design line consistency check and data conflict check on the project files of each discipline, publishes the pile number segment data, integrates the project files of each discipline, and updates the project version number of the project files. The discrete project files of each discipline are integrated into a complete overall project file to ensure the integrity and traceability of each design line data of the overall project file.

[0027] The design line consistency check includes the following steps:

[0028] Compare the design lines of the submitted project file with those of the target library. The target library is the internal library, professional library or project library to which the project file is submitted. The route design is carried out based on the design line. The design line is determined first, and then the design is carried out for this design line.

[0029] Extract the design line ID and design line name from the submitted project file, and compare the extracted design line ID and design line name with the design line ID and design line name of the project file in the target library to see if they are consistent:

[0030] If the design line IDs are consistent but the design line names are inconsistent, the submitter is prompted to choose to keep the design line name in the submitted project file or modify the design line name in the submitted project file to be consistent with that in the target library;

[0031] If the design line IDs are inconsistent but the design line names are consistent, the submitter is prompted to determine whether the design line in the submitted project file and the design line in the target library are the same design line. If so, the design line ID of the submitted project file is modified to be consistent with the design line ID in the target library.

[0032] If the design line ID and design line name are the same, the design line consistency check passes.

[0033] Data conflict checking includes the following steps:

[0034] Check whether the submitted design line data conflicts with the design line data in the target library. If there is a conflict: prompt the user that there is a conflict, and list the pile number segment data of the conflicting design line data. The user can choose whether to use the target library version or the local library version for each pile number segment data;

[0035] Conflicts mainly refer to data conflicts. Designer A and Designer B are both modifying the design of the same design line. Designer A submits the design line data to the target library first. When Designer B submits the same design line data later, a conflict prompt will appear. The design line data on the target library has changed. Designer B needs to choose whether to use the target library version or the modified version of the local library for the design line data.

[0036] When checking for data conflicts, the verification is performed according to the design lines and paragraphs. The steps are as follows:

[0037] Verify design line: compare the design line data of the target library with the design line data of the target library for the same design line ID. If they are inconsistent, it will prompt that the design line data conflict;

[0038] Further, the pile number paragraph data of the submitted project file with the same design line ID is compared with the pile number paragraph data of the target library. If they are inconsistent, a pile number paragraph data conflict is prompted;

[0039] Furthermore, for the same design line ID and the same pile number segment, the plane data of the submitted project file is compared with the plane data of the target library. If they are inconsistent, a plane data conflict is prompted, and the user can choose whether to use the target library version or the local library version for each pile number segment data;

[0040] Furthermore, for the same design line ID and the same pile number section, the longitudinal data of the submitted project file is compared with the longitudinal data of the target library. If they are inconsistent, a longitudinal data conflict is prompted;

[0041] Furthermore, for the same design line ID and the same pile number segment, the cross-section data of the submitted project file is compared with the cross-section data of the target library. If they are inconsistent, a cross-section data conflict is prompted;

[0042] Furthermore, for the same design line ID and the same pile number segment, the cross data of the submitted project file is compared with the cross data of the target library. If they are inconsistent, a cross data conflict is prompted;

[0043] Furthermore, for the same design line ID and the same pile number segment, the earthwork data of the submitted project file is compared with the earthwork data of the target library. If they are inconsistent, a prompt will be given that the earthwork data conflict;

[0044] Furthermore, for the same design line ID and the same pile number segment, the structure data of the submitted project file is compared with the structure data of the target library. If they are inconsistent, a structure data conflict is prompted.

[0045] Compared with the prior art, the present invention has the following beneficial effects:

[0046] (1) No extra time and energy is spent on version control by designers

[0047] This method effectively reduces the extra workload of designers on version control. Through automated version management or intelligent prompt system, designers do not need to spend extra time and energy to manually track and update the version of design data. They can focus more on the design itself and improve design efficiency and quality. This automated version control method not only reduces the possibility of human error, but also makes the entire design process smoother and more efficient.

[0048] (2) Improve the accuracy of design data

[0049] By implementing the version control method, every modification of the pile number and paragraph data of the design line data of the highway design project file will be recorded in detail, ensuring the transparency and traceability of data changes. This can not only reduce data errors and confusion, but also quickly locate and correct errors when problems occur, thereby significantly improving the accuracy of design data.

[0050] With version control, designers can clearly know the source, modification content and time of each pile number segment data version, making the design process more rigorous and reliable.

[0051] (3) Promote design collaboration

[0052] Traditional highway design often adopts a stand-alone mode, and it is difficult to effectively coordinate data between different pile number sections. The version control method can realize the sharing and collaborative editing of pile number section data, so that different pile number section data can be seamlessly merged, thereby improving design efficiency and quality.

[0053] Through version control, designers can view and update other designers' work progress and data in real time, reduce duplication of work and communication costs, and enhance the collaboration capabilities of the entire design team.

[0054] (4) If problems are found during data submission and merging, they can be discovered and corrected in a timely manner

[0055] In the process of design line data submission and merging, this method can detect and find problems in real time, providing designers with a quick feedback mechanism. Once version conflicts or other potential problems are found, the problems will be presented in a visual form, which is convenient for quick location and modification. This form greatly shortens the time for problem solving, reduces the risk in the design process, and also ensures the consistency and accuracy of design data.

[0056] In summary, this patent can bring significant beneficial effects in the above aspects by implementing version control. These effects will help improve the overall quality and efficiency of highway design and promote the sustainable development of the highway construction industry. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 It is a project file structure diagram of the present invention;

[0058] Figure 2 It is the overall diagram of data interaction of the present invention; DETAILED DESCRIPTION

[0059] In order to facilitate those skilled in the art to understand and implement the present invention, the present invention is further described in detail below in conjunction with embodiments. It should be understood that the implementation examples described herein are only used to illustrate and explain the present invention and are not used to limit the present invention.

[0060] A highway design data version control method adopts the following technical scheme to realize unified management and version control of design data, as well as collaborative work and data sharing among design teams, and includes the following steps.

[0061] Step 1: Build the designer's local library, the server's group library, professional library, and project library;

[0062] Step 2: Determine the various design lines of the project and build a project team according to different disciplines.

[0063] In this embodiment, the overall project is divided into project groups, among which:

[0064] Project Group 1 is responsible for the route design of the main line with a pile number range of K0+000 to K100+000;

[0065] Project Team 2 is responsible for the route design of the main line within the pile number range of K101+000 to K200+000;

[0066] Project Group 3 is responsible for the design of bridges within the main design line's pile number range of K5+000~K5+500, K106+000~K107+000, and K160+000~K160+500.

[0067] Arrangement of designers for each project team:

[0068] In project group 1, team member A is responsible for the route design of the pile number range K0+000~K40+000, team member B is responsible for the route design of the pile number range K41+000~K100+000, and is the leader of route group 1 (project leader).

[0069] In Project Group 2, member C is responsible for the route design of the pile number range K101+000~K150+000, member D is responsible for the route design of the pile number range K151+000~K200+000, and is the leader of Route Group 2 (project leader).

[0070] In project group three, member E is responsible for bridge design and route group three (project leader) for the pile number range of K5+000~K5+500, K106+000~K107+000, and K160+000~K160+500.

[0071] Step 3: For each project group, the project leader creates a new project file corresponding to the project group in the local library. The version number of the project file is the project version number, and submits the project file to the group library, or the designer pulls other professional project files from the professional library to the group library;

[0072] The project file includes multiple design line data. The attributes of the design line data include the design line ID and the design line name. In the entire project, the design line ID remains unchanged, and the design line name may be different due to different designer notes.

[0073] Each design line data includes data of each pile number section. Different pile number sections may involve different specialties, such as routes, bridges, tunnels, etc. The attributes of the pile number section data include the starting pile number, the ending pile number, the effective time, and the expiration time.

[0074] The data of each pile number section include plane data, longitudinal data, cross-section data, intersection data, earthwork data, and structure data.

[0075] In this embodiment:

[0076] The project leader of Project Group 1 creates the project file and performs plane alignment work, forming a new project version number 0f981d97967794526e73e7d1, and the corresponding version number within the group is V1-1.

[0077] The designers and project leader of Project 1 implement the subsequent steps 4-6.

[0078] The project leader of Project Group 2 created the project file and carried out plane alignment work, forming a new project version number 0f981d97967794526e73e7e1, and the corresponding group version number is V2-1.

[0079] The designers and project leader of Project Group 2 implement the subsequent steps 4-6.

[0080] The project files of the internal library of Project Group 3 are pulled from the professional library. The designers and project leader of Project Group 3 implement the subsequent steps 4-6.

[0081] Step 4: The designer pulls the project file from the group library and designs the corresponding pile number segment data of the corresponding design line.

[0082] Step 5: The designer submits the project file containing the designed pile number segment data to the group library. The group library performs design line consistency check and data conflict check, publishes the pile number segment data, updates the effective time and expiration time of the pile number segment data, and updates the project version number of the project file.

[0083] For newly created and updated pile number paragraph data, the effective time is usually set to the time when the pile number paragraph data is published, and the expiration time is "9999-12-31 23:59:59", which means that the pile number paragraph data will never be invalid in theory unless the pile number paragraph data is updated. Before publishing a new version of the pile number paragraph data, the expiration time of the last version of the pile number paragraph data updated this time is updated to one second before the time when the new version of the pile number paragraph data is published. Set the effective time of the new version of the pile number paragraph data to the current time, and the expiration time to "9999-12-31 23:59:59".

[0084] In this embodiment, the project version numbers of the project files pulled to the local library by members A and B of project group one are both "0f981d97967794526e73e7d1", and the corresponding in-group version number is "V1-1". Members A and B respectively complete the route design of the corresponding pile number segment data, and submit the project files to the in-group library successively. When submitting, a design line consistency check and a data conflict check are performed, and the effective time and expiration time of the pile number segment data are updated. The project version numbers of the project files submitted by members A and B to the in-group library are "0f981d97967794526e73e7d2" and "0f981d97967794526e73e7d3" respectively, and the corresponding in-group version numbers are "V1-2" and "V1-3". In the subsequent step 6, the project leader pulls the project file with the project version number "0f981d97967794526e73e7d3", and after discovering the problem, makes modifications. The modified project version number is "0f981d97967794526e73e7d4".

[0085] The project version numbers of the project files pulled to the local library by members C and D of project group 2 are both "0f981d97967794526e73e7e1", and the corresponding group version numbers are "V2-1". Members C and D respectively completed the route design of the corresponding pile number section data, and submitted the project files to the group library one after another. When submitting, they performed a design line consistency check and a data conflict check, and updated the effective time and expiration time of the pile number section data. The project version numbers of the project files submitted by members C and D to the group library are "0f981d97967794526e73e7e2" and "0f981d97967794526e73e7e3" respectively, and the corresponding group version numbers are "V2-2" and "V2-3". In the subsequent step 6, the project leader pulls the project file with the project version number "0f981d97967794526e73e7e3", finds the problem, and modifies it. The modified project version number is "0f981d97967794526e73e7e4", and the corresponding group version number is "V2-4"

[0086] In this embodiment, the project leader of project group 2 first submits the project file with the revised version number "0f981d97967794526e73e7e4" to the professional library.

[0087] The project version number of the project files pulled to the local library by member E of project group 3 is "0f981d97967794526e73e7e4". Member E completes the bridge design of the corresponding pile number segment data, and submits the project files to the group library. When submitting, the design line consistency check and data conflict check are performed, and the effective time and expiration time of the pile number segment data are updated. The project version number of the project files submitted by member E to the group library is "0f981d97967794526e73e7f1", and the corresponding group version number is "V3-1". In the subsequent step 6, the project leader pulls the project file with the project version number "0f981d97967794526e73e7f1", and after discovering the problem, he modifies it. The modified project version number is "0f981d97967794526e73e7f2", and the corresponding group version number is "V3-2".

[0088] Step 6: The project leader pulls the project files in the group library to the local library for review, and submits them to the professional library after review. The professional library performs design line consistency check and data conflict check, publishes pile number segment data, updates the effective time and expiration time of the pile number segment data, and updates the project version number of the project file. The professional library feeds back the updated project files to the group library.

[0089] As an optional solution, the project leader pulls the project files in the group library to the local library for review, and after review, it can be submitted to the professional library, which will perform design line consistency check and data conflict check, publish pile number segment data, update the effective time and expiration time of the pile number segment data, and update the project version number of the project file. The professional library will feed back the updated project files to the group library.

[0090] The professional library is used to store project files of various project groups (different majors can correspond to different project groups, including routes, bridges, tunnels, etc.). The project files of a project group can be used by designers of project groups of other majors, but cannot be modified by designers of project groups of other majors.

[0091] Step 7: The general project manager pulls the project files of each discipline from the professional library for review, and submits them to the project library after review. The project library performs design line consistency check and data conflict check on the project files of each discipline, publishes the pile number segment data, integrates the project files of each discipline, and updates the project version number of the project files. The discrete project files of each discipline are integrated into a complete overall project file to ensure the integrity and traceability of each design line data of the overall project file.

[0092] The design line consistency check includes the following steps:

[0093] Compare the design lines of the submitted project file with those of the target library. The target library is the internal library, professional library or project library to which the project file is submitted. The route design is carried out based on the design line. The design line is determined first, and then the design is carried out for this design line.

[0094] Extract the design line ID and design line name from the submitted project file, and compare the extracted design line ID and design line name with the design line ID and design line name of the project file in the target library to see if they are consistent:

[0095] If the design line IDs are consistent but the design line names are inconsistent, the submitter is prompted to choose to keep the design line name in the submitted project file or modify the design line name in the submitted project file to be consistent with that in the target library;

[0096] If the design line IDs are inconsistent but the design line names are consistent, the submitter is prompted to determine whether the design line in the submitted project file and the design line in the target library are the same design line. If so, the design line ID of the submitted project file is modified to be consistent with the design line ID in the target library.

[0097] If the design line ID and design line name are the same, the design line consistency check passes.

[0098] Data conflict checking includes the following steps:

[0099] Check whether the submitted design line data conflicts with the design line data in the target library. If there is a conflict: prompt the user that there is a conflict, and list the pile number segment data of the conflicting design line data. The user can choose whether to use the target library version or the local library version for each pile number segment data;

[0100] Conflicts mainly refer to data conflicts. Designer A and Designer B are both modifying the design of the same design line. Designer A submits the design line data to the target library first. When Designer B submits the same design line data later, a conflict prompt will appear. The design line data on the target library has changed. Designer B needs to choose whether to use the target library version or the modified version of the local library for the design line data.

[0101] When checking for data conflicts, the verification is performed according to the design lines and paragraphs. The steps are as follows:

[0102] Verify design line: compare the design line data of the target library with the design line data of the target library for the same design line ID. If they are inconsistent, it will prompt that the design line data conflict;

[0103] Further, the pile number paragraph data of the submitted project file with the same design line ID is compared with the pile number paragraph data of the target library. If they are inconsistent, a pile number paragraph data conflict is prompted;

[0104] Furthermore, for the same design line ID and the same pile number segment, the plane data of the submitted project file is compared with the plane data of the target library. If they are inconsistent, a plane data conflict is prompted, and the user can choose whether to use the target library version or the local library version for each pile number segment data;

[0105] Furthermore, for the same design line ID and the same pile number section, the longitudinal data of the submitted project file is compared with the longitudinal data of the target library. If they are inconsistent, a longitudinal data conflict is prompted;

[0106] Furthermore, for the same design line ID and the same pile number segment, the cross-section data of the submitted project file is compared with the cross-section data of the target library. If they are inconsistent, a cross-section data conflict is prompted;

[0107] Furthermore, for the same design line ID and the same pile number segment, the cross data of the submitted project file is compared with the cross data of the target library. If they are inconsistent, a cross data conflict is prompted;

[0108] Furthermore, for the same design line ID and the same pile number segment, the earthwork data of the submitted project file is compared with the earthwork data of the target library. If they are inconsistent, a prompt will be given that the earthwork data conflict;

[0109] Furthermore, for the same design line ID and the same pile number segment, the structure data of the submitted project file is compared with the structure data of the target library. If they are inconsistent, a structure data conflict is prompted.

[0110] When pulling project files, you can pull them according to the effective time or according to the project version number.

[0111] It should be noted that the embodiments described in the present invention are merely examples of the spirit of the present invention. Those skilled in the art may make various modifications or additions to the described embodiments or replace them in similar ways, but they will not deviate from the spirit of the present invention or exceed the scope defined by the attached claims.

Claims

1. A highway design data version control method, characterized in that: The following steps are involved: Step 1: Build local libraries, group libraries, professional libraries, and project libraries; Step 2: Determine the various design lines and project groups of the project; Step 3: For each project group, the project leader creates a new project file corresponding to the project group in the local library. The version number of the project file is the project version number, and submits the project file to the group library, or the designer pulls other professional project files from the professional library to the group library; Step 4: The designer pulls the project file from the group library and designs the corresponding pile number segment data of the corresponding design line; Step 5: The designer submits the project file containing the designed pile number segment data to the group library, which performs design line consistency check and data conflict check, publishes the pile number segment data, updates the effective time and expiration time of the pile number segment data, and updates the project version number of the project file; Step 6: The project leader pulls the project files in the group library to the local library for review, and submits them to the professional library after review. The professional library performs design line consistency check and data conflict check, publishes pile number segment data, updates the effective time and expiration time of the pile number segment data, and updates the project version number of the project file. The professional library feeds back the updated project files to the group library; Step 7: The chief project manager pulls the project files of each discipline from the professional library for review, and submits them to the project library after review. The project library performs design line consistency check and data conflict check on the project files of each discipline, publishes the pile number paragraph data, integrates the project files of each discipline, and updates the project version number of the project files.

2. A highway design data version control method according to claim 1, characterized in that: The project file includes a plurality of design line data, and the attributes of the design line data include a design line ID and a design line name.

3. A highway design data version control method according to claim 2, characterized in that: The design line data includes various pile number segment data, and the attributes of the pile number segment data include the starting pile number, the end pile number, the effective time, and the expiration time; The pile number segment data includes plane data, longitudinal data, cross-section data, intersection data, earthwork data, and structure data.

4. A highway design data version control method according to claim 1, characterized in that: The updating of the validity time and expiration time of the pile number segment data comprises the following steps: For newly created and updated pile number segment data, the effective time is set to the time when the pile number segment data is published, and the expiration time is "9999-12-31 23:59:59"; For the previous version of the pile number paragraph data, the expiration time is updated to one second before the release time of the new version of the pile number paragraph data.

5. A highway design data version control method according to claim 1, characterized in that: The design line consistency check includes the following steps: Compare the design lines of the submitted project files with those of the target library, which is the group library, professional library or project library to which the project files are submitted; Extract the design line ID and design line name from the submitted project file, and compare the extracted design line ID and design line name with the design line ID and design line name of the project file in the target library to see if they are consistent: If the design line IDs are consistent but the design line names are inconsistent, the submitter is prompted to choose to keep the design line name in the submitted project file or modify the design line name in the submitted project file to be consistent with that in the target library; If the design line IDs are inconsistent but the design line names are consistent, the submitter is prompted to determine whether the design line in the submitted project file and the design line in the target library are the same. If so, the design line ID of the submitted project file is modified to be consistent with the design line ID in the target library. If the design line ID and the design line name are the same, the design line consistency check passes; otherwise, the design line consistency check fails.

6. A highway design data version control method according to claim 1, characterized in that: The data conflict check comprises the following steps: Compare the design line data of the target library submitted with the same design line ID with the design line data of the target library. If they are inconsistent, it will prompt a design line data conflict; Compare the pile number paragraph data of the submitted project file with the same design line ID with the pile number paragraph data of the target library. If they are inconsistent, it will prompt that the pile number paragraph data conflict; For the same design line ID and the same pile number segment, the plane data of the submitted project file is compared with the plane data of the target library. If they are inconsistent, a plane data conflict prompt will be displayed, and the user can choose whether to use the target library version or the local library version for each pile number segment data; For the same design line ID and the same pile number section, compare the longitudinal data of the submitted project file with the longitudinal data of the target library. If they are inconsistent, it will prompt that the longitudinal data conflict; For the same design line ID and the same pile number segment, the cross-section data of the submitted project file is compared with the cross-section data of the target library. If they are inconsistent, a cross-section data conflict is prompted; For the same design line ID and the same pile number segment, compare the cross data of the submitted project file with the cross data of the target library. If they are inconsistent, a cross data conflict will be prompted. For the same design line ID and the same pile number section, compare the earthwork data of the submitted project file with the earthwork data of the target database. If they are inconsistent, it will prompt that the earthwork data conflict; For the same design line ID and the same pile number segment, the structural data of the submitted project file is compared with the structural data of the target library. If they are inconsistent, a structural data conflict is prompted.

Images