CN112182871A

CN112182871A - System and method for converting three-dimensional pipeline model into MapGIS model

Info

Publication number: CN112182871A
Application number: CN202011009688.1A
Authority: CN
Inventors: 沈杰
Original assignee: Shanghai Nuclear Engineering Research and Design Institute Co Ltd
Current assignee: Shanghai Nuclear Engineering Research and Design Institute Co Ltd
Priority date: 2020-09-23
Filing date: 2020-09-23
Publication date: 2021-01-05
Anticipated expiration: 2040-09-23
Also published as: CN112182871B

Abstract

The invention discloses a system and a method for converting a three-dimensional pipeline model into a MapGIS model, and the system and the method comprise an external data reading module, an S3D model data downloading module, a point-line structure calculating module, a point-line structure duplicate removal module, a point-line table generating module and an Excel file generating module; according to the scheme, the automatic conversion from the S3D three-dimensional pipeline model to the MapGIS pipe network model is realized by the method of generating the xls-format intermediate file from the S3D three-dimensional pipeline layout model and importing the xls-format intermediate file into the MapGIS, the link of secondary modeling of designers is omitted, the data utilization rate of the S3D three-dimensional model is improved, and the workload of the designers is reduced. The whole process is completed automatically, the operation is simple and convenient, and the production efficiency is high.

Description

System and method for converting three-dimensional pipeline model into MapGIS model

Technical Field

The invention belongs to the field of three-dimensional model processing, and particularly relates to a conversion method of an S3D three-dimensional model.

Background

S3D (Smart 3D) is a widely used three-dimensional design software. The S3D software is used as integrated and multi-professional-participated three-dimensional factory modeling software, so that three-dimensional modeling and design inspection of professional designers can be rapidly assisted, and the working efficiency and the design quality are greatly improved. In the chemical and energy industries, the S3D software has been widely used and has had countless cases of success.

The MapGIS software is a full-space intelligent GIS platform which integrates advanced technologies such as big data, Internet of things, cloud computing and artificial intelligence, visualizes the concept of full space, the insight of big data and the perception of artificial intelligence into an easily understood expression mode through a GIS language, realizes the storage, management, efficient integration and analysis and mining of super-large-scale geographic data, and provides stronger technical support for various industries and applications thereof in the field of geographic spatial information.

Under the condition that S3D software is used for three-dimensional modeling and the MapGIS software is used for building a geographic information system, because no available software interface between the MapGIS software and the S3D software exists at present, a designer can only manually build the MapGIS model by referring to the S3D three-dimensional model, a large amount of working time of the designer is occupied in the secondary modeling process, and the utilization rate of the S3D three-dimensional model is reduced.

Disclosure of Invention

The invention provides a system and a method for converting a three-dimensional pipeline model into a MapGIS model, which realize the automatic conversion from an S3D three-dimensional pipeline model to a MapGIS pipe network model by realizing the generation of an xls-format intermediate file from an S3D three-dimensional pipeline layout model and importing the xls-format intermediate file into the MapGIS, save the link of secondary modeling of designers, improve the data utilization rate of the S3D three-dimensional model and reduce the workload of the designers. The whole process is completed automatically, the operation is simple and convenient, and the production efficiency is high.

A system for converting a three-dimensional pipeline model into a MapGIS model comprises an external data reading module, an S3D model data downloading module, a point-line structure calculating module, a point-line structure duplicate removal module, a point-line table generating module and an Excel file generating module;

the external data reading module is used for reading external data stored in the S3D database;

the S3D model data downloading module is used for downloading the data in the external data reading module to the memory of the S3D model data downloading module;

the dotted line structure calculation module is used for acquiring the dotted line relation set relation of all pipeline elements by the model data in the S3D model data downloading module through a topological relation algorithm;

the point-line structure duplicate removal module is used for carrying out duplicate removal processing on points with consistent coordinates in the point-line structure calculation module to form a point-line structure without repeated coordinate points;

the point-line table generating module is used for converting the model data read out by the point-line structure duplication eliminating module into a point-line table meeting the requirement of MapGIS;

the Excel file generation module is used for converting the dotted line table into an xls file format.

The invention also provides a method for converting the three-dimensional pipeline model into the MapGIS model, and a system for converting the S3D three-dimensional pipeline model into the MapGIS model comprises the following steps:

s1, obtaining external data required by model conversion through the external data reading module, wherein the external data comprises S3D project configuration information, database types and system number information required to be converted;

s2, downloading relevant pipeline model data from the S3D database and storing the data in the memory of the S3D model data downloading module;

s3, acquiring the topological connection relations of all elements by the pipeline model data downloaded by the S3D model data downloading module through a topological relation algorithm, and storing the topological connection relations into corresponding point-line data structures;

s4, finding out repeated endpoint removal and tee joint combination and processing variable diameter points in the point-line structure duplicate removal module to obtain a new point-line data structure;

s5, converting the de-duplicated point-line data structure set into a point-line table form acceptable to MapGIS;

and S6, converting the dotted line table into an XLS file format.

Preferably, the step of S3 is as follows:

s3.1, acquiring corresponding pipeLine object pipeLine sets according to the system number input by the user;

s3.2, acquiring all corresponding pipe object sets according to the pipe line set, and creating an integral point structure and a line structure object;

s3.3, circularly reading all the pipe section pipe in the pipe object set, and entering S3.4 if the circulation is not finished; if the circulation is finished, S3.21 is entered;

s3.4, finding a corresponding pipe feature set according to the pipe object set;

s3.5, judging the type of each feature in the pipeline feature set, recording a corresponding starting point, an end point, a central point and a type, and storing the type into a custom set pipeline feature List;

s3.6, finding out a starting point from the custom set pidingFeatureList, wherein the starting point conditions are 'end point' and 'variable diameter point', meanwhile, one end point is not connected with an object in any other pidingFeatureList, the other end point is connected with an object which is not the 'end point' and the 'variable diameter point', no branch exists in the pidingFeatureList, and if the starting point is found, entering S3.7; otherwise, recording the problem of the current pipe section, returning to S3.3 for analyzing the next pipe section;

s3.7, setting the current object as a starting object, setting the coordinate of the connection between the current object and other objects as currentLocation, storing the point structure and the line structure of the current pipe, taking the current object as an above PingFeatureList, and removing the current object from the user-defined set PingFeatureList;

s3.8, circularly processing the objects in the user-defined set pimingFeatureList, and entering the next step if the processing is not finished, or entering S3.19 if the processing is finished;

s3.9, if the number of the end point type objects in the custom set pidingFeatureList is exactly two, directly removing the end point type objects from the custom set pidingFeatureList;

s3.10, if the user-defined set pimingFeatureList is empty, returning to S3.3, otherwise, entering the next step;

s3.11, searching a subsequent connection object according to the welding connection condition, if the end point coordinate is consistent with the currentLocation, if the point structure and the line structure for recording the object to the current pipe are found, replacing the object with abovePipingFeature, replacing the currentLocation with another end point coordinate, returning to S3.8, otherwise, entering the next step;

s3.12, according to the fact that the above-mentioned abovePipingFeatureList is a branch processing of a tee joint, whether the tee joint connected with the above-mentioned abovePipingFeatureList in a branch is existed or not is checked, if the tee joint exists, the tee joint object is used as a nextPipingFeatureList and is stored in a tPontStructList, the nextPipingFeatureis used as an abovePipingFeatureFeatureType and is stored in a point structure and a line structure of the current pipe, the S3.8 is returned, and if the tee joint object does not exist, the next step is carried out;

s3.13, judging whether a tee object in the tPoint structList has an object with a starting point or an end point consistent with the currentLocation or whether a tee corresponding to the above-mentioned abovePipingFeture exists in the tPoint structList, and if the tee object exists and the object is not the last two in the PiperUnLinestructList, supplementing the information of the object in the current Piperun line structure to form a closed path;

s3.14, if only one end point and one reducing point are left in the user-defined set pimingFeatureList, respectively storing the two into the current point structure and the current line structure of the pipe, returning to S3.8, if the two are left as the end points, removing the two objects, returning to S3.8, and otherwise, entering the next step;

s3.15, considering non-welding connection, finding out a corresponding part from the above instrumentation feature, then finding out a connection part corresponding to the part, finding out a corresponding feature according to the connection part, then changing the currentLocation into an end point coordinate corresponding to the feature, returning to S3.8, and if the part cannot be found, entering the next step;

s3.16, representing that the branch is finished, now considering whether a feature object consistent with the starting point or the end point of the existing tee object can be searched from the existing tee set, if so, taking the end point coordinate of the tee object connected with other objects as the currentLocation coordinate, taking the tee object as the above-mentioned three-way object, returning to S3.8, otherwise, entering the next step;

s3.17, searching whether a branch object exists in the three-way object in the user-defined set pimingFeatureList, if the currentLocation is changed into a point with a center coordinate of the branch object closer to that of the three-way object, taking the three-way object as an above PingFeatfeature, returning to S3.8, and otherwise, entering the next step;

s3.18, searching whether a new starting point exists in the custom set pipingFeatureList, wherein the starting point judgment condition is consistent with S3.6, if no current pipe section pipe is in trouble, writing a log and reporting an error and returning to S3.3, otherwise, setting the new starting point and currentLocation and returning to S3.8;

s3.19, checking whether the last feature of the pipe section has a corresponding three-way feature or not, and if so, storing the last feature into the line structure of the current pipe section to form a closed loop;

s3.20, removing points with coincident coordinates in a point structure finally formed by the pipe section pipe, wherein the points are generally coincident with an end point and a tee joint point, keeping the tee joint point to remove the end point, removing corresponding objects in the line structure at the same time, then storing the point structure and the line structure of the pipe section pipe into the integral point structure and the integral line structure, and returning to S3.3;

and S3.21, finishing all pipern analysis to form a final point structure and a final line structure.

Compared with the prior art, the invention has the following beneficial effects:

1. the system and the method for converting the three-dimensional pipeline model into the MapGIS model provide an acquisition method of the professional topological connection relation of the S3D pipeline, and provide more possibilities for the management and application of the S3D model.

2. The system and the method for converting the three-dimensional pipeline model into the MapGIS model provided by the invention provide a method for converting the professional S3D pipeline element into the dotted line model, and provide more possibilities for the management and application of the S3D model.

3. The system and the method for converting the three-dimensional pipeline model into the MapGIS model can automatically convert the S3D three-dimensional pipeline model into the Excel file which is imported by the MapGIS software support, realize the automatic conversion of the layout model into the geographic information system model, avoid the labor waste caused by secondary modeling, and greatly improve the design efficiency and quality.

4. The system and the method for converting the S3D three-dimensional pipeline model into the MapGIS model support two modes of generation by taking the system as a unit and factory generation, and are flexible and easy to use.

5. The system and the method for converting the three-dimensional pipeline model into the MapGIS model have the advantages that the whole process is completed automatically, manual intervention is not needed, the operation is simple and convenient, and the production efficiency is high.

6. The system and the method for converting the S3D three-dimensional model pipeline type into the MapGIS model provide a log query function, can still complete the analysis and calculation of other pipelines under the condition of error of a single pipeline, and have strong robustness.

Drawings

FIG. 1 is a schematic diagram of a system and method for converting a three-dimensional pipeline model into a MapGIS model according to an embodiment.

FIG. 2 is a flowchart illustrating an implementation method for converting a three-dimensional pipeline model into a MapGIS model according to an embodiment.

Fig. 3 is a flowchart illustrating an embodiment of an S3D algorithm for acquiring professional dotted-line relation data sets of a three-dimensional model pipeline.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.

As shown in fig. 1, the system and method for converting a three-dimensional pipeline model into a MapGIS model includes:

the external data reading module is used for reading external data required by the three-dimensional model conversion module, and the external data comprises system number information required to be extracted from the S3D project configuration information;

and the S3D model data downloading module is used for reading data stored in the S3D database into a program memory, so that the subsequent processing and calculation efficiency is improved, and the range of the downloaded data is determined according to the data acquired by the external data reading module.

The point-line structure calculating module is used for acquiring the point-line relation set relation of all the elements by the model data downloaded by the S3D pipeline model data downloading module through a topological relation algorithm;

the point-line structure duplicate removal module is used for carrying out duplicate removal treatment on points with consistent coordinates in the point-line structure to form a point-line structure without repeated coordinate points;

the point and line table generating module is used for converting the converted point and line model into a point and line table format meeting the requirement of MapGIS;

and the Excel file generation module is used for converting the generated point line table into an xls file format.

As shown in fig. 2, the method for converting the S3D three-dimensional model into the MapGIS model includes the following steps:

s1, obtaining external data required by model conversion through an external data reading module, wherein the external data comprises S3D project configuration information, database types and system number information required to be converted;

s2, downloading relevant pipeline model data from the S3D database and storing the data in a memory;

s3, acquiring the topological connection relation of all elements by the pipeline model data downloaded by the S3D model data downloading module through a topological relation algorithm, and storing the topological connection relation into a corresponding point-line data structure;

s4, finding out repeated endpoint removal and tee joint combination from the point-line data structure obtained in S3, and processing the variable diameter points to obtain a new point-line data structure;

s5, converting the dotted line data structure set in the S4 into a dotted line table form acceptable by MapGIS;

s6, converting the converted dotted line table in S5 into XLS file format.

Preferably, the step of obtaining the topological connection relationships of all pipeline elements by the topological relationship algorithm according to the pipeline model data downloaded by the pipeline model data downloading module of S3D of S3, and storing the obtained topological connection relationships as corresponding dotted line relationship data sets includes the following steps:

s3.1, acquiring oid of all corresponding pipe lines according to a system number input by a user, creating a result set list pipe line, creating a line object lineStruct (containing oid of pipe, point coordinates and a point sequence) set pipe line, and creating a point object pointStruct (containing point coordinates, point types and point standby coordinates) set pointList;

s3.2, obtaining the pipRunOid of all the pipRuns through an xSystemHierarchy interface according to oid in the result set obtained in S3.1, and forming a piplun set pipRunList;

s3.3, circularly reading the pipRunOid in the pipRunList, entering S3.4 if the circulation is not ended, and entering S3.85 if the circulation is ended;

s3.4, obtaining a corresponding pip feature object set pip feature List through an xPathSpecification interface according to the pip RunOid obtained in the S3.3, establishing a self-defined set pip FeatureList of myFeaturetype, and entering the S3.5;

s3.5, circularly acquiring the pipe feature Oid in the pipe feature List, if the circulation is not finished, creating a myFeature object, and entering S3.6, and if the circulation is finished, entering S.22;

s3.6, judging whether the pip feature object is the CPPipeAlongLegPathFeat object or not through a JRteAlongLegPathFeat interface, if so, entering S3.7, and if not, entering S3.8;

s3.7, acquiring coordinates of a starting point and an end point of the object, storing the coordinates into a myFeature object, judging the type of the object according to the 'eFunction' attribute, and entering S3.9 if the 'eFunction' object is '4', or entering S.10 if the 'eFunction' object is not '4';

s3.8, judging whether the pip feature object is the CPPipeTurnPathFeat object or not through a JRtepPeterTurnPathFeat interface, if so, entering S3.11, and if not, entering S3.12;

s3.9, marking the myFeture object as a tee joint, recording the coordinate of the central point, storing the myFeture object into the myFeture object, storing the myFeture object into pinchgFeatureList, and returning to S3.5;

s3.10, judging whether the object is a valve or not through an XPathGeneratedParts relation and a JRtepartData _ CL interface, if so, marking the myFeture object as the valve, recording the coordinate of the central point on the myFeture object, storing the myFeture object into PipingFeatureList, and returning to S3.5;

s3.11, acquiring a start point, an end point and an inflection point coordinate of the object, storing the start point, the end point and the inflection point coordinate into the myFeture object, marking the myFeture object as an elbow, judging whether the myFeture object is an angle valve through an XPathGeneratedParts relation and a JRtepartData _ CL interface, if the myFeture object is further marked as the angle valve, storing the myFeture object into a PipingFeartureList, and returning to S3.5;

s3.12, judging whether the pip feature object is the CPPipeCurvePathFeat object or not through a JRtECurvePathFeat interface, if so, entering S3.11, and if not, entering S3.13;

s3.13, judging whether the pip feature object is the CPPipeBranchFeat object or not through the JRtepPerBrachFeat interface, if so, entering S3.14, and if not, entering S3.15;

s3.14, acquiring the coordinates of a starting point and an end point of the object, storing the coordinates into a myFeature object, acquiring a related object through an XOffLinefeatures relationship, acquiring the coordinates of a center line point of the related object, storing the coordinates into the myFeature object, marking the myFeature object as an end point, storing the myFeature object into a pincgFeatureList, and returning to S3.5;

s3.15, judging whether the pip feature object is the CPPipeStraightPathFeat object or not through a JRtepPeptitrapraLightPathFeat interface, if so, entering S3.16, and if not, entering S3.17;

s3.16, acquiring the coordinates of the starting point and the end point of the object, storing the coordinates into the myFeature object, storing the myFeature object into the pinchgfeatureList without marking the myFeature object, and returning to S3.5;

s3.17, the pipe feature is certain to be CPPipeEndPathFeat, the coordinates of the starting point, the end point and the central point of the object are obtained and stored into the myFeture object, whether the pipe feature has corresponding part is judged according to the XPathGeneratedParts relation, if yes, the pipe feature enters S3.18, and if not, the pipe feature enters S3.19;

s3.18, judging the specific type of part through JRtePartData _ CL, entering S3.20 if the type of the 'ShortCodeHierarchy type' is 15 or 20, entering S3.21 if the type of the 'ShortCodeHierarchy type' is 25, and otherwise entering S3.19;

s3.19, marking the myFeture object as an end point, storing the myFeture object into the pingFeatureList, and returning to S3.5;

s3.20, marking the myFeture object as a diameter-variable point, storing the myFeture object to the pinchgFeatureList, and returning to S3.5;

s3.21, marking the myFeature object as an end point, wherein part corresponding to the myFeature is a flange; acquiring a connection item object through the XRelConnectionAndPartOcc relationship by the flange object acquired in S3.17, and then acquiring another flange part of the flange connection according to the connection item object and the XRelConnectionAndPartOcc; searching the flange surface connection coordinate location of the other flange part through the JDistribPort interface; if the central coordinate of the myFeature is consistent with the starting point, changing the end point coordinate corresponding to the myFeature into location, otherwise, changing the starting point coordinate corresponding to the myFeature into location, storing the myFeature object into pincegfeatureList, and returning to S3.5;

s3.22, if the pidingFeatureList set is empty, directly returning to S3.3, otherwise, entering S3.23;

s3.23, judging whether the pidingFeatureList only contains an end point and a reducing point, if so, entering S3.24, otherwise, entering S3.25;

s3.24, storing all the points in the pipingFeatureList into the pointList, wherein the coordinates of the center point of the point are the coordinates of the point of the pointStruct object, and simultaneously storing all the points in the pipingFeatureList into the lineList, wherein oid of the pipeRun is to be placed into the lineStruct, and the sequence is 1 and 2 respectively, and returning to S3.3;

s3.25, finding out all myfeatures of which the types are marked as 'end points' and 'variable diameter points' in the pidingFeatureList to form a myEndFeatureList set;

s3.26, circularly searching each myFeature in the myEndFeatureList, if a new myFeature exists, entering S3.27, otherwise, entering S3.30;

s3.27, if myFeatur has an object of which one end point is not connected with any other object in the pinchgFeatureList and the other end point is connected with the objects of the non-end point and the variable diameter point, if the myFeatur has the object of which the other end point is connected with the objects of the non-end point and the variable diameter point, the myFeatur does not return to S3.26;

s3.28, finding whether the feature corresponding to the feature exists through the XOffLinefeatures relation, if so, representing the feature as a branch feature, then judging whether the corresponding feature is in the feature to be processed in the system, if so, returning to S3.26 to find the starting point again, otherwise, entering S3.29;

s3.29, taking the myFeature as an initial feature, taking a point where the myFeature object is connected with other objects as an initial point, and setting a coordinate object currentLocation as a current initial point;

s3.30, establishing a pipe feature object set tPointStructList as a storage set of branch points, establishing a pointStruct object set pipe PointStructList and a lineStruct object set pipe LineStructList, and entering S3.31;

s3.31, constructing a line table according to the piperun obtained in the S3.3, newly building a lineS structure object MyLineStrect, setting npd and oid of the MyLineStrect to be the same as the piperun, and using pointIndex to arrange pointStructure objects, so that from 1, oid of the MyFeture of S3.29 is the pointoid of the current MyLineStrect, storing the MyLineStrect into the PiperLineStrect list, and entering S3.32;

s3.32, creating a pointStruct object myPointstruct, taking the central coordinate of myFeture as the pointLocation of the myPointstruct, taking the type of the myFeture as the type of the myPointstruct, storing the myFeture into a PiperUnPointstructList, and entering S3.33;

s3.33, after the myFeature is processed, removing the myFeature from the pinchgfeatureList, and entering S3.34;

s3.34, creating a pip feature object abovePiplingfeature, storing the last processed pip feature object, wherein myFeature is set as abovePipeidingfeature; entering S3.35;

s3.35, whether currentLocation is empty or not, if so, indicating that a starting point is not found in the process of S3.26-S3.29, emptying a piprunPointstructList and a pipruneStrectList, recording that the current piprun has a problem, returning to S3.3 to start next piprunprocessing, and otherwise, entering S3.36;

s3.36, defining oid of a pointStruct object recorded by a String type attribute above Point object Oid, and entering S3.37;

s3.37, if the PipingFeatureList set is not empty, then S3.38 is entered, otherwise S3.80 is entered;

s3.38, finding the myFeature object set nextpipingFeatureList which is consistent with currentLocation coordinate from the pidingFeatureList, and entering S3.39;

s3.39, searching an object with the type of 'endpoint' from the nextpipingFeatureList, putting the object into a breakFeatureList set, and entering S3.40;

s3.40, if the number of the elements in the breakFeatureList is 2, the two endpoint objects are independently paired, the elements in the breakFeatureList are removed from the pipingFeatureList, and the step S3.41 is entered;

s3.41, judging whether the pidingFeatureList is empty, if so, entering S3, otherwise, entering S3.42;

s3.42, creating a piping feature type object nextPipingFeature for storing the connection object, entering S3.43 if the number of nextpipingfeatureList elements is more than 1, entering S3.44 as nextPipingFeature if equal to 1, and entering S3.47 if not;

s3.43, finding out an object with the type of 'three-way' from the nextpipingFeatureList, if the object exists, the object is nextpipingFeatureif the object with the consistent starting point and ending point exists, otherwise, the object is nextpipingFeatureif the object exists, otherwise, the object with the type exists, if the object exists, the object is nextpipingFeatureif the object exists, otherwise, the first element of the set is taken as the nextpipingFeatureS, and the operation enters S3.44;

s3.44, if the type of nextPipingFeature is 'tee', adding the type of nextPipingFeature into the tPoint structList, and entering S3.45;

s3.45, setting the endpoint coordinate of the nextPipingFeature object inconsistent with currentLocation as the starting coordinate currentLocation of the next loop, if the type of the nextPipingFeature object is not empty, entering S3.46, otherwise, removing the nextPipingFeature object from the PipingFeatureList, setting abovePipingFeaturefeature as nextPipingFeature, and returning to S3.37;

s3.46, newly building a lineStruct object tempLineStruct, storing pointIndex plus 1 together with npd and oid of current picture in tempLineStruct, storing oid of nextpictefeature in pointOid of tempLineStruct, if the above-mentioned, storing above-mentioned;

s3.47, if the current situation is that a point which can be directly connected with currentLocation cannot be found, generating a branchExistTable connected with an above PavePipingFeature object through an XOffLineFeatures relation, if an object exists in the branchExistTable and simultaneously exists in the pinceFeatureList, setting the object as nextpipingFeature, and entering S3.48, otherwise, entering S3.51;

s3.48, using the starting point coordinate of the nextpipengfeature object as currentLocation, if the type of the nextpipengfeature object is not empty, entering S3.49, otherwise entering S3.50;

s3.49, newly building a lineStruct object tempLineStruct, adding 1 to pointIndex, storing the pointIndex and current pirrun npd and oid together into tempLineStruct, storing nextppingFeature oid into pointOid of the tempLineStruct, if the above-mentioned is not empty, storing the above-mentioned into above-mentioned attribute of tempLineStruct and setting the above-mentioned to be empty, storing the above-mentioned into a pilotLinestruct list, and entering S3.50;

s3.50, adding nextPipingFeature into the tPointStructList, simultaneously storing oid, center point coordinates and type of the nextPipingFeature into the newly-built pointStruct object and adding to the picoPointStructList, removing the nextPipingFeature object from the pingFeatureList, setting abovePipingFeture as nextpIintFeture, and returning to S3.37;

s3.51, searching whether an object with an end point consistent with currentLocation exists in the tPoint StuctList, if so, further judging that oid of the object cannot be abovePoint Oid and cannot be pointenlinestructList pointent, if both are satisfied, entering S3.52, otherwise, entering S3.53;

s3.52, creating a lineStruct object tempLineStruct, adding 1 to pointIndex, storing the pointIndex and current pipun npd and oid together into tempLineStruct, storing nextppingFeature oid into pointOid of the tempLineStruct, if the above-mentioned aotpoint Oid is not empty, storing the above-mentioned aotpoint Oid into above-mentioned attribute of the tempLineStruct, storing the tempLineStruct into a pilotlinestruct, and entering S3.54;

s3.53, if the branchExistTable has an object, searching whether the first three-way object in the branchExistTable is in the tPointStructList, if the object exists and meets the condition that the object is not the last two objects in the PiperLineStrectList set and oid is not abovePoint, assigning the object to nextPipingFeture, and entering S3.52;

s3.54, if the pidingFeatureList only has two features and is both an end point or a diameter-changing point, entering S3.55, otherwise, entering S3.57;

s3.55, if the two feature objects are consistent in type, directly ignoring, returning to S3.37, otherwise, entering S3.56;

s3.56, respectively creating lineStrect objects myLineStrectTemp for two features, adding 1 to pointIndex, storing the pointIndex and npd and oid of the current pipe into tempLineStrect, storing oid of nextPipingFeture into pointOid of tempLineStrect, additionally setting an isrestart object as true for the first feature, storing the tempLineStrect into pinceStrect, simultaneously storing oid, a center coordinate and a type corresponding to the feature into the pointStrect object, adding the center coordinate and the type into myPointStrect, and returning to S3.37;

s3.57, acquiring an entity set pidingComarray corresponding to the above outlined Feture object through an XPathGeneratedParts relationship, setting whether an ending mark isFinish is false, entering S3.58 if the length of the pidingComarray is not 0, and otherwise, entering S3.62;

s3.58, reading each entity part in the pipingCompRarray in a cycle, and entering S3.59 if the entity exists, or entering S3.62 if the next entity does not exist;

s3.59, acquiring a connectionItem object through an XRelConnectionAndPartOcc relation, then acquiring another part connected according to the connectionItem object and the XRelConnectionAndPartOcc, acquiring a feature corresponding to the part according to XPathGeneratedParts, and entering S3.60 if oid of the feature is in a pidgFeatureList, or entering S3.61;

s3.60, finding out the corresponding myFeture type object from the pidingFeatureList, setting the myFeture type object as nextpingFeatureif the type is 'tee', adding the object into the tPoint StructList, setting the end point which is located in S3.59 and is closer to currentLocation as currentLocation, changing the isfining into true, and returning to S3.37;

s3.61, if the feature corresponding to the connection part can not be found in the PiperUnPointstructList, the coordinates of the starting point, the end point and the central point of the feature are obtained through the JRtepathFiture interface, an object of which the type is an end point and the coordinate of the central point is equal to any one of the coordinates of the starting point, the end point and the central point of the feature is found in the PipingFeatureList, if the object exists, the coordinate which is closer to the currentLocation in the starting point and the end point of the object is found to be used as a new currentLocation, the isFinish is changed into true, and the operation returns to S3.37;

s3.62, circularly acquiring each branch point object in the tPoint structList, and if the next branch point object exists, entering S3.63, otherwise, entering S3.71;

s3.63, acquiring the last branch point object in the tPoint structList, assigning to a newly-built myFeture object tPipingFeture, searching for the myFeture object with the consistent starting point and the consistent ending point of the tPipingFetureList, if the myFeture object exists, setting currentLocation as the coordinate of the tPipingFeture matched with the myFeture, setting abovePoint as oid of the tPipingFeture, then returning to S3.37, and if the myFeture object does not exist, entering S3.64;

s3.64, searching a branchFeature set of a branch object corresponding to the tPiingfeature through an XOffLinefeatures relation, if yes, entering S3.65, if not, removing the tPiingfeature from the tPoint structList, and returning to S3.62;

s3.65, setting a flag exist Branch as false, circularly traversing a branchFeature set, if a branchFeature existing in a pinchgeateurelist can be found, taking a point which is farthest away from a tPingFeture coordinate in the branchFeature as currentLocation, then taking oid of the tPingFeture as abovePoint, returning to S3.37, otherwise, entering S3.66;

s3.66, acquiring a part corresponding to the tPipingFeture through an XPathGeneratedParts relation, if the part does not exist, removing the tPipingFeture from the tPoint structList, and returning to S3.62; otherwise, acquiring a corresponding part set pipingCompRray, and entering S3.67;

s3.67, reading each entity part in the pipingCompRarray in a cycle, and entering S3.68 if the entity exists, and entering S3.70 if the next entity does not exist;

s3.68, acquiring a connectionItem object through an XRelConnectionAndPartOcc relation, then acquiring another part connected according to the connectionItem object and the XRelConnectionAndPartOcc, acquiring a feature corresponding to the part according to XPathGeneratedParts, entering S3.69 if oid of the feature is in a pidgFeatureList, and otherwise entering S3.70;

s3.69, finding out the corresponding myFeture type object from the piping FeatureList and setting the object as the nextPipingFeture, if the type is 'tee', adding the object into the tPontStructList, setting the endpoint coordinate closer to the tPoingFeture coordinate in the nextPipingFeture as currentLocation, setting the abovePoint Oid as oid of the tPoingFeture, and returning to S3.37;

s3.70, removing the tPipingFeatur from the tPoint structList, and returning to S3.62;

s3.71, newly searching feature objects with the types of 'end points' or 'variable diameter points' from the pincipagFeatureList to form a myEndPipingFeatureList set, newly establishing a myFeature type endFeatur which is empty, and entering S3.72;

s3.72, circularly traversing myEndPipingFeatureList to each object tempFeature, and entering S3.73 if the object tempFeatform exists, or entering S3.76 if the object tempFeatform does not exist;

s3.73, if the tempFeatur has an object of which one end point is not connected with any other object in the pimingFeatureList and the other end point is connected with the objects of the non end point and the variable diameter point, if the tempFeatur has an object of which the other end point is connected with the objects of the non end point and the variable diameter point, the step does not return to S3.72;

s3.74, finding out whether the feature corresponding to the feature exists through the XOffLinefeatures relation, if yes, representing the feature as a branch feature, then judging whether the corresponding feature is in the feature to be processed in the system, if yes, returning to S3.72 to find the starting point again, otherwise, entering S3.75;

s3.75, taking the tempFeature as the endFeature, taking the point where the tempFeature object is connected with other objects as a starting point, setting a currentLocation coordinate object as the current starting point, and entering S3.76;

s3.76, if the endFeature is empty, the current pipeline has problems, writing the log, returning to S3.3, and if the endFeature is not empty, entering S3.77;

s3.77, creating a lineStruct object myLinestruct, setting npd and oid of the myLinestruct to be the same as the piperun, adding 1 to a pointIndex to store the pointIndex of the myLinestruct, setting an attribute of isrestart of the myLinestruct to be true, setting oid of endFeture to be the pointoid of the current myLinestruct, if the anovePoint is not null, storing the anovePoint into the anovityOid of the myLinestruct and setting the anovePoint to be null, storing the myLinestruct into the pipilestruct, and entering S3.78;

s3.78, creating a pointStruct object myPointstruct, taking the central coordinate of the endFeature as the pointLocation of the myPointstruct, taking the type of the endFeature as the type of the myPointstruct, storing the type of the endFeature into a PiperUnPointstructList, and entering S3.79;

s3.79, remove endFeature from pincegfeaturelist and set endFeature to above clipingfeature, return to S3.37;

s3.80, checking whether a branch object exists in the last object in the PiperunlineSercutList through an XOffLineFeatures relation, if so, entering S3.81, otherwise, entering S3.83;

s3.81, searching whether a branch object found by S3.80 exists in the tPoint structList, if not, entering S3.83, if so, locating the branch object to lastExtrafeature, and entering S3.82;

s3.82, if the pilotPoint is not an object with the abovePoint Oid of oid of lastExtraFeture and the pointeid of oid of the abovePingFeture in the pilotLineTrucList, creating a tempLineTruct, wherein the lineOids and npd of the tempLineTruct both take the attribute of the pilotun, the pointeIndex is added with 1 and then is given to the pointIndex of the tempLineTruct object, the pointeOid of the tempLineTruct is set to oid of the lastExtraFeture, and if the abovePoint Oid is not empty, the abovePoint Oid of the tempLineTruct is set to abovePoint Oid, and the tempLineTruct is stored in the pilotUnLineTructtList;

s3.83, finding out points like pointLocation in the PiperUnPointstructList, removing repeated points which are generally an end point and a tee joint point, reserving the tee joint point, removing the breakpoint, removing the end point and simultaneously removing objects in the PiperUnLinestructList corresponding to the removed point, and entering S3.84;

s3.84, respectively adding the PiperunLineStrectList and PiperPointStrectList into lineList and pointList, and returning to S3.3;

and S3.85, ending.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is intended to include such modifications and variations. The foregoing examples or embodiments are merely illustrative of the present invention, which may be embodied in other specific forms or in other specific forms without departing from the spirit or essential characteristics thereof. The described embodiments are, therefore, to be considered in all respects as illustrative and not restrictive. The scope of the invention should be indicated by the appended claims, and any changes that are equivalent to the intent and scope of the claims should be construed to be included therein.

Claims

1. A system for converting a three-dimensional pipeline model into a MapGIS model is characterized by comprising an external data reading module, an S3D model data downloading module, a point-line structure calculating module, a point-line structure duplicate removal module, a point-line table generating module and an Excel file generating module;

2. A method for converting a three-dimensional pipeline model into a MapGIS model, which comprises the steps of using the system for converting the S3D three-dimensional pipeline model into the MapGIS model of claim 1:

and S6, converting the dotted line table into an XLS file format.

3. The method of converting a three-dimensional pipeline model into a MapGIS model according to claim 2, wherein the step of S3 is as follows: