A method and system for dynamically linking and updating maps
By analyzing the node residence time in the update operation sequence from the map device, filtering effective nodes and optimizing the rendering order, the performance problem of map linkage update in traditional technology is solved, and more efficient rendering and response speed is achieved.
Patent Information
- Application Number
- CN202411322646.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-23
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2044-09-23
AI Technical Summary
Traditional map linkage update technology in high frequency and complex map data scenarios leads to performance problems in rendering update nodes from map devices, such as rendering delay and excessive resource consumption.
By analyzing the residence time of each node in the received update operation sequence from the map device, it is determined that the node whose residence time is shorter than the preset threshold is an invalid node, and its rendering operation is skipped; for nodes whose residence time exceeds the threshold, Filter it as a valid node and add it to the optimized update sequence for rendering.
Reduces unnecessary rendering operations, reduces waste of system resources and rendering delay, improves the response speed of map updates, and optimizes the overall system performance.
Smart Images

Figure CN118838978B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to electronic maps, and in particular to a method and system for dynamically linking and updating maps. Background Art
[0002] With the rapid development of geographic information systems (GIS) and map application technologies, more and more devices, such as smartphones, tablets, and smart monitoring terminals, can share map information between multiple devices through linkage, such as between mobile phones and wearable devices, and between multi-screen cars. In this multi-device linkage scenario, users can zoom in and out, pan, and perform other operations on the map through the main device, and other slave map devices will synchronously update the corresponding map view. This linkage update function is widely used in remote collaboration, map navigation, security monitoring, and other fields.
[0003] Traditional map linkage update technology usually relies on the master device sending the full sequence of update operations to the slave map device. After receiving the sequence, the slave map device gradually renders each node in order to ensure the consistency of the map state. However, as the complexity of map data and the frequency of interaction increase, the traditional solution of rendering each updated node from the map device has exposed some significant performance issues.
[0004] In actual applications, the operations of the master device are often continuous and high-frequency, especially when the user quickly zooms or pans the map, the master device may stay in certain areas for very short periods of time. Slave map devices are usually auxiliary devices, and their performance is often far inferior to that of the master device. When processing these frequently changing operations one by one, they are often unable to keep up with the operation rhythm of the master device due to performance bottlenecks (such as processor performance, memory resource limitations, etc.), resulting in significant rendering delays and affecting user experience. In addition, the hardware performance of different slave map devices varies greatly, and high-frequency map update operations may cause greater resource consumption and performance burden on devices with lower performance. Summary of the invention
[0005] In order to solve the problems in the prior art, the present invention provides a method for dynamically linking and updating a map, the method comprising the following steps: receiving an update operation sequence transmitted by a master map device from a slave map device, the sequence comprising a plurality of update nodes, each node comprising a zoom level, a center point coordinate, a layer status and a timestamp of the map; analyzing the residence time of each node according to the received update operation sequence; determining nodes whose residence time is shorter than a preset threshold as invalid nodes, and skipping the rendering operation of these nodes from the slave device; screening nodes whose residence time exceeds the preset threshold as valid nodes, and adding them to a second update sequence; and executing corresponding map rendering operations according to the generated second update sequence from the slave device.
[0006] Another aspect of the present invention provides a map dynamic linkage update system, comprising the following modules:
[0007] An acquisition module, used for receiving an update operation sequence transmitted by a master map device from a map device, the sequence comprising a plurality of update nodes, each node comprising a zoom level, a center point coordinate, a layer state and a timestamp of a map;
[0008] A first analysis module, configured to analyze the residence time of each node according to the update operation sequence received from the map device;
[0009] The second analysis module is used to determine that the nodes whose residence time is shorter than a preset threshold are invalid nodes, and the slave device will skip the rendering operation of these nodes;
[0010] A third analysis module is used to screen nodes whose residence time exceeds a preset threshold as valid nodes and add them to the second update sequence;
[0011] A rendering module is used to perform corresponding map rendering operations from the device according to the generated second update sequence
[0012] The present invention analyzes the residence time of each node and skips invalid nodes whose residence time is shorter than a preset threshold, so that the slave device can avoid unnecessary rendering operations, thereby reducing the waste of system resources and rendering delays and improving the response speed of map updates.
[0013] The preset threshold is dynamically adjusted according to the system load information, so that the slave device can adaptively allocate resources according to the current performance status, ensuring that the rendering pressure is reduced under high load and the rendering response speed is improved under low load, thereby optimizing the overall system performance.
[0014] By giving priority to rendering nodes where users have stayed for a long time or visited frequently in the past, we ensure that the map areas that users are interested in can be presented quickly, providing a better interactive experience.
[0015] Based on the basic farmland information in the current view and the overall direction of the operation sequence, map nodes related to user operations are processed first to ensure that the main directions and areas of user operations can be updated in a timely manner, thereby improving the effectiveness of rendering and the user experience.
[0016] In summary, the present invention optimizes the rendering order and performance scheduling of slave devices through intelligent screening and dynamic adjustment of rendering strategies, improves the efficiency of dynamic linkage updates of maps and user experience, and is particularly suitable for multi-device linkage scenarios that require efficient processing of map updates. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0018] Figure 1 is a flow chart of the method of the present invention. DETAILED DESCRIPTION
[0019] Below, the invention is preferably described in conjunction with the accompanying drawings and specific implementation methods.
[0020] This embodiment solves the above problem through the following steps:
[0021] In one embodiment, reference Figure 1 The present invention provides a method for dynamically linking and updating maps. By synchronizing update operations in a map application between multiple devices, map interaction actions (such as zooming, panning, layer switching, etc.) on a master device can be reflected in real time on other slave map devices. This method is usually used in a multi-device collaborative environment, such as synchronized display of maps between mobile phones and smart watches, tablet computers and computer monitors, and car main screens and secondary screens.
[0022] Dynamic linkage refers to the map view being updated in real time or near real time on multiple devices without the user having to manually operate each device. The main purpose of this method is to ensure that the map display status can be consistent in multi-device scenarios, improve the user's map operation experience on different devices, and is widely used in navigation systems, monitoring systems, remote collaboration, and other scenarios that require real-time interaction between multiple devices.
[0023] The slave map device receives an update operation sequence transmitted by the master map device, where the sequence includes multiple update nodes, each of which includes a zoom level, a center point coordinate, a layer state, and a timestamp of the map.
[0024] Specifically, each update node in the update operation sequence includes at least the following information: the zoom level of the map, which is used to indicate the map display zoom ratio of the main map device at the current node; the center point coordinates, which are used to identify the geographical location of the view center of the main map device during the map operation, usually expressed in longitude and latitude; the layer state, which is used to describe the display or hiding state of each layer in the map, indicating the geographic information layer displayed in the main map device at the current node; the timestamp, which is used to mark the time when the main map device generates the update node, so that the slave map device can perform synchronous rendering according to the time series.
[0025] For example, when the main map device performs zoom and pan operations, a node in the update operation sequence may contain the following information: the zoom level is 12, the center point coordinates are (121.4737, 31.2304) (longitude 121.4737, latitude 31.2304, indicating the geographic location of a certain place), the layer state is "basic farmland layer is on, satellite layer is off", and the timestamp is 2024-09-06 14:35:20. This node describes that the main map device displays a map with a zoom level of 12 at 14:35:20 on September 6, 2024, with a certain place as the center point, and only displays the basic farmland layer and hides the satellite layer.
[0026] After receiving this update node from the map device, it will update its own map view accordingly based on this information to maintain synchronization with the main map device. This update process ensures the consistency of the status of multiple devices in map operations and guarantees the real-time and consistent experience of users viewing maps on multiple devices.
[0027] The slave map device analyzes the residence time of each node according to the received update operation sequence.
[0028] Specifically, the slave map device reads the timestamp information in the update node and calculates the time interval between adjacent nodes, thereby determining the time the master map device stays on each update node. This analysis is used to identify quick or short stops made by the master map device during map operations, as well as longer stops, so that the slave map device can adopt different processing strategies based on the stop time to optimize rendering efficiency and resource utilization.
[0029] For example, suppose the update operation sequence contains two consecutive update nodes: the first node has a timestamp of 2024-09-06 14:35:20, a zoom level of 12, a center point coordinate of (121.4737, 31.2304), and a layer state of "basic farmland layer on, satellite layer off"; the second node has a timestamp of 2024-09-06 14:35:23, a zoom level of 13, a center point coordinate of (121.4800, 31.2300), and a layer state of "basic farmland layer on, satellite layer on". By calculating the time difference between adjacent nodes, it is found that the main map device stays on the first node for 3 seconds.
[0030] After analyzing the dwell time, the slave map device determines that the master map device has a shorter dwell time on the first update node, so it may not have a higher rendering priority, and can choose to skip or delay rendering of the node. For the second update node with a longer dwell time, the slave map device will give priority to rendering to ensure that the map operation corresponding to the node can be displayed on the slave map device screen in time.
[0031] This dwell time-based analysis process enables the map device to dynamically optimize rendering order and strategy, reduce unnecessary rendering burden, and improve the overall performance of map linkage updates. Especially in scenarios where the map device performance is weak or operations are frequent, it can effectively reduce rendering delays and provide a smoother user experience.
[0032] For nodes whose residence time is shorter than a preset threshold, they are determined to be invalid nodes, and the rendering operation of these nodes will be skipped from the map device.
[0033] Specifically, after receiving the update operation sequence, the slave map device calculates the master map device's stay time on each node by analyzing the timestamp information of each updated node. If the stay time of a node is shorter than the preset threshold, the node will be regarded as an invalid node, and the slave map device will not render it, thus avoiding unnecessary resource consumption and rendering delays.
[0034] For example, assuming that the preset dwell time threshold is 0.3 seconds, the main map device performs continuous map operations, and the two adjacent nodes in the update operation sequence have the following information:
[0035] The first node: The timestamp is 2024-09-06 14:35:20.000, the zoom level is 12, the center point coordinates are (121.4737, 31.2304), and the layer status is "Basic farmland layer is on, satellite layer is off".
[0036] The second node: The timestamp is 2024-09-06 14:35:20.200, the zoom level is 13, the center point coordinates are (121.4800, 31.2300), and the layer status is "Basic farmland layer on, satellite layer on".
[0037] By calculating the time intervals between adjacent nodes, the master map device spends 0.2 seconds on the first node, which is lower than the preset 0.3 second time threshold. Therefore, the slave map device determines that the first node is an invalid node and skips its rendering operation.
[0038] For nodes whose residence time exceeds a preset threshold, they are screened as valid nodes and added to the second update sequence.
[0039] Specifically, after receiving and parsing the update operation sequence transmitted by the master map device, the slave map device analyzes the timestamp information of each node and calculates the master map device's stay time at each node. If the stay time of a node exceeds a preset time threshold (for example, 0.3 seconds), the node will be regarded as a valid node and added to the second update sequence for subsequent rendering.
[0040] For example, suppose the main map device generates two consecutive update nodes when performing a map operation, containing the following information:
[0041] The first node: the timestamp is 2024-09-06 14:35:20.000, the zoom level is 12, the center point coordinates are (121.4737, 31.2304), and the layer status is "basic farmland layer is on, satellite layer is off".
[0042] The second node: The timestamp is 2024-09-06 14:35:20.500, the zoom level is 13, the center point coordinates are (121.4800, 31.2300), and the layer status is "Basic farmland layer on, satellite layer on".
[0043] The slave map device performs a time analysis on the two update nodes and finds that the first node stays for 0.5 seconds, which exceeds the preset 0.3 second time threshold. Therefore, the first node is determined to be a valid node and added to the second update sequence. The second update sequence is an optimized update operation sequence generated by the slave map device, which only contains valid nodes where the master map device stays for a longer time during the operation. The slave map device will render these nodes first.
[0044] The slave map device performs a corresponding map rendering operation according to the generated second update sequence.
[0045] Specifically, the slave map device filters the update operation sequence transmitted by the master device, retains only valid nodes whose residence time exceeds a preset threshold, and generates a second update sequence for these valid nodes. After receiving and processing the sequence, the slave map device gradually performs map rendering operations according to each node in the second update sequence, thereby achieving synchronous update of the map status with the master device.
[0046] Each valid node contains multiple parameters related to map display, such as the map's zoom level, center point coordinates, layer status, and timestamp information. The slave map device renders these valid nodes in turn to ensure that the map operations of the master device are fully and accurately reflected on the slave map device.
[0047] For example, assume that the generated second update sequence contains the following valid nodes:
[0048] The first valid node: the zoom level is 12, the center point coordinates are (121.4737, 31.2304), the layer status is "basic farmland layer is on, satellite layer is off", and the timestamp is 2024-09-06 14:35:20.500.
[0049] The second valid node: the zoom level is 13, the center point coordinates are (121.4800, 31.2300), the layer status is "basic farmland layer on, satellite layer on", and the timestamp is 2024-09-06 14:35:22.000.
[0050] The slave map device first renders the map state of the first valid node, that is, zooms the map to level 12, sets the center point of the view to (121.4737, 31.2304), displays the basic farmland layer, and hides the satellite layer. Subsequently, the slave map device continues to render the map state of the second valid node, adjusts the zoom level to 13, updates the center point to (121.4800, 31.2300), and turns on the satellite layer display. By performing rendering operations in the order of valid nodes in the second update sequence, the slave map device can accurately synchronize the map state of the master device and avoid rendering delays caused by processing invalid nodes.
[0051] This rendering process ensures that the slave map device can effectively optimize resource utilization, reduce unnecessary rendering burden, and ensure synchronization with the map state of the master device. Through this effective node-based rendering strategy, the slave map device can provide a smoother user experience, especially in scenarios where the master device frequently zooms and pans, greatly reducing the delay in map linkage updates.
[0052] Furthermore, the optimized dynamic threshold adjustment method dynamically adjusts the rendering time threshold of the slave map device by comprehensively considering the system load, the main device operating frequency, the historical rendering performance and the network status, so as to improve the response efficiency and user experience during the dynamic linkage update of the map.
[0053] Monitor the system load information of the map device in real time, including but not limited to CPU usage, memory usage, and GPU rendering load.
[0054] For example, if the system load is higher than the preset threshold (such as 80%), the rendering time threshold is appropriately increased to reduce the update nodes that need to be processed. If the system load is lower than the preset threshold (such as 30%), the rendering time threshold is lowered to allow more update nodes to be rendered.
[0055] The slave map device analyzes the update operation sequence transmitted by the master device and calculates the operation frequency of the master device. Specifically, the slave map device records the number of update nodes received per second. For example, if the operation frequency is higher than the preset frequency threshold (such as 10 updates per second), the rendering time threshold is increased to avoid high-frequency rendering from placing too much burden on the slave map device. If the operation frequency is lower than the preset frequency threshold (such as 3 updates per second), the rendering time threshold is appropriately lowered to ensure that the slave map device can respond to the operation of the master device more promptly.
[0056] Track and record the time taken for each rendering operation from the map device, and analyze the historical rendering performance. Specifically, calculate the average rendering time taken over a period of time (such as the past 30 seconds) from the map device. For example, if the historical rendering time takes an upward trend, indicating that the rendering task is becoming heavier, then the rendering time threshold should be appropriately increased. If the historical rendering time takes a downward trend, indicating that the rendering pressure is reduced, then the rendering time threshold should be appropriately lowered to improve the timeliness of the rendering response.
[0057] The slave map device monitors the network delay between the slave device and the master device in real time. If the network delay increases (for example, more than 100ms), the rendering time threshold is appropriately increased to avoid invalid rendering due to network transmission bottlenecks.
[0058] If the network latency decreases or remains stable, the rendering time threshold can be appropriately lowered to ensure that the update operation can be reflected on the slave map device as soon as possible.
[0059] Based on the comprehensive analysis of the above factors, the map device dynamically adjusts the rendering time threshold according to the following formula:
[0060]
[0061] Among them, initial_threshold is the initial threshold, α, β, γ, δ are the weight factors of system load, operating frequency, rendering performance and network status respectively, load_adjustment is the adjustment value of system load threshold, frequency_adjustment is the adjustment value of operating frequency threshold, performance_adjustment is the adjustment value of rendering performance threshold and network_adjustment is the adjustment value of network status threshold. The map device ensures that dynamic_threshold is always between the preset minimum threshold min_threshold and the maximum threshold max_threshold.
[0062] To avoid excessive adjustment of the rendering threshold that affects the user experience, the dynamically adjusted threshold dynamic_threshold is limited to the range of min_threshold and max_threshold. For example, min_threshold can be set to 0.2 seconds and max_threshold can be set to 1.0 seconds.
[0063] Continuously monitor rendering performance, system load, and operation frequency from the map device, and make dynamic feedback adjustments after each rendering operation is completed. According to the current system status and operation conditions, adjust the threshold in real time to optimize the next rendering task, ensuring efficient use of device resources and optimizing user experience.
[0064] Furthermore, by analyzing the user's behavior records in previous map operations, map nodes where the user has stayed for a long time are preferentially selected for rendering.
[0065] The map device regularly records the user's map operation data and builds a history database. Each record entry in the database includes:
[0066] The zoom level of the map zoom_level.
[0067] The center point coordinates center_lat, center_lng are used to identify the specific map location that the user has viewed.
[0068] Cumulative_stay_time is the cumulative time that the user stays at the map node, which is used to measure the user's attention level.
[0069] After each user operation is completed, the system will update the corresponding node record in the database based on the user's stay time.
[0070] The slave map device receives an update operation sequence transmitted by the master device, which includes multiple update nodes, each of which contains the following information:
[0071] The zoom level of the map zoom_level.
[0072] Center point coordinates center_lat, center_lng.
[0073] Layer status layer_status.
[0074] The current stay time, stay_time, is used to indicate the length of time the user stays at the current node on the master device.
[0075] The slave map device first checks each node in the update operation sequence one by one according to the history database. For each update node, the system will filter according to the following conditions:
[0076] Historical stay time: Find the user's historical cumulative stay time at the node (cumulative_stay_time).
[0077] If the historical residence time exceeds the preset threshold value threshold_time, the node is determined to be a node that the user cares about and is preferentially added to the second update sequence.
[0078] Current stay time: If the current stay time of the node stay_time exceeds the preset threshold threshold_time, even if the historical record of the node is insufficient, the node will still be regarded as a valid node and will be processed first.
[0079] For nodes that do not meet the above conditions, the slave map device regards them as low-priority nodes, and the rendering of the nodes is delayed or skipped.
[0080] According to the above screening process, the nodes that meet the conditions are added to the second update sequence. The priority order of nodes in the second update sequence is as follows:
[0081] High priority nodes: nodes that the user history shows as being visited for a long time or frequently.
[0082] Valid nodes: nodes whose stay time in the current operation exceeds the threshold.
[0083] The second update sequence will be arranged in order of node priority to ensure that the nodes that users care about most are rendered first.
[0084] After each rendering operation is completed, the current user's stay data is updated to the history database from the map device, including:
[0085] Update of cumulative stay time: add the current stay time stay_time to the cumulative_stay_time in the historical record.
[0086] If the node is new, a new record entry is created and the cumulative_stay_time is initialized.
[0087] By analyzing the historical data of the user's stay time in previous map operations, map nodes where the user has stayed for a long time or visited frequently are given priority for rendering. After receiving the update operation sequence of the master device, the slave map device dynamically adjusts the priority of each node based on the historical records and current operation time, and only adds valid nodes that meet the preset threshold to the second update sequence. This can effectively optimize the resource utilization of the slave map device, reduce invalid rendering, and improve user experience and the real-time nature of map updates.
[0088] Further, according to the operation sequence and the basic farmland in the current view, nodes consistent with the basic farmland in the current view are preferentially added to the second update sequence.
[0089] First, the basic farmland information within the user's current view range is obtained from the map device through the map API. This information usually includes the main basic farmland or road sections displayed within the current view range.
[0090] Basic farmland information may include the name, location coordinates, polyline data, etc. of the basic farmland, and can be obtained through the basic farmland layer of the GIS system or external data sources (such as navigation services).
[0091] The map device filters the nodes in the update operation sequence according to the basic farmland information within the current view range.
[0092] If the geographic location or center point coordinates of an updated node match the basic farmland information in the current view, it means that the node is associated with the basic farmland that the user is viewing, and it is considered a high priority node.
[0093] The specific matching method may be that the center point of the node is located in the buffer area of a certain basic farmland, or the geographical location of the node is close to the main basic farmland in the current view.
[0094] According to the basic farmland matching results, the map device will prioritize the qualified nodes to be added to the second update sequence. Nodes that match the basic farmland information will be given a higher priority to ensure that these nodes can be rendered first.
[0095] Non-matching nodes are considered low priority nodes and can be rendered later or processed when rendering resources are sufficient.
[0096] Assume that the center point of the map currently viewed by the user is located at (121.4737, 31.2304), and the current view displays two main spots: Spot 1 and Spot 2.
[0097] The slave map device receives a sequence of update operations from the master device, which contains multiple nodes, such as:
[0098] Node 1: zoom level is 12, center point is (121.4737, 31.2304), timestamp is 2024-09-06 14:35:20.
[0099] Node 2: zoom level is 13, center point is (121.4800, 31.2300), timestamp is 2024-09-06 14:35:25.
[0100] For node 1, check whether its center point is close to the spot in the current view (such as spot 1 or spot 2). Since node 1 is near spot 1, the system adds the node to the second update sequence.
[0101] For node 2, it is found that its location does not match the basic farmland map in the current view, so this node will not be processed as a priority.
[0102] According to the generated second update sequence, the system renders node 1 first to ensure that the first street-related area in the user's view can be updated in time. Node 2 is processed late or skipped.
[0103] Furthermore, the overall direction of the node is determined according to the operation sequence, and the nodes that are consistent with the overall direction are preferentially added to the second update sequence. By analyzing the update operation sequence of the master device, the overall direction of the user's movement or zooming in the map operation is determined, and the update nodes that are consistent with the direction are preferentially processed. This method optimizes resource allocation by screening nodes that meet the user's operation direction and preferentially adding them to the second update sequence for rendering, thereby ensuring that the slave map device can respond to the user's operation needs quickly and accurately.
[0104] The slave map device calculates the operation direction of the master device by analyzing the continuous nodes in the update operation sequence. The specific steps are as follows:
[0105] Extract the center point coordinates of consecutive nodes: Extract the geographic center point coordinates of adjacent nodes from the operation sequence to form a set of coordinate point sequences.
[0106] Calculate the displacement vector: For each pair of consecutive nodes, calculate the displacement vector between them, that is, the direction vector from the center point of the previous node to the center point of the next node.
[0107] Determine the overall direction: All displacement vectors are accumulated and averaged to obtain the overall movement direction in the user operation sequence. This direction can be expressed as a unit vector (dir_x, dir_y) to describe the main translation direction of the user in the operation.
[0108] The map device performs direction screening on each node in the update operation sequence based on the calculated overall operation direction. The specific screening method is as follows:
[0109] Calculate node direction vector: For each node, calculate the direction vector between the node and the previous node, which indicates the specific movement direction of the user when operating the node.
[0110] Compare with the overall direction: Compare the direction vector of the node with the overall direction of the operation sequence and calculate the angle or projection between the two. If the direction of the node is consistent or close to the overall direction, the node is determined to be consistent with the overall direction.
[0111] The nodes that are screened out from the map device and are consistent with the overall direction are preferentially added to the second update sequence to ensure that these nodes can be rendered first.
[0112] If the direction of a node is inconsistent with the overall direction, the node is considered a low-priority node and can be delayed or skipped.
[0113] The slave map device performs the map rendering operation step by step according to the generated second update sequence in the order of priority. Nodes consistent with the overall direction will be rendered first to ensure that the main direction in the user operation can be updated and displayed in time.
[0114] For nodes that are not consistent with the overall direction, the map device can decide whether to delay rendering based on the current resource situation.
[0115] As the user's operation changes (such as zooming or panning), the map device can update the overall direction of the operation sequence in real time and dynamically adjust the priority of the rendering node according to the new direction.
[0116] For example:
[0117] Assuming that the user performs continuous panning operations on the map, the operation sequence generated by the master device is as follows:
[0118] Node 1: Center point (121.4737, 31.2304), timestamp 2024-09-06 14:35:20.
[0119] Node 2: Center point (121.4740, 31.2310), timestamp 2024-09-06 14:35:25.
[0120] Node 3: Center point (121.4745, 31.2320), timestamp 2024-09-06 14:35:30.
[0121] By calculating the displacement vectors from node 1 to node 2 and node 2 to node 3, it is found that the overall direction is from south to north (increasing along the latitude direction).
[0122] The map device compares the calculated overall direction with the direction of each node and finds that the directions of nodes 2 and 3 are consistent with the overall direction, so they are added to the second update sequence first.
[0123] Nodes 2 and 3 are rendered first from the map device to ensure that the main direction of the user's panning operation can be updated in time.
[0124] By giving priority to rendering nodes that are consistent with the overall direction, the system can better respond to user operation needs, reduce rendering delays for irrelevant nodes, and increase the update speed of the map.
[0125] This method can adjust the rendering order in real time according to the user's operation mode, ensuring that the map device can respond flexibly in high-frequency interaction scenarios and maintain a smooth user experience.
[0126] On the other hand, the present invention also provides a map dynamic linkage update system, comprising the following modules:
[0127] An acquisition module, used for receiving an update operation sequence transmitted by a master map device from a map device, the sequence comprising a plurality of update nodes, each node comprising a zoom level, a center point coordinate, a layer state and a timestamp of a map;
[0128] A first analysis module, configured to analyze the residence time of each node according to the update operation sequence received from the map device;
[0129] The second analysis module is used to determine that the nodes whose residence time is shorter than a preset threshold are invalid nodes, and the slave device will skip the rendering operation of these nodes;
[0130] A third analysis module is used to screen nodes whose residence time exceeds a preset threshold as valid nodes and add them to the second update sequence;
[0131] The rendering module is used to execute the corresponding map rendering operation according to the generated second update sequence from the device.
[0132] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.
[0133] The present invention does not particularly specify the structure of some modules, which shall be subject to the contents recorded in the prior art. The prior art mentioned in the above background technology section and the specific embodiment section of the present invention can be used as part of the present invention to understand the meaning of some technical features or parameters. The scope of protection of the present invention shall be subject to the contents actually recorded in the claims.
Claims
1. A method for dynamically updating a map, characterized in that: The method comprises the following steps: The slave map device receives an update operation sequence transmitted by the master map device, the sequence comprising a plurality of update nodes, each node comprising a zoom level, a center point coordinate, a layer state and a timestamp of the map; The slave map device analyzes the residence time of each node according to the received update operation sequence; For nodes whose residence time is shorter than the preset threshold, they are determined to be invalid nodes, and the slave device will skip the rendering operation of these nodes; For nodes whose residence time exceeds a preset threshold, they are screened as valid nodes and added to the second update sequence; The slave device performs corresponding map rendering operations according to the generated second update sequence.
2. A method for dynamically updating a map according to claim 1, characterized in that: The slave map device monitors its own system load information in real time, and updates the preset threshold value according to the system load information.
3. A method for dynamically updating a map according to claim 1, characterized in that: The user's behavior records in previous map operations are analyzed, and map nodes where the user has stayed longer than a preset time are preferentially selected to be added to the second update sequence.
4. A method for dynamically updating a map according to claim 1, characterized in that: According to the operation sequence and the current view being basic farmland patch data, nodes consistent with the basic farmland patch data of the current view are preferentially added to the second update sequence.
5. A method for dynamically updating a map according to claim 1, characterized in that: The overall direction of the nodes is determined according to the operation sequence, and nodes that are consistent with the overall direction are preferentially added to the second update sequence.
6. A map dynamic linkage update system, characterized in that: The system includes the following modules: An acquisition module, used for receiving an update operation sequence transmitted by a master map device from a map device, the sequence comprising a plurality of update nodes, each node comprising a zoom level, a center point coordinate, a layer state and a timestamp of a map; A first analysis module, configured to analyze the residence time of each node according to the update operation sequence received from the map device; The second analysis module is used to determine that the nodes whose residence time is shorter than a preset threshold are invalid nodes, and the slave device will skip the rendering operation of these nodes; A third analysis module is used to screen nodes whose residence time exceeds a preset threshold as valid nodes and add them to the second update sequence; The rendering module is used to execute the corresponding map rendering operation according to the generated second update sequence from the device.
7. A map dynamic linkage update system according to claim 6, characterized in that: The slave map device monitors its own system load information in real time, and updates the preset threshold value according to the system load information.
8. A map dynamic linkage update system according to claim 6, characterized in that: The user's behavior records in previous map operations are analyzed, and map nodes where the user has stayed longer than a preset time are preferentially selected to be added to the second update sequence.
9. A map dynamic linkage update system according to claim 6, characterized in that: According to the operation sequence and the current view being basic farmland patch data, nodes consistent with the basic farmland in the current view are preferentially added to the second update sequence.
10. A map dynamic linkage update system according to claim 6, characterized in that: The overall direction of the nodes is determined according to the operation sequence, and nodes that are consistent with the overall direction are preferentially added to the second update sequence.
Citation Information
Patent Citations
Personalized map multi-screen display method and device based on WebGIS environment
CN109086016A
A data display method using multiple maps
CN109829090A
Information point validity identification method, apparatus and device, and storage medium
CN111860503A
Method and device for realizing map synchronous interaction on spliced screen
CN111913633A
Laser map updating method based on grid detection, terminal and computer equipment
CN112380312A
