A method and system for online modeling of latitude and longitude data based on a cesium three-dimensional engine

Abstract

The present application relates to the technical field of geographic information system, and particularly relates to a latitude and longitude data online modeling method and system based on a Cesium three-dimensional engine. The method comprises the following steps: S1, obtaining a latitude and longitude data packet of a client, wherein the latitude and longitude data packet comprises an engineering coordinate system and latitude and longitude design information; S2, a server parses the latitude and longitude data packet and extracts a model point set; the model point set comprises a slope, a road surface, a bridge pier, a tunnel, a center line and a label; S3, a three-dimensional model is generated according to the model point set by calling a geometry construction interface of the Cesium three-dimensional engine; S4, continuous stake numbers, design stake numbers, model types and design parameter extension attributes are bound to the three-dimensional model, and rendering styles are set; and S5, the generated three-dimensional model is loaded into a Cesium three-dimensional scene for online display and interaction. The present application also comprises a system for implementing the method, and by parsing latitude and longitude data and generating a three-dimensional model, online modeling and visual display of engineering data are realized, and the modeling efficiency and interactivity are improved.

Description

Technical Field

[0001] This invention relates to the field of Geographic Information System (GIS) technology, and in particular to an online modeling method and system for latitude and geography data based on the Cesium 3D engine, which is suitable for geographic data visualization and 3D scene construction. Background Technology

[0002] With the development of 3D geographic information systems, traditional 2D geographic data can no longer meet the demands for high-precision and panoramic 3D modeling. Especially when dealing with large-scale geographic scenes and complex latitude and longitude data (such as elevation data and geological models), constructing accurate 3D models is a current research and application hotspot. However, existing 3D geographic modeling methods often require complex preprocessing and localization, making online modeling and real-time updates impossible.

[0003] Cesium, a WebGL-based 3D geographic visualization engine, is widely used for real-time rendering of large-scale geographic scenes. Although Cesium supports the display of 3D models, it lacks close integration with geographic data, especially in online modeling and visualization optimization for terrain, imagery, and road latitude and longitude data. Summary of the Invention

[0004] This application aims to address at least one of the technical problems existing in the prior art, namely the need for cumbersome local processing to achieve 3D modeling and the inability to support real-time updates. This application provides an online modeling method and system based on latitude and geography data using the Cesium 3D engine. It can perform online parsing and automatic 3D modeling of latitude and geography engineering data such as roads, pavements, slopes, bridges, and tunnels, resulting in 3D visualization models that can be rendered and interacted with in real time. In this method, coordinate projection transformation and data parsing are performed based on the latitude and geography data packets uploaded by the client. By constructing model point sets, calling the Cesium geometry interface to generate models, and binding design parameters and extended attributes, automatic modeling and rendering of various types of engineering objects can be achieved. This reduces preprocessing steps, improves modeling efficiency, and supports online display and interaction.

[0005] In a first aspect, embodiments of this application provide an online latitude and geodetic data modeling method based on the Cesium 3D engine, which may include:

[0006] S1. Obtain the client's latitude and longitude data packet containing engineering coordinate system and latitude and longitude design information;

[0007] S2. The server parses the latitude and geography data packet and extracts the model point set; the model point set includes slopes, road surfaces, bridge piers, tunnels, centerlines, and labels;

[0008] S3. Generate a 3D model by calling the geometry construction interface of the Cesium 3D engine based on the model point set;

[0009] S4. Bind the continuous station number, design station number, model type and extended design parameter attributes to the 3D model, and set the rendering style;

[0010] S5. Load the generated 3D model into the Cesium 3D scene for online display and interaction.

[0011] The online latitude and longitude data modeling method based on the Cesium 3D engine according to the embodiments of this application has at least the following beneficial effects:

[0012] The method in this application first uploads the original latitude and longitude data packet via the client and automatically parses it on the server, avoiding tedious local preprocessing. Then, by extracting and uniformly managing point sets of various models such as slopes, road surfaces, bridge piers, and tunnels, it achieves rapid organization of multi-source engineering data. Next, it uses the geometry construction interface of the Cesium 3D engine to generate the corresponding 3D model, and binds extended attributes such as station number, model type, and design parameters to this model. Finally, the model is loaded into a 3D scene for online display and interaction. Through the combination of coordinate projection transformation, attribute binding, and custom rendering styles, it achieves the effects of supporting real-time modeling of large-scale engineering data, reducing manual intervention, and improving modeling efficiency and accuracy, realizing online visualization and interactive operation of engineering data.

[0013] According to some embodiments of this application, the slope model point set obtained by parsing in S2 is used to construct the three-dimensional geometric surfaces and polylines of the cut slope, cut platform, fill slope, fill platform and ditch.

[0014] According to some embodiments of this application, the pavement model point set obtained by parsing in S2 includes earth shoulders, hard shoulders, driving lanes and median strips, and the corresponding pavement model is constructed based on Cesium's polygon geometry interface.

[0015] According to some embodiments of this application, the bridge pier model data obtained by parsing in S2 includes position coordinates and placement angle, and in S3, the prefabricated gltf model is loaded through the Cesium Model interface and placed in the corresponding position.

[0016] According to some embodiments of this application, the tunnel model data obtained by parsing in S2 includes the centerline coordinate point set and the road width, and the tunnel model is generated in S3 using Cesium's PolylineVolumeGeometry interface.

[0017] According to some embodiments of this application, the set of label points obtained by parsing in S2 includes highway stakes, 100-meter stakes, 20-meter stakes, 10-meter stakes, as well as bridge, tunnel, and culvert labels. In S3, the corresponding three-dimensional text labels are constructed through the Cesium LabelCollection interface.

[0018] Secondly, embodiments of this application provide an online latitude and longitude data modeling system based on the Cesium 3D engine, the system including:

[0019] The data upload module is used to receive latitude and longitude data packets uploaded by the client;

[0020] The data parsing module is used to parse the latitude and geography data package and extract the model point set, which includes slope, road surface, bridge pier, tunnel, centerline and label;

[0021] The model building module is used to generate a 3D model by calling the Cesium geometry building interface based on the model point set;

[0022] The attribute binding module is used to bind station number, model type and design parameter extended attributes to the 3D model, and set the rendering style;

[0023] The online display module is used to load the 3D model into the Cesium 3D scene for display and interaction.

[0024] The online latitude and longitude data modeling system based on the Cesium 3D engine according to the embodiments of this application has at least the following beneficial effects:

[0025] The system in this embodiment first receives latitude and longitude data packets transmitted from the client through the data upload module, avoiding tedious local processing of the original engineering data. Then, the data parsing module automatically extracts multiple model point sets, including slopes, road surfaces, bridge piers, tunnels, and labels, achieving integrated parsing of multi-source data. Next, the model building module calls the Cesium engine interface to generate a 3D model, and the attribute binding module further adds extended information such as station number, model type, and design parameters to the model and sets the rendering style. Finally, the online display module loads the model into a 3D scene for users to browse and interact with. By relying on modular division of labor and collaboration, the system achieves rapid online modeling and visualization of complex engineering data, significantly improving modeling efficiency and accuracy, and achieving the effect of reducing manual intervention and supporting real-time display and interaction.

[0026] Thirdly, embodiments of this application provide a computer device, the computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the methods described above.

[0027] Fourthly, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for executing the online latitude-geographic data modeling method based on the Cesium 3D engine as described in the first aspect embodiment above. Since the computer-readable storage medium employs all the technical solutions of the reservoir planar fluid identification method of the above embodiments, it possesses at least all the beneficial effects brought about by the technical solutions of the above embodiments.

[0028] Other features and advantages of this application will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing this application. Attached Figure Description

[0029] Figure 1 This is a flowchart illustrating the steps of the online latitude and geodetic data modeling method based on the Cesium 3D engine in Example 1.

[0030] Figure 2 This is a flowchart illustrating the steps of the online latitude and geodetic data modeling method based on the Cesium 3D engine in Example 2.

[0031] Figure 3 This is a flowchart of the slope model steps in Example 2;

[0032] Figure 4 This is a schematic diagram of the data format for constructing the roadbed model in Example 2;

[0033] Figure 5 This is a schematic diagram of the data format for constructing a highway subgrade model in Example 2;

[0034] Figure 6 This is a schematic diagram of the data format for the left lane of the highway pavement model in Example 2;

[0035] Figure 7 This is a schematic diagram of the data format for the right lane of the highway pavement model in Example 2;

[0036] Figure 8 This is a schematic diagram of the data format for constructing the bridge model in Example 2;

[0037] Figure 9 This is a schematic diagram of the data format for constructing the tunnel model in Example 2;

[0038] Figure 10 This is a schematic diagram of the data format for constructing the road centerline model in Example 2;

[0039] Figure 11 This is a schematic diagram of the data format for constructing the highway pile label model in Example 2;

[0040] Figure 12 This is a schematic diagram of the data format for constructing a 20-meter pile label model in Example 2;

[0041] Figure 13 This is a schematic diagram of the data format for constructing the 10-meter pile label model in Example 2;

[0042] Figure 14 This is a schematic diagram of the data format for constructing a bridge model after parsing latitude and longitude text in Example 2.

[0043] Figure 15 This is a schematic diagram of the online display of the 3D wireframe model for Example 2;

[0044] Figure 16 This is a schematic diagram of the online display of the three-dimensional surface model in Example 2;

[0045] Figure 17 This is a schematic diagram of the online display of road surface and slope models in Example 2;

[0046] Figure 18 This is a schematic diagram of the online display tunnel model for Example 2;

[0047] Figure 19 This is a schematic diagram of the bridge model displayed online in Example 2;

[0048] Figure 20 This is a schematic diagram of the online display of the bridge pier model in Example 2. Detailed Implementation

[0049] The present application will now be described in further detail with reference to experimental examples and specific embodiments. However, this should not be construed as limiting the scope of the subject matter of the present application to the following embodiments. All technologies implemented based on the content of the present application fall within the scope of protection of the present application.

[0050] Unless otherwise specified, the terms "upper," "lower," "left," "right," "center," "inner," "outer," and "side" used in the description of specific embodiments of this application to indicate orientation or positional relationships are based on the orientation or positional relationships shown in the accompanying drawings, or the orientation or positional relationship in which the product / equipment / device is usually placed during use. These terms are merely for the purpose of facilitating the description of the solution in this application or simplifying the description in specific embodiments, so as to enable those skilled in the art to quickly understand the solution, and do not indicate or imply that a particular device / component / element must have a specific orientation, or be constructed and operated in a specific positional relationship. Therefore, they should not be construed as limitations on this application.

[0051] In the description of the embodiments of this application, technical terms such as "first" and "second" only distinguish one entity or operation from another, and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary or secondary relationship of the indicated technical features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly defined.

[0052] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0053] Example 1

[0054] During the research process, the applicant discovered that traditional latitude-geographic data modeling methods require cumbersome local data preprocessing, format conversion, and multiple software integration steps to transform and display latitude-geographic data in an engineering coordinate system into a visualized 3D geographic model. This necessitates offline generation of model files before importing them into a 3D engine for display. When solving practical engineering problems, existing technologies cannot meet the demands for rapid parsing, automatic modeling, and interactive rendering of large-scale latitude-geographic data such as roads, bridges, and tunnels, in order to achieve real-time online modeling and dynamic display. Therefore, after researching this issue, the applicant proposed an online latitude-geographic data modeling method based on the Cesium 3D engine. Addressing the low efficiency of online parsing and 3D modeling of latitude-geographic data, this method establishes a technical solution involving coordinate projection transformation, model point set parsing, 3D geometry construction, and attribute binding. This enables the automatic generation and online rendering of various 3D models, including roads, pavements, slopes, bridges, and tunnels, on the server side, achieving real-time display and interaction without complex preprocessing.

[0055] Please refer to Figure 1 , Figure 1 This diagram illustrates the steps of an online latitude and longitude data modeling method based on the Cesium 3D engine, as provided in an embodiment of this application. The method may include:

[0056] S1. Obtain the client's latitude and longitude data packet containing engineering coordinate system and latitude and longitude design information;

[0057] S2. The server parses the latitude and geography data packet and extracts the model point set; the model point set includes slopes, road surfaces, bridge piers, tunnels, centerlines, and labels;

[0058] S3. Generate a 3D model by calling the geometry construction interface of the Cesium 3D engine based on the model point set;

[0059] S4. Bind the continuous station number, design station number, model type and extended design parameter attributes to the 3D model, and set the rendering style;

[0060] S5. Load the generated 3D model into the Cesium 3D scene for online display and interaction.

[0061] The online latitude and longitude data modeling method based on the Cesium 3D engine according to the embodiments of this application has at least the following beneficial effects:

[0062] The method in this application first uploads the original latitude and longitude data packet via the client and automatically parses it on the server, avoiding tedious local preprocessing. Then, by extracting and uniformly managing point sets of various models such as slopes, road surfaces, bridge piers, and tunnels, it achieves rapid organization of multi-source engineering data. Next, it uses the geometry construction interface of the Cesium 3D engine to generate the corresponding 3D model, and binds extended attributes such as station number, model type, and design parameters to this model. Finally, the model is loaded into a 3D scene for online display and interaction. Through the combination of coordinate projection transformation, attribute binding, and custom rendering styles, it achieves the effects of supporting real-time modeling of large-scale engineering data, reducing manual intervention, and improving modeling efficiency and accuracy, realizing online visualization and interactive operation of engineering data.

[0063] According to some embodiments of this application, the slope model point set obtained by parsing in S2 is used to construct the three-dimensional geometric surfaces and polylines of the cut slope, cut platform, fill slope, fill platform and ditch.

[0064] According to some embodiments of this application, the pavement model point set obtained by parsing in S2 includes earth shoulders, hard shoulders, driving lanes and median strips, and the corresponding pavement model is constructed based on Cesium's polygon geometry interface.

[0065] According to some embodiments of this application, the bridge pier model data obtained by parsing in S2 includes position coordinates and placement angle, and in S3, the prefabricated gltf model is loaded through the Cesium Model interface and placed in the corresponding position.

[0066] According to some embodiments of this application, the tunnel model data obtained by parsing in S2 includes the centerline coordinate point set and the road width, and the tunnel model is generated in S3 using Cesium's PolylineVolumeGeometry interface.

[0067] According to some embodiments of this application, the set of label points obtained by parsing in S2 includes highway stakes, 100-meter stakes, 20-meter stakes, 10-meter stakes, as well as bridge, tunnel, and culvert labels. In S3, the corresponding three-dimensional text labels are constructed through the Cesium LabelCollection interface.

[0068] The online modeling method for latitude and geography data based on the Cesium 3D engine provided in this application can be applied to many technical fields, such as intelligent transportation, digital city construction, infrastructure operation and maintenance management, and engineering visualization simulation. In the above implementation, when modeling and controlling latitude and geography data such as roads, bridges, and tunnels, the client can upload the original data, the server automatically parses and generates a model point set, and then the Cesium engine is used to complete the 3D geometry construction and attribute binding, thereby achieving real-time rendering and interactive display of the model, reducing manual preprocessing, improving modeling efficiency, and ensuring model accuracy. Specific implementation methods can be found in the descriptions in the following embodiments, which will not be elaborated here.

[0069] Example 2

[0070] As a further optimization of the preceding embodiments, this application provides a specific implementation of an online latitude and geography data modeling method based on the Cesium 3D engine, illustrated using a real-world scene modeling task as an example. The task background is to build a 10-square-kilometer 3D model of an urban area, including buildings, terrain, roads, and annotations, using both the method of this invention and traditional modeling processes.

[0071] This invention achieves online modeling of latitude and geography data through the following steps, such as... Figure 2 As shown.

[0072] 1. Client Uploads Route Latitude and Longitude Data: The client uploads a route latitude and longitude data package using a specified file structure. This data package is generated by the latitude and longitude software and includes files in the following formats: .prj (Road Segment Independent Coordinate System), K31.ctr, K31.DMX, K31.HDM, K31.JD, K31.lj, K31.pm, K31.Prj, K31.STA, K31.sup, K31.TF, K31.wid, and K31.ZDM. The .prj file is an additional project-independent coordinate system added to this method, designed to project and transform the engineering coordinate system to three-dimensional geographic coordinates.

[0073] The specific content of the independent coordinate system .prj file for a certain road section is as follows: PROJCS["DFLH_DL>2000",GEOGCS["GCS_wGS_1984",DATUM["D_WGS84",SPHEROID["WGS84",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARA METER["scale_factor",1.00051325899996],PARAMETER["central_meridian",101.0007172],PARAMETER["latitude_of_origin ",0],PARAMETER["false_easting",500070.141289437],PARAMETER["false_northing",66.5212078280747],UNIT["Meter",1]].

[0074] 2. Server-side parsing of latitude and longitude data: The server parses the uploaded data, extracts road design information, and generates the following data sets: slope model point set BP_ARAAY, pavement model point set LM_ARAAY, pier model data QD_ARAAY, tunnel model data SD_ARAAY, design center point set MIDDLE_ARAAY, highway pile label point set 1000_ARAAY, 100-meter pile label point set 100_ARAAY, 20-meter pile label point set 20_ARAAY, 10-meter pile label point set 10_ARAAY, bridge label point set QLNAME_ARAAY, tunnel label point set SDNAME_ARAAY, and culvert label point set HDNAME_ARAAY.

[0075] 3. Three-dimensional model construction:

[0076] (1) Constructing a slope model

[0077] The slope model point set BP_ARAAY data is obtained by the client from the server by setting the sampling interval of the station number and the threshold setting of 10 meters. The model types of (PL) continuous station number 27334.4 and (DE) design station number A27334.4 include WFBP_L11_3, WFBP_L11_2, WFBP_L11_1, etc. WFBP represents cut, L11 represents level 11 cut, and the last digit [3,2] represents cut slope and [2,1] represents cut platform.

[0078] The model construction rule method is as follows: Obtain the list of model type names from the i=0th item of the BP_ARAAY array: WFBP_L11_3, WFBP_L11_2, WFBP_L11_1, WFBP_L10_3, WFBP_L10_2, etc. The BP_ARAAY array and model types are constructed in order.

[0079] The steps of the slope model flowchart are as follows: Figure 3 As shown.

[0080] 1. Input data (BP_ARAAY): Obtain the longitudinal profile data of the slope with the station sampling interval and threshold set to 10 meters from the client and store it in the BP_ARAAY array.

[0081] 2. Parse model types: Starting from the i=0th item in the BP_ARAAY array, extract all model types (such as WFBP_L11_3, WFBP_L11_2, etc.).

[0082] 3. Determine the station interval: Calculate the interval ΔPL between consecutive station numbers and determine whether it is greater than 50 meters.

[0083] 4. Discard discontinuous model data: If ΔPL>50, discard the data and skip incomplete data.

[0084] 5. Constructing Geometry and Polylines: Based on the model type, use the Cesium API to construct polygon geometries and polylines.

[0085] 6. Bind extended attributes: Bind extended attributes (such as consecutive station numbers, design station numbers, model type, design parameters, PDF files, etc.) to each model.

[0086] 7. Apply rendering styles: Set custom rendering styles (such as color and material) according to different model types.

[0087] 8. Output rendering results: Render the final 3D model for display on the client.

[0088] Faces and polylines can be constructed as follows, for example:

[0089]

[0090] PolygonGeometry / PolylineGeometry: Geometry construction interfaces provided by the Cesium 3D engine, used to generate polygonal faces and polyline geometry respectively; Coordinates[…]: used to represent the input 3D coordinate sequence, including longitude (X), latitude (Y), and elevation (Z); BPMX A RAAY: An array of point sets for the slope model, where BPMX A RAAY[i] represents the slope data of the i-th station section, BPMX A RAAY[i+1] represents the next adjacent cross-section data; i / i+1: adjacent cross-section indices arranged in station order, used to ensure the continuity of the model. When the distance between adjacent station numbers ΔPL is greater than a preset threshold (e.g., 50 meters), it indicates that the cross-section is discontinuous or incomplete, and the model data is discarded. Using the PolygonGeometry and PolylineGeometry APIs provided by the Cesium 3D engine, polygonal faces and polyline models are drawn, and extended attributes and custom rendering styles are assigned to the models. WFBP L 113. WFBP L 112: Type identifier for slope model, where "WFBP" indicates a cut slope; L "11" indicates the slope grade; the subscript number indicates the specific sub-components under that grade, such as the slope body, slope platform, etc.

[0091] Extended attributes include, for example, binding consecutive station numbers, design station numbers, model types, design parameters, and drawing PDF files.

[0092] Customize the rendering style and set different material textures or colors according to the model type. For example: cut slope Color=#0a8700, cut platform Color=#D3D3D3, ditch bottom Color=#0000FF, ditch Color=#AAAAAA, fill slope Color=#0a8700, fill platform Color=#D3D3D3.

[0093] like Figure 4 As shown, Figure 4 The required data format for constructing a roadbed model. Highway roadbed models are divided into... Figure 4 and Figure 5 The roadbed model includes: cut slopes, cut platforms, ditch bottoms, side ditches, fill slopes, and fill platforms. Triangular patch model data is constructed from points, and the Cesium method is called to render the model and set model attribute IDs for associating with design attributes.

[0094] (2) Road surface model point set

[0095] The LM_ARAAY road surface model point set data is obtained from the server by the client by setting the sampling interval by station number and setting the threshold to 10 meters. The model types for (PL) continuous station number 5460 and (DE) design station number 5640 include LM_L6, LM_L5, LM_L4, LM_L3, LM_L2, LM_L1, LM_R6, LM_R5, LM_R4, LM_R3, LM_R2, and LM_R1. LM represents the road surface, [L6, L5, R6, R5] represents the earth shoulder, [L5, L4, R5, R4] represents the hard shoulder, [L4, L3, L2, L1] represents the left lane, [R4, R3, R2, R1] represents the right lane, and [L1, R1] represents the median strip.

[0096] The model construction rules and methods are as follows: Obtain the list of model type names from the i=0th item of the LM_ARAAY array: LM_L6, LM_L5, LM_L4, LM_L3, LM_L2, LM_L1, LM_R6, LM_R5, LM_R4, LM_R3, LM_R2, LM_R1, etc. The LM_ARAAY array and model types are constructed in order.

[0097] For example:

[0098]

[0099] If the consecutive station intervals of LM_ARAAY[[i].PL and LM_ARAAY[[i+1].PL are greater than 50 meters, it indicates that the cross-section is discontinuous or incomplete, and the model data is discarded. Using the PolygonGeometry and PolylineGeometry APIs provided by the Cesium 3D engine, polygonal faces and polyline models are drawn, and extended attributes and custom rendering styles are assigned to the models.

[0100] Extended attributes include, for example, binding consecutive station numbers, design station numbers, model types, design parameters, and drawing PDF files.

[0101] Customize the rendering style and set different material textures or colors according to the model type. For example: dirt shoulder Color=#7F7F7F, hard shoulder Color=#3F3F3F, left lane Color=#000000, right lane Color=#000000, median strip Color=4F6128.

[0102] like Figure 6 and Figure 7As shown in the figure, the code is used to build a road surface model, including the required data format.

[0103] The road surface model is divided into left lanes and right lanes, respectively corresponding to... Figure 6 and Figure 7 The road surface model includes: unpaved shoulders, hard shoulders, left-hand driveway, right-hand driveway, and median strip. Surfaces are created from points, and then different textures or colors are applied to these surfaces to achieve rapid, real-time modeling.

[0104] (3) Pier model data

[0105] The bridge pier model data, QD_ARAAY data, is obtained from the server, including the coordinates of all bridge piers along the route and the prefabricated glTF model. The parameters are: (PL) continuous station number 32150.0, (DE) design station number A32150.00000000, (OBJURL) prefabricated model link, (ANGLE) prefabricated model placement angle, (NAME) bridge pier name, (X) bridge pier longitude, (Y) bridge pier latitude, and (Z) bridge pier elevation. Using the Model API provided by the Cesium 3D engine, the X, Y, Z, and ANGLE parameters are converted into Cartesian3 and Matrix4 for model placement and rotation angles. The 3D model is then displayed, and extended attributes and custom rendering styles are assigned to it.

[0106] Extended attributes, such as binding consecutive station numbers, design station numbers, model names, design parameters, and drawing PDF files, etc.

[0107] Customize rendering styles and set different material textures or colors based on the model type.

[0108] like Figure 8 As shown, Figure 8 The required data format for constructing a bridge model. Specifically, PL represents continuous station numbers, DE represents design station numbers, OBJURL represents the prefabricated bridge model file, ANGLE represents the bridge model placement angle, NAME represents the bridge name, and XYZ represents the bridge model position.

[0109] (4) Tunnel model data

[0110] Tunnel model data SD_ARAAY data, obtained from the server, is a set of coordinate points for all tunnels along the route. Figure 9As shown, (PLS) represents the continuous chainage of the starting point, (PLE) the continuous chainage of the ending point, (DES) the design chainage of the starting point, (DEE) the design chainage of the ending point, (NAME) the tunnel name, (WIDS) the road width of the starting point, (WIDE) the road width of the ending point, and (XYZS) the set of coordinate points of the tunnel center. Using the PolylineVolumeGeometry API provided by the Cesium 3D engine, a 3D surface model is drawn using the XYZS coordinate point set and the road width parameter, and extended attributes and custom rendering styles are assigned to the model.

[0111] Extended attributes include, for example, binding the starting point continuous chainage, the ending point continuous chainage, the starting point design chainage, the ending point design chainage, the tunnel name, design parameters, and drawing PDF files.

[0112] Customize the rendering style, setting the material texture or color of the tunnel model. Fill color: fillColor=F5F5F5.

[0113] like Figure 9 As shown, Figure 9 The required data format for constructing the tunnel model includes: PLS and PLE representing the start and end chainages of consecutive chainages, DES and DEE representing the start and end chainages of the design chainages, NAME representing the tunnel name, WIDS and WIDE representing the tunnel design parameters, and XYZS representing the set of coordinate points for the tunnel pavement centerline.

[0114] (5) Design the centerline point set

[0115] The road centerline model data is MIDDLE_ARAAY data, obtained from the server as a set of coordinate points for the route design center. Figure 10 As shown, (X) represents longitude, (Y) represents latitude, and (Z) represents elevation. Using the PolylineGeometry API provided by the Cesium 3D engine, a 3D line model is drawn using the X, Y, and Z coordinate parameters, and extended attributes and custom rendering styles are assigned to the model.

[0116] Extended attributes, such as binding design parameters and drawing PDF files.

[0117] Customize the rendering style and set the color of the line model in the design. Fill color fillColor=F5F5F5.

[0118] like Figure 10 As shown, Figure 10 The required data format for constructing the road centerline model. Where X represents longitude, Y represents latitude, and Z represents elevation.

[0119] (6) Highway pile label model

[0120] The highway stake label model data 1000_ARAAY data is obtained from the server, with a set of stake coordinate points spaced 1000 meters apart, as shown below. Figure 11 As shown, (PL) represents the continuous station number, (DE) represents the design station number, (TEXT) represents the station name, (X) represents the longitude value, (Y) represents the latitude value, and (Z) represents the elevation value. Using the LabelCollection API provided by the Cesium 3D engine, a 3D text model is drawn using the X, Y, and Z coordinate points and the TEXT station name parameter, and extended attributes and custom rendering styles are assigned to the model.

[0121] Extended attributes include, for example, binding consecutive station numbers, design station numbers, station names, design parameters, and drawing PDF files.

[0122] Customize the rendering style, set the style of the highway post label model, fill color fillColor=#FFFFFF, font name and size font=16px sans-serif, font outline color outlineColor=#000000, font outline width outlineColor=2, label display distance condition distanceDisplayCondition=newDistanceDisplayCondition(0, 5000), label text horizontal and vertical alignment, etc.

[0123] like Figure 11 As shown, Figure 11 The required data format for constructing a highway stake label model. Here, PL represents continuous stake number, DE represents design stake number, TEXT represents label name, X represents longitude, Y represents latitude, and Z represents elevation.

[0124] (7) 100-meter stake label model

[0125] Highway pile label model data 100_ARAAY data, obtained from the server, is a set of pile coordinate points spaced 100 meters apart, (PL) continuous pile number, (DE) design pile number, (TEXT) pile name, (X) longitude value, (Y) latitude value, and (Z) elevation value.

[0126] The model is constructed in the same way as the highway pile label model.

[0127] (8) Twenty-meter stake model

[0128] The 20-meter pile label model data (20_ARAAY data) is obtained from the server, using a set of pile coordinate points spaced 20 meters apart, as shown below. Figure 12 As shown, Figure 12 The required data format for constructing a 20-meter pile label model. Here, PL represents continuous pile number, DE represents design pile number, TEXT represents label name, X represents longitude, Y represents latitude, and Z represents elevation.

[0129] The model is constructed in the same way as the highway pile label model.

[0130] (9) Ten-meter pile label model

[0131] The 10-meter pile label model data, 10_ARAAY data, is obtained from the server as a set of pile coordinate points spaced 10 meters apart. Figure 13 As shown, Figure 13 The required data format for constructing a 10-meter pile label model. Here, PL represents continuous pile number, DE represents design pile number, TEXT represents label name, X represents longitude, Y represents latitude, and Z represents elevation.

[0132] The model is constructed in the same way as the highway pile label model.

[0133] (10) Bridge label model

[0134] The bridge label model data, QL_ARAAY data, is obtained from the server, containing all bridge coordinate point sets: (PLS) starting continuous station number, (PLE) ending continuous station number, (DES) starting design station number, (DEE) ending design station number, (NAME) bridge name, (STYPE) bridge type, (SVALUE) bridge span, (WIDS) starting road width, (WIDE) ending road width, and (XYZS) bridge coordinate point set. Using the LabelCollection and PolylineCollection APIs provided by the Cesium 3D engine, 3D text and 3D line models are drawn using the X, Y, Z coordinate points and TEXT station name parameters, and extended attributes and custom rendering styles are assigned to the models.

[0135] Extended attributes include: binding the starting continuous chainage, the ending continuous chainage, the starting design chainage, the ending design chainage, the bridge name, the bridge type, the bridge span, design parameters, and the drawing PDF file, etc.

[0136] Customize the rendering style, set the bridge label model style, text fill color fillColor=#000000, font name and size font=16px sans-serif, font background color backgroundColor=#FF0000, font outline color outlineColor=#000000, font outline width outlineColor=2, label display distance condition distanceDisplayCondition=new DistanceDisplayCondition(0, 5000), label text horizontal and vertical alignment, etc.

[0137] like Figure 14 As shown, Figure 14 After parsing the latitude and longitude text, the bridge model data format (including continuous starting station PLS, continuous ending station PLE, design starting station DES, design ending station DEE, bridge name NAME, original design information and attributes, etc.) is a custom format.

[0138] (11) Tunnel Label Model

[0139] The same method is used to construct bridge tags.

[0140] (12) Culvert Label Model

[0141] The same method is used to construct bridge tags.

[0142] 4. Custom Rendering and Extended Attributes: Each model supports custom rendering styles, including different materials, colors, and transparency. For example, cut slopes can be set to green, and road surfaces to black. It also supports binding additional design parameters, drawings, PDF files, etc.

[0143] Online model display

[0144] The constructed 3D model is loaded into the Cesium 3D engine, and then overlaid with imagery and terrain for online display. Users can access the 3D model through a browser or other clients, and perform operations such as flying into the construction site location (bridge, tunnel, culvert, station) to browse the map, rotate the map, and zoom the map. Figure 15 and Figure 16 Display 3D wireframe models and 3D surface models online.

[0145] The 3D wireframe model includes cut slopes, cut platforms, ditch bottoms, side ditches, fill slopes, fill platforms, earth shoulders, hard shoulders, left lanes, right lanes, medians, center lines, tunnel models, bridge models, highway marker labels, 100-meter marker labels, 20-meter marker labels, 10-meter marker labels, bridge labels, tunnel labels, and culvert labels.

[0146] Figure 17 Based on the K54+440 station number, fly in and highlight the road surface and slope model; Figure 18 To fly into and highlight the tunnel model based on its name; Figure 19 To allow users to fly into and highlight bridge models based on their bridge names, it also supports flying into specific bridge piers, such as... Figure 20 As shown, Figure 20 To highlight a specific bridge pier model.

[0147] Online sharing model

[0148] After the 3D model is generated, users can share it by linking or embedding code. It supports multiple users accessing it simultaneously and provides a plotting function, allowing users to plot points, lines, surfaces, circles, rectangles, images, and other information on the map.

[0149] It should be understood that the various modules of the online latitude and geodetic data modeling system based on the Cesium 3D engine provided in the above embodiments are only illustrated by the division of each functional module in the above description. In practical applications, the above functions can be assigned to different functional modules as needed. That is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0150] The functional modules in the above embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of the embodiments of this application.

[0151] Based on the same concept, embodiments of this application also provide a computer device, which may include a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the online latitude and longitude data modeling method based on the Cesium 3D engine as described above.

[0152] Based on the same concept, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the online latitude and geodetic data modeling method based on the Cesium 3D engine as described above.

[0153] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects.

[0154] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0155] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for online modeling of latitude and geography data based on the Cesium 3D engine, characterized in that, include: S1. Obtain the client's latitude and longitude data packet containing engineering coordinate system and latitude and longitude design information; S2. The server parses the latitude and geodetic data packet and extracts the model point set; the model point set includes slopes, road surfaces, bridge piers, tunnels, centerlines, and labels; wherein, the model point sets of slopes and road surfaces are obtained and extracted from the server according to the station sampling interval and threshold parameters set by the client; S3. Generate a 3D model by calling the geometry construction interface of the Cesium 3D engine based on the model point set; S4. Bind the continuous station number, design station number, model type and extended design parameter attributes to the 3D model, and set the rendering style; S5. Load the generated 3D model into the Cesium 3D scene for online display and interaction.

2. The method according to claim 1, characterized in that, The slope model point set obtained from S2 is used to construct the three-dimensional geometric surfaces and polylines of the cut slope, cut platform, fill slope, fill platform and ditch.

3. The method according to claim 1, characterized in that, The pavement model point set obtained by parsing in S2 includes earth shoulders, hard shoulders, driving lanes and median strips, and the corresponding pavement model is constructed based on Cesium's polygon geometry interface.

4. The method according to claim 1, characterized in that, The bridge pier model data obtained in S2 includes position coordinates and placement angle. In S3, the prefabricated glTF model is loaded through the Cesium Model interface and placed in the corresponding position.

5. The method according to claim 1, characterized in that, The tunnel model data obtained by parsing in S2 includes the centerline coordinate point set and the road width. In S3, the tunnel model is generated using Cesium's PolylineVolumeGeometry interface.

6. The method according to claim 1, characterized in that, The set of label points obtained by parsing in S2 includes highway stakes, 100-meter stakes, 20-meter stakes, 10-meter stakes, as well as bridge, tunnel, and culvert labels. In S3, the corresponding three-dimensional text labels are constructed through Cesium's LabelCollection interface.

7. An online modeling system for latitude and longitude data based on the Cesium 3D engine, characterized in that, include: The data upload module is used to receive latitude and longitude data packets uploaded by the client; The data parsing module parses the latitude and geodetic data packets and extracts the model point set. The model point set includes slopes, road surfaces, bridge piers, tunnels, centerlines, and labels. The model point sets for slopes and road surfaces are obtained and extracted from the server according to the station sampling interval and threshold parameters set by the client. The model building module is used to generate a 3D model by calling the Cesium geometry building interface based on the model point set; The attribute binding module is used to bind station number, model type and design parameter extended attributes to the 3D model, and set the rendering style; The online display module is used to load the 3D model into the Cesium 3D scene for display and interaction.

8. The system according to claim 7, characterized in that, The data parsing module is further used to determine the interval between consecutive station numbers, and discards the corresponding model data when the station number interval is greater than a preset threshold.

9. A computer device, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as claimed in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 6.

Images