Road design specification translation verification method and system based on shape constraint language

Abstract

The invention discloses a road design specification translation verification method and system based on a shape constraint language, and the method comprises the steps: S1, obtaining a road model file in an IFC format, and converting the road model file into an RDF data graph through a pre-established RDF converter; s2, constructing an attribute shape graph of the road model, and obtaining a new RDF data graph according to the RDF data graph and the attribute shape graph based on a rule engine of an SHACL processor; s3, translating specification articles for verifying road design specifications into a regular shape graph; and S4, taking the regular shape graph and the new RDF data graph as input of an SHACL processor, performing road model verification of road shape constraint based on a verification engine of the SHACL processor, and outputting a verification report of the road model. The problems of low automation degree, high labor cost, low efficiency and the like due to the fact that current model design specification inspection mainly depends on inspection personnel to inspect one by one according to specifications are solved.

Description

Technical Field

[0001] The present invention relates to the technical field of road design specification translation, and in particular to a road design specification translation verification method and system based on shape constraint language. Background Art

[0002] As a basic component of transportation infrastructure, roads directly affect traffic safety and quality of life. In order to ensure the safety of road projects, strict road design specifications have been formulated. The specifications written in natural language are provided for human reading and cannot be understood and processed by computers. At present, the design specification inspection of the model mainly relies on inspectors to check one by one according to the specifications, which has problems such as low automation, high labor costs and low efficiency. Summary of the invention

[0003] The present invention provides a road design specification translation and verification method and system based on shape constraint language to overcome the above technical problems.

[0004] In order to achieve the above object, the technical solution of the present invention is:

[0005] A road design specification translation and verification method based on shape constraint language specifically comprises the following steps:

[0006] S1: Obtain a road model file in IFC format and convert it into an RDF data graph through a pre-established RDF converter;

[0007] S2: construct an attribute shape graph of the road model, and obtain a new RDF data graph according to the RDF data graph and the attribute shape graph based on the rule engine of the SHACL processor;

[0008] S3: Translate the specification clauses used to verify the road design specifications into regular shape diagrams;

[0009] S4: Using the regular shape graph and the new RDF data graph as inputs of the SHACL processor, and performing road model verification based on the road shape constraints based on the verification engine of the SHACL processor, and outputting a verification report of the road model.

[0010] Furthermore, the S1 specifically includes the following steps:

[0011] S11: Call the Civil3D_IFC plug-in to convert the preset road model format into an IFC format file;

[0012] S12: Based on the pre-established RDF converter, the IFC format file is converted according to the data conversion rule and the RDF data graph of the road model is obtained.

[0013] Furthermore, the data conversion rule in S12 is specifically:

[0014] The dynamic link library corresponding to the road model is obtained by calling the Ifcopenshell compilation library, and the IFC format file is parsed based on the dynamic link library to obtain the key data of the road model;

[0015] According to the key data of the road model, the route entities and entity relationships in the IFC format file are mapped by entity connection, and the obtained RDF data graph is output in the Turtle syntax format.

[0016] Furthermore, the key data at least includes route entity information for characterizing road segments, entity relationship information for characterizing connection relationships between road segments, attribute information for characterizing route entity length, and corresponding length attribute value;

[0017] The length attribute value includes any one of a double type number, an integer type number, and a string type character string.

[0018] Furthermore, the construction of the attribute shape graph of the road model in S2 includes the following steps:

[0019] S21: By calling the IfcRelDefinesByProperties plug-in, the route entities are physically connected based on the properties of the route entity length;

[0020] S22: Based on the SHACL-SPARQL processor, by adding a route entity length attribute, a component category for distinguishing components of each route entity is obtained, and the component category at least includes a circular arc, a straight line, and a transition curve Clothoid;

[0021] S23: defining the radius attribute of the route entity component according to the optimized route entity to construct a new attribute relationship of the road model, and then obtaining the attribute shape diagram of the road model.

[0022] Furthermore, the method for constructing the new attribute relationship of the road model is as follows:

[0023] Confirm the radius attributes of the road model and the shape nodes of the route entity components;

[0024] Define the connection relationship between the shape nodes of the route entity components, and use SHACL-SPARQL to query the value range of the radius attribute of the existing route entity components;

[0025] Call the CONSTRUCT tool to establish a new attribute relationship between the shape node of the route entity component and the value range of the radius attribute, and obtain the attribute shape diagram.

[0026] Furthermore, the S3 translates the specification clauses used to verify the road design specification into a regular shape diagram, specifically including:

[0027] S31: Structural processing of specification clauses according to the verification requirements of the road model to obtain specification parsing data;

[0028] And the structured processing is specifically as follows

[0029] According to the article number and format characteristics of the specification, the full text of the specification is parsed based on natural language processing technology to obtain the shape constraint category keywords of different inspection specification categories;

[0030] The shape constraint category keywords include at least a circular curve radius, a circular curve length, a road lane width, and a road slope;

[0031] S32: Based on the rule statement of the regular shape graph, construct the regular shape graph according to the specification parsing data; and the rule statement of the regular shape graph at least includes

[0032] Use CirculararcShape to represent the shape constraint category keyword;

[0033] Use the rdf:type sh:NodeShape statement to specify the node shape of a CirculararcShape.

[0034] Use the sh:targetClass ifc:IfcAlignmentHorizontalSegment statement to verify that the route entity is a circular curve;

[0035] Use sh:property[......] statement to express the constraint path of the circular curve radius and circular curve length of the route entity to be verified;

[0036] Use minInclusive to constrain the range of hasCirculararcRadius attribute values;

[0037] Use severity to describe the severity of not meeting the constraint.

[0038] A road design specification translation and verification system based on shape constraint language, comprising a road model building module, an RDF converter acquisition module, a SHACL processor, an attribute shape graph acquisition module, a rule shape graph acquisition module and a verification report acquisition module;

[0039] The road model building module is used to build the road model to be model verified and convert it into a road model file in IFC format;

[0040] The RDF converter acquisition module is used to convert the road model file in IFC format according to the data conversion rule and obtain the RDF data graph of the road model;

[0041] The attribute shape graph acquisition module is used to construct an attribute shape graph of a road model;

[0042] The SHACL processor includes a rule engine module and a verification engine module;

[0043] The rule engine module is used for a rule engine based on a SHACL processor to obtain a new RDF data graph according to the RDF data graph and the attribute shape graph;

[0044] The regular shape map acquisition module is used to translate the specification clauses used to verify the road design specification into a regular shape map;

[0045] The verification engine module is used for verifying the road model of the road shape constraint based on the verification engine of the SHACL processor;

[0046] The verification report acquisition module is used to output a verification report of the road model according to the verification result of the verification engine module.

[0047] Beneficial effects: The present invention provides a road design specification translation and verification method and system based on shape constraint language. By constructing an attribute shape graph of a road model, a rule engine based on a SHACL processor obtains a new RDF data graph according to the RDF data graph and the attribute shape graph, and translates the specification clauses used to verify the road design specification into a rule shape graph. SHACL is combined with the SPARQL query language to achieve specification translation of the road design specification, execute rule checking, and return an inspection report, thereby realizing automatic compliance review of the model, accelerating the review speed, reducing the current dependence of my country's compliance review work on expert knowledge, reducing the subjectivity of the review results, and improving the efficiency, accuracy, and intelligence level of compliance review. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0049] Figure 1 It is a flow chart of the road design specification translation and verification method based on shape constraint language of the present invention;

[0050] Figure 2This is a core block diagram of the translation and verification of the road design specification based on the shape constraint language in this embodiment;

[0051] Figure 3 This is a schematic diagram of the route realization-attribute connection path in this embodiment;

[0052] Figure 4 This is a schematic diagram of constructing the first circular curve in this embodiment;

[0053] Figure 5 This is a schematic diagram for constructing the second circular curve in this embodiment;

[0054] Figure 6 This is a schematic diagram of exporting a road model into an .ifc format file through the Civil3D_IFC_2024 plug-in in this embodiment;

[0055] Figure 7 This is a schematic diagram of converting an ifc file into a ttl file through an RDF converter in this embodiment;

[0056] Figure 8 It is a schematic diagram of the inspection report through the SHACL converter in this embodiment. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are 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.

[0058] This embodiment provides a road design specification translation and verification method based on shape constraint language, such as Figure 1 to Figure 2 As shown, the specific steps include:

[0059] S1: Obtain a road model file in IFC format and convert it into an RDF data graph through a pre-established RDF converter, which specifically includes the following steps:

[0060] S11: Call the Civil3D_IFC_2024 plug-in to convert the preset road model format into an IFC format file;

[0061] S12: Based on the existing RDF converter, convert the IFC format file according to the data conversion rule and obtain the RDF data graph of the road model;

[0062] The data conversion rules are specifically:

[0063] The dynamic link library corresponding to the road model is obtained by calling the Ifcopenshell compilation library, and the IFC format file is parsed based on the dynamic link library to obtain the key data of the road model;

[0064] The key data at least includes route entity information for characterizing road segments, entity relationship information for characterizing connection relationships between road segments, attribute information for characterizing route entity length and corresponding length attribute value;

[0065] The length attribute value includes any one of a double type number, an integer type number, and a string type character string;

[0066] Based on the entities and entity relationships in the plug-in IFC4x3_ADD2 standard, the route entities and entity relationships in the IFC format file are mapped to entity connections according to the key data of the road model, and the RDF data graph obtained is output in the Turtle syntax format;

[0067] S2: construct an attribute shape graph of the road model, and obtain a new RDF data graph according to the RDF data graph and the attribute shape graph based on the rule engine of the SHACL processor;

[0068] The construction of the attribute shape graph of the road model comprises the following steps:

[0069] S21: By calling the IfcRelDefinesByProperties plug-in, the route entities are physically connected based on the properties of the route entity length;

[0070] S22: Based on the SHACL-SPARQL processor, by adding a route entity length attribute, a component category for distinguishing components of each route entity is obtained, and the component category at least includes a circular arc, a straight line, and a transition curve Clothoid;

[0071] S23: defining the radius attribute of the route entity component according to the optimized route entity to construct a new attribute relationship of the road model, and then obtaining the attribute shape diagram of the road model.

[0072] The method for constructing the new attribute relationship of the road model is as follows:

[0073] Confirm the radius attributes of the road model and the shape nodes of the route entity components;

[0074] Define the connection relationship between the shape nodes of the route entity components, use SHACL-SPARQL to query the value range of the radius attribute of the existing route entity components, call the CONSTRUCT tool, establish a new attribute relationship between the shape nodes of the route entity components and the radius attribute value, and obtain the attribute shape diagram.

[0075] In this embodiment, the IFC4x3_ADD2 standard described in the express language is converted into the ttl format through ExpresstoOwl.exe; Figure 3 As shown, the route entity IfcAlignment_177 and its route length attribute value in the IFC4x3_ADD2 standard are connected to the storage attribute container IfcPropertySet entity through the IfcRelDefinesByProperties_181 relationship entity. The route entity is IfcAlignment_177, and the relationship entity is IfcRelDefinesByProperties_181, the entities related to the length attribute IfcPropertySet_180, IfcPropertySingleValue_190, etc., and the entities related to the length attribute value type IfcReal_13189, IfcIdentifier_13195, etc., and the length attribute value can be a number of double or integer type or a string of string type;

[0076] The attribute shape graphs constructed in this embodiment include a hasCirculararcRadius attribute shape graph, a hasCirculararcLength attribute shape graph, and a hasAlignmentLength attribute shape graph;

[0077] And the construction rule statement of the hasCirculararcRadius attribute shape map is

[0078]

[0079] Among them, rdf:type owl:DatatypeProperty indicates that the type type is used to specify that hasCirculararcRadius is a data property; rdf:type sh:NodeShape indicates that the type type is used to specify that hasCirculararcRadius is a node shape; sh:targetClass ifc:IfcAlignmentHorizontalSegment indicates that the target class to which the constraint applies is the IfcAlignmentHorizontalSegment entity; rdf:type sh:SPARQLRule indicates that the type type is used to specify that the rule is written in accordance with the SPARQL query language; sh:prefixes ifc:,express:,: is used to specify prefixes to simplify the namespace in the SPARQL query; sh:construct "......" defines a construct CONSTRUCT query for constructing a new property relationship; $this:hasCirculararcRadius? Radius: $this represents the entity of the current constraint target, that is, the IfcAlignmentHorizontalSegment entity,? radius is a variable, indicating the radius value; WHERE{......}: defines a WHERE clause, and the curly braces define the query matching path (connection relationship); $this ifc:predefinedType_IfcAlignmentHorizontalSegment ifc:CIRCULARARC indicates that $this entity should conform to

[0080] The predefinedType_IfcAlignmentHorizontalSegment attribute connects this path of CIRCULARARC entity;

[0081] $thisifc:startRadiusOfCurvature_IfcAlignmentHorizontalSegment? arg1 indicates that $this entity should conform to

[0082] The connection relationship between the startRadiusOfCurvature_IfcAlignmentHorizontalSegment attribute and the arg1 variable 1; arg1 refers to the IfcLengthMeasure entity;

[0083] ?arg1 express:hasDouble?num: ?arg1 variable should be connected to another variable?num through the hasDouble attribute,?num refers to the attribute value, that is, the radius of the circular curve; bind(ABS(?num)as?radius) means using the BIND function in SPARQL to assign the absolute value of the?num variable to the?radius variable;

[0084] The construction rule statement of the hasCirculararcLength attribute shape diagram is

[0085]

[0086] The construction rule statement of the hasAlignmentLength attribute shape graph is

[0087]

[0088] S3: Translating the specification clauses used to verify the road design specification into a regular shape diagram, specifically including the following steps:

[0089] S31: Structural processing of specification clauses according to the verification requirements of the road model to obtain specification parsing data;

[0090] And the structured processing is specifically as follows

[0091] According to the article number and format characteristics of the specification, the full text of the specification is parsed based on natural language processing technology to obtain the shape constraint category keywords of different inspection specification categories;

[0092] The shape constraint category keywords include at least a circular curve radius, a circular curve length, a road lane width, and a road slope;

[0093] S32: Based on the rule statement of the regular shape graph, construct the regular shape graph according to the specification parsing data; and the rule statement of the regular shape graph at least includes

[0094] Use CirculararcShape to represent the shape constraint category keyword;

[0095] Use the rdf:type sh:NodeShape statement to specify the node shape of a CirculararcShape.

[0096] Use the sh:targetClass ifc:IfcAlignmentHorizontalSegment statement to verify that the route entity is a circular curve;

[0097] Use sh:property[......] statement to express the constraint path of the circular curve radius and circular curve length of the route entity to be verified;

[0098] Use minInclusive to constrain the range of hasCirculararcRadius attribute values;

[0099] Use severity to describe the severity of not meeting the constraint.

[0100] In this embodiment, the specification clauses are translated into regular shape diagrams. Taking the "Urban Road Alignment Design Specifications" CJJ193-2012 as an example, the minimum radius of circular curves is specified in Table 6.3.2 of Chapter 6 Plane Design according to different design speeds, and the minimum length of circular curves is specified in Table 6.3.4-1 according to different design speeds. And the tabular specification clauses are converted into text format, such as when the design speed is 60km / h, the radius of the circular curve should be greater than or equal to 600m; when the design speed is 60km / h, the length of the circular curve should be greater than or equal to 50m. The same inspection target circular curve IfcAlignmentHorizontalSegment entity and different inspection conditions are translated into a regular shape diagram CirculararcShape, and the rule statement for translating the specification clauses used to verify the road design specification into a regular shape diagram is:

[0101] :CirculararcShape

[0102] rdf:type sh:NodeShape;

[0103] sh:targetClass ifc:IfcAlignmentHorizontalSegment;

[0104] sh:property[

[0105] sh:path:hasCirculararcRadius;

[0106] sh:minInclusive 600;

[0107] sh:severity sh:Warning;

[0108] sh:message "Circular curve radius is less than the minimum value of 600"];

[0109] sh:property[

[0110] sh:path:hasCirculararcLength;

[0111] sh:minInclusive 50;

[0112] sh:severity sh:Warning;

[0113] sh:message "Circular curve length is less than the minimum value of 50"].

[0114] S4: Using the regular shape graph and the new RDF data graph as inputs of the SHACL processor, and performing road model verification based on the road shape constraints based on the verification engine of the SHACL processor, and outputting a verification report of the road model.

[0115] At the same time, based on the same invention essence, the present invention also provides a road design specification translation and verification system based on shape constraint language, including a road model construction module, an RDF converter acquisition module, a SHACL processor, an attribute shape graph acquisition module, a rule shape graph acquisition module and a verification report acquisition module;

[0116] The road model building module is used to build the road model to be model verified and convert it into a road model file in IFC format;

[0117] The RDF converter acquisition module is used to convert the road model file in IFC format according to the data conversion rule and obtain the RDF data graph of the road model;

[0118] The attribute shape graph acquisition module is used to construct an attribute shape graph of a road model;

[0119] The SHACL processor includes a rule engine module and a verification engine module;

[0120] The rule engine module is used for a rule engine based on a SHACL processor to obtain a new RDF data graph according to the RDF data graph and the attribute shape graph;

[0121] The regular shape map acquisition module is used to translate the specification clauses used to verify the road design specification into a regular shape map;

[0122] The verification engine module is used for verifying the road model of the road shape constraint based on the verification engine of the SHACL processor;

[0123] The verification report acquisition module is used to output a verification report of the road model according to the verification result of the verification engine module.

[0124] This embodiment constructs an attribute shape graph of the road model, and a rule engine based on the SHACL processor obtains a new RDF data graph according to the RDF data graph and the attribute shape graph. At the same time, the specification clauses used to verify the road design specifications are translated into a rule shape graph, and SHACL is combined with the SPARQL query language to achieve specification translation of the road design specifications, execute rule checks, and return inspection reports, thereby realizing automatic compliance review of the model, accelerating the review speed, reducing the current compliance review work in my country The dependence on expert knowledge, reducing the subjectivity of the review results, and improving the efficiency, accuracy, and intelligence level of compliance review.

[0125] The simulation experiment process in this embodiment is as follows: based on the design speed of 60 km / h, a road model is created by Autodesk Civil 3D 2024, and the total length of the road is 801.453 meters. The route consists of straight lines, circular curves, and transition curves (circular curves). The radius of the first circular curve is 500 meters and the length is 45.016 meters. The radius of the second circular curve is 700 meters and the length is 155.356 meters. Figures 4 to 5 . Use the Civil3D_IFC_2024 plug-in to export the road model to an .ifc format file. The export version is IFC4x3_ADD2. Figure 6 . The ifc file is converted into a ttl file through the RDF converter. The converter uses Pycharm 2022 as the development platform and uses the third-party library ifcopenshell to parse the routes, roads, circular curves, and transition curves in the ifc file. The parsed components are output in ttl format through a custom entity extraction function, such as Figure 7 . Operate the SHACL processor on the Eclipse 2024 platform, input the attribute shape graphs hasCirculararcRadius, hasCriculararcLength and ttl files into the SHACL processor, and output a new RDF data graph. The new RDF data graph will automatically add new attribute relationships based on the query path in the attribute shape graph, that is, directly connect the circular curve entity with the circular curve radius attribute value through the hasCirculararcRadius attribute. Input the new RDF data graph and the standard shape graph CirculararcShape into the SHACL converter for inspection. The inspection report is as follows: Figure 8 As shown, it can be seen from the report that the circular curve entity IfcAlignmentHorizontalSegment_204, the attribute hasCirculararcRadius and the radius value 500.0, the attribute hasCirculararcLength and the length value 45.01602 that do not meet the requirements of the specification have been checked.

[0126] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A road design specification translation and verification method based on shape constraint language, characterized in that: The specific steps include: S1: Obtain the road model file in IFC format and convert it into an RDF data graph through a pre-established RDF converter; S2: construct an attribute shape graph of the road model, and obtain a new RDF data graph according to the RDF data graph and the attribute shape graph based on the rule engine of the SHACL processor; S3: Translate the specification clauses used to verify the road design specifications into regular shape diagrams; S4: Using the regular shape graph and the new RDF data graph as inputs of the SHACL processor, and performing road model verification based on the road shape constraints based on the verification engine of the SHACL processor, and outputting a verification report of the road model.

2. A road design specification translation and verification method based on shape constraint language according to claim 1, characterized in that: The S1 specifically includes the following steps: S11: Call the Civil3D_IFC plug-in to convert the preset road model format into an IFC format file; S12: Based on the pre-established RDF converter, the IFC format file is converted according to the data conversion rule and the RDF data graph of the road model is obtained.

3. The method for translating and verifying road design specifications based on shape constraint language according to claim 2 is characterized in that: The data conversion rules described in S12 are specifically: The dynamic link library corresponding to the road model is obtained by calling the Ifcopenshell compilation library, and the IFC format file is parsed based on the dynamic link library to obtain the key data of the road model; According to the key data of the road model, the route entities and entity relationships in the IFC format file are mapped to entity connections, and the obtained RDF data graph is output in the Turtle syntax format.

4. The method for translating and verifying road design specifications based on shape constraint language according to claim 3 is characterized in that: The key data at least includes route entity information for characterizing road segments, entity relationship information for characterizing connection relationships between road segments, attribute information for characterizing route entity length and corresponding length attribute value; The length attribute value includes any one of a double type number, an integer type number, and a string type character string.

5. A road design specification translation and verification method based on shape constraint language according to claim 4, characterized in that: The attribute shape diagram of the road model constructed in S2 specifically includes the following steps S21: By calling the IfcRelDefinesByProperties plug-in, the route entities are physically connected based on the properties of the route entity length; S22: Based on the SHACL-SPARQL processor, by adding a route entity length attribute, a component category for distinguishing components of each route entity is obtained, and the component category at least includes a circular arc, a straight line, and a transition curve Clothoid; S23: defining the radius attribute of the route entity component according to the optimized route entity to construct a new attribute relationship of the road model, and then obtaining the attribute shape diagram of the road model.

6. A road design specification translation and verification method based on shape constraint language according to claim 5, characterized in that: The method for constructing the new attribute relationship of the road model is as follows: Confirm the radius attributes of the road model and the shape nodes of the route entity components; Define the connection relationship between the shape nodes of the route entity components, and use SHACL-SPARQL to query the value range of the radius attribute of the existing route entity components; Call the CONSTRUCT tool to establish a new attribute relationship between the shape node of the route entity component and the value range of the radius attribute to obtain the attribute shape diagram.

7. A road design specification translation and verification method based on shape constraint language according to claim 6, characterized in that: The S3 translates the specification clauses used to verify the road design specification into a regular shape diagram, specifically including: S31: Structural processing of specification clauses according to the verification requirements of the road model to obtain specification parsing data; And the structured processing is specifically as follows: According to the article number and format characteristics of the specification, the full text of the specification is parsed based on natural language processing technology to obtain the shape constraint category keywords of different inspection specification categories; The shape constraint category keywords include at least a circular curve radius, a circular curve length, a road lane width, and a road slope; S32: Based on the rule statements of the regular shape graph, construct the regular shape graph according to the specification parsing data; And the rule statement of the regular shape graph at least includes Use CirculararcShape to represent the shape constraint category keyword; Use the rdf:type sh:NodeShape statement to specify the node shape of a CirculararcShape. Use the sh:targetClass ifc:IfcAlignmentHorizontalSegment statement to verify that the route entity is a circular curve; Use sh:property[......] statement to express the constraint path of the circular curve radius and circular curve length of the route entity to be verified; Use minInclusive to constrain the range of hasCirculararcRadius attribute values; Use severity to describe the severity of not meeting the constraint.

8. A verification system based on any one of the shape constraint language based road design specification translation verification methods according to claims 1 to 7, characterized in that: It includes a road model building module, an RDF converter acquisition module, a SHACL processor, an attribute shape graph acquisition module, a rule shape graph acquisition module and a verification report acquisition module; The road model building module is used to build the road model to be model verified and convert it into a road model file in IFC format; The RDF converter acquisition module is used to convert the road model file in IFC format according to the data conversion rule and obtain the RDF data graph of the road model; The attribute shape graph acquisition module is used to construct an attribute shape graph of a road model; The SHACL processor includes a rule engine module and a verification engine module; The rule engine module is used for a rule engine based on a SHACL processor to obtain a new RDF data graph according to the RDF data graph and the attribute shape graph; The regular shape map acquisition module is used to translate the specification clauses used to verify the road design specification into a regular shape map; The verification engine module is used for performing road model verification of road shape constraints based on the verification engine of the SHACL processor; The verification report acquisition module is used to output a verification report of the road model according to the verification result of the verification engine module.

Images