Visual display method, device, computer equipment and medium for massive data

Abstract

The present disclosure provides a method, device, computer equipment and medium for visual display of massive data, including: obtaining first entity data, the first entity data is used to describe the massive data corresponding to different entities in a real environment; converting the data format of the first entity data based on an open source database and a project object model to obtain second entity data, the data format of the second entity data is a JSON format; performing multi-level detail processing on the second entity data to obtain a pyramid structure map, the pyramid structure map includes multiple structural layers, and different structural layers respectively include the number of display faces and display detail of different entities; the pyramid structure map performs instantiation batch rendering to obtain a rendering result, so as to display the spatiotemporal changes of the massive data corresponding to different entities based on the rendering result. Thereby, it is convenient to perform visual display of massive data, and at the same time, the display authenticity of the entity situation is improved by displaying the spatiotemporal changes of massive data.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer processing technology, and in particular, to a visualization display method, apparatus, computer equipment, and medium applicable to massive data. Background Art

[0002] With the rapid development of computer technology, the cost of collecting massive amounts of physical data is gradually decreasing, but the resulting change is that the amount of data is also increasing, and the richness of the massive information that a system can display is becoming more and more important.

[0003] In the related art, data display is mainly achieved through data graphs or data lists, such as drawing a data change curve chart with the aggregated data, or listing the aggregated data based on the data size relationship / time relationship and displaying it in a table.

[0004] However, using the above implementation method, it is difficult to effectively display the massive amount of data. Summary of the invention

[0005] The embodiments described herein provide a method, apparatus, computer device, and medium for visualizing and displaying massive amounts of data, which overcome the above-mentioned problems.

[0006] In a first aspect, according to the present disclosure, a method for visualizing and displaying massive data is provided, comprising:

[0007] Acquire first entity data, where the first entity data is used to describe a large amount of data corresponding to different entities in a real environment, and the large amount of data is used to describe entity attribute information and entity evolution information;

[0008] Performing data format conversion on the first entity data based on an open source database and a project object model to obtain second entity data, wherein the data format of the second entity data is a JSON format;

[0009] Performing multi-level detail processing on the second entity data to obtain a pyramid structure map, wherein the pyramid structure map includes multiple structure layers, and different structure layers respectively include the number of display faces and display detail degrees of different entities, and the number of display faces and display detail degrees of different entities are determined based on the location and importance of the corresponding entity in the real environment;

[0010] Performing instantiation batch rendering on the pyramid structure map to obtain rendering results, so as to display the spatiotemporal changes of the massive data corresponding to different entities based on the rendering results;

[0011] Among them, the instantiation batch rendering includes: entity rendering, component rendering and texture rendering, the entity rendering is used to batch render the entity attribute information, the component rendering is used to additionally render the entity key information, the entity key information includes the timeline and / or hot events, and the texture rendering is used to perform flow simulation rendering of the entity evolution information.

[0012] In a second aspect, according to the content of the present disclosure, a visualization display device for massive data is provided, comprising:

[0013] An acquisition module, used to acquire first entity data, where the first entity data is used to describe a large amount of data corresponding to different entities in a real environment, where the large amount of data is used to describe entity attribute information and entity evolution information;

[0014] A conversion module, configured to convert the data format of the first entity data based on an open source database and a project object model to obtain second entity data, wherein the data format of the second entity data is a JSON format;

[0015] A processing module is used to perform multi-level detail processing on the second entity data to obtain a pyramid structure map, wherein the pyramid structure map includes multiple structure layers, and different structure layers respectively include the number of display faces and display detail degrees of different entities, and the number of display faces and display detail degrees of different entities are determined based on the location and importance of the corresponding entity in the real environment;

[0016] A rendering module, used for instantiating batch rendering of the pyramid structure map to obtain rendering results, so as to display the spatiotemporal changes of the massive data corresponding to different entities based on the rendering results;

[0017] Among them, the instantiation batch rendering includes: entity rendering, component rendering and texture rendering, the entity rendering is used to batch render the entity attribute information, the component rendering is used to additionally render the entity key information, the entity key information includes the timeline and / or hot events, and the texture rendering is used to perform flow simulation rendering of the entity evolution information.

[0018] In a third aspect, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps of the method for visualizing display of massive data in any of the above embodiments are implemented.

[0019] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method for visualizing display of massive data in any of the above embodiments are implemented.

[0020] The visualization display method of massive data provided by the embodiment of the present application obtains first entity data, the first entity data is used to describe the massive data corresponding to different entities in the real environment, and the massive data is used to describe entity attribute information and entity evolution information; based on the open source database and the project object model, the data format of the first entity data is converted to obtain second entity data, and the data format of the second entity data is JSON format; the second entity data is processed at multiple levels of detail to obtain a pyramid structure map, the pyramid structure map includes multiple structural layers, and different structural layers respectively include the number of display surfaces and display details of different entities, and the number of display surfaces and display details of different entities are determined based on the location and importance of the corresponding entity in the real environment; the pyramid structure map is instantiated and batch rendered to obtain a rendering result, so as to display the spatiotemporal changes of the massive data corresponding to different entities based on the rendering result; wherein the instantiated batch rendering includes: entity rendering, component rendering and texture rendering, the entity rendering is used to batch render the entity attribute information, the component rendering is used to additionally render the entity key information, the entity key information includes the timeline and / or hot events, and the texture rendering is used to perform flow simulation rendering on the entity evolution information. In this way, by unifying the data format of massive data, the complexity of data operations is reduced, and the entity data with a unified format is processed at multiple levels of detail and divided into different structural layers for rendering, the rendering results of the entity data are effectively obtained, which facilitates the visualization of massive data. At the same time, the display authenticity of the entity situation is improved by displaying the temporal and spatial changes of massive data.

[0021] The above description is only an overview of the technical solution of the embodiment of the present application. In order to more clearly understand the technical means of the embodiment of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments will be briefly described below. It should be noted that the drawings described below only relate to some embodiments of the present disclosure, but are not intended to limit the present disclosure, wherein:

[0023] Figure 1 It is a flow chart of a method for visualizing display of massive data provided by the present disclosure.

[0024] Figure 2 It is a structural schematic diagram of a visualization display system for massive data provided by the present disclosure.

[0025] Figure 3 It is a structural schematic diagram of a visualization display device for massive data provided by the present disclosure.

[0026] Figure 4 It is a structural schematic diagram of a computer device provided by the present disclosure.

[0027] It should be noted that the elements in the drawings are schematic and not drawn to scale. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution of the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all of the embodiments. Based on the described embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative work also fall within the scope of protection of the present disclosure.

[0029] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by a person skilled in the art to which the subject matter of the present disclosure belongs. It will be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the specification and the relevant art, and will not be interpreted in an idealized or overly formal form unless otherwise explicitly defined herein. As used herein, a statement that two or more parts are "connected" or "coupled" together shall mean that the parts are joined together directly or through one or more intermediate components.

[0030] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase "embodiments" in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0031] The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists, A and B exist at the same time, and B exists. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship. Terms such as "first" and "second" are only used to distinguish one component (or a part of a component) from another component (or another part of a component).

[0032] In the description of the present application, unless otherwise specified, "plurality" means more than two (including two), and similarly, "multiple groups" means more than two groups (including two).

[0033] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0034] Figure 1 FIG. 1 is a flow chart of a method for visualizing display of massive data provided by an embodiment of the present disclosure. Figure 1 As shown in FIG. 1 , the specific process of the visualization display method of massive data includes:

[0035] S110: Acquire first entity data.

[0036] The first entity data may be used to describe the massive data corresponding to different entities in the real environment, and the massive data is used to describe entity attribute information and entity evolution information.

[0037] Entities in the real environment may include but are not limited to: fixed plants, mobile organisms, mobile devices, etc. Fixed plants may include grass, trees, etc., mobile organisms may include animals, microorganisms, etc., and mobile devices may include airplanes, tanks, drones, etc.

[0038] The entity attribute information may be the entity's size, color, name, location, etc. The entity evolution information may be the entity's historical development information, such as the development process and version updates in different periods.

[0039] S120: Convert the data format of the first entity data based on the open source database and the project object model to obtain second entity data.

[0040] The data format of the second entity data is JSON format.

[0041] The open source database may be a MySqL database, the project object model may be Maven, and the data format of the first entity data is converted into a JSON format through the MySqL database and the Maven background management.

[0042] Before converting the data format of the first entity data based on the open source database and the project object model to obtain the second entity data, the data format of the first entity data may be identified first, and the first entity data may be divided into JSON format data and non-JSON format data based on the data format of the first entity data.

[0043] Performing data format conversion on the first entity data based on the open source database and the project object model to obtain the second entity data may include: performing data format conversion on non-JSON format data obtained by dividing the first entity data based on the open source database and the project object model to obtain the second entity data, so as to save data conversion resources while improving data conversion efficiency.

[0044] S130: Perform multi-level detail processing on the second entity data to obtain a pyramid structure map.

[0045] Among them, the pyramid structure map includes multiple structural layers, and different structural layers include the number of display surfaces and display details of different entities. The number of display surfaces and display details of different entities are determined based on the location and importance of the corresponding entities in the real environment.

[0046] For example, the open source JavaScript library Cesium can be used to overlay LOD (Levels of Detail) to load a pyramid structure map. LOD technology determines the resource allocation for entity rendering based on the location and importance of the nodes of the entity model in the real environment, reduces the number of display surfaces and display details of non-important entities, and thus obtains efficient rendering operations.

[0047] In some embodiments, multi-level detail processing is performed on the second entity data to obtain a pyramid structure map, including:

[0048] The positions of different entities in the real environment and the types of different entities in the real environment are obtained; based on the positions of different entities in the real environment and the types of different entities in the real environment, the importance of different entities in the real environment is determined; based on the positions of different entities in the real environment and the importance of different entities in the real environment, the structural layers to which different entities belong in the initial tower structure are determined, and the initial tower structure is a pyramid structure; the number of display faces and the degree of display details of entities in different structural layers of the initial tower structure are adjusted to obtain a pyramid structure map, and different structural layers in the pyramid structure map have different rendering resources.

[0049] The types of different entities in the real environment may include: animals, plants, microorganisms, electronic devices, etc.

[0050] Determining the importance of different entities in the real environment based on the locations of different entities in the real environment and the types of different entities in the real environment may include: determining the importance of different entities in the real environment based on the locations of different entities in the real environment, the types of different entities in the real environment and the number of different entities living in local areas / global areas in the real environment.

[0051] For example, the more concentrated the location of an entity in the real environment, the higher the level of the type of an entity in the real environment, and the more the number of entities in the local area / global area of ​​the real environment, the higher the importance of the entity in the real environment. The level of the type of the entity in the real environment can be customized, such as defining the level of importance of animals, plants, microorganisms, and electronic devices in the real environment to gradually decrease.

[0052] The higher the structural layers in the initial tower structure, the more rendering resources are required.

[0053] Adjusting the number of display faces and display details of entities in different structural layers in the initial tower structure to obtain a pyramid structure map may include: adjusting the number of display faces and display details of entities in this structural layer based on the level accuracy corresponding to different structural layers.

[0054] For example, the level precision corresponding to different structural layers can match the corresponding pre-display surface number and pre-display detail level. Based on the level precision corresponding to different structural layers, the number of display surfaces and display detail level of the entity in this structural layer are adjusted.

[0055] Therefore, by obtaining the positions of different entities in the real environment and the types of different entities in the real environment, the importance of different entities in the real environment is determined, so as to determine the structural layers to which different entities belong in the initial tower structure, and adjust the number of display surfaces and display details of entities in different structural layers in the initial tower structure to obtain a pyramid structure map, which is convenient for effective division of rendering resources for different entities.

[0056] S140, instantiating and batch rendering the pyramid structure map to obtain rendering results.

[0057] The pyramid structure map is instantiated and batch rendered to obtain rendering results, so as to display the spatiotemporal changes of the massive data corresponding to different entities based on the rendering results.

[0058] Instantiated batch rendering includes: entity rendering, component rendering and texture rendering. Entity rendering is used for batch rendering of entity attribute information. Component rendering is used for additional rendering of entity key information. Entity key information includes timeline and / or hot events. Texture rendering is used for flow simulation rendering of entity evolution information.

[0059] Component rendering can be achieved by adding components such as timeline and hot event display on the basis of Vue2.0 framework, and combining information such as entity structure, entity relationship, trend development, etc. to propose radical, conservative, compromise and other execution plans, so as to present the spatiotemporal changes of the environmental situation constituted by the entity to the user.

[0060] In some embodiments, instantiated batch rendering is performed on the pyramid structure map to obtain rendering results, including:

[0061] The rendering resources corresponding to each structural layer are used respectively, and the entity attribute information corresponding to the entities is batch rendered based on the number of display surfaces and display details of the entities included in each structural layer; based on the key information corresponding to different entities, additional rendering of timelines and / or hot events is performed for different entities; the entity evolution information corresponding to different entities is used to simulate the flow characteristics of different entities to obtain rendering results.

[0062] Among them, when simulating the flow characteristics of different entities, the flow texture (Material) in the programmable graphics rendering pipeline (shder) can be used on the basis of WebGL application simulation to simulate the changes in environmental trade relations. The principle is essentially a texture that records 2D vector information.

[0063] The color on the FlowMap (usually the RG channel) records the direction of the vector field at that location, allowing a certain part of the model to show quantitative flow characteristics. The flow effect is simulated by offsetting the UV in the shader and then sampling the texture.

[0064] You only need to specify the three properties of type, uniforms, and components to build a Fabric JSON. The system will use the agreed vertex shader and fragment shader codes according to the process of Material->Appearance->Renderer to vividly display the dynamic changes of data.

[0065] In some embodiments, the rendering resources corresponding to each structural layer are respectively used to batch render the entity attribute information corresponding to the entities based on the number of display surfaces and display detail of the entities included in each structural layer, including:

[0066] In different structural layers, the entity objects that need to be rendered and the multiple attribute parameters corresponding to the entity objects are determined, and each attribute parameter corresponds to a rendering number; the entity objects that need to be rendered and the multiple attribute parameters corresponding to the entity objects are sent to the GPU cache, so that the GPU cache uses the rendering resources corresponding to the different structural layers to batch render the entity attribute information corresponding to the entities based on the entity objects in different structural layers, the multiple attribute parameters corresponding to the entity objects, the number of display surfaces of the entities included in the different structural layers, and the display detail level.

[0067] Among them, based on the rendering sequence number corresponding to each attribute parameter, the attribute parameters of the entity objects in different structural layers, the number of display surfaces of the entities included in different structural layers, and the display detail level can be batch rendered to correspond to the entity attribute information of the entity.

[0068] A Primitive is constructed based on each batch queue (determined by the rendering sequence number), including all GeometryInstances in the queue. Due to the powerful parallel capability of the graphics card, the time required to draw one triangle is the same as the time required to draw N triangles (N depends on the number of vertices). Therefore, encapsulating multiple Geometries into one VBO as much as possible is a key idea to improve rendering performance (batching & instantiation). Instancing avoids the scheduling of memory and video memory between the same attributes, and optimizes the scheduling of different attributes, thereby improving rendering efficiency.

[0069] For example, for grass, trees, or a large number of aircraft and tanks, these often have a large amount of data, but at the same time there are only slight differences such as position, rotation, color, etc. If they are rendered like regular objects, the drawing instructions used must be many, and the resource usage will be large. First, the number of times the CPU submits data to the GPU (including setting data buffers, rendering status, and calling the drawing of rendering primitives, i.e. drawcall), and second, the drawing on the GPU (including vertex processing and pixel drawing). As the number of scene objects increases, the pressure on the CPU and GPU will increase.

[0070] In this embodiment, an object (entity) to be drawn is specified, as well as a plurality of different parameters, and then drawn in a drawing call according to the parameters, which is so-called instantiation.

[0071] When rendering, the CPU can assemble their different attributes (position, size, rotation, color, etc.) and other Instancing material information into a Buffer (array) and pass it to a cache area of ​​the GPU. When the GPU renders these objects, there will be a global array index, which will be incremented after each object is rendered, so that each object can get its own position, color and other information based on this id. When rendering these objects, only one DrawCall is needed to pass the array to the GPU cache, and a large number of objects can be rendered.

[0072] At present, there are a lot of real-time data of all kinds. Data is certainly valuable, but the essence of application is not to obtain data, but to filter data, which is a processing of data, and to grasp the valuable parts of data in terms of breadth and depth. In the era of massive data, there are many channels for obtaining data, but the key lies in the ability to filter data and display data, and to generate value through data processing. In addition to the authority of data, the visualization of statistical analysis of data can further improve everyone's recognition of the authenticity of data. Based on the comprehensiveness of content depth and breadth, through the quantitative change of cold numbers in the background to the qualitative change of personalized expressions in the front end, it assists decision-making and analysis of future development trends.

[0073] In this embodiment, first entity data is obtained, and the first entity data is used to describe the massive data corresponding to different entities in the real environment, and the massive data is used to describe entity attribute information and entity evolution information; the first entity data is converted into a data format based on an open source database and a project object model to obtain second entity data, and the data format of the second entity data is a JSON format; the second entity data is processed at multiple levels of detail to obtain a pyramid structure map, and the pyramid structure map includes multiple structural layers, and different structural layers respectively include the number of display surfaces and display detail degrees of different entities, and the number of display surfaces and display detail degrees of different entities are determined based on the location and importance of the corresponding entity in the real environment; the pyramid structure map is instantiated and batch rendered to obtain a rendering result, so as to display the spatiotemporal changes of the massive data corresponding to different entities based on the rendering result; wherein the instantiated batch rendering includes: entity rendering, component rendering and texture rendering, the entity rendering is used to batch render the entity attribute information, the component rendering is used to perform additional rendering on the entity key information, and the entity key information includes the timeline and / or hot events, and the texture rendering is used to perform flow simulation rendering on the entity evolution information. In this way, by unifying the data format of massive data, the complexity of data operations is reduced, and the entity data with a unified format is processed at multiple levels of detail and divided into different structural layers for rendering, the rendering results of the entity data are effectively obtained, which facilitates the visualization of massive data. At the same time, the display authenticity of the entity situation is improved by displaying the temporal and spatial changes of massive data.

[0074] Based on the description of the above embodiment, the method of this embodiment may further include:

[0075] Obtain associated entities, historical development data, and predicted development data corresponding to different entities; perform entity development analysis on rendering results based on the associated entities, historical development data, and predicted development data corresponding to different entities.

[0076] The associated entity may be an entity with which an entity exchanges information / data. For example, when the entity is an enterprise, its associated entity may be a cooperating enterprise with which the entity has conducted project cooperation.

[0077] The predicted development data refers to the future development data corresponding to this entity, which can be used to show the future development trend of this entity.

[0078] Therefore, through the associated entities, historical development data and predicted development data corresponding to different entities, the rendering results are analyzed for entity development in combination with historical data and future data, thereby improving the effectiveness of entity development analysis.

[0079] The method of this embodiment may also include:

[0080] In response to a result viewing request sent by a target client, a rendering result and an entity development analysis result corresponding to the rendering result are sent to the target client.

[0081] Alternatively, other clients that obtain data associated with the first entity perform instantiated batch rendering on the pyramid structure map, and after obtaining the rendering results, send the rendering results to other clients; after performing entity development analysis on the rendering results based on the associated entities, historical development data, and predicted development data corresponding to different entities, send the entity development analysis results corresponding to the rendering results to other clients.

[0082] Among them, the system itself uses B / S architecture. In order to be widely used in the situation display field, compatible with C / S architecture, and embedded in more business systems, the system adopts a data proxy method based on the WebSocket protocol to open up the data association interface between the situation module and the existing business system, and realize real-time (or quasi-real-time) two-way interaction between the situation display module and the business system data.

[0083] Therefore, it can support the server to push functions directly to the client without waiting for the client's request, and increase the access of emergency events in data display. It can also display the flexible access of modules and realize comprehensive integration with various business systems.

[0084] In some embodiments, if it is detected that new entity data is generated under the time axis corresponding to different entities, event analysis is performed on the new entity data to obtain event analysis results; based on the event analysis results, the entity development analysis results corresponding to the rendering results are updated.

[0085] See also Figure 2 As shown, when a new situation is detected under the timeline, event analysis is continued for the new situation, and the event analysis may include: expert discussion, event sorting, and situation processing. The entity development analysis results may be radical solutions, conservative solutions, or compromise solutions. Thus, the entity development analysis results are effectively updated in real time according to the timeline detection results.

[0086] like Figure 2 As shown, this embodiment converts the relevant data into Json format by combining the open source MySqL database and Maven background management, and uses the open source JavaScript library Cesium to overlay the pyramid structure map loaded by LOD (to determine whether the current level meets the accuracy requirements. If not, it is necessary to continue to request the algorithm of the next level), and add various components (timeline, hot event display) on the basis of the Vue2.0 framework. Combined with information such as the situation, alliance relations, trend analysis, etc., a variety of executable solutions such as radical, conservative, and compromise are proposed to present the spatiotemporal changes of the environmental situation to users.

[0087] Figure 3 The schematic diagram of the structure of a visualization display device for mass data provided by this embodiment is as follows: The visualization display device for mass data may include: an acquisition module 310 , a conversion module 320 , a processing module 330 and a rendering module 340 .

[0088] The acquisition module 310 is used to acquire first entity data, where the first entity data is used to describe the massive data corresponding to different entities in the real environment, and the massive data is used to describe entity attribute information and entity evolution information.

[0089] The conversion module 320 is used to convert the data format of the first entity data based on the open source database and the project object model to obtain second entity data, where the data format of the second entity data is JSON format.

[0090] The processing module 330 is used to perform multi-level detail processing on the second entity data to obtain a pyramid structure map, wherein the pyramid structure map includes multiple structural layers, and different structural layers respectively include the number of display surfaces and display detail levels of different entities, and the number of display surfaces and display detail levels of different entities are determined based on the location and importance of the corresponding entities in the real environment.

[0091] The rendering module 340 is used to perform instantiation batch rendering on the pyramid structure map to obtain rendering results, so as to display the spatiotemporal changes of the mass data corresponding to different entities based on the rendering results.

[0092] Among them, the instantiation batch rendering includes: entity rendering, component rendering and texture rendering, the entity rendering is used to batch render the entity attribute information, the component rendering is used to additionally render the entity key information, the entity key information includes the timeline and / or hot events, and the texture rendering is used to perform flow simulation rendering of the entity evolution information.

[0093] In this embodiment, optionally, the processing module 330 is specifically configured to:

[0094] The positions of different entities in the real environment and the types of different entities in the real environment are obtained; based on the positions of different entities in the real environment and the types of different entities in the real environment, the importance of different entities in the real environment is determined; based on the positions of different entities in the real environment and the importance of different entities in the real environment, the structural layers to which different entities belong in an initial tower structure are determined, wherein the initial tower structure is a pyramid structure; the number of display faces and the degree of display details of entities in different structural layers of the initial tower structure are adjusted to obtain the pyramid structure map, wherein different structural layers in the pyramid structure map have different rendering resources.

[0095] In this embodiment, optionally, the rendering module 340 includes: a first rendering unit, a second rendering unit and a simulation unit.

[0096] The first rendering unit is used to respectively use the rendering resources corresponding to each structural layer to batch render the entity attribute information corresponding to the entities based on the number of display surfaces and display detail of the entities included in each structural layer.

[0097] The second rendering unit is used to perform additional rendering of timelines and / or hot events for different entities based on key information corresponding to different entities.

[0098] The simulation unit is used to simulate the flow characteristics of different entities based on the entity evolution information corresponding to the different entities to obtain the rendering result.

[0099] In this embodiment, optionally, the rendering module 340 is specifically used to:

[0100] In different structural layers, the entity objects that need to be rendered and the multiple attribute parameters corresponding to the entity objects are determined, and each of the attribute parameters corresponds to a rendering number; the entity objects that need to be rendered and the multiple attribute parameters corresponding to the entity objects are sent to the GPU cache, so that the GPU cache uses the rendering resources corresponding to the different structural layers to batch render the entity attribute information corresponding to the entities based on the entity objects in different structural layers, the multiple attribute parameters corresponding to the entity objects, the number of display surfaces of the entities included in the different structural layers, and the display detail level.

[0101] In this embodiment, optionally, it also includes: an analysis module.

[0102] The acquisition module 310 is also used to acquire related entities, historical development data and predicted development data corresponding to different entities.

[0103] The analysis module is used to perform entity development analysis on the rendering result based on the associated entities, the historical development data and the predicted development data corresponding to different entities.

[0104] In this embodiment, optionally, it also includes: a sending module.

[0105] The sending module is also used to respond to a result viewing request sent by a target client, and send the rendering result and the entity development analysis result corresponding to the rendering result to the target client; or, obtain other clients associated with the first entity data, and after instantiating batch rendering of the pyramid structure map to obtain rendering results, send the rendering results to the other clients; after performing entity development analysis on the rendering results based on the associated entities corresponding to different entities, the historical development data and the predicted development data, send the entity development analysis results corresponding to the rendering results to the other clients.

[0106] In this embodiment, the module is optionally updated.

[0107] The analysis module is further used to perform event analysis on the new entity data to obtain event analysis results if it is detected that new entity data is generated under the time axis corresponding to different entities.

[0108] An updating module is used to update the entity development analysis result corresponding to the rendering result based on the event analysis result.

[0109] The visualization display device for massive data provided by the present disclosure can execute the above method embodiments. Its specific implementation principles and technical effects can be found in the above method embodiments, and the present disclosure will not repeat them here.

[0110] The present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0111] The computer device includes a memory 410 and a processor 420 that are connected to each other through a system bus. It should be noted that the figure only shows a computer device with components 410-420, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0112] Computer devices can be computing devices such as desktop computers, notebooks, PDAs, and cloud servers. Computer devices can interact with users through keyboards, mice, remote controls, touch pads, or voice control devices.

[0113] The memory 410 includes at least one type of readable storage medium, and the readable storage medium includes a non-volatile memory or a volatile memory, for example, a flash memory, a hard disk, a multimedia card, a card-type memory (for example, an SD or DX memory, etc.), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc., and the RAM may include a static RAM or a dynamic RAM. In some embodiments, the memory 410 may be an internal storage unit of a computer device, for example, a hard disk or a memory of the computer device. In other embodiments, the memory 410 may also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card or a flash card (FlashCard) equipped on the computer device. Of course, the memory 410 may also include both the internal storage unit of the computer device and its external storage device. In this embodiment, the memory 410 is generally used to store the operating system and various application software installed on the computer device, such as the program code of the above method. In addition, the memory 410 may also be used to temporarily store various data that have been output or are to be output.

[0114] The processor 420 is generally used to perform the overall operation of the computer device. In this embodiment, the memory 410 is used to store program codes or instructions, the program code includes computer operation instructions, and the processor 420 is used to execute the program codes or instructions stored in the memory 410 or process data, such as running the program code of the above method.

[0115] In this article, the bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus system can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0116] Another embodiment of the present application also provides a computer-readable medium, which may be a computer-readable signal medium or a computer-readable medium. A processor in a computer reads a computer-readable program code stored in the computer-readable medium, so that the processor can execute the functional actions specified in each step or a combination of steps in the above method; and generate a device for implementing the functional actions specified in each block or a combination of blocks in the block diagram.

[0117] Computer-readable media include but are not limited to electronic, magnetic, optical, electromagnetic, infrared memory or semiconductor systems, devices or apparatuses, or any appropriate combination of the foregoing, the memory is used to store program codes or instructions, the program codes include computer operating instructions, and the processor is used to execute the program codes or instructions of the above methods stored in the memory.

[0118] For the definitions of memory and processor, please refer to the description of the aforementioned computer device embodiment and will not be repeated here.

[0119] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0120] Each functional unit or module in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional unit.

[0121] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0122] In the claims, any reference symbols placed between brackets shall not be construed as limiting the claims. The word "comprising" described in the present application does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present application can be implemented with the aid of hardware comprising several different elements and with the aid of a suitably programmed computer. In a unit claim that lists a number of devices, several units of these devices may be embodied by the same hardware item. The use of first, second, and third, etc. does not indicate any order, and these words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.

[0123] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for visualizing massive data, characterized in that: include: Acquire first entity data, where the first entity data is used to describe a large amount of data corresponding to different entities in a real environment, and the large amount of data is used to describe entity attribute information and entity evolution information; Performing data format conversion on the first entity data based on an open source database and a project object model to obtain second entity data, wherein the data format of the second entity data is a JSON format; Performing multi-level detail processing on the second entity data to obtain a pyramid structure map, wherein the pyramid structure map includes multiple structure layers, and different structure layers respectively include the number of display faces and display detail degrees of different entities, and the number of display faces and display detail degrees of different entities are determined based on the location and importance of the corresponding entity in the real environment; Performing instantiation batch rendering on the pyramid structure map to obtain rendering results, so as to display the spatiotemporal changes of the massive data corresponding to different entities based on the rendering results; The instantiation batch rendering includes: entity rendering, component rendering and texture rendering. The entity rendering is used to perform batch rendering of the entity attribute information. The component rendering is used to perform additional rendering of entity key information, and the entity key information includes a timeline and / or hot events. The texture rendering is used to perform flow simulation rendering of the entity evolution information. The instantiated batch rendering of the pyramid structure map to obtain the rendering result includes: The rendering resources corresponding to each structural layer are respectively used to batch render the entity attribute information corresponding to the entities in each structural layer based on the number of display surfaces and display detail of the entities; based on the key information corresponding to different entities, additional rendering of timelines and / or hot events is performed on different entities; based on the entity evolution information corresponding to different entities, the flow characteristics of different entities are simulated to obtain the rendering results; Obtaining related entities, historical development data, and predicted development data corresponding to different entities; the related entity is the entity corresponding to an entity when performing information / data interaction, and the predicted development data is the future development data corresponding to the entity, which is used to show the future development trend of the entity; Based on the associated entities, the historical development data, and the predicted development data corresponding to different entities, entity development analysis is performed on the rendering results.

2. The method according to claim 1, characterized in that The performing multi-level-of-detail processing on the second entity data to obtain a pyramid structure map includes: Obtain the locations of different entities in the real environment and the types of different entities in the real environment; Determine the importance of different entities in the real environment based on the locations of different entities in the real environment and the types of different entities in the real environment; Based on the locations of different entities in the real environment and the importance of different entities in the real environment, determining the structural layers to which different entities belong in the initial tower structure, wherein the initial tower structure is a pyramid structure; The number of display faces and display detail of entities in different structural layers of the initial tower structure are adjusted to obtain the pyramid structure map, in which different structural layers in the pyramid structure map have different corresponding rendering resources.

3. The method according to claim 1, characterized in that The method of using rendering resources corresponding to each structural layer to batch render entity attribute information corresponding to the entities based on the number of display surfaces and display detail of the entities included in each structural layer includes: In different structural layers, determining entity objects that need to be rendered and a plurality of attribute parameters corresponding to the entity objects, each of the attribute parameters corresponding to a rendering sequence number; The entity objects that need to be rendered and multiple attribute parameters corresponding to the entity objects are sent to the GPU cache, so that the GPU cache uses the rendering resources corresponding to different structural layers to batch render the entity attribute information corresponding to the entities based on the entity objects in different structural layers, the multiple attribute parameters corresponding to the entity objects, the number of display surfaces of the entities included in different structural layers, and the display detail level.

4. The method according to claim 1, characterized in that Also includes: In response to a result viewing request sent by a target client, sending the rendering result and the entity development analysis result corresponding to the rendering result to the target client; Alternatively, obtaining other clients associated with the first entity data, performing instantiation batch rendering on the pyramid structure map, and after obtaining rendering results, sending the rendering results to the other clients; After performing entity development analysis on the rendering result based on the associated entities, the historical development data, and the predicted development data corresponding to different entities, the entity development analysis result corresponding to the rendering result is sent to the other client.

5. The method according to claim 4, characterized in that Also includes: If it is detected that new entity data is generated under the time axis corresponding to different entities, event analysis is performed on the new entity data to obtain event analysis results; Based on the event analysis result, the entity development analysis result corresponding to the rendering result is updated.

6. A visual display device for massive data, characterized in that: include: An acquisition module, used to acquire first entity data, where the first entity data is used to describe a large amount of data corresponding to different entities in a real environment, where the large amount of data is used to describe entity attribute information and entity evolution information; A conversion module, configured to convert the data format of the first entity data based on an open source database and a project object model to obtain second entity data, wherein the data format of the second entity data is a JSON format; A processing module is used to perform multi-level detail processing on the second entity data to obtain a pyramid structure map, wherein the pyramid structure map includes multiple structure layers, and different structure layers respectively include the number of display faces and display detail degrees of different entities, and the number of display faces and display detail degrees of different entities are determined based on the location and importance of the corresponding entity in the real environment; A rendering module, used for instantiating batch rendering of the pyramid structure map to obtain rendering results, so as to display the spatiotemporal changes of the massive data corresponding to different entities based on the rendering results; The instantiation batch rendering includes: entity rendering, component rendering and texture rendering. The entity rendering is used to perform batch rendering of the entity attribute information. The component rendering is used to perform additional rendering of entity key information, and the entity key information includes a timeline and / or hot events. The texture rendering is used to perform flow simulation rendering of the entity evolution information. The rendering module includes: a first rendering unit, a second rendering unit and a simulation unit; The first rendering unit is used to respectively use the rendering resources corresponding to each structural layer to batch render the entity attribute information corresponding to the entity based on the number of display surfaces and display detail of the entity included in each structural layer; the second rendering unit is used to perform additional rendering of the timeline and / or hot events for different entities based on the key information corresponding to different entities; the simulation unit is used to simulate the flow characteristics of different entities based on the entity evolution information corresponding to different entities to obtain the rendering results; Also includes: analysis module; The acquisition module is further used to acquire associated entities, historical development data and predicted development data corresponding to different entities; the associated entity is the entity corresponding to an entity when performing information / data interaction, and the predicted development data is the future development data corresponding to the entity, which is used to show the future development trend of the entity; The analysis module is used to perform entity development analysis on the rendering results based on the associated entities, the historical development data and the predicted development data corresponding to different entities.

7. A computer device, characterized in that: The method comprises a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, a method for visualizing and displaying massive data as claimed in any one of claims 1 to 5 is implemented.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for visualizing and displaying massive data as claimed in any one of claims 1 to 5 is implemented.

Images