Method and system for displaying mass point locations of browser

Abstract

The invention provides a method and a system for displaying mass point locations of a browser, and relates to the technical field of mass point location data processing. The method mainly comprises the following steps: firstly, building a BS network architecture which comprises a front-end processing end and a rear-end processing end; the front end sends a loading request to the rear end, and the rear end loads the point location data to a specified browser through the front end according to the loading request, judges whether the point location data is blocked or not based on loading time, starts a rear end optimization process if the point location data is blocked or not, pushes the data in a paging manner, starts a display optimization process after the front end receives the data, determines whether layered aggregation is needed or not, and adjusts a display scale and renders if aggregation is needed. And finally loading to a browser for displaying. According to the method, through framework building, data loading, lagging judgment, the point location loading optimization process at the rear end and the point location display optimization process at the front end, the pressure of data loading and processing is effectively reduced, so that the browser is smoother when displaying massive point locations, the user operation response is quicker, and the user experience is greatly improved.

Description

Technical Field

[0001] The present invention mainly relates to the technical field of massive point data processing, and in particular to a browser massive point display method and system. Background Art

[0002] In today's era of vigorous development of Internet technology, the application of big data is becoming more and more extensive, and the display of massive points has become an indispensable requirement in many fields. Especially in applications based on BS architecture, the scene of displaying point information in the browser is very common. However, the performance of the browser limits the effect of massive point display to a certain extent.

[0003] Traditional point loading methods often cause many problems when faced with massive point data. Due to the huge amount of data that the browser needs to process, its hardware conditions such as computing resources and memory face severe challenges, which inevitably leads to browser freezes during the loading process. For example, when loading a large number of geographic information points or monitoring data points, the page response is slow, and user operations such as zooming and panning the map become extremely unsmooth, seriously affecting the user experience.

[0004] This lag problem not only reduces user satisfaction with a single application, but may even lead to decision delays or operational errors in some scenarios that require high real-time and interactivity, such as real-time traffic monitoring and large-scale logistics distribution and dispatching systems. For major Internet companies, it is urgent to solve the problem of smooth display of massive points, which is directly related to the competitiveness of products and user retention rate. Only by achieving smooth display of massive points can users have an extremely fast experience and meet the growing business needs and user expectations. Summary of the invention

[0005] The technical problem to be solved by the present invention is to provide a browser massive point display method and system in view of the deficiencies in the prior art.

[0006] The technical solution of the present invention to solve the above technical problem is as follows: A method for displaying a large number of points in a browser comprises the following steps:

[0007] Building a BS network architecture, wherein the BS network architecture includes a front-end processing end and a back-end processing end;

[0008] The front-end processor sends a load request to the back-end processor;

[0009] The back-end processor loads the point data into the designated browser through the front-end processor based on the loading request, and determines whether there is a point loading jam in the designated browser based on the loading time. If so, the point loading optimization process of the back-end processor is started, and the point data is pushed in pages through the point loading optimization process to obtain paged point data carrying a paged identifier, and the corresponding paged point data are pushed to the front-end processing end one by one according to the paged identifier;

[0010] When the front-end processing end receives the paged point data, it starts the point display optimization process, and determines through the point display optimization process whether to perform layered aggregation processing on the paged point data. If so, multiple aggregated point data are obtained, and the display ratio of the multiple aggregated point data is adjusted, the adjusted aggregated point data is rendered, and the final point data is loaded into the designated browser for display.

[0011] Another technical solution of the present invention to solve the above technical problem is as follows: A browser massive point display system includes a BS network architecture, and the BS network architecture includes a front-end processing end and a back-end processing end;

[0012] The front-end processor is used to send a loading request to the back-end processor;

[0013] The back-end processor is used to load the point data into the designated browser through the front-end processor based on the loading request, and judge whether there is a point loading jam in the designated browser based on the loading time. If so, start the point loading optimization process of the back-end processor, and perform paging push processing on the point data through the point loading optimization process to obtain paging point data carrying paging identifiers, and push the corresponding paging point data to the front-end processing end one by one according to the paging identifiers;

[0014] The front-end processing end is also used to start the point display optimization process when receiving the paged point data, and determine through the point display optimization process whether to perform layered aggregation processing on the paged point data. If so, multiple aggregated point data are obtained, and the display ratio of the multiple aggregated point data is adjusted, the adjusted aggregated point data is rendered, and the final point data is loaded into the designated browser for display.

[0015] Another technical solution of the present invention to solve the above-mentioned technical problem is as follows: a browser massive point display system, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the browser massive point display method as described above is implemented.

[0016] The beneficial effects of the present invention are: by building an architecture, loading data, judging jams, optimizing the point loading process at the back end, and optimizing the point display process at the front end, the pressure of data loading and processing is effectively reduced, making the browser smoother when displaying massive points, and the user operation response faster, greatly improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A schematic flow chart of a method for displaying a large number of points in a browser provided by an embodiment of the present invention;

[0018] Figure 2 A schematic connection diagram of the modules of the browser massive point display system provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0019] The principles and features of the present invention are described below in conjunction with the accompanying drawings. The examples given are only used to explain the present invention and are not used to limit the scope of the present invention.

[0020] In order to solve the problem of unsmooth display of massive points on a browser, the present invention proposes a method and system for displaying massive points in a browser, a back-end point loading optimization process and a front-end point display optimization process, to realize a solution for displaying massive points in a browser.

[0021] Example 1: Figure 1 As shown, an embodiment of the present invention provides a browser mass point display method, comprising the following steps:

[0022] Building a BS network architecture, wherein the BS network architecture includes a front-end processing end and a back-end processing end;

[0023] The front-end processor sends a load request to the back-end processor;

[0024] The back-end processor loads the point data into the designated browser through the front-end processor based on the loading request, and determines whether there is a point loading jam in the designated browser based on the loading time. If so, the point loading optimization process of the back-end processor is started, and the point data is pushed in pages through the point loading optimization process to obtain paged point data carrying a paged identifier, and the corresponding paged point data are pushed to the front-end processing end one by one according to the paged identifier;

[0025] When the front-end processing end receives the paged point data, it starts the point display optimization process, and determines through the point display optimization process whether to perform layered aggregation processing on the paged point data. If so, multiple aggregated point data are obtained, and the display ratio of the multiple aggregated point data is adjusted, the adjusted aggregated point data is rendered, and the final point data is loaded into the designated browser for display.

[0026] In this embodiment, by building an architecture, loading data, determining jams, optimizing the point loading process at the back end, and optimizing the point display process at the front end, the pressure of data loading and processing is effectively reduced, making the browser smoother when displaying massive points, and user operation responses faster, greatly improving the user experience.

[0027] Preferably, the process of judging whether there is a point loading jam in the specified browser based on the loading time is described in detail below:

[0028] Load the network tool in the designated browser, obtain the loading time of the point data through the network tool, and compare the loading time with the preset time. If it is greater than the preset time, it is determined that the designated browser has a point loading jam.

[0029] In this embodiment, the preset time can be set to 3 seconds, that is, if the loading time is greater than 3 seconds, it can be determined that there is a point loading jam in the specified browser.

[0030] In this embodiment, the method of loading the network tool in the specified browser to obtain the point data loading time and comparing it with the preset time (such as 3 seconds) to determine whether it is stuck is simple and effective to quantify the stuck situation. This allows developers to accurately locate the problem and promptly find out whether the browser exceeds the acceptable performance range when loading massive points, thereby providing a clear basis for subsequent optimization measures and helping to improve the pertinence and efficiency of optimization work.

[0031] Preferably, the following is a detailed introduction to the process of performing paging push processing on the point data through the point loading optimization process to obtain paging point data carrying paging identifiers, and pushing the corresponding paging point data to the front-end processing end one by one according to the paging identifiers:

[0032] Perform paging query processing on the point data in chronological order to obtain multiple paging point data, create a paging identifier for each paging point data, and store the multiple paging point data carrying the paging identifier in a pre-built redis database;

[0033] The webSocket server is deployed on the back-end processor. When the front-end processor sends a loading request to the back-end processor again, the webSocket server is connected to the front-end processor. Each paging point data is retrieved from the redis database through the webSocket server, and the corresponding paging point data is pushed to the front-end processor one by one according to the paging identifier.

[0034] It should be understood that the back-end point loading optimization process is to solve the problem of slow page loading and jamming due to low efficiency of back-end data return when displaying massive points in the browser. It mainly includes paging data query, redis database cache data and webSocket server data transmission paging data push and other steps. Among them,

[0035] Paginated data query: When the front-end requests massive point data from the back-end, the back-end uses the existing database paging technology to query the point data in paginated order in chronological order. This step divides all point data in an orderly manner, providing a basis for subsequent processing.

[0036] Redis database cache data: Store the results of paging query in the Redis database, and create cache identifiers based on paging identifiers (such as keywords such as page numbers) to mark paging data. The purpose of this is to facilitate quick and accurate acquisition of data when it is needed later, thereby improving data reading efficiency.

[0037] WebSocket data transmission paging data push: The backend establishes a webSocket server and waits for the client to connect. After the connection is established, the previously created data cache identifier paging data is sent. Then, through the paging identifier in the Redis cache, the cached data is pushed page by page to the front end for processing, thereby achieving efficient data transmission, reducing data transmission time, and improving overall performance.

[0038] In this embodiment, BS architecture deployment is adopted, the front end is deployed through nginx middleware, and the back end runs in the JVM environment, on this basis, webSocket communication is established.

[0039] During the front-end optimization process, the front-end connects to the back-end through webSocket to request point data, and the back-end transmits the data to the front-end through webSocket. The front-end receives data in data lazy loading mode. For example, when optimizing the point data in the current field of view, the front-end requests the back-end data, and the back-end transmits the relevant data to the front-end through webSocket.

[0040] In this embodiment, the optimization process of the backend involves multiple key steps, such as paging data query using existing database paging technology to orderly segment data, laying the foundation for subsequent processing; redis database cache data creates cache identifiers to facilitate fast and accurate data acquisition and improve reading efficiency; webSocket data transmission paging data push establishes an efficient communication mechanism to push data page by page and reduce transmission time. Overall, it effectively solves the problem of slow page loading and jamming caused by low efficiency of backend return data, improves the performance of backend data processing and transmission, and ensures that data can reach the front end for display in a timely and accurate manner.

[0041] Preferably, the following is a detailed description of the process of determining whether to perform hierarchical aggregation processing on the paging point data through the point display optimization process, and if so, obtaining multiple aggregated point data, adjusting the display ratio of the multiple aggregated point data, performing accelerated rendering processing on the adjusted aggregated point data, and loading the final point data into the designated browser for display:

[0042] Call the openLayers library and create a point display layer based on the openLayers library;

[0043] When the front-end processing end sends a loading request to the back-end processor again, the current page field of view is obtained from the designated browser, and whether the current page is a zoom page is determined according to the current window field of view. If so, the paging point data is layered, and all the layered paging point data are aggregated based on the similarity between the multiple layered paging point data to obtain multiple aggregated point data, and the number of aggregated point data is adjusted according to the zoom ratio, and the adjusted aggregated point data is displayed in the point display layer according to the number, and the GPU graphics processing unit is called to load the point display layer containing the aggregated point data into the GPU graphics processing unit for accelerated rendering, and the final point data is loaded into the designated browser for display;

[0044] If not, the paged point data is directly displayed in the point display layer, and the GPU graphics processing unit is called to load the point display layer containing the paged point data into the GPU graphics processing unit for rendering, and the final point data is loaded into the designated browser for display.

[0045] It should be understood that the front-end point display optimization process is mainly aimed at improving the front-end display effect and performance when displaying massive points in the browser. It mainly includes layer creation, data connection and loading, field of view data processing, zoom operation related optimization, data rendering and display and other steps. Among them,

[0046] Layer creation: Based on openLayers technology, that is, calling the openLayers library, introducing the ol.js and ol.css files related to the openLayers library on the front-end page to create a point display layer, providing a basic framework for the subsequent display of point data.

[0047] Data connection and loading: Establish a webSocket connection and use lazy loading mode: The front end connects to the back end through webSocket to request point data. Open webSocket to receive back-end data and use data lazy loading mode to load data, that is, load data only when it is needed, avoiding loading a large amount of data at one time and causing jamming, and improving data loading efficiency.

[0048] Field of view data processing: optimize the point data of the current field of view, preload and calculate the point data, then perform layered processing on the paged point data, aggregate similar data, and calculate the number of point aggregations. This can reduce the amount of data that needs to be processed and displayed, and improve performance and display effects.

[0049] Optimizations related to zooming operations: 1) Adjust data display according to zoom ratio: When the user adjusts the map field of view by zooming the map with the mouse, the front end will request the back end for the point data in the current field of view, and then adjust the number of point displays in real time according to the point zoom ratio. Within the visible range, load the aggregated point data to ensure that there is appropriate data display at different zoom ratios to improve the user experience. 2) Maximum zoom ratio processing: When the zoom reaches the maximum ratio, all point data in the current field of view are displayed. At this time, the data is no longer aggregated, and all point information in the field of view is fully presented.

[0050] Data rendering and display: Load the pre-processed point data into the client GPU graphics processing unit, use the GPU's high-performance computing capabilities to accelerate the rendering process, and use the WebGLPoints method in the openLayers library to load the pre-processed point data (i.e., the final point data), and use the WebGLPoints plug-in to accelerate the display of the final point data and output it to the specified browser. Achieve efficient and smooth display of massive points.

[0051] In this embodiment, the front-end optimization process improves the display effect and performance from multiple aspects. Layer creation is based on openLayers technology to provide a framework for point display; data connection and loading use webSocket connection and lazy loading mode to avoid jamming caused by loading a large amount of data at one time; field of view data processing reduces the amount of data and improves performance through pre-load calculation, layered aggregation, etc.; zoom operation related optimization adjusts the display quantity in real time according to the zoom ratio, provides appropriate data display at different zoom levels, and handles the maximum zoom ratio at the same time; data rendering and display use GPU acceleration and WebGLPoints method to achieve efficient and smooth display. Taken together, the display quality and operation fluency of the front end when processing massive points are significantly improved, enhancing the user experience.

[0052] Taking a situation map display project as an example, the browser massive point display method proposed by the present invention is used to process the massive point data of the situation map. The specific process is:

[0053] 1) Load a large number of points in the browser in the usual way and display them on the situation map. Open Google Chrome, view the situation map display page, and check if the page is stuck.

[0054] 2) Optimize the back-end interface of the situation map and optimize the efficiency of the data returned by the back-end. The optimization process is as follows:

[0055] 2.1) The front end requests the back end data, and the back end uses paging technology to query the data and perform paging queries on all points;

[0056] 2.2) Save the query results in the redis database and create cache identification paging data to facilitate the application of later data;

[0057] 2.3) WebSocket data transmission, the backend establishes a webSocket server, waits for the client to connect, and sends data cache identification paging data;

[0058] 2.4) Push data page by page to the front-end for processing through paging identifiers.

[0059] 3) Front-end optimization: optimize the points displayed on the front-end. The optimization process is as follows:

[0060] 3.1) The front-end uses openLayers technology, introduces ol.js and ol.css files in the front-end page, and creates a point display layer.

[0061] 3.2) The front end connects to the back end through webSocket, requests point data, opens webSocket to receive back end data, and loads data in data lazy loading mode;

[0062] 3.3) Optimize the situation data within the current field of view, preload and calculate the situation data, perform layered processing on the situation data, aggregate similar situation data, and calculate the number of aggregates;

[0063] 3.4) When zooming in and out the map with the mouse, adjust the map field of view, and request the backend for the point data of the current field of view;

[0064] 3.5) According to the point scaling ratio, the number of points displayed is adjusted in real time, and the aggregated point data is loaded within the visible range;

[0065] 3.6) When the zoom reaches the maximum scale, all point data in the current field of view are displayed, and the data is no longer aggregated;

[0066] 3.7) Load the preprocessed point data into the GPU and use the WebGLPoints method to load the data and display it in the Google Chrome browser.

[0067] Example 2: Figure 2 As shown, another embodiment of the present invention further provides a browser mass point display system, including a BS network architecture, wherein the BS network architecture includes a front-end processing end and a back-end processing end;

[0068] The front-end processor is used to send a loading request to the back-end processor;

[0069] The back-end processor is used to load the point data into the designated browser through the front-end processor based on the loading request, and judge whether there is a point loading jam in the designated browser based on the loading time. If so, start the point loading optimization process of the back-end processor, and perform paging push processing on the point data through the point loading optimization process to obtain paging point data carrying paging identifiers, and push the corresponding paging point data to the front-end processing end one by one according to the paging identifiers;

[0070] The front-end processing end is also used to start the point display optimization process when receiving the paged point data, and determine through the point display optimization process whether to perform layered aggregation processing on the paged point data. If so, multiple aggregated point data are obtained, and the display ratio of the multiple aggregated point data is adjusted, the adjusted aggregated point data is rendered, and the final point data is loaded into the designated browser for display.

[0071] Preferably, in the backend processor, judging whether there is a point loading jam in the specified browser based on the loading time is specifically as follows:

[0072] Load the network tool in the designated browser, obtain the loading time of the point data through the network tool, and compare the loading time with the preset time. If it is greater than the preset time, it is determined that the designated browser has a point loading jam.

[0073] Preferably, in the back-end processor, the point data is processed by paging and pushing through the point loading optimization process to obtain paging point data carrying paging identifiers, and the paging point data corresponding to the paging identifiers are pushed to the front-end processing end one by one, specifically:

[0074] Perform paging query processing on the point data in chronological order to obtain multiple paging point data, create a paging identifier for each paging point data, and store the multiple paging point data carrying the paging identifier in a pre-built redis database;

[0075] The webSocket server is deployed on the back-end processor. When the front-end processor sends a loading request to the back-end processor again, the webSocket server is connected to the front-end processor. Each paging point data is retrieved from the redis database through the webSocket server, and the corresponding paging point data is pushed to the front-end processor one by one according to the paging identifier.

[0076] Preferably, in the front-end processor, it is determined through the point display optimization process whether to perform hierarchical aggregation processing on the paged point data. If so, multiple aggregated point data are obtained, and the display ratio of the multiple aggregated point data is adjusted, the adjusted aggregated point data is accelerated for rendering, and the final point data is loaded into the designated browser for display, specifically:

[0077] Call the openLayers library and create a point display layer based on the openLayers library;

[0078] When the front-end processing end sends a loading request to the back-end processor again, the current page field of view is obtained from the designated browser, and whether the current page is a zoom page is determined according to the current window field of view. If so, the paging point data is layered, and all the layered paging point data are aggregated based on the similarity between the multiple layered paging point data to obtain multiple aggregated point data, and the number of aggregated point data is adjusted according to the zoom ratio, and the adjusted aggregated point data is displayed in the point display layer according to the number, and the GPU graphics processing unit is called to load the point display layer containing the aggregated point data into the GPU graphics processing unit for accelerated rendering, and the final point data is loaded into the designated browser for display;

[0079] If not, the paged point data is directly displayed in the point display layer, and the GPU graphics processing unit is called to load the point display layer containing the paged point data into the GPU graphics processing unit for rendering, and the final point data is loaded into the designated browser for display.

[0080] Embodiment 3: Another embodiment of the present invention further provides a browser massive point display system, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the browser massive point display method as described above is implemented.

[0081] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.

[0082] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0083] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of 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.

[0084] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present invention.

[0085] In addition, each functional unit in each embodiment of the present invention 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 units.

[0086] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for displaying a large number of points in a browser, characterized in that: The steps include: Building a BS network architecture, wherein the BS network architecture includes a front-end processing end and a back-end processing end; The front-end processor sends a load request to the back-end processor; The back-end processor loads the point data into the designated browser through the front-end processor based on the loading request, and determines whether there is a point loading jam in the designated browser based on the loading time. If so, the point loading optimization process of the back-end processor is started, and the point data is pushed in pages through the point loading optimization process to obtain paged point data carrying a paged identifier, and the corresponding paged point data are pushed to the front-end processing end one by one according to the paged identifier; When the front-end processing end receives the paged point data, it starts the point display optimization process, and determines through the point display optimization process whether to perform layered aggregation processing on the paged point data. If so, multiple aggregated point data are obtained, and the display ratio of the multiple aggregated point data is adjusted, the adjusted aggregated point data is rendered, and the final point data is loaded into the designated browser for display.

2. The browser mass point display method according to claim 1, characterized in that: The step of judging whether there is a point loading jam in the specified browser based on the loading time is specifically as follows: Load the network tool in the designated browser, obtain the loading time of the point data through the network tool, and compare the loading time with the preset time. If it is greater than the preset time, it is determined that the designated browser has a point loading jam.

3. The browser mass point display method according to claim 1, characterized in that: The point data is processed by paging through the point loading optimization process to obtain paging point data with paging identifiers, and the paging point data corresponding to the paging identifiers are pushed to the front-end processing end one by one, specifically: Perform paging query processing on the point data in chronological order to obtain multiple paging point data, create a paging identifier for each paging point data, and store the multiple paging point data carrying the paging identifier in a pre-built redis database; The webSocket server is deployed on the back-end processor. When the front-end processor sends a loading request to the back-end processor again, the webSocket server is connected to the front-end processor. Each paging point data is retrieved from the redis database through the webSocket server, and the corresponding paging point data is pushed to the front-end processor one by one according to the paging identifier.

4. The browser mass point display method according to claim 3 is characterized in that: The point display optimization process determines whether to perform hierarchical aggregation processing on the paged point data. If so, multiple aggregated point data are obtained, and the display ratio of the multiple aggregated point data is adjusted. The adjusted aggregated point data is accelerated for rendering, and the final point data is loaded into the specified browser for display, specifically: Call the openLayers library and create a point display layer based on the openLayers library; When the front-end processing end sends a loading request to the back-end processor again, the current page field of view is obtained from the designated browser, and whether the current page is a zoom page is determined according to the current window field of view. If so, the paging point data is layered, and all the layered paging point data are aggregated based on the similarity between the multiple layered paging point data to obtain multiple aggregated point data, and the number of aggregated point data is adjusted according to the zoom ratio, and the adjusted aggregated point data is displayed in the point display layer according to the number, and the GPU graphics processing unit is called to load the point display layer containing the aggregated point data into the GPU graphics processing unit for accelerated rendering, and the final point data is loaded into the designated browser for display; If not, the paged point data is directly displayed in the point display layer, and the GPU graphics processing unit is called to load the point display layer containing the paged point data into the GPU graphics processing unit for rendering, and the final point data is loaded into the designated browser for display.

5. The browser mass point display method according to any one of claims 1 to 4, characterized in that: The final point data is loaded into the designated browser for display, specifically: The GPU graphics processing unit is connected to the WebGLPoints plug-in in the openLayers library, the final point data is sent to the WebGLPoints plug-in, and the final point data is accelerated to display through the WebGLPoints plug-in, and output to the specified browser.

6. A browser massive point display system, characterized in that: The BS network architecture includes a front-end processing end and a back-end processing end; The front-end processor is used to send a loading request to the back-end processor; The back-end processor is used to load the point data into the designated browser through the front-end processor based on the loading request, and judge whether there is a point loading jam in the designated browser based on the loading time. If so, start the point loading optimization process of the back-end processor, and perform paging push processing on the point data through the point loading optimization process to obtain paging point data carrying paging identifiers, and push the corresponding paging point data to the front-end processing end one by one according to the paging identifiers; The front-end processing end is also used to start the point display optimization process when receiving the paged point data, and determine through the point display optimization process whether to perform layered aggregation processing on the paged point data. If so, multiple aggregated point data are obtained, and the display ratio of the multiple aggregated point data is adjusted, the adjusted aggregated point data is rendered, and the final point data is loaded into the designated browser for display.

7. The browser massive point display system according to claim 6, characterized in that: In the back-end processor, judging whether there is a point loading jam in the specified browser based on the loading time is as follows: Load the network tool in the designated browser, obtain the loading time of the point data through the network tool, and compare the loading time with the preset time. If it is greater than the preset time, it is determined that the designated browser has a point loading jam.

8. The browser massive point display system according to claim 6, characterized in that: In the back-end processor, the point data is processed by paging and pushing through the point loading optimization process to obtain paging point data carrying paging identifiers, and the paging point data corresponding to the paging identifiers are pushed to the front-end processing end one by one, specifically: Perform paging query processing on the point data in chronological order to obtain multiple paging point data, create a paging identifier for each paging point data, and store the multiple paging point data carrying the paging identifier in a pre-built redis database; The webSocket server is deployed on the back-end processor. When the front-end processor sends a loading request to the back-end processor again, the webSocket server is connected to the front-end processor. Each paging point data is retrieved from the redis database through the webSocket server, and the corresponding paging point data is pushed to the front-end processor one by one according to the paging identifier.

9. The browser massive point display system according to claim 8, characterized in that: In the front-end processor, the point display optimization process is used to determine whether to perform hierarchical aggregation processing on the paged point data. If so, multiple aggregated point data are obtained, and the display ratio of the multiple aggregated point data is adjusted. The adjusted aggregated point data is accelerated for rendering, and the final point data is loaded into the designated browser for display, specifically: Call the openLayers library and create a point display layer based on the openLayers library; When the front-end processing end sends a loading request to the back-end processor again, the current page field of view is obtained from the designated browser, and whether the current page is a zoom page is determined according to the current window field of view. If so, the paging point data is layered, and all the layered paging point data are aggregated based on the similarity between the multiple layered paging point data to obtain multiple aggregated point data, and the number of aggregated point data is adjusted according to the zoom ratio, and the adjusted aggregated point data is displayed in the point display layer according to the number, and the GPU graphics processing unit is called to load the point display layer containing the aggregated point data into the GPU graphics processing unit for accelerated rendering, and the final point data is loaded into the designated browser for display; If not, the paged point data is directly displayed in the point display layer, and the GPU graphics processing unit is called to load the point display layer containing the paged point data into the GPU graphics processing unit for rendering, and the final point data is loaded into the designated browser for display.

10. A browser mass point display system, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, it implements the browser massive point display method as described in any one of claims 1 to 5.

Images