Three-dimensional visual rendering method and device for geographic space data

Abstract

The invention provides a three-dimensional visualization rendering method for geographic space data, and the method comprises the steps: receiving a rendering request which is used for indicating the visualization of business index data associated with a building in a three-dimensional scene; calling a preprocessing module to obtain original geographic space data and business index data, and preprocessing the original geographic space data and the business index data to generate standardized data; sending a data acquisition request to a back-end server based on the display view field range of the current viewport and the LOD level parameter; obtaining a three-dimensional tile set generated and returned by the back-end server according to the view field, the LOD hierarchy parameters and the standardized data; and calling a front-end rendering engine to load the three-dimensional tile set, and performing three-dimensional rendering on the three-dimensional model of the corresponding building and the service data by taking the service index data as a rendering basis according to the association relationship between the service index data and the building. According to the application, automatic processing from data preprocessing to scene rendering can be realized through front and rear end collaborative interaction, so that the system efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of three-dimensional geographic information data technology, and in particular to a three-dimensional visualization rendering method and apparatus for geospatial data. Background Technology

[0002] 3D geographic information systems are widely used in urban planning, facility management, smart cities and other fields. The 3D visualization of geospatial data provides a more intuitive and dynamic service platform for diverse business interactions and operations.

[0003] Existing technologies typically employ manual modeling and rendering. First, geospatial data is converted into model files using modeling tools like CityEngine. Then, an intermediate format is output, and the data is manually published as a web service to achieve front-end visualization. Therefore, this approach has the following drawbacks: On the one hand, existing technologies rely on a large number of manual, repetitive mechanical operations, resulting in a low degree of automation in the overall process from data conversion to service release. This not only makes it difficult to improve the efficiency of 3D modeling, but also introduces the risk of data deviation due to multiple conversions of intermediate formats, ultimately restricting the development efficiency and quality of the overall application.

[0004] On the other hand, the high-precision rendering requirements for large-scale building data require the preparation of a large amount of detailed modeling data in advance and its overall loading through Web services, resulting in slow system response, low rendering efficiency, and difficulty in supporting smooth dynamic interaction and real-time presentation, thus limiting its application potential in macro-level scenarios.

[0005] Therefore, in this context, how to provide a 3D visualization rendering method for geospatial data that can automate the process from data preprocessing to scene rendering through front-end and back-end collaborative interaction, thereby improving system efficiency, is a technical problem that needs to be solved. Summary of the Invention

[0006] In view of the above-mentioned problems of the prior art, this application provides a three-dimensional visualization rendering method and apparatus for geospatial data, which can realize automated processing from data preprocessing to scene rendering through front-end and back-end collaborative interaction, thereby improving system efficiency.

[0007] To achieve the above objectives, the first aspect of this application provides a three-dimensional visualization rendering method for geospatial data, applied to a front-end, comprising the following steps: Receive a rendering request, which is used to instruct the visualization of business indicator data associated with buildings in a three-dimensional scene; The preprocessing module is invoked to obtain the original geospatial data and the business indicator data, and the original geospatial data is preprocessed to generate standardized data; wherein, the standardized data contains the geometric information of at least one building, the geometric information includes two-dimensional contour data and height data, and the business indicator data is associated with the corresponding building; Based on the current viewport's display field of view and Level of Detail (LOD) parameters, a data retrieval request is sent to the backend server. Obtain the set of 3D tiles generated and returned by the backend server based on the field of view, LOD level parameters, and the standardized data; The front-end rendering engine is invoked to load the set of three-dimensional tiles. Based on the relationship between the business indicator data and the buildings, the business indicator data is used as the rendering basis to render the three-dimensional model of the corresponding building, so as to realize the three-dimensional visualization of each building and its associated business indicators.

[0008] As described above, by receiving rendering requests for visualizing building-related business indicator data at the front end, the preprocessing module is called to fuse the original geospatial data and business indicator data to generate standardized data containing two-dimensional contours, height information, and business relationships. This achieves automatic binding and linkage between business data and three-dimensional geospatial models, avoiding the efficiency loss and data distortion caused by traditional manual modeling and intermediate format conversion.

[0009] Based on the current viewport's field of view and LOD (Level of Detail) parameters, the system dynamically requests a suitable 3D tile set from the backend. The frontend rendering engine then loads this tile set and performs differentiated rendering of the building model based on business metrics data. Leveraging tile-based rendering and LOD mechanisms, the system effectively supports efficient, smooth, and detailed 3D visualization of business metrics in large-scale architectural scenarios. This significantly improves the system's response performance and interactive experience in complex business scenarios, thereby achieving automated processing from data preprocessing to scene rendering through frontend-backend collaborative interaction, enhancing the overall efficiency and accuracy of the system.

[0010] As one possible implementation of the first aspect, after generating the standardized data, it is determined whether the number of buildings contained therein exceeds a preset threshold. If the preset threshold is not exceeded, the front-end rendering engine is directly invoked to generate a three-dimensional model for each building based on the two-dimensional contour data and corresponding height data in the standardized data, and then rendered according to the business indicator data associated with it, so as to realize the three-dimensional visualization display of the building and business application.

[0011] As shown above, in scenarios with a small number of buildings, the system can bypass tile rendering and backend request processes, and directly build and render 3D models in real time on the front end based on standardized data, avoiding unnecessary network communication and backend computing overhead. This implementation method complements the tile rendering mechanism in the aforementioned large-scale scenarios, together forming an adaptive data scale-aware rendering strategy, further enhancing the automated processing capabilities of front-end and back-end collaboration, and improving the system's response efficiency and resource utilization under different data volumes.

[0012] As one possible implementation of the first aspect, the building information also includes floor data, and the business indicator data corresponds to at least one floor of the building; The preprocessing module further preprocesses the business indicator data to generate mapping parameters for rendering, and incorporates the mapping parameters into the standardized data.

[0013] As described above, by defining floor data and establishing a correspondence between business indicator data and at least one floor of the building, a more refined 3D display can be achieved. This method not only enhances the detail of the building's exterior but also delves into the building's internal structure, providing users with a more multi-dimensional information display.

[0014] As one possible implementation of the first aspect, the process of calling the front-end rendering engine to load the 3D tile set and perform 3D model rendering includes: The floor data of each building in the three-dimensional tile set is analyzed, and each building is divided into multiple corresponding floor units; Based on the rendering parameters mapped to the business indicator data corresponding to each floor unit in the standardized data, each floor unit is rendered separately.

[0015] As described above, by parsing the floor data in the 3D tile set during the rendering stage and dividing the building into fine-grained floor units, combined with the rendering parameters mapped to the business indicators associated with each floor unit in the standardized data, differentiated rendering at the floor level for large-scale data is achieved. This process is automatically completed through standardized data and tile structures generated collaboratively by the front-end and back-end, without manual intervention. This further enhances the automation capability of the entire process from data preprocessing to scene rendering, effectively supporting the actual needs for refined and efficient 3D visualization in complex business scenarios.

[0016] As one possible implementation of the first aspect, the process of generating and rendering three-dimensional models of each building based on the two-dimensional contour data and corresponding height data in the standardized data includes: Based on the two-dimensional outline data, height data, and floor data of the building, extrusion modeling is performed floor by floor to generate a three-dimensional model of each floor. The 3D model of the corresponding floor is rendered based on the rendering parameters mapped from the business indicator data associated with each floor.

[0017] Based on the above, a floor-level 3D model is generated using the building's 2D outline, height, and floor data. Correspondingly, floor-level 3D rendering is performed on the business data, simplifying the conversion process from 2D to 3D and improving work efficiency.

[0018] As one possible implementation of the first aspect, the front end stores the generated standardized data in a shared storage location and enables the back end server to access the shared storage location to obtain the standardized data for generating the three-dimensional tile set.

[0019] As described above, by storing the standardized data generated by the front end in a shared storage location and making it directly accessible to the back end server, efficient collaboration between the front end and the back end at the data level is achieved.

[0020] As one possible implementation of the first aspect, obtaining the 3D tile set of the backend server includes: Receive the access address of the tile service path returned by the backend server; Based on the access address, the three-dimensional tile set is obtained from the tile service path.

[0021] As described above, by receiving the tile service path access address returned by the backend and dynamically loading the 3D tile set accordingly, the frontend does not need to pre-load or download the entire model data; it only needs to obtain the tile content required for the current viewport. This approach not only reduces network transmission overhead and memory usage but also improves loading efficiency and interactive smoothness in large-scale scenes.

[0022] As one possible implementation of the first aspect, it also includes: When a change is detected in the displayed field of view and / or LOD level parameters, the target area that needs to be incrementally updated and the corresponding LOD level are determined based on the changed part, and this information is sent to the backend. Obtain the incremental 3D tile set generated by the backend based on the target region requiring incremental updates and its corresponding LOD level, as well as the standardized data; The incremental 3D tile set is loaded by the front-end rendering engine, and the 3D models of the buildings contained therein are rendered to update the 3D visualization of the buildings in the current view.

[0023] As described above, by using incremental update rendering, when the viewport field of view or LOD level parameters change, only the target area requiring incremental update and its corresponding LOD level are determined for the changed part. The system then requests the corresponding incremental 3D tile set from the backend, avoiding the repeated loading and rendering of the full data. The incremental update strategy, in deep collaboration with standardized data and tile service architecture, further improves the automated rendering process that links the frontend and backend.

[0024] A second aspect of this application provides a three-dimensional visualization rendering device for geospatial data, deployed at a front end, comprising: A request receiving module is used to receive a rendering request, which is used to instruct the visualization of business indicator data associated with buildings in a three-dimensional scene. The preprocessing call module is used to call the preprocessing module to obtain the original geospatial data and the business indicator data, and to preprocess the original geospatial data to generate standardized data; wherein, the standardized data contains the geometric information of at least one building, the geometric information includes two-dimensional contour data and height data, and the business indicator data is associated with the corresponding building; The request sending module is used to send data retrieval requests to the backend server based on the display field of view and the level of detail (LOD) parameters of the current viewport. The tile acquisition module is used to acquire the set of three-dimensional tiles generated and returned by the backend server based on the field of view, LOD level parameters and the standardized data; The rendering execution module is used to call the front-end rendering engine to load the three-dimensional tile set, and based on the relationship between the business indicator data and the buildings, use the business indicator data as the rendering basis to render the three-dimensional model of the corresponding building, so as to realize the three-dimensional visualization of each building and its associated business indicators.

[0025] A third aspect of this application provides a computing device, including: a processor and a memory storing program instructions thereon, the program instructions, when executed by the processor, causing the processor to perform a three-dimensional visualization rendering method for geospatial data as described in any of the first aspects.

[0026] The fourth aspect of this application provides a computer-readable storage medium having program instructions stored thereon, which, when executed by a computer, cause the computer to perform the three-dimensional visualization rendering method for geospatial data as described in any of the first aspects.

[0027] The fifth aspect of this application provides a computer program product including program instructions that, when executed by a computer, cause the computer to perform the three-dimensional visualization rendering method for geospatial data as described in any of the first aspects. Attached Figure Description

[0028] Figure 1 This is a flowchart of the three-dimensional visualization rendering method for geospatial data provided in the first embodiment of this application; Figure 2a This is a flowchart of the three-dimensional visualization rendering method for geospatial data provided in the second embodiment of this application; Figure 2b This is a schematic diagram of the logical functional modules provided in the second embodiment of this application; Figure 2c This is a schematic diagram of the rendering effect provided in the second embodiment of this application; Figure 2d This is the overall system execution flowchart provided in the second embodiment of this application; Figure 2e This is a schematic diagram of the user interaction process provided in the second embodiment of this application; Figure 3 This is a schematic diagram of a three-dimensional visualization rendering device for geospatial data provided in an embodiment of this application; Figure 4 This is a schematic structural diagram of a computing device provided in an embodiment of this application.

[0029] It should be understood that the dimensions and shapes of the blocks in the above structural diagrams are for reference only and should not constitute an exclusive interpretation of the embodiments of the present invention. The relative positions and inclusion relationships between the blocks presented in the structural diagrams are only schematic representations of the structural relationships between the blocks, and are not intended to limit the physical connection methods of the embodiments of the present invention. Detailed Implementation

[0030] The technical solutions provided in this application will be further described below with reference to the accompanying drawings and embodiments. It should be understood that the system architecture and business scenarios provided in the embodiments of this application are mainly for illustrating possible implementations of the technical solutions of this application and should not be construed as the sole limitation on the technical solutions of this application. Those skilled in the art will recognize that the technical solutions provided in this application are equally applicable to similar technical problems as system architectures evolve and new business scenarios emerge.

[0031] It should be understood that the three-dimensional visualization rendering scheme for geospatial data provided in the embodiments of this application includes a three-dimensional visualization rendering method, apparatus, computing device, computer-readable storage medium, and computer program product for geospatial data. Since these technical solutions solve problems based on the same or similar principles, some repetitive details may not be repeated in the following descriptions of specific embodiments. However, it should be considered that these specific embodiments have mutual references and can be combined with each other.

[0032] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. In case of any inconsistency, the meaning set forth in this specification or derived from the content described herein shall prevail. Furthermore, the terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application. To accurately describe the technical content of this application and to accurately understand the invention, the following explanations or definitions of the terms used in this specification are provided before describing specific embodiments: 1) Geospatial data: Data describing the location, shape, distribution, attributes, and interrelationships of objects on the Earth's surface. In this application, geospatial data includes spatial information of buildings, which is represented by two-dimensional contour data (such as latitude and longitude coordinates) and attribute data. The attribute data includes height-related fields, such as height and floor. It is easy to understand that the attribute fields may also include other fields, such as building identifier (building_id) and building name (name).

[0033] 2) Tile: A small data block (i.e., a structured data unit) generated by slicing (i.e., dividing and organizing) large-scale continuous geospatial data according to spatial extent and level of detail (LOD). Each tile can be independently loaded, parsed, rendered and stitched together as needed.

[0034] In a 3D tile set, the data for each tile includes the 3D spatial coordinates of the buildings and floors belonging to that tile (such as the 3D spatial coordinates of the vertices of each floor) and the business information of each building or floor (related to rendering parameters). The front-end rendering engine can load the 3D tile set and use the 3D spatial coordinates and rendering parameters to render and realize the 3D visualization of each building and floor.

[0035] 2) CesiumLab: A data processing toolkit designed specifically for the Cesium 3D Earth engine. Its main function is to convert raw geospatial data in various formats into tile datasets that conform to the 3D Tiles specification and support streaming and Level of Detail (LOD).

[0036] 3) Octree Spatial Index Structure: A tree-like data structure for efficiently organizing and managing 3D spatial data. It constructs a hierarchy by recursively dividing a 3D spatial cube into eight sub-cubes, and is applied to the generation and scheduling of 3D tile data with multiple levels of detail (LOD).

[0037] 4) LOD (Levels of Detail): A core graphics rendering optimization technology. Its principle is to dynamically select models of different complexities (number of vertices, texture resolution) for rendering the same object based on the viewing distance or screen ratio, thereby significantly improving the rendering performance and interactive smoothness of large-scale 3D scenes with minimal impact on visual perception.

[0038] In this application, the LOD level is used to control the configuration parameters for slice generation and scheduling. The thresholds at both ends of the LOD level (or the start and end levels of LOD) can be denoted as minZoom / maxZoom (minimum / maximum scaling level). For example, minZoom (e.g., 10) represents the coarsest level, with a large coverage area and the greatest model simplification (e.g., a single tile covering an entire urban area); maxZoom (e.g., 16) represents the finest level, with a small coverage area and preservation of complete geometric details (e.g., floors within a single building).

[0039] 5) GeoJSON (JavaScript Object Notation for Geographic Data): A lightweight, open standard data format based on JSON for representing the geospatial features and non-spatial attributes of an object. A GeoJSON object includes two members: a geometry member, used to define the spatial shape and location of the feature; and a properties member, used to define non-spatial attribute information, such as business data (e.g., name, value, status), thereby enabling the integrated encoding, transmission, and parsing of the object's geospatial and business data within a single file.

[0040] 6) Shapefile (.shp, often abbreviated as SHP file): This is a vector data storage format widely used in Geographic Information Systems (GIS). A complete Shapefile actually consists of multiple files (the main file .shp stores the geometric figures, the index file .shx, the attribute table file .dbf, etc.). It can store geometric features such as points, lines, and polygons and their related attribute information, and is one of the standard exchange formats in the GIS field.

[0041] 7) WGS84 (World Geodetic System 1984): A globally used geographic coordinate system standard. It uses a rotating ellipsoid to define the shape and size of the Earth and uses longitude and latitude as coordinate values. In the fields of web maps and 3D earth visualization (such as Google Maps and Cesium), spatial data in other coordinate systems usually need to be converted to the WGS84 coordinate system before they can be loaded and used.

[0042] 8) Boundary coordinates: In the field of geographic information, these refer to the geographic coordinate boundary values ​​of a rectangular area in the four cardinal directions (north, south, east, and west). In 3D visualization, boundary coordinates are often used to define the field of view of the current map view or the area of ​​analysis of interest to the user.

[0043] 9) Tomcat (Apache Tomcat): An open-source, lightweight web application server and Servlet container. In this embodiment, Tomcat serves as a hosting and publishing platform for 3D tile data services and web applications. It stores and provides 3D Tiles files and front-end pages generated by CesiumLab via the HTTP protocol, enabling streaming access by browser clients.

[0044] 10) White-film rendering: This is a common term in the fields of 3D Geographic Information Systems (3D GIS) and digital city modeling, specifically referring to the simplified, textureless, monochrome (such as green, yellow, red, white, etc.) 3D model visualization of urban features such as buildings. Unless otherwise specified, rendering in this application refers to white-film rendering.

[0045] 11) Stretching and Rendering: In a narrow sense, stretching refers to the process of dynamically constructing a 3D model represented by spatial coordinates, while rendering refers to the process of visualizing the 3D model. In this application, the front-end rendering engine can stretch the object in the height direction based on the 2D contour data and height data of the object (e.g., a building or a floor) to construct the object represented by each 3D spatial coordinate, and then render it based on rendering parameters (such as color, texture, etc.) to achieve visualization of the 3D object; the front-end rendering engine can also obtain a set of 3D tiles from the back-end and use the parameters contained in the tiles (including the 3D spatial coordinate parameters and rendering parameters of each object) to directly render and achieve visualization of the 3D object.

[0046] 11) Front-end and back-end: Front-end refers to applications running on user devices, such as web browsers, web-based applications, or client software running on computers, mobile phones, or tablets. For simplicity, front-end can also be used broadly to refer to the user device and the applications running on it.

[0047] The backend refers to services deployed on network-side devices, such as those deployed on network-side servers (which can be called business servers), and can be used to respond to requests or calls from the frontend and process pre-defined business logic (such as slicing). For simplicity, it can also be used to refer to network-side devices and the services running on them.

[0048] This application provides a 3D visualization rendering scheme for geospatial data. It receives a rendering request, which instructs the visualization of business indicator data associated with buildings in a 3D scene. A preprocessing module is invoked to acquire raw geospatial data and the business indicator data, and the raw geospatial data is preprocessed to generate standardized data. The standardized data includes geometric information of at least one building, including 2D contour data and height data, and the business indicator data is associated with the corresponding building. Based on the current viewport's display field of view and Level of Detail (LOD) parameters, a data acquisition request is sent to the backend server. A 3D tile set generated and returned by the backend server based on the field of view, LOD parameters, and the standardized data is acquired. The frontend rendering engine loads the 3D tile set and, based on the association between the business indicator data and buildings, uses the business indicator data as the rendering basis to render the 3D model of the corresponding building. This achieves automated processing from data preprocessing to scene rendering through front-end and back-end collaborative interaction, thereby improving system efficiency. This solution is applicable to geospatial data visualization scenarios in various fields such as smart cities, communication networks, energy and power, and digital twins. The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0049] The first embodiment of this application provides a three-dimensional visualization rendering method for geospatial data, which will be described below in conjunction with... Figure 1 The implementation of each step of the method is described in detail, including steps S10-S40.

[0050] S10: Receive a rendering request, which is used to instruct the visualization of business indicator data associated with buildings in a three-dimensional scene.

[0051] In some embodiments, the rendering request is triggered by the user through the front-end interactive interface, which is used to specify the business dimension to be visualized (such as energy consumption, traffic flow, rent level, etc.) and the target area range, and the system starts the subsequent data preprocessing and 3D rendering process accordingly.

[0052] In some embodiments, users can select a target building entity through interactive operations (such as box selection or clicking) to trigger a rendering request.

[0053] S20: Call the preprocessing module to obtain the original geospatial data and the business indicator data, and preprocess the original geospatial data to generate standardized data; wherein, the standardized data contains the geometric information of at least one building, the geometric information includes two-dimensional contour data and height data, and the business indicator data establishes a correlation with the corresponding building.

[0054] In some embodiments, the raw geospatial data can be imported from external sources via a front-end interactive interface. These sources may include urban basic geographic information databases published by natural resources authorities, OpenStreetMap open-source map data, building outline data provided by commercial map service providers, spatial databases such as PostgreSQL / PostGIS and Oracle Spatial, or vector surface data generated by UAV aerial surveying. The formats include, but are not limited to, Shapefile, GeoJSON, KML, or PostGIS spatial tables, containing two-dimensional outline data of each building and associated attribute data. The attribute data includes height-related fields and can be combined with the two-dimensional outline data of each building.

[0055] In some embodiments, the preprocessing method includes at least one of the following: coordinate transformation, geometric cleaning, standard format conversion, attribute standardization, and data simplification. Coordinate transformation refers to converting the coordinates of geospatial data to a coordinate system consistent with the user's current view (such as WGS84); geometric cleaning includes repairing and cleaning geometric surfaces in the model data; standard format conversion refers to unifying the output format; attribute standardization refers to checking and standardizing the attributes of business data; and data simplification refers to simplifying complex model data.

[0056] In some embodiments, the building information further includes floor data, and the business indicator data corresponds to at least one floor of the building; The preprocessing module further preprocesses the business indicator data to generate mapping parameters for rendering, and incorporates the mapping parameters into the standardized data.

[0057] In some embodiments, the floor data has at least one of the following attributes: floor number, floor height, and floor elevation. The business data can be displayed and analyzed at the floor level.

[0058] In some embodiments, the standardized data generated after preprocessing is output in the GeoJSON standard data format. The GeoJSON object includes two members: a geometry member, which defines the spatial shape and location of features (floor features, building features); and a properties member, which defines non-spatial attribute information, such as business data (e.g., name, value, status).

[0059] In some embodiments, the front end stores the generated standardized data in a shared storage location and enables the back end server to access the shared storage location to obtain the standardized data for generating the three-dimensional tile set.

[0060] S30: Based on the current viewport's display field of view and Level of Detail (LOD) parameters, send a data retrieval request to the backend server.

[0061] In some embodiments, the display field of view is calculated in real time by the front-end rendering engine based on the camera viewpoint, while the LOD level parameter is dynamically determined based on the distance between the viewpoint and the target building, the screen pixel density, or the performance strategy set by the user. The system combines the two into a tile index request parameter, which is used to accurately indicate the spatial range and detail granularity of the three-dimensional tiles to be generated by the back-end.

[0062] In some embodiments, it also includes: After generating the standardized data, it is determined whether the number of buildings contained therein exceeds a preset threshold; If the preset threshold is not exceeded, the front-end rendering engine is directly invoked to generate a 3D model for each building based on the 2D contour data and corresponding height data in the standardized data. This model is then rendered according to the associated business indicator data to achieve a 3D visualization display of the relationship between the building and business applications. This allows for the visualization of business data such as communication signals and networks, resources and energy, security, population density, and economic performance.

[0063] In some embodiments, determining whether the number of buildings included in the standardized data exceeds a preset threshold includes: counting the number of buildings in the standardized data and comparing it with a preset threshold. The threshold can be dynamically adjusted based on the performance of the front-end hardware.

[0064] S40: Obtain the set of three-dimensional tiles generated and returned by the backend server based on the field of view, LOD level parameters and the standardized data.

[0065] In some embodiments, obtaining the 3D tile set of the backend server includes: Receive the access address of the tile service path returned by the backend server; Based on the access address, the three-dimensional tile set is obtained from the tile service path.

[0066] In some embodiments, the server generates a set of 3D tiles based on the field of view, LOD level parameters, and standardized data, including: The server acquires standardized data and, for each building, stretches it based on its two-dimensional outline data and corresponding height data to generate a three-dimensional model. The three-dimensional models of each building are sliced ​​according to the field of view and LOD level parameters to generate the three-dimensional tile set.

[0067] In some embodiments, the tiling process includes: dividing the geospatial data in three-dimensional space based on an octree spatial index structure to obtain multiple tiles and the spatial relationships between the multiple tiles; wherein, multiple tile versions with different precision levels are generated for the same spatial region.

[0068] In some embodiments, slicing can be performed by automated scripts (such as Python or Node.js-based tools) that drive slicing tools (such as CesiuimLab command-line tools, CLI) to generate tiles in batches without manual intervention.

[0069] In some embodiments, it also includes: When a change is detected in the displayed field of view and / or LOD level parameters, the target area that needs to be incrementally updated and the corresponding LOD level are determined based on the changed part, and this information is sent to the backend. Obtain the incremental 3D tile set generated by the backend based on the target region requiring incremental updates and its corresponding LOD level, as well as the standardized data; The incremental 3D tile set is loaded by the front-end rendering engine, and the 3D models of the buildings contained therein are rendered to update the 3D visualization of the buildings in the current view.

[0070] In some embodiments, rendered tiles are cached in the local storage of the front end. When the display field of view and / or LOD level parameters change, the local storage is first checked to see if the tiles that need to be rendered are already present. For the field of view and / or LOD level parameters of tiles that are not cached, they are determined to be the incremental 3D tile set that needs to be generated.

[0071] In some embodiments, incremental updates also respond to user modifications to the building's 3D model and / or business indicator data. These modifications may include changes to the geometric parameters of the model data (such as the coordinates and height of the building outline), and / or modifications to the business indicator data (such as signal strength), and / or changes to the rendering rules of the business data (such as adjusting the threshold of rendering parameters), and / or adding or removing data.

[0072] Through the aforementioned incremental update mechanism, the published model service and business data can avoid re-executing the entire process from data modification to service release, thus solving the problem of insufficient system flexibility and adaptability in existing technologies, which makes it difficult to meet the business needs of real-time analysis and rapid decision-making.

[0073] S50: Call the front-end rendering engine to load the three-dimensional tile set, and based on the relationship between the business indicator data and the building, use the business indicator data as the rendering basis to render the three-dimensional model of the corresponding building, so as to realize the three-dimensional visualization of each building and its associated business indicators.

[0074] In some embodiments, the process of calling the front-end rendering engine to load the 3D tile set and perform 3D model rendering includes: The floor data of each building in the three-dimensional tile set is analyzed, and each building is divided into multiple corresponding floor units; Based on the rendering parameters mapped to the business indicator data corresponding to each floor unit in the standardized data, each floor unit is rendered separately.

[0075] In some embodiments, the process of generating and rendering three-dimensional models of each building based on the two-dimensional contour data and corresponding height data in the standardized data includes: Based on the two-dimensional outline data, height data, and floor data of the building, extrusion modeling is performed floor by floor to generate a three-dimensional model of each floor. The 3D model of the corresponding floor is rendered based on the rendering parameters mapped from the business indicator data associated with each floor.

[0076] In some embodiments, Cesium open-source components (including tools such as Viewer, Cesium3DTileset, and Cesium3DTileStyle) can be used for 3D rendering (such as geometric stretching and shading). Alternatively, other 3D graphics engines or frameworks with WebGL rendering capabilities can be used as alternative implementations, such as Three.js, Mapbox GL JS, and other 3D rendering engines that support geometry generation with vector outlines and support loading and parsing streaming 3D tile formats such as 3D Tiles.

[0077] In some embodiments, rendering or incremental updates are performed, and the camera position is also controlled to jump to a specified relative observation position of the 3D model on the first floor.

[0078] In some embodiments, the above methods are also integrated into various analysis systems, such as spatial distribution and density analysis, regional indicator correlation analysis, emergency evacuation simulation, facility layout planning, and signal coverage simulation, to support visualization and decision support for different business scenarios.

[0079] The second embodiment of this application provides a three-dimensional visualization rendering method for geospatial data. The following will refer to... Figure 2a The flowchart shown and Figure 2b The system for implementing this method is shown, and this embodiment will be described as follows. Figure 2b As shown, the system in this embodiment consists of a geographic data preprocessing module, a 3D Tiles slicing module, a 3D visualization module, and a front-end and back-end interactive linkage module. The method provided in this second embodiment includes the following steps S200-S230.

[0080] S200: The front end responds to the user's rendering request by calling the preprocessing module to preprocess the raw geospatial data and business data to obtain standardized data.

[0081] First, the preprocessing module preprocesses the raw geospatial data (GIS data) to resolve inherent problems such as inconsistent projection coordinate systems, geographic geometric errors, missing attributes, data redundancy, chaotic data formats, and topological errors, thus preventing memory overflow during stretching. Second, the module preprocesses the business data to address the mismatch between business data and geospatial data.

[0082] The raw geospatial data used in this application embodiment includes building information, including two-dimensional outline data and height data. Depending on the data source, the building information may also include three-dimensional model data of the building / floor. The server (backend) sends a request to the browser client (frontend) to process the raw geospatial data.

[0083] The server-side Python script drives the following operations to automate the processing of raw geospatial data and business data: (1) Coordinate transformation: Check whether the coordinate system of the original geospatial data is consistent with the default coordinate system WGS84 (EPSG: 4326) of the current view of the client. If they are inconsistent, they need to be converted to the default coordinate system of the current view of the client.

[0084] (2) Geometric cleaning: If the two-dimensional building outline data has geometric surfaces, then repair the self-intersecting polygons of the model in the geospatial data and remove invalid geometric surfaces, such as scattered fragmented surfaces with an area of ​​less than 1 square meter.

[0085] (3) Attribute Standardization: Check whether the attribute data of the building model conforms to the specifications, whether there are any missing data, and whether there is a primary key relationship with the business data. Since this application embodiment adopts the method of rendering the data in building layers, this step needs to check whether the building elements or floor elements (flattened processing) of the building model have the attributes of floor number, actual floor height, and absolute floor height. These can be called floor data. Among them, the absolute floor height = ground reference elevation + floor number * single floor height.

[0086] If the original geospatial data includes building height or floor information, it can be directly used as floor data. If the original geospatial data is missing floor data, it can be estimated and set based on the number of floors attribute (which may be derived from business data) combined with preset floor height parameters, or the default value can be used to ensure that the floor data is complete.

[0087] (4) Data simplification: The control points / vertices of circular, irregular, and other building outlines (models) are simplified and thinned to reduce the number of control points / vertices as much as possible without affecting the building's outline, thereby reducing the performance consumption of subsequent processing. For example, if the building information also includes a 3D model, the number of vertices of a building with more than 1,000 vertices can be reduced by 20% to simplify the data.

[0088] (5) Format conversion: The building model and its attribute data and business data (indicator name, value, rendering threshold, corresponding color, etc.) are associated through the primary key id and output in geoJSON format.

[0089] (7) Output: Store the converted geoJSON file in the specified shared path for subsequent loading and processing. For large geoJSON files, they can be sliced ​​and stored.

[0090] The front-end stores the generated standardized data in geoJSON file format to a shared storage location, and enables the back-end server to access the shared storage location to obtain the standardized data for generating the 3D tile set.

[0091] S210: Determine the data size of the preprocessed standardized data, and select the appropriate rendering method according to the different scale modes.

[0092] This application embodiment automatically assesses the data scale by determining whether the geoJSON file requested by the client contains a large number of buildings. For example, the server presets 2000 buildings as a threshold and compares whether the number of buildings in the geoJSON file exceeds the threshold. If it does not exceed the threshold, the data file required for small-scale data rendering is configured through step S211; if it exceeds the threshold, the data file required for large-scale data rendering is configured through step S212.

[0093] like Figure 2cAs shown, the 5G signal strength of each floor in each building within the framed complex is displayed. After loading geoJSON, the 5G signal strength is rendered using green, yellow, and red colors (representing good, medium, and poor signal strength, respectively). When a user sees a red floor area, they can intuitively check that the signal on that floor is poor, requiring further investigation into the cause of the poor network performance, thus providing network optimization and response measures.

[0094] S211: Configure the data required for small-scale data rendering.

[0095] This application's embodiment uses the Cesium core rendering engine based on WebGL for rendering. It natively integrates the WGS84 coordinate system, supports multiple data sources, and ensures accurate positioning and seamless 2D / 3D rendering of global geospatial data.

[0096] When the data size is small, the client directly loads the server-side geoJSON file as the data source by calling the GeoJsonDataSource function of the Cesium API.

[0097] Based on the values ​​of the business data associated with the building / floor elements in the geoJSON file and the rendering rules set by the client user, determine and associate the rendering colors of the building / floor elements.

[0098] S212: Configure the data required for large-scale data rendering.

[0099] For large building complexes, the Cesium client cannot directly stretch the entire 2D outline, which can easily cause browser memory overflow. Therefore, an automated pre-slicing process is used on the server side. This process mainly relies on the CesiumLab CLI command-line script for automated execution.

[0100] like Figure 2d As shown, the client sends a full update request to the server, which then calls the CesiumLab CLI command-line tool to perform pre-tiling, configured using the Cesium tileset command. Specifically, the attribute field representing the geometric height of the building element itself is specified using the extrude-height parameter in the input GeoJSON file; its absolute elevation reference field is specified using the height parameter. The tool then extrudes each 2D contour into a 3D geometry based on this.

[0101] The tool automatically calculates the total 3D space occupied by all generated 3D geometry and uses this as the root node boundary of the octree spatial index. Simultaneously, the LOD level of the generated tiles is defined using the minzoom and maxzoom parameters (typically set to 10 and 16).

[0102] Based on the definitions of minzoom and maxzoom, CesiumLab automatically and recursively calculates and generates tiles of all intermediate levels within the aforementioned total spatial range, ultimately forming a tile set from low detail (level 10) to high detail (level 16), including tileset.json and .b3dm tile files. The tileset.json file describes the spatial relationships and LOD levels and is located in the root directory; the .b3dm files are the tile entity files, stored in folders according to an octree structure based on the tiling strategy and LOD level.

[0103] Once the CesiumLab tile command is executed, the entire tile directory, output_dir folder, will be stored directly in the Tomcat-deployed web server directory. The front-end code can then access the tileset.json file within it in real time.

[0104] S220: The client loads data and performs full rendering.

[0105] The client uses Cesium to drive the 3D rendering engine to perform rendering, and outputs the final image to the Canvas canvas for presentation to the user.

[0106] First, prepare the basic environment. This includes including Cesium's core JavaScript library and its accompanying Cascading Style Sheets (CSS) in the webpage.

[0107] Next, the Cesium framework code is initialized, including: creating a Cesium.Viewer instance to initialize the 3D globe scene view; configuring user interface components such as map controls and layer selectors; setting the initial position, orientation, and field of view of the scene camera to define the default viewing angle; binding a series of user interaction event listeners to the scene to implement operations such as map panning, zooming, and flight navigation; and enabling functions such as viewing and selecting the attributes of entity elements (such as buildings and floors) in the scene; simultaneously, loading or initializing rendering rule configuration data used to map business data to visual colors.

[0108] For small-scale data rendering, the Cesium rendering engine takes the height attribute of the building / floor features contained in the geoJSON file as input and calls the entity.polygon.extrudedHeight operation API to stretch the outline of the building / floor features to form building / floor entities.

[0109] It takes the rendering color of the associated building / floor elements as input and calls the entity.polygon.material API to assign different rendering colors to the entities.

[0110] For large-scale data rendering, the Cesium.Cesium3DTileset object is used to load and parse the tile entity file via a URL relative path. Next, business data is associated through the entity property of the Cesium entity object. Finally, the rendering color of each floor is set through the color property of the Cesium3DTileStyle object and the floor number property inherent in the building model. The tileset.reloadTiles interface is called for WebGL rendering, and then loadLevels is used to initialize the LOD level, and flyTo is used to jump the camera's view to the specified position.

[0111] The client automatically caches the tiles of the currently displayed result locally.

[0112] S230: Users interact with geospatial data through the client, and the system determines whether to perform a full / incremental update rendering based on the content modified by the interaction.

[0113] When users view and modify geospatial data, they can interact through the client to achieve dynamic scheduling and real-time rendering.

[0114] When a user performs view operations such as dragging, zooming, and panning the map, or modifies model geometry data (such as building height), business data, or rendering rules, the client determines whether to send a full / incremental update rendering request to the server based on different situations.

[0115] When modifying model geometry or business data, small-scale data requires a full update and rendering, while large-scale data requires an incremental update and rendering of the affected tile data. For example, if building A is changed from 2 floors to 10 floors, the modification is sent to the server. The server updates the corresponding tile files based on the building entity's primary key ID and then returns the changes to the client.

[0116] When a user performs a view operation, if the requested view area is one that has been previously accessed and is cached on the client, the cached data is directly called. If the client does not have or does not have some of the tiles in the current view, the system automatically calculates the boundary coordinates, tilt angle, LOD level, and other parameters of the current view and sends a request to the server to perform a full / incremental update rendering.

[0117] When importing raw geospatial data by selecting buildings in batches using map selection tools, sometimes a situation arises where, after the user moves the current viewpoint, a request is needed for geospatial data that has not been tiled or imported to the server. In this case, in response to the user's request, the geospatial data for that portion is tiled.

[0118] like Figure 2e As shown, when the field of view of the Cesium Camera changes, resulting in large-scale unprocessed geospatial data appearing in the field of view, it is determined that tiling is required. A request for tile files (3DTiles) of the current field of view range is sent to the (tiling) server. After receiving the request, the server reads the preprocessed geoJSON file, generates the tile file of the corresponding range according to the method in step S212, and returns it to the front end (client).

[0119] The third embodiment of this application provides a three-dimensional visualization rendering device for geospatial data. This device can be used to implement the three-dimensional visualization rendering method for geospatial data in the above embodiments and is deployed on a front end, such as... Figure 3 As shown, it includes: The request receiving module is used to receive a rendering request, which is used to instruct the visualization of business indicator data associated with buildings in a three-dimensional scene; specifically, the request receiving module can be used to implement step S10 in the first embodiment and its optional embodiments.

[0120] The preprocessing invocation module is used to invoke the preprocessing module to obtain the original geospatial data and the business indicator data, and to preprocess the original geospatial data to generate standardized data; wherein, the standardized data includes the geometric information of at least one building, the geometric information includes two-dimensional contour data and height data, and the business indicator data is associated with the corresponding building; specifically, the preprocessing invocation module can be used to implement step S20 in the first embodiment and its optional embodiments.

[0121] The request sending module is used to send a data acquisition request to the backend server based on the display field of view and the level of detail (LOD) parameters of the current viewport; specifically, the request sending module can be used to implement step S30 in the first embodiment and its optional embodiments.

[0122] The tile acquisition module is used to acquire the three-dimensional tile set generated and returned by the backend server based on the field of view, LOD level parameters and the standardized data; specifically, the tile acquisition module can be used to implement step S40 in the first embodiment and its optional embodiments.

[0123] The rendering execution module is used to call the front-end rendering engine to load the 3D tile set, and based on the association between the business indicator data and the buildings, use the business indicator data as the rendering basis to render the 3D model of the corresponding building, so as to realize the 3D visualization of each building and its associated business indicators. Specifically, this rendering execution module can be used to implement step S50 in the first embodiment and its optional embodiments.

[0124] The fourth embodiment of this application provides a three-dimensional visualization rendering system for geospatial data. This system can be used to implement the three-dimensional visualization rendering method for geospatial data in the above embodiments, such as... Figure 2b As shown, the 3D visualization rendering system for this geospatial data includes: The geographic data preprocessing module is used to acquire raw geospatial data and perform preprocessing, including at least one of the following: coordinate transformation, geometric cleaning, attribute standardization, data simplification, and format conversion.

[0125] The 3D Tiles slicing module is used to read GeoJson data on demand and call the CesiumLabCLI command line to perform slicing processing to obtain a 3D tile set; it then matches and stores each tile file in the 3D tile set with its corresponding business data.

[0126] The 3D visualization module is used to directly perform 3D stretching on small-scale data with no more than a preset threshold of buildings; to render 3D models on large-scale data with more than a preset threshold of buildings by loading tile files; and to render the above 3D models according to business data.

[0127] The front-end and back-end interaction module is used by the front-end to send a request for tile files to the back-end as needed; the back-end calls the 3D Tiles slicing module to perform slicing processing as needed; and then transmits the tile files to the front-end for updating rendering.

[0128] Figure 4 This is a schematic structural diagram of a computing device 900 provided in an embodiment of this application. This computing device can execute various optional embodiments of the methods described above. The computing device can be a terminal, or a chip or chip system within the terminal. Figure 4 As shown, the computing device 900 includes: a processor 910, a memory 920, and a communication interface 930.

[0129] It should be understood that Figure 4 The communication interface 930 in the computing device 900 shown can be used to communicate with other devices, and may specifically include one or more transceiver circuits or interface circuits.

[0130] The processor 910 can be connected to the memory 920. The memory 920 can be used to store the program code and data. Therefore, the memory 920 can be a storage unit inside the processor 910, an external storage unit independent of the processor 910, or a component that includes both the storage unit inside the processor 910 and the external storage unit independent of the processor 910.

[0131] Optionally, the computing device 900 may also include a bus. The memory 920 and communication interface 930 can be connected to the processor 910 via the bus. The bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 The symbol is represented by a line without an arrow, but this does not mean that there is only one bus or one type of bus.

[0132] It should be understood that in the embodiments of this application, the processor 910 may be a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor. Alternatively, the processor 910 may employ one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0133] The memory 920 may include read-only memory and random access memory, and provides instructions and data to the processor 910. A portion of the processor 910 may also include non-volatile random access memory. For example, the processor 910 may also store device type information.

[0134] When the computing device 900 is running, the processor 910 executes computer execution instructions stored in the memory 920 to perform any of the operational steps of the above method and any of the optional embodiments thereof.

[0135] It should be understood that the computing device 900 according to the embodiments of this application can correspond to the corresponding subject in executing the methods according to the various embodiments of this application, and the above and other operations and / or functions of each module in the computing device 900 are respectively for implementing the corresponding processes of the methods of this embodiment. For the sake of brevity, they will not be described in detail here.

[0136] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0137] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0138] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0139] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0140] In addition, the functional units in the various embodiments of this application 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.

[0141] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0142] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, is used to perform the above-described method, which includes at least one of the schemes described in the above embodiments.

[0143] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0144] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0145] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including, but not limited to, wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0146] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0147] Furthermore, the terms "first, second, third, etc." or similar terms such as module A, module B, and module C used in the specification and claims are only used to distinguish similar objects and do not represent a specific ordering of objects. It is understood that, where permissible, a specific order or sequence may be interchanged so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0148] In the above description, the labels of the steps involved, such as S110, S120, etc., do not mean that the steps will necessarily be executed. The order of the steps can be interchanged or executed simultaneously if permitted.

[0149] The term "comprising" as used in the specification and claims should not be construed as limiting itself to what follows; it does not exclude other elements or steps. Therefore, it should be interpreted as specifying the presence of the mentioned feature, integral, step, or component, but does not exclude the presence or addition of one or more other features, integrals, steps, or components, or groups thereof. Thus, the statement "device comprising means A and B" should not be limited to a device consisting solely of components A and B.

[0150] The terms "an embodiment" or "an embodiment" as used in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in at least one embodiment of this application. Therefore, the terms "in one embodiment" or "in an embodiment" appearing throughout this specification do not necessarily refer to the same embodiment, but may refer to the same embodiment. Furthermore, in one or more embodiments, the particular features, structures, or characteristics can be combined in any suitable manner, as will be apparent to those skilled in the art from this disclosure.

[0151] Note that the above are merely preferred embodiments and the technical principles employed in this application. Those skilled in the art will understand that this application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of this application, all of which fall within the scope of protection of this application.

Claims

1. A method for three-dimensional visualization rendering of geospatial data, characterized in that, Applied to front-end, including: Receive a rendering request, which is used to instruct the visualization of business indicator data associated with buildings in a three-dimensional scene; The preprocessing module is invoked to obtain the original geospatial data and the business indicator data, and the original geospatial data is preprocessed to generate standardized data; wherein, the standardized data contains the geometric information of at least one building, the geometric information includes two-dimensional contour data and height data, and the business indicator data is associated with the corresponding building; Based on the current viewport's display field of view and Level of Detail (LOD) parameters, a data retrieval request is sent to the backend server. Obtain the set of 3D tiles generated and returned by the backend server based on the field of view, LOD level parameters, and the standardized data; The front-end rendering engine is invoked to load the set of three-dimensional tiles. Based on the relationship between the business indicator data and the buildings, the business indicator data is used as the rendering basis to render the three-dimensional model of the corresponding building, so as to realize the three-dimensional visualization of each building and its associated business indicators.

2. The method according to claim 1, characterized in that, Also includes: After generating the standardized data, it is determined whether the number of buildings contained therein exceeds a preset threshold; If the preset threshold is not exceeded, the front-end rendering engine is directly invoked to generate a three-dimensional model for each building based on the two-dimensional contour data and corresponding height data in the standardized data, and then rendered according to the business indicator data associated with it, so as to realize the three-dimensional visualization display of the building and business application.

3. The method according to claim 2, characterized in that, The building information also includes floor data, and the business indicator data corresponds to at least one floor of the building; The preprocessing module further preprocesses the business indicator data to generate mapping parameters for rendering, and incorporates the mapping parameters into the standardized data.

4. The method according to claim 3, characterized in that, The process of calling the front-end rendering engine to load the 3D tile set and perform 3D model rendering includes: The floor data of each building in the three-dimensional tile set is analyzed, and each building is divided into multiple corresponding floor units; Based on the rendering parameters mapped to the business indicator data corresponding to each floor unit in the standardized data, each floor unit is rendered separately.

5. The method according to claim 3, characterized in that, The process of generating and rendering three-dimensional models of each building based on the two-dimensional contour data and corresponding height data in the standardized data includes: Based on the two-dimensional outline data, height data, and floor data of the building, extrusion modeling is performed floor by floor to generate a three-dimensional model of each floor. The 3D model of the corresponding floor is rendered based on the rendering parameters mapped from the business indicator data associated with each floor.

6. The method according to claim 1, characterized in that, The front end stores the generated standardized data in a shared storage location, and enables the back end server to access the shared storage location to obtain the standardized data for generating the three-dimensional tile set.

7. The method according to claim 1, characterized in that, The step of obtaining the 3D tile set of the backend server includes: Receive the access address of the tile service path returned by the backend server; Based on the access address, the three-dimensional tile set is obtained from the tile service path.

8. The method according to claim 1, characterized in that, Also includes: When a change is detected in the displayed field of view and / or LOD level parameters, the target area that needs to be incrementally updated and the corresponding LOD level are determined based on the changed part, and this information is sent to the backend. Obtain the incremental 3D tile set generated by the backend based on the target region requiring incremental updates and its corresponding LOD level, as well as the standardized data; The incremental 3D tile set is loaded by the front-end rendering engine, and the 3D models of the buildings contained therein are rendered to update the 3D visualization of the buildings in the current view.

9. A three-dimensional visualization rendering device for geospatial data, characterized in that, Deployed on the front end, including: A request receiving module is used to receive a rendering request, which is used to instruct the visualization of business indicator data associated with buildings in a three-dimensional scene. The preprocessing call module is used to call the preprocessing module to obtain the original geospatial data and the business indicator data, and to preprocess the original geospatial data to generate standardized data; wherein, the standardized data contains the geometric information of at least one building, the geometric information includes two-dimensional contour data and height data, and the business indicator data is associated with the corresponding building; The request sending module is used to send data retrieval requests to the backend server based on the display field of view and the level of detail (LOD) parameters of the current viewport. The tile acquisition module is used to acquire the set of three-dimensional tiles generated and returned by the backend server based on the field of view, LOD level parameters and the standardized data; The rendering execution module is used to call the front-end rendering engine to load the three-dimensional tile set, and based on the relationship between the business indicator data and the buildings, use the business indicator data as the rendering basis to render the three-dimensional model of the corresponding building, so as to realize the three-dimensional visualization of each building and its associated business indicators.

10. A computing device, characterized in that, include: processor, and A memory having stored program instructions that, when executed by the processor, cause the processor to perform the three-dimensional visualization rendering method for geospatial data as described in any one of claims 1 to 8.

Images