Electronic map access method, device and system
Technical Field
The present invention relates to the field of information processing technologies, and in particular, to a method, a device, and a system for accessing an electronic map.
Background
The map is a miniature of the real world and is closely related to the daily life of people. The network service provided by the electronic map becomes an extension of the traditional map by virtue of real-time performance, large information amount and rich functions, and simultaneously embodies the practicability and the rapid convenience which cannot be replaced by the traditional map.
With the continuous development of internet technology, electronic maps have become one of the internet services that people often use. The user needs to obtain the required information through the electronic map, and the specific steps comprise:
the first step is as follows: the client sends a map access request to a website server with a map function through a map engine.
The second step is that: after receiving the access request, the website server searches map information including a common point (namely a position point in a map) requested by the client by using locally stored map information, and returns common point coordinates representing the common point in the searched map information and a display identifier displayed on the map by each common point to a map engine of the client.
The third step: after receiving the common point coordinates and the display marks of the common points displayed on the map, a map engine of the client determines the display positions of the common points in the map according to the common point coordinates, loads the display marks of the common points on the corresponding positions of a display interface of the client by calling a Marker function, and displays the electronic map loaded with the common points and the display related icons, characters and the like at the specific positions for a user.
As shown in fig. 1, when a client initiates an access request for "lucky car distribution" to a website server through a map engine, the website server searches map information including the "lucky car distribution" according to a preset map scale, and returns common point coordinates (such as coordinates of lucky car distribution, coordinates of a navy place, coordinates of a grand building, and the like) included in the searched map information and a display identifier of each common point displayed on the map to the map engine of the client.
After receiving the information sent by the website server, the map engine of the client loads and displays the display identifier of the common point according to the coordinates of the common point, so as to obtain the electronic map shown in fig. 1. The electronic map shown in fig. 1 includes a large number of common points, and when a common point is shown in the electronic map according to the coordinates of the common point, the contents of the shown common point include:
the icon is loaded on the electronic map and represents a mark of the position of the common point;
text loaded next to the icon to annotate the descriptive text portion;
an icon frame, a frame loaded on the icon;
a text box, a box loaded on the text;
and rendering a frame, and loading the icon frame and the frame on the text frame, namely the smallest circumscribed rectangle formed by combining the icon frame and the text frame.
With the reduction of the scale of the electronic map and the improvement of the positioning precision of the geographic position, the number of the common points in the map is more and more, and when the number of the common points in the map reaches a certain value, for example, when the number of the common points in the map with a certain area reaches 1000, the electronic map can be considered to need to record a large number of common points.
When the map engine in the client loads the electronic map by using the above method, if the electronic map needs to be loaded according to the coordinates and the display identifiers of a large number of common points, the map engine is limited by the performance of the device due to the excessive amount of data to be processed, and the problem of delayed loading and even failed loading of the electronic map occurs. Meanwhile, with the improvement of the positioning precision of the geographic position, more and more information needs to be loaded in the electronic map, so that the current method for loading the electronic map by the map engine in the client cannot meet the browsing requirement of the user on the electronic map, and other effective methods need to be found to solve the problem.
Disclosure of Invention
The embodiment of the invention provides an electronic map access method, electronic map access equipment and an electronic map access system, which are used for solving the problems that when a user accesses an electronic map, the electronic map response is slow and even a map engine fails to load information when a client loads a large number of common points in the prior art.
An access method of an electronic map, the method comprising:
a rendering server receives an electronic map access request which is initiated by a client and contains a common point identifier;
the rendering server determines a map slice identifier corresponding to the common point identifier in the electronic map access request according to the corresponding relation between the locally stored map slice identifier and the common point identifier;
and the rendering server sends the map slice corresponding to the determined map slice identification and other map slices adjacent to the map slice in the electronic map to the client.
An access method of an electronic map, the method comprising:
the method comprises the steps that a client sends an electronic map access request containing a common point identifier to a rendering server;
the method comprises the steps that a client receives a map slice returned by a rendering server, wherein the map slice is a map slice represented by a map slice identifier corresponding to a common point identifier in an electronic map access request and other map slices adjacent to the map slice in the electronic map according to the corresponding relation between the locally stored map slice identifier and the common point identifier;
and the client combines the received map slices into the electronic map.
An access server of an electronic map, the server comprising:
the receiving module is used for receiving an electronic map access request which is initiated by a client and contains a common point identifier;
the searching module is used for determining a map slice identifier corresponding to the common point identifier in the electronic map access request according to the corresponding relation between the locally stored map slice identifier and the common point identifier;
and the sending module is used for sending the map slice corresponding to the determined map slice identification and other map slices adjacent to the map slice in the electronic map to the client.
An access client of an electronic map, the client comprising:
the request sending module is used for sending an electronic map access request containing the common point identifier to the rendering server;
the receiving module is used for receiving the map slice returned by the rendering server, wherein the map slice is the map slice represented by the map slice identifier corresponding to the common point identifier in the electronic map access request and other map slices adjacent to the map slice in the electronic map according to the corresponding relation between the map slice identifier and the common point identifier stored locally by the rendering server;
and the combination module is used for combining the received map slices into the electronic map.
An electronic map access system, the system comprising:
the rendering server is used for receiving an electronic map access request which is initiated by a client and contains a common point identifier, determining a map slice identifier corresponding to the common point identifier in the electronic map access request according to the corresponding relation between the locally stored map slice identifier and the common point identifier, and sending a map slice corresponding to the determined map slice identifier and other map slices adjacent to the map slice in the electronic map to the client;
and the client is used for initiating the electronic map access request and combining the received map slices into the electronic map.
The invention has the following beneficial effects:
the embodiment of the invention determines the map slice identifier corresponding to the common point identifier requested by the client by the rendering server according to the corresponding relation between the map slice identifier and the common point identifier stored locally, and transmits the map slice represented by the determined map slice identification and other map slices adjacent to the map slice in the electronic map to the client, because the display identification of the common point at the coordinate position is already displayed in the map slice received by the client, the client can directly combine the received map slices into the electronic map, the electronic map is obtained without loading the common point coordinates and the display identification sent by the rendering server, the data processing amount of the client is greatly reduced, even if the electronic map displayed by the client contains massive common points, the client can quickly respond to obtain the electronic map combined by the map slices.
Drawings
FIG. 1 is an electronic map with common point coordinates and display identifiers locally loaded at a client;
FIG. 2 is an electronic map sliced and assembled from maps after gridding by a rendering server;
fig. 3 is a flowchart of an access method of an electronic map according to a first embodiment;
FIG. 4(a) is a schematic of adjacent slices;
FIG. 4(b) is an electronic map of a client assembly;
FIG. 5 is a flowchart of the second embodiment;
fig. 6 is a schematic structural diagram of an access server of an electronic map according to a third embodiment;
fig. 7 is a schematic structural diagram of an access client of an electronic map according to a fourth embodiment;
fig. 8 is a schematic structural diagram of an access system of an electronic map according to a fifth embodiment.
Detailed Description
In order to achieve the purpose of the present invention, embodiments of the present invention provide an electronic map access method, device, and system, where after a rendering server receives an electronic map access request that includes a common point identifier and is initiated by a client, the rendering server determines, according to a correspondence between a locally stored map slice identifier and the common point identifier, a map slice identifier corresponding to the common point identifier requested by the client, and sends a map slice represented by the determined map slice identifier and other map slices adjacent to the map slice in the electronic map to the client, and the client combines the received map slices into an electronic map.
Compared with the prior art, when the client side accesses the electronic map, the client side can acquire the map slices which show the display marks of the common points at the coordinate positions of the common points in the form of pictures from the rendering server, the client side can obtain the electronic map which can be displayed to a user on the display interface of the client side after combining the received map slices, and even if the displayed electronic map contains massive common points, the process of displaying the electronic map by the client side cannot be influenced by the performance of map engine equipment in the client side.
It should be noted that the common points referred to in the embodiments of the present invention indicate points (e.g., buildings) existing on the electronic map.
Before a client side initiates an electronic map access request to a rendering server, the rendering server can preprocess locally stored electronic maps with various scales:
the rendering server may store a plurality of electronic maps in advance, and since each electronic map may include a plurality of common points, the rendering server also stores common point information for each common point. The common point information includes:
a common point identifier for uniquely identifying the common point, such as "1234", "lucky car bond";
common point coordinates such as longitude and latitude coordinates for representing a position of the common point in the map;
and the display identifier is used for representing the display content of the common point in the map.
The display identifier comprises content of an icon and text;
the display identifier also comprises a dimension range of the rendering frame relative to the common point coordinate, the position and the size of the rendering frame can be determined according to the common point coordinate and the relative dimension range, and the common point coordinate is a reference for determining the position and the size of the rendering frame, so the common point coordinate can be called as a reference point of the rendering frame area;
the display identifier further comprises a coordinate size range of the icon frame and the text frame relative to the upper left corner point of the rendering frame, and the positions and the sizes of the icon frame and the text frame can be determined according to the coordinates and the relative size range of the upper left corner point of the rendering frame.
In order to improve the information storage efficiency, the rendering server can perform gridding operation on the electronic map to obtain a plurality of pictures with the same size, namely map slices; after a certain electronic map is subjected to gridding operation, the obtained map slices can be spliced into the electronic map. The map slices after gridding are numbered and marked as slice identifiers, as shown in fig. 2.
And the rendering server renders the display identifier in the common point information to the map slice containing the common point according to the common point coordinate in the common point information represented by the corresponding common point identifier aiming at each map slice, so that the map slice in the rendering server is a picture which already displays the display identifier of the common point at the coordinate position of the common point.
As can be seen from fig. 2, one map slice may include one common point, may also include a plurality of common points, and may not include a common point, and in particular, since a common point includes an icon box, a text box, and a rendering box when being displayed in an electronic map, a situation may also occur in which the rendering box of a common point is divided into different map slices.
After the rendering server gridds the electronic map into a map slice, the rendering server can store the common point information of the common points contained in the map slice by taking the map slice as a unit, and the specific mode is as follows:
the rendering server establishes and stores a corresponding relation between the map slice identifier and the common point identifier according to the common points contained in the map slice, and the common point identifier is a part of common point information and can uniquely represent one common point, so that the common point information represented by the common point identifier corresponding to the map slice identifier, namely the corresponding relation between the map slice and the common point information, can be determined through the corresponding relation.
When the rendering server stores the common point information by taking a map slice as a unit, aiming at a certain common point information, the storage format is as follows:
specifically, when a rendering frame of a common point is divided into different map slices, it is assumed that an icon frame and a text frame of a common point 1111 are divided into two map slices adjacent to each other on the left and right (a map slice identifier on the left is a, and a map slice identifier on the right is B), and at this time, the map slice identifier a and the map slice identifier B both establish a corresponding relationship with 1111; among 1111 common point information corresponding to the map slice identifier a, there is "id": 1111. "pos": { "lng": 116, "lat": 39}, "bounds": [111, 222, 333, 444], "Icon": { "px": 5, "py": 8, "width": 12, "height": 12}, however, the content of "text" is false; among 1111 common point information corresponding to the map slice identifier B, there is "id": 1111. "bounds": [111, 222, 333, 444], "text", however, the contents of "Icon" and "pos" are false.
The embodiments of the present application will be described in detail below with reference to the accompanying drawings.
The first embodiment is as follows:
as shown in fig. 3, a flowchart of an access method of an electronic map according to a first embodiment is shown, where the method includes:
step 101: and the rendering server receives an electronic map access request which is initiated by the client and contains the common point identification.
In the scheme of this step 101, the common point identifier in the electronic map access request initiated by the client may be a numeric identifier similar to "1111" or a character string identifier similar to "good luck automobile fittings".
The rendering server may be a web server having an electronic map and having a map rendering function.
Step 102: and the rendering server determines the map slice identifier corresponding to the common point identifier in the electronic map access request according to the corresponding relation between the locally stored map slice identifier and the common point identifier.
Since the rendering server grids the electronic map into a plurality of map slices during preprocessing, and stores the corresponding relationship between the map slice identifier and the common point identifier, in this step 102, the rendering server may locally search for the map slice identifier corresponding to the common point identifier according to the common point identifier in the electronic map access request, and the map slice represented by the searched map slice identifier is a map slice in the electronic map accessed by the client.
Because the electronic map can be formed by splicing a plurality of map slices, according to a map scale carried in an electronic map access request initiated by a client, a plurality of map slices around the map slice with the slice identifier of 6741.3102 are determined by taking the map scale carried in the electronic map access request as the center, so that the electronic map formed by splicing the determined map slices can be correctly displayed in a display interface of the client by taking the map scale carried in the electronic map access request as the center.
Preferably, after determining the map slices that need to be returned to the client, the rendering server may further determine that the map slices contain common point information of common points.
Still taking the level 13 view level of the electronic map shown in fig. 2 as an example, the rendering server queries that the map slice identifier corresponding to "mansion building" is 6741.3102, and simultaneously determines that the map slice identifier 6741.3102 also corresponds to other common point identifiers: "newsstand" and "permanence of civilian beauty", and further, it can be determined that the common points included in the map slice identified as 6741.3102 are "mansion", "newsstand" and "permanence of civilian beauty".
Step 103: and the rendering server sends the map slice corresponding to the determined map slice identification and other map slices adjacent to the map slice in the electronic map to the client.
The adjacent other map slices refer to: the positions of the map slices corresponding to the determined map slice identifications in the electronic map are in an adjacent relationship, generally refer to the map slices on the upper part, the lower part, the left part and the right part of the determined map slices, and may further include the map slices on the upper left part, the lower left part, the upper right part and the lower right part of the determined map slices according to different viewing ranges of the electronic map, as shown in fig. 4 (a).
In addition, depending on the range of the electronic map that the user needs to view, the adjacent other map slices may be not limited to the map slices in the eight directions described above, and may be a map slice related to drawing a circle on the electronic map with a set value as a radius around a specific map slice.
Step 104: and the client combines the received map slices into the electronic map.
Specifically, when receiving the map slices sent by the rendering server, the client combines the map slices into the electronic map in the order of the slice identifiers in the map slices, as shown in fig. 4 (b).
The scheme of the first embodiment realizes that the rendering server determines the map slice identifier corresponding to the common point identifier requested by the client according to the corresponding relationship between the locally stored map slice identifier and the common point identifier, and sends the map slice represented by the determined map slice identifier and other map slices adjacent to the map slice in the electronic map to the client, because the display identifier of the common point at the coordinate position is already displayed in the map slice received by the client, the client can directly combine the received map slices into the electronic map without loading the common point coordinate and the display identifier sent by the rendering server to obtain the electronic map, thereby greatly reducing the data processing amount of the client and avoiding the electronic map loading delay in the process of locally loading massive common point information by the client, and even the loading failure of the electronic map.
Example two:
in the scheme of the first embodiment of the invention, the rendering server sends the map slices to the client, the client combines the received map slices into the electronic map and displays the electronic map, and a user can conveniently operate the electronic map displayed by the client.
As shown in fig. 5, which is a flowchart of the second embodiment, the method includes the following steps:
step 201: after receiving the map slices sent by the rendering server and combining the map slices into the electronic map, the client acquires the common point information of the common points contained in the received map slice identifiers from the rendering server.
The specific implementation process of this step 201 includes, but is not limited to, the following two ways:
the first mode is as follows:
after the client end is combined into the electronic map, the slice identifiers of all maps contained in the currently displayed electronic map are determined, the determined slice identifiers of the map are sent to the rendering server, and the rendering server is requested to send the common point information represented by the common point identifiers corresponding to the determined slice identifiers of the map to the client end.
For example: the client sends a request message containing a slice identifier to the rendering server as follows: http:// xxx. mapabc. com? tile 6741.3102, 6741.3103, 6741.3104& z 13& rid 782699, where 6741.3102 is a slice id.
The second mode is as follows:
after the client side is combined into the electronic map, the rendering server determines the map slice sent to the client side at this time and sends the common point information of the common points contained in the map slice to the client side.
After receiving the common point information sent by the rendering server, the client can take the map slice as a unit and locally store the common point information.
Step 202: the client monitors a mouse move event, judges whether the mouse is located in a rendering frame area in an electronic map displayed by the client, and if so, executes step 203; otherwise, continuing to monitor the MouseMOVE.
Since the electronic map displayed by the client includes the display identifiers of the multiple common points, that is, the displayed electronic map has rendering frames of the multiple common points, in this step 202, an area occupied by the rendering frame in the electronic map may be referred to as a rendering frame area.
Specifically, in step 202, when the client monitors a mouse displacement event, the step of determining whether the current position of the mouse belongs to any rendering frame area in the electronic map includes:
the first step is as follows: and acquiring the position information of the mouse in the electronic map.
The second step is that: and determining a map slice identifier corresponding to the position information.
The third step: judging whether the position information belongs to the range covered by the common point represented by the common point identifier corresponding to the map slice identifier, if so, determining that the mouse is positioned in a rendering frame area in the displayed electronic map; otherwise, determining that the mouse is not located in the rendering frame area in the displayed electronic map.
Step 203: the client determines common point information represented by a rendering frame area where the mouse is currently located according to the common point information acquired from the rendering server, and determines whether coordinates of a common point (i.e., coordinates of a reference point of the rendering frame area) in the common point information exist, if so, the step 205 is executed; otherwise, step 204 is performed.
In the scheme of this step 203, the client may first determine a map slice corresponding to a position in the rendering frame area where the mouse is currently located, and then determine common point information of a common point represented by the rendering frame area where the mouse is currently located according to a corresponding relationship between the map slice identifier and the common point identifier.
If the coordinate of the reference point in the common point information of the common point represented by the rendering frame area where the mouse is currently located exists, the current position of the mouse and the reference point of the rendering frame area are in the same map slice; otherwise, the current position of the mouse and the reference point of the rendering frame area are not in the same map slice.
Step 204: and the client determines the reference point of the rendering frame area from other map slices adjacent to the map slice according to the map slice where the mouse is currently located.
The adjacent map slices refer to the map slices which are used for splicing the electronic map and are positioned on the left, the right, the upper and the lower parts of the map slices in position.
Specifically, when it is determined that the position of the current rendering frame area of the mouse is not in the same map slice as the reference point of the rendering frame area, the method for determining the reference point of the rendering frame area includes:
the first step is as follows: the client reads a first common point identifier, wherein the first common point identifier is a common point identifier corresponding to a rendering frame area determined in a map slice where the mouse is located currently.
The second step is that: and the client reads the common point information with the same identification as the first common point identification from the adjacent map slice.
The third step: and the client acquires the coordinate of the reference point of the rendering frame area where the mouse is currently positioned from the read common point information.
Step 205: the client determines a reference point of a rendering frame area where the mouse is located currently, and generates a covering layer covering the rendering frame area according to the reference point and the size of the rendering frame area.
In this step 205, the overlay layer has operability, where the size of the overlay layer is the same as the size of the rendering frame where the mouse is currently located, and changes with the change of the size of the rendering frame to which the mouse is shifted. The attribute information of the overlay layer may be, but is not limited to, a transparent rectangular frame.
Specifically, the client calls a Marker function once to generate an overlay layer of the rendering frame area according to the determined reference point and the size of the rendering frame area.
And when the client determines that the mouse is displaced from one rendering frame area to another rendering frame area, the client moves the generated position of the coverage layer according to the reference point of the rendering frame area to which the mouse is most recently displaced. That is to say, the position of the overlay layer may move with the change of the rendering frame area where the mouse is located.
Step 206: after generating a coverage layer covering a rendering frame area where a mouse is currently located, a client monitors whether an operation aiming at the coverage layer exists currently; if yes, go to step 207; otherwise, the monitoring is continued.
The monitored operation may be whether a Click event for the overlay layer occurs with the mouse, and if so, it is determined that there is an operation for the overlay layer; otherwise, it indicates that there is no operation for the overlay layer.
Step 207: and the client initiates a query request to the local or through an API, wherein the query request contains the determined common point information.
In this step 207, when the client monitors the Click event, it initiates a query request containing common point information, and obtains related information corresponding to the common point information carried in the query request, where the common point information carried in the query request is an identifier or a common point coordinate of a common point covered by the coverage layer.
The related information refers to information loaded in the electronic map and associated with common point information, such as: position information, traffic information, public transportation information, surrounding entertainment information, etc. related to a certain general point.
Specifically, if the client locally stores the corresponding relationship between each piece of common information and the relevant information of the common point information, when the client monitors the Click event of the current mouse for the overlay layer, the relevant information corresponding to the locally stored common point information is loaded on the overlay layer and displayed to the user.
If the client does not locally store the corresponding relation between each common information and each related information, when the client monitors the Click event of the current mouse aiming at the overlay layer, a query request containing the common point information is initiated, information interaction is carried out with a corresponding operator server through an API (application programming interface), the related information corresponding to the determined common point information is obtained, and the determined related information is loaded on the overlay layer by a local map engine of the client.
Preferably, after the client sends the electronic map access request to the rendering server, the rendering server determines that the common point information is limited according to the target information carried in the received access request, the rendered electronic map has a limited map range, so that when the client monitors the drag event of the mouse on the currently displayed electronic map, that is, when the electronic map displayed by the client to the user changes (for example, when the currently displayed electronic map is dragged upwards by the mouse, a part of the map slice originally displayed on the upper portion of the electronic map is not displayed any more, and a non-existent map slice needs to be displayed on the lower portion of the electronic map after being dragged), at this time, the client can delete the map slice which is not displayed any more and the corresponding common point information, and notify the rendering server that the newly added map slice and the corresponding common point information are needed.
And after receiving the notification of the client, the rendering server generates the map slice to be displayed after the dragging and the corresponding common point information to the client, the client uses the newly received map slice as a part of the electronic map displayed after the dragging and stores the common point information represented by the common point identifier corresponding to the identifier of the newly received map slice, and then the scheme of the second embodiment can be repeatedly executed so that the user can conveniently operate the new electronic map displayed after the dragging.
Specifically, if the user wants to view the electronic map of other scales, a new electronic map access request is initiated to the client, and the parameters and the target information of the scales which the user wants to view are carried in the new electronic map access request. The client sends the electronic map access request to the rendering server, the rendering server sends a new electronic map to the client again according to the scheme of the first embodiment, and the client can also execute the operation of the second embodiment on the newly received electronic map.
Example three:
as shown in fig. 6, which is a schematic structural diagram of an access server of an electronic map according to a third embodiment, the server includes: a receiving module 61, a searching module 62 and a sending module 64. Wherein,
the receiving module 61 is used for receiving an electronic map access request which is initiated by a client and contains a common point identifier;
the searching module 62 is configured to determine, according to a correspondence between a locally stored map slice identifier and a common point identifier, a map slice identifier corresponding to the common point identifier in the electronic map access request;
and a sending module 64, configured to send the map slice corresponding to the determined map slice identifier and other map slices adjacent to the map slice in the electronic map to the client.
Preferably, the server further comprises:
the dividing module 65 is configured to perform meshing operation on the stored electronic map to obtain a plurality of map slices;
the determining module 66 is configured to establish a corresponding relationship between a map slice identifier and a common point identifier according to common points included in a map slice, where common point information corresponding to the common point identifier includes common point coordinates in an electronic map and a display identifier displayed on the electronic map by each common point;
and the rendering module 63 is configured to render the display identifier in the common point information to the map slice including the common point according to the common point coordinate in the common point information represented by the corresponding common point identifier.
Specifically, the sending module is further configured to send, to the client, common point information of common points included in each map slice sent to the client.
Example four:
as shown in fig. 7, which is a structural diagram of an access client of an electronic map according to a fourth embodiment, the client includes: a request sending module 71, a receiving module 72 and a combining module 73. Wherein,
a request sending module 71, configured to send an electronic map access request including a common point identifier to a rendering server;
a receiving module 72, configured to receive a map slice returned by the rendering server, where the map slice is a map slice represented by a map slice identifier corresponding to a common point identifier in the electronic map access request and is determined by the rendering server according to a correspondence between the locally stored map slice identifier and the common point identifier, and other map slices adjacent to the map slice in the electronic map;
and a combining module 73 for combining the received map slices into an electronic map.
Specifically, the receiving module 72 is further configured to, after receiving the map slice, obtain, from the rendering server, common point information of common points included in the received map slice, where the common point information includes common point coordinates in the electronic map and a display identifier that each common point displays on the electronic map.
Preferably, the client further comprises: a listening module 74, a determining module 75, and a querying module 76. Wherein,
a monitoring module 74, configured to monitor a mouse displacement MouseMove event;
the judging module 75 is configured to judge whether the mouse is located in a rendering frame area in the electronic map displayed by the client;
and the query module 76 is configured to, when the determination result of the determination module is yes, determine, according to the received common point information, common point information indicated by the rendering frame area where the mouse is currently located, and query, locally or through an application interface API, related information corresponding to the determined common point information.
Specifically, the query module 76 is specifically configured to generate an overlay layer covering a rendering frame area where the mouse is currently located, and monitor whether there is an operation on the overlay layer, and if so, initiate a query request to a local area or through an API, where the query request includes the determined common point information.
The query module 76 is specifically configured to determine a reference point of a rendering frame area where the mouse is currently located, and generate a coverage layer covering the rendering frame area according to the reference point and the size of the rendering frame area.
The query module 76 is further configured to determine, when the position in the rendering frame area where the mouse is currently located is not in the same map slice as the reference point of the rendering frame area, a map slice to which the position in the rendering frame area where the mouse is currently located belongs, and determine the reference point of the rendering frame area from the map slices adjacent to the determined map slice.
Preferably, the client further comprises: and an adjustment module 77. Wherein,
an adjusting module 77, configured to determine that, when the mouse is shifted from one rendering frame area to another rendering frame area, the client moves the generated position of the overlay layer according to the reference point of the rendering frame area to which the mouse is most recently shifted, and adjusts the generated size of the overlay layer according to the size of the rendering frame area to which the mouse is most recently shifted.
Example five:
as shown in fig. 8, which is a schematic structural diagram of an access system of an electronic map according to a fifth embodiment of the present invention, the system includes: a rendering server 81 and a client 82. Wherein,
the rendering server 81 is configured to receive an electronic map access request including a common point identifier initiated by a client, determine a map slice identifier corresponding to the common point identifier in the electronic map access request according to a correspondence between a locally stored map slice identifier and the common point identifier, and send a map slice corresponding to the determined map slice identifier and other map slices adjacent to the map slice in the electronic map to the client;
and the client 82 is used for initiating the electronic map access request and combining the received map slices into the electronic map.
Specifically, the rendering server 81 is further configured to perform a meshing operation on the locally stored electronic map to obtain a plurality of map slices, and establish a corresponding relationship between a map slice identifier and a common point identifier according to common points included in the map slices, where common point information corresponding to the common point identifier includes common point coordinates in the electronic map and a display identifier displayed on the electronic map by each common point.
The rendering server 81 is further configured to render, for each map slice, the display identifier in the common point information to the map slice including the common point according to the common point coordinate in the common point information indicated by the corresponding common point identifier.
The rendering server 81 is further configured to send common point information that each map slice sent to the client includes common points to the client.
The client 82 is configured to obtain, from the rendering server, common point information of common points included in the received map slice, where the common point information includes common point coordinates in the electronic map and a display identifier displayed on the electronic map by each common point.
The client 82 is further configured to monitor a mouse displacement event, determine whether the mouse is located in a rendering frame area in the electronic map displayed by the client, if so, determine, according to the received common point information, common point information represented by the rendering frame area where the mouse is currently located, and query, locally or through an application interface API, related information corresponding to the determined common point information.
The client 82 is specifically configured to determine a reference point of a rendering frame area where the mouse is currently located, and generate a covering layer covering the rendering frame area according to the reference point and the size of the rendering frame area.
The client 82 is specifically configured to generate a coverage layer covering a rendering frame area where the mouse is currently located, and monitor whether an operation is performed on the coverage layer, if yes, initiate a query request to a local or through an API, where the query request includes the determined common point information.
The client 82 is specifically configured to determine a map slice to which a position in the rendering frame area where the mouse is currently located belongs when the position in the rendering frame area where the mouse is currently located is not in the same map slice as the reference point of the rendering frame area, and determine the reference point of the rendering frame area from the map slices adjacent to the determined map slice.
The client 82 is further configured to, when determining that the mouse is displaced from one rendering frame area to another rendering frame area, move the position of the generated overlay layer according to the reference point of the rendering frame area to which the mouse is most recently displaced, and adjust the size of the generated overlay layer according to the size of the rendering frame area to which the mouse is most recently displaced.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.