Rail transit system data generation method and system based on structure definition file, electronic equipment and readable storage medium

Abstract

The invention provides a rail transit system data generation method based on a structure definition file, electronic equipment and a readable storage medium. The method comprises the following steps: S1, generating a corresponding XSD file based on a rail transit system database; s2, loading and analyzing the XSD file, and generating a visual interface; s3, analyzing a rail transit system database, and filling the interface with data in the rail transit system database; s4, editing the data in the interface, and updating the rail transit system database based on an editing result of the data in the interface; s5, updating the XSD file; and updating an interface and a rail transit system database based on the updated XSD file. The method has the advantages that the flexibility, adaptability and correctness of making and maintaining the rail transit system data are greatly improved, and the working efficiency of rail transit database management is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of rail transit database management, and in particular to a rail transit system data generation method, system, electronic equipment and readable storage medium based on a structure definition file. Background Art

[0002] In the train automatic control system, two-way communication is achieved between the train and the ground equipment through the communication network. Among them, the database of rail transit system data is the basis for the operation of the train automatic control system and its subsystems, and contains important information about the physical equipment and logical areas related to signal control on the current line, such as the location parameters of tracks, switches, signal machines, secondary detection equipment, and signal area division.

[0003] The production process of rail transit system data is very cumbersome, requiring data producers to edit the system database files according to construction drawings and other parameter documents. Due to the large number of adaptation projects and frequent product upgrades, it is necessary to add or delete equipment parameters and re-divide signal areas according to product functions, and the structure of the rail transit system database files also needs to be upgraded accordingly.

[0004] Under this premise, how to achieve high flexibility and high adaptability of the aforementioned operations and improve the efficiency of data production in the rail transit system has become an urgent problem to be solved. Summary of the invention

[0005] The purpose of the present invention is to provide a rail transit system data generation method, system, electronic device and readable storage medium based on a structure definition file, which can intuitively display the data hierarchy in the rail transit system database and can visually edit the data in the rail transit system database. At the same time, the rail transit system database can be upgraded by upgrading the structure definition file. The problem of poor data consistency and high maintenance cost when managing the rail transit system database in a traditional way is solved.

[0006] In order to achieve the above object, a method for generating rail transit system data based on a structure definition file comprises the following steps:

[0007] S1. Generate the corresponding XSD file based on the rail transit system database;

[0008] S2. Load and parse the XSD file to generate a visual interface;

[0009] S3, parsing the rail transit system database, and filling the interface with data from the rail transit system database;

[0010] S4, editing the data in the interface; and updating the rail transit system database based on the editing result of the data in the interface;

[0011] S5. Update the XSD file; update the interface and the rail transit system database based on the updated XSD.

[0012] Optionally, the rail transit system database includes at least: equipment location information, equipment configuration parameter information, route location information and logical area information; the equipment includes at least: tracks, signals, switches, vehicles; the logical area information includes at least: track sections, speed limit areas.

[0013] Optionally, the XSD file includes a root element of complex attributes, which corresponds to a root node of the rail transit system database; the root node includes a plurality of child nodes stored in a tree structure, and the child nodes correspond to tables or fields in the tables in the rail transit system database;

[0014] The root element includes multiple child elements, which correspond to the multiple child nodes respectively; the upper and lower hierarchical relationships between the multiple child elements correspond to the parent-child relationships between the multiple child nodes;

[0015] The XSD file describes the hierarchical relationship between the plurality of sub-elements, the constraints of the sub-elements, and the reference relationship between different sub-elements.

[0016] Optionally, the constraint conditions include at least: data type, enumeration type, and maximum number of occurrences of the sub-element.

[0017] Optionally, step S2 includes:

[0018] S21, loading the XSD file;

[0019] S22, traverse and parse the root elements and sub-elements of the XSD file;

[0020] S23, generating an interface component based on the parsing result in step S22;

[0021] S24, organizing the generated interface components to form a tree display area, a list display area and an editing area in the interface;

[0022] The tree display area displays the plurality of sub-nodes in the form of a tree structure; the list display area is used to display the table corresponding to the selected sub-node and the data in the table; the data selected in the list display area is displayed through the editing area and the data is edited.

[0023] Optionally, step S22 includes:

[0024] S221. If the attribute of the root element / child element is a simple attribute, record its constraint condition;

[0025] S222: If the attribute of the root element / child element is a complex attribute, recursively parse its descendant elements and the attributes of the descendant elements to generate a hierarchical structure;

[0026] S223. If the attribute of the root element / child element is an optional attribute, record a combination of descendant elements of the root element / child element;

[0027] S224: If the root element / child element includes a reference element, generate a corresponding reference rule for the reference element.

[0028] Optionally, step S23 includes:

[0029] S231, generating a text box or a drop-down box for the sub-element of the simple attribute;

[0030] S232, generating a nested interface for the root element / sub-element of the complex attribute;

[0031] S233, generating a selection button and an editable box for the sub-element of the optional attribute;

[0032] S234. Generate a selection button and an editable drop-down box for the reference element, and fill in the reference data.

[0033] Optionally, in step S4, by clicking the "Save" button in the editing area, the edited data is submitted to the rail transit system database, and the legality of the submitted data is verified; if it is illegal, the rail transit system database is not updated.

[0034] The present invention also provides a rail transit system data generation system based on a structure definition file, which is used to implement the rail transit system data generation method according to the present invention, and the system comprises:

[0035] XSD file parsing module, used to load and parse XSD files;

[0036] Database parsing module, used to parse the rail transit system database;

[0037] An interface processing module, which generates a corresponding interface based on the parsed XSD file, and loads the data in the rail transit system database into the interface based on the parsing result of the rail transit system database; the interface processing module also updates the rail transit system database based on the editing result of the data in the interface;

[0038] A structure upgrade module updates the interface and the rail transit system database based on the updated XSD file.

[0039] Optionally, the interface processing module further verifies whether the editing result is legal, and if so, updates the rail transit system database.

[0040] The present invention also provides an electronic device, comprising: a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the steps of the rail transit system data generation method based on the structure definition file as described in the present invention are implemented.

[0041] The present invention also provides a readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method for generating rail transit system data based on a structure definition file as described in the present invention are implemented.

[0042] Compared with the prior art, the beneficial effects of the present invention include at least:

[0043] 1) The rail transit system data generation method, system, electronic device and readable storage medium based on the structure definition file of the present invention generate a loading interface for the rail transit system data according to the structure definition file (i.e., XSD file). In the XSD file, the upper and lower hierarchical relationships between the child elements correspond to the parent-child relationship between the child nodes in the rail transit system database. Therefore, the visual interface generated according to the XSD file can reflect the data hierarchy in the rail transit system database. The present invention can also automatically parse the rail transit system database and load the corresponding data in the database into the generated interface, thereby realizing a visual display of the data content in the rail transit system database, which has good intuitiveness. The present invention can also visually edit the data in the rail transit system database, has good ease of use, and reduces the difficulty of editing operations. The automated parsing and interface generation process reduces manual operations. The present invention greatly improves the work efficiency and accuracy of rail transit database management and reduces labor costs.

[0044] 2) The present invention can also upgrade the XSD file based on project changes and equipment changes on the line. When the XSD file is updated, the visual interface and the rail transit system database can be automatically synchronized and adjusted without manual intervention. It has high flexibility and universality, and significantly reduces the workload.

[0045] 3) The present invention can intuitively input and modify data through tree display, list display and editing area, and the user experience is good. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solution of the present invention, the following briefly introduces the drawings required for the description. Obviously, the drawings described below are an embodiment of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work:

[0047] Figure 1 A flowchart of a method for generating rail transit system data based on a structure definition file in an embodiment of the present invention;

[0048] Figure 2 It is a structural diagram of a rail transit system data generation system based on a structure definition file in an embodiment of the present invention. DETAILED DESCRIPTION

[0049] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0050] It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0051] It should also be understood that the terms used in this application specification are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in this application specification and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0052] It should be further understood that the term “and / or” used in the specification and appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0053] As used in this specification and the appended claims, the term "if" may be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [described condition or event] is detected" may be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0054] In addition, in the description of the present application, the terms "first", "second", "third", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0055] This embodiment provides a method for generating rail transit system data based on a structure definition file, such as Figure 1 As shown, it includes the steps:

[0056] S1. Generate the corresponding XSD file based on the rail transit system database.

[0057] In this embodiment, the rail transit system database includes at least: equipment location information, equipment configuration parameter information, route location information and logical area information; the equipment includes at least: tracks, signals, switches, and vehicles. The logical area information includes at least: track sections and speed restriction areas.

[0058] The following is part of the content of the XSD file in this embodiment.

[0059] <xs:element name="GENERIC_SYSTEM_PARAMETERS">

[0060] <xs:complextype>

[0061] <xs:sequence>

[0062] <xs:element name="Tracks"type="TrackType"maxOccurs="65535" / >

[0063] <xs:element name="Points"type="PointType"maxOccurs="65535" / >

[0064] < / xs:sequence>

[0065] <xs:attribute name="Date"type="xs:date" / >

[0066] <xs:attribute name="Version"type="xs:string" / >

[0067] <xs:attribute name="Writer_Name"type="xs:string" / >

[0068] < / xs:complextype>

[0069]

[0070] <xs:complexType name="PointType">

[0071] <xs:sequence>

[0072] <xs:element name="ID"type="xs:integer" / >

[0073] <xs:element name="Name"type="xs:string" / >

[0074] <xs:element name="Track_ID"type="xs:integer" / >

[0075] <xs:element name="Orientation"type="xs:string"minOccurs="0">

[0076] <xs:element name="Kp_Toe">

[0077] <xs:complextype>

[0078] <xs:attributeGroup ref="Kp" / >

[0079] < / xs:complextype>

[0080]

[0081] <xs:choice>

[0082] <xs:element name="Interoperable_ID type=type="xs:integer" / >

[0083] <xs:element name="Interoperable_ID_Not_Defined"type="xs:integer"fixed="0" / >

[0084] < / xs:choice>

[0085] < / xs:sequence>

[0086]

[0087] <xs:keyref name="ref-point-to-track"refer="key-track-id">

[0088] <xs:selector xpath="Points / Track_ID" / >

[0089] <xs:field xpath="." / >

[0090]

[0091] <xs:key name="key-track-id">

[0092] <xs:selector xpath="Tracks" / >

[0093] <xs:field xpath="@ID" / >

[0094]

[0095] The XSD file includes a root element of a complex attribute, which corresponds to a root node of the rail transit system database. The root node includes multiple child nodes stored in a tree structure, which correspond to tables or fields in the tables in the rail transit system database.

[0096] The root element includes multiple child elements, and the multiple child elements correspond to multiple child nodes respectively. The upper and lower hierarchical relationships between the multiple child elements correspond to the parent-child relationships between the multiple child nodes. The XSD file describes the upper and lower hierarchical relationships between the multiple child elements, the constraints of the child elements, and the reference relationships between different child elements. The constraints include at least: the data type, enumeration type, and maximum number of occurrences of the child elements.

[0097] The XSD file in this embodiment includes a root element GENERIC_SYSTEM_PARAMETERS of a complex attribute. The attributes of the root element GENERIC_SYSTEM_PARAMETERS include date, version and author information.

[0098] The root element GENERIC_SYSTEM_PARAMETERS includes the sub-element Tracks and the sub-element Points, which correspond to the tables named Tracks and Points in the rail transit system database, respectively. The tables Points and Tracks store the parameters of multiple turnouts and multiple tracks, respectively.

[0099] In the above XSD file, under the sub-element Points, there are also sub-elements ID, Name, Track_ID, Orientation, Kp_Toe, Interoperable_ID, which correspond to the fields ID, Name, Track_ID, Orientation, Kp_Toe, Interoperable_ID in the table Points, respectively. The fields ID, Name, Track_ID, Orientation, Kp_Toe, Interoperable_ID are used to store the device ID number, device name, track ID, direction, turnout center coordinates, and interconnection ID, respectively. Among them, the attributes of the sub-elements ID, Name, Track_ID, and Orientation are simple attributes (Simple Attribute). The attributes of the sub-element Kp_Toe are complex attributes, and the attributes of the sub-element Interoperable_ID are optional attributes (Optional Attribute).

[0100] The sub-elements under the sub-element Points can also be called descendant elements of the sub-element Points. The data type of the sub-element determines the data type of the corresponding field. For example, if the data type of the sub-element ID is "Interger (integer)", the data type of the ID field is also an integer.

[0101] The root element GENERIC_SYSTEM_PARAMETERS also contains reference elements ref-point-to-track and key-track-id. The reference relationship between the two is: the descendant element Track_ID of the child element Points is associated with the descendant element ID of the child element Tracks using a reference. In other words, in the rail transit system database, the content of the Track_ID field in the table Points is consistent with the content of the Track_ID field in the table Tracks.

[0102] S2. Load and parse the XSD file to generate a visual interface.

[0103] Step S2 includes:

[0104] S21. Load the XSD file.

[0105] S22. Traverse and parse the root elements and sub-elements of the XSD file.

[0106] Step S22 includes:

[0107] S221. If the attribute of the root element / child element is a simple attribute, record its constraint condition.

[0108] S222. If the attribute of the root element / child element is a complex attribute, recursively parse its descendant elements and the attributes of the descendant elements to generate a hierarchical structure.

[0109] S223. If the attribute of the root element / child element is an optional attribute, record the combination of descendant elements of the root element / child element.

[0110] S224. If the root element / child element contains a reference element, generate a corresponding reference rule for the reference element.

[0111] S23. Generate an interface component based on the analysis result in step S22.

[0112] In this embodiment, step S23 includes:

[0113] S231. Generate a text box or a drop-down box for the child elements of simple attributes.

[0114] S232. Generate a nested interface for the root element / sub-element of complex attributes.

[0115] S233. Generate a selection button and an editable box for the child element of the optional attribute.

[0116] S234. Generate a selection button and an editable drop-down box for the reference (Keyref / key) element, and fill in the reference data.

[0117] S24. Organize the generated interface components to form a tree display area, a list display area and an editing area in the interface.

[0118] S3. Parse the rail transit system database and fill the interface with data in the rail transit system database.

[0119] In this embodiment, the root node GENERIC_SYSTEM_PARAMETERS and the child nodes Tracks and Points under the root node GENERIC_SYSTEM_PARAMETERS are displayed in the tree display area.

[0120] When the child node Points in the tree display area is selected, the table Points is displayed in the list display area, and the values ​​of the fields ID, Name, Track_ID, Orientation, Kp_Toe, and Interoperable_ID are loaded into the table Points. As shown below:

[0121] Table Points

[0122] ID Name Track_ID Orientation Kp_Toe Interoperable_ID 1 P001 T001 Convergent Kp_Toe_Detail Not_Defined 2 P002 T002 Divergent Kp_Toe_Detail 2

[0123] The present invention generates a loading interface for rail transit system data based on a structure definition file (i.e., an XSD file). Since the upper and lower hierarchical relationships between child elements in the XSD file correspond to the parent-child relationships between child nodes in the rail transit system database. Therefore, the visualization interface generated based on the XSD file can reflect the data hierarchy in the rail transit system database. The present invention can also automatically parse the rail transit system database and fill the generated interface with the corresponding data in the database, thereby realizing a visualization display of the data content in the database, which is very intuitive.

[0124] S4. Edit the data in the interface; based on the editing results of the data in the interface, update the rail transit system database.

[0125] In one embodiment, the first row of the Points table is selected in the list display area. The first row of the Points table is displayed in the editing area, and the data of the row is edited in the editing area (for example, the content of the Orientation field is modified to "Divergent"). After the editing is completed, click the "Save" button, and the rail transit database adaptively modifies the content in the database according to the editing results.

[0126] The following shows the steps for a user to add a new turnout data to a rail transit system database in another embodiment:

[0127] 1) Click the "New" button on the interface.

[0128] 2) Click the Points node in the list display area to enter the editing area.

[0129] 3) In the editing area, enter ID=3, Name=P003, select Track_ID=T003, and select Orientation=Convergent.

[0130] 4) Click the Kp_Toe field in the editing area to display the Value, Corrected_Gap_Value, and Is_In_Long_Gap fields under the Kp_Toe field, enter: Kp_Toe.Value=200, Kp_Toe.Corrected_Gap_Value=10, select Kp_Toe.Is_In_Long_Gap=true.

[0131] 5) In the edit area, Interoperable_ID displays a check box and an edit box. When "Interoperable_ID_Not_Defined" is checked, a fixed value of 0 is displayed in the edit box. When "Interoperable_ID" is checked, the corresponding value can be entered in the edit box.

[0132] 6) Click the "Save" button to submit the newly created data to the rail transit system database. Verify whether the submitted data is legal (for example, check whether the Track_Id field exists in the Tracks table).

[0133] 7) If the data submitted is not legal, the rail transit system database will not be updated. If it is legal, the newly added turnout data will be saved to the rail transit system database.

[0134] The present invention can visually edit the data in the rail transit system database, has good usability, and reduces the difficulty of editing operations. The automated parsing and interface generation process reduces manual operations. The present invention greatly improves the work efficiency and accuracy of rail transit database management and reduces labor costs.

[0135] S5. Update the XSD file; update the interface and the rail transit system database based on the updated XSD.

[0136] In the present invention, the XSD file can be upgraded based on project changes and equipment changes on the line. The updated XSD file is loaded and parsed, and the combination and display mode of the interface are dynamically adjusted to ensure that the interface is consistent with the new version of the XSD file. At the same time, the structure and content of the system database are automatically updated to adapt to the definitions and constraints in the new version of the XSD file without manual intervention.

[0137] Therefore, the present invention has high flexibility and universality, and significantly reduces the workload of maintaining the system database when the project changes or the equipment on the line changes.

[0138] In one embodiment, the sub-element Interoperable_ID is deleted under the sub-element Points in the XSD file, and a new sub-element Safety_Level is added. The description of the sub-element Safety_Level in the upgraded XSD file is as follows:

[0139]

[0140]

[0141] After the XSD file is upgraded, perform the following steps:

[0142] A) Load the updated XSD file and automatically update the interface, including:

[0143] A-1) Add a new column Safety_Level (indicating safety level) to the Points table in the list display area and delete the column Interoperable_ID.

[0144] A-2) Add a drop-down box in the editing area, with options including High, Medium, and Low.

[0145] B) Ensure the compatibility and consistency of the updated data, migrate the rail transit system database, add a new field Safety_Level to all turnout devices and add a default value (such as Medium), delete the Interoperable_ID field of all turnout devices, and automatically clean up the corresponding content in the database.

[0146] C) Synchronize the newly added columns to the Points table in the rail transit system database to ensure that the database content is consistent with the interface display content.

[0147] Updated table Points

[0148] ID Name Track_ID Orientation Kp_Toe Safety_Level 1 P001 T001 Convergent Kp_Toe_Detail Medium 2 P002 T002 Divergent Kp_Toe_Detail Medium

[0149] Furthermore, this embodiment also provides a rail transit system data generation system based on a structure definition file, which is used to implement the rail transit system data generation method as described in this embodiment. Figure 2 As shown, the system includes: an XSD file parsing module 11, a database parsing module 12, an interface processing module 13 and a structure upgrading module 14.

[0150] The XSD file parsing module 11 is used to load and parse the XSD file.

[0151] The database parsing module 12 is used to parse the rail transit system database 20 .

[0152] The interface processing module 13 generates a corresponding interface based on the parsed XSD file (eg, interface component), and loads data in the rail transit system database 20 into the interface based on the parsed result of the rail transit system database 20 .

[0153] When the edited data is submitted to the rail transit system database 20 through the interface, the interface processing module 13 also verifies whether the editing result in the interface is legal. If legal, the rail transit system database 20 is updated based on the editing result in the interface.

[0154] The structure upgrade module 14 updates the interface and the rail transit system database 20 based on the updated XSD file.

[0155] Furthermore, this embodiment also provides an electronic device, comprising: a memory, a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the steps of the rail transit system data generation method based on the structure definition file as described in the present invention are implemented.

[0156] Furthermore, this embodiment also provides a readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method for generating rail transit system data based on a structure definition file as described in the present invention are implemented.

[0157] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0158] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A method for generating rail transit system data based on a structure definition file, characterized in that: Contains steps: S1. Generate the corresponding XSD file based on the rail transit system database; S2. Load and parse the XSD file to generate a visual interface; S3, parsing the rail transit system database, and filling the interface with data from the rail transit system database; S4, editing the data in the interface; and updating the rail transit system database based on the editing result of the data in the interface; S5, updating the XSD file; The interface and the rail transit system database are updated based on the updated XSD.

2. The rail transit system data generation method based on the structure definition file according to claim 1, characterized in that: The rail transit system database includes at least: equipment location information, equipment configuration parameter information, route location information and logical area information; the equipment includes at least: tracks, signals, switches, and vehicles; the logical area information includes at least: track sections and speed limit areas.

3. The rail transit system data generation method based on the structure definition file according to claim 1, characterized in that: The XSD file includes a root element of complex attributes, which corresponds to a root node of a rail transit system database; the root node includes a plurality of child nodes stored in a tree structure, and the child nodes correspond to tables or fields in the tables in the rail transit system database; The root element includes multiple child elements, which correspond to the multiple child nodes respectively; the upper and lower hierarchical relationships between the multiple child elements correspond to the parent-child relationships between the multiple child nodes; The XSD file describes the hierarchical relationship between the plurality of sub-elements, the constraints of the sub-elements, and the reference relationship between different sub-elements.

4. The method for generating rail transit system data based on a structure definition file according to claim 3, characterized in that: The constraint conditions include at least: data type, enumeration type, and maximum number of occurrences of the sub-element.

5. The method for generating rail transit system data based on a structure definition file according to claim 3, characterized in that: Step S2 includes: S21, loading the XSD file; S22, traverse and parse the root elements and sub-elements of the XSD file; S23, generating an interface component based on the parsing result in step S22; S24, organizing the generated interface components to form a tree display area, a list display area and an editing area in the interface; The tree display area displays the plurality of sub-nodes in the form of a tree structure; the list display area is used to display the table corresponding to the selected sub-node and the data in the table; the data selected in the list display area is displayed through the editing area and the data is edited.

6. The method for generating rail transit system data based on a structure definition file according to claim 5, characterized in that: Step S22 includes: S221. If the attribute of the root element / child element is a simple attribute, record its constraint condition; S222: If the attribute of the root element / child element is a complex attribute, recursively parse its descendant elements and the attributes of the descendant elements to generate a hierarchical structure; S223. If the attribute of the root element / child element is an optional attribute, record a combination of descendant elements of the root element / child element; S224: If the root element / child element includes a reference element, generate a corresponding reference rule for the reference element.

7. The method for generating rail transit system data based on a structure definition file according to claim 6, characterized in that: Step S23 includes: S231, generating a text box or a drop-down box for the sub-element of the simple attribute; S232, generating a nested interface for the root element / sub-element of the complex attribute; S233, generating a selection button and an editable box for the sub-element of the optional attribute; S234. Generate a selection button and an editable drop-down box for the reference element, and fill in the reference data.

8. The method for generating rail transit system data based on a structure definition file according to claim 5, characterized in that: In step S4, by clicking the "Save" button in the editing area, the edited data is submitted to the rail transit system database, and the legitimacy of the submitted data is verified; If it is illegal, the rail transit system database will not be updated.

9. A rail transit system data generation system based on a structure definition file, used to implement the rail transit system data generation method according to any one of claims 1 to 8, characterized in that: The system comprises: XSD file parsing module, used to load and parse XSD files; Database parsing module, used to parse the rail transit system database; An interface processing module, which generates a corresponding interface based on the parsed XSD file, and loads the data in the rail transit system database into the interface based on the parsing result of the rail transit system database; the interface processing module also updates the rail transit system database based on the editing result of the data in the interface; A structure upgrade module updates the interface and the rail transit system database based on the updated XSD file.

10. The rail transit system data generation system based on the structure definition file according to claim 9, characterized in that: The interface processing module also verifies whether the editing result is legal, and if so, updates the rail transit system database.

11. An electronic device, characterized in that: The electronic device comprises: a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the steps of the method for generating rail transit system data based on a structure definition file as described in any one of claims 1 to 8 are implemented.

12. A readable storage medium, characterized in that: The readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for generating rail transit system data based on a structure definition file as described in any one of claims 1 to 8 are implemented.

Images