JP7634465B2 - Map information creation device, map display system, and map information creation program - Google Patents

Description

This disclosure relates to a map information creation device, a map display system, and a map information creation program that create map information to be displayed.

In infrastructure facilities such as power system facilities, facilities are managed by displaying utility poles and other geographical features on a map. Systems for managing such infrastructure facilities use client terminals such as PCs (Personal Computers) and tablets. These client terminals are operated by facility work supervisors, field workers, etc. to access a server and display geographical features on a map based on map information sent from the server.

For example, when a client terminal displays a system diagram used in the power industry, it displays various facilities managed by the power company, such as utility poles and wires. However, when a client terminal attempts to display a wide-area system diagram on the screen, it needs to display a large number of facilities, which can take a long time to process and cause the user to wait. For this reason, when displaying a map on a client terminal, it is desirable to display a detailed map with a small processing load.

The graphic creation and display device described in Patent Document 1 quickly displays small-scale maps by thinning out the graphic data corresponding to the graphic type data set for each scale from the entire graphic data.

Japanese Patent Application Publication No. 11-095974

However, the technology in Patent Document 1 has the problem that as the amount of graphic data increases, the processing load when displaying a map increases, and it is not always possible to display a detailed map within the desired processing load.

The present disclosure has been made in consideration of the above, and aims to provide a map information creation device that can create map information for displaying a detailed map within a desired processing load.

In order to solve the above-mentioned problems and achieve the object, a map information creation device of the present disclosure includes a communication unit that receives a map display request from a terminal, in which at least one of a display area and a scale of an infrastructure facility on a map is specified, and a map information generation unit that creates map information for displaying a thinned map in which some of the features included in the map are thinned, based on the map display request. The map information generation unit acquires, based on the map display request, information on the features included in the display area as range feature information from a first database that stores feature information, acquires thinning information corresponding to the features included in the range feature information from a second database that stores thinning information that sets whether each feature is to be displayed on the thinned map, as request thinning information, creates map information using the range feature information and the request thinning information , and the communication unit transmits the map information to the terminal.

The map information creation device disclosed herein has the advantage of being able to create map information for displaying a detailed map within a desired processing load.

FIG. 1 is a diagram showing a configuration of a map display system according to an embodiment; FIG. 1 is a diagram for explaining an overview of a thinning process performed by a server according to an embodiment; FIG. 1 is a diagram showing a configuration of a server included in a map display system according to an embodiment; FIG. 1 is a diagram showing a configuration of a client terminal included in a map display system according to an embodiment; FIG. 1 is a diagram for explaining a registration process of update thinning information registered by a map display system according to an embodiment; 1 is a flowchart showing a registration process procedure of update thinning information registered by a map display system according to an embodiment; FIG. 1 is a diagram for explaining a map display process of a map displayed by a map display system according to an embodiment; 1 is a flowchart showing a map display process procedure of a map displayed by a map display system according to an embodiment; A flowchart showing a registration process procedure of a thinned feature registered by a server according to an embodiment. FIG. 11 is a diagram for explaining a first process performed by a server according to an embodiment to perform a thinning-out determination; FIG. 11 is a diagram for explaining a second process performed by the server according to the embodiment to perform thinning determination; FIG. 11 is a diagram for explaining a third process performed by the server according to the embodiment to perform thinning determination; FIG. 11 is a diagram for explaining a fourth process performed by the server according to the embodiment to perform thinning determination; FIG. 13 is a diagram for explaining a fifth process performed by the server according to the embodiment to perform thinning determination; FIG. 1 is a diagram for explaining a map area that is set when the server according to the embodiment creates update thinning information; FIG. 1 is a diagram illustrating a configuration example of a processing circuit included in a server according to an embodiment when the processing circuit is realized by a processor and a memory; FIG. 1 is a diagram illustrating an example of a processing circuit in a server according to an embodiment, in which the processing circuit is configured with dedicated hardware;

The map information creation device, map display system, and map information creation program according to the embodiments of the present disclosure are described in detail below with reference to the drawings.

Embodiment
1 is a diagram showing a configuration of a map display system according to an embodiment. The map display system 1 includes a server 10 which is a map information creation device, one or more client terminals 20 which are map display devices, a feature DB (DataBase) 60, and a thinning information DB 40. The feature DB 60 is a first database, and the thinning information DB 40 is a second database.

The map display system 1 is a system that displays a map of infrastructure facilities such as power system facilities on the client terminal 20. The map display system 1 displays a map with as much detail as possible while keeping the processing load when displaying the map below a specific value by thinning out certain features according to the scale, display area, etc. In other words, the map display system 1 reduces the processing load when displaying a wide-area system map, improving the user experience.

The server 10 is capable of communicating with the client terminal 20 via a communication network such as the Internet. The server 10 is also connected to a feature DB 60 and a thinning information DB 40. At least one of the feature DB 60 and the thinning information DB 40 may be located within the server 10.

The server 10 is a web server such as a geographic information system (GIS) server. The server 10 registers edited feature information (feature editing information 31, described later) sent from the client terminal 20 in the feature DB 60. The server 10 also acquires feature information corresponding to the feature editing information 31 (updated feature information 32, described later) from the feature DB 60. The server 10 creates information indicating which features on the map should be thinned out (updated thinning information 33, described later) based on the updated feature information 32, and registers this information in the thinning information DB 40.

The features in the embodiment include utility poles, transformers, switches, and electric wires. Of these features, utility poles, transformers, and switches are point features, and electric wires are line features. In other words, point features include at least one of utility poles, transformers, and switches, and line features include electric wires. Line features are features that connect point features together.

When the server 10 receives a request to display a map from the client terminal 20 (a map display request 51, described later), the server 10 creates map information (map information 56, described later) corresponding to the map display request 51. The server 10 creates the map information 56 using the feature DB 60 and the thinning information DB 40.

The server 10 of the embodiment creates map information 56 based on the priority of thinning out features to display as much detailed information as possible while keeping the processing load when displaying a map within a desired processing load. The server 10 reduces the processing load when displaying a map by thinning out specific features based on the priority of thinning out features. The server 10 transmits the created map information 56 to the client terminal 20. The client terminal 20 is a PC, tablet, smartphone, etc. The client terminal 20 displays a map 25 corresponding to the map information 56.

The map 25 displayed by the client terminal 20 is a map corresponding to the map display request 51. In the map 25, point features are shown as dots, and line features are shown as lines. In the map 25 displayed by the client terminal 20, some of the features have been thinned out. That is, in the map 25, certain point features are not shown, and certain line features are simplified. In this way, the map 25 is a thinned out map in which some of the features included in the map before thinning out (hereinafter referred to as the original map) have been thinned out. The original map is a map (an unthinned map) in which all features are arranged on a background map described below.

When a user edits information about features included in the original map of map 25 using client terminal 20, client terminal 20 creates feature editing information 31 corresponding to the editing results and transmits it to server 10. As a result, server 10 registers feature editing information 31 in feature DB 60.

The client terminal 20 stores a map (background map) that serves as the background of the original map, and creates feature editing information 31 that associates coordinates on this background map with information about features displayed at those coordinates. The background map is a map from which all features have been deleted from the original map. Positions on the background map correspond to positions on the Earth (latitude and longitude). In other words, the background map is a map in which at least latitude and longitude are specified. The background map may include roads, buildings, mountains, rivers, and the like. The user specifies a position (coordinates) on the background map and then edits the information about the feature at that position. The coordinates on the background map, the coordinates on the original map, and the coordinates on the thinned map are the same coordinates.

The feature DB 60 stores overall feature information (overall feature information 81, described later), which is feature information on the entire feature, and the original map. The feature DB 60 may store a background map instead of the original map. The overall feature information 81 is updated by the feature editing information 31. That is, the server 10 updates the portion of the overall feature information 81 stored in the feature DB 60 that corresponds to the feature editing information 31 by the feature editing information 31.

When the server 10 registers the feature editing information 31, it acquires the updated feature information 32 corresponding to this feature editing information 31, and creates the updated thinning information 33 using the updated feature information 32. Specifically, the server 10 divides the map 25 into multiple map areas, and creates the updated thinning information 33 for each map area. The server 10 creates the updated thinning information 33 for each map area for all scales that can be set on the map 25. Note that when only a specific map area in the map 25 is updated, the server 10 creates the updated thinning information 33 for the updated map area. The server 10 registers the updated thinning information 33 in the thinning information DB 40.

The thinning information DB 40 stores overall thinning information (overall thinning information 82 described later), which is thinning information for the entire feature. The overall thinning information 82 includes a list of identification information for the features to be thinned (feature identification information 54 described later). The overall thinning information 82 is updated by the updated thinning information 33. That is, the server 10 updates the portion of the overall thinning information 82 stored in the thinning information DB 40 that corresponds to the updated thinning information 33 with the updated thinning information 33.

When a map display request 51 is sent from the client terminal 20, the server 10 uses the feature DB 60 and the thinning information DB 40 to create a thinned map 25 and transmits it to the client terminal 20.

The client terminal 20 receives the map 25 corresponding to the map display request 51 from the server 10 and displays it. This allows the map display system 1 to display a map as detailed as possible on the client terminal 20 while suppressing the display processing load below a specific value.

Here, an overview of the thinning process performed by the server 10 will be described. FIG. 2 is a diagram for explaining an overview of the thinning process performed by the server according to the embodiment. The server 10 creates maps 41 to 46 by thinning out specific features according to the scale of the map on which the features are displayed, the size of the display area, and the like.

Map 41 is a part of the original map before thinning, and includes point features 70 and line features 80. Map 41 shows the arrangement of point features 70 and line features 80. Server 10 creates map 46 by thinning out specific features from map 41 so that the processing load for display is below a specific value and as many features as possible can be displayed. In this case, server 10 decides which features to thin out based on the thinning priority of each feature. That is, server 10 thins out features in order of highest thinning priority until the processing load for display is below a specific value.

The priority of thinning is high when features can be thinned while maintaining the overview of the original map. The overview of the original map is easily maintained by retaining branching points of line features 80, end points of point features 70, and the like contained in the original map. Therefore, branching points of line features 80, end points of point features 70, and the like contained in the original map have a low priority for thinning.

The server 10 creates a map 46 by thinning out specific point features 70 and line features 80 from the map 41 and simplifying specific line features 80. When simplifying specific line features 80, the server 10 reconstructs the line features 80 so that the connections between the point features 70 that were not thinned are maintained. This enables the server 10 to display on the client terminal 20 a number of features that correspond to the processing load of the display while maintaining the overview of the original map. Information indicating which features on the map 41 are to be thinned out is updated thinning information 33, and is created by the server 10.

Figure 3 is a diagram showing the configuration of a server provided in the map display system according to the embodiment. The server 10 has a communication unit 11, a registration unit 12, and a map information generation unit 13.

The communication unit 11 communicates with the client terminal 20. When the communication unit 11 receives feature editing information 31 from the client terminal 20, it sends the received feature editing information 31 to the registration unit 12.

Feature editing information 31 is information that indicates the editing content of a feature. In other words, feature editing information 31 indicates the editing result of the feature information. Feature editing information 31 includes feature identification information 54 for identifying the feature, the position of the feature changed by the user, and the attributes of the feature changed by the user. The client terminal 20 is capable of receiving an instruction to create feature editing information 31 (an instruction to edit the feature information) from the user while displaying the original map or map 25.

The client terminal 20 creates feature editing information 31 by adding features, deleting features, changing the location of features, changing the attributes of features, etc., in accordance with editing instructions from the user. The attributes of a feature include, for example, information indicating whether the feature is normal or abnormal, whether there has been a power outage at the feature, the date the feature was installed, the date the feature was inspected, and the results of inspection of the feature.

When the communication unit 11 receives a map display request 51 from the client terminal 20, it sends the received map display request 51 to the registration unit 12. The map display request 51 is information for requesting map information 56 used to display the map 25. The map display request 51 includes the scale (scale information 85 described later) and area (display area) requested to be displayed as the map 25. That is, the client terminal 20 transmits to the server 10 a map display request 51 indicating the scale and area specified by the user. Note that once one of the scale and area requested to be displayed as the map 25 is determined, the other can be inferred, so it is sufficient that the map display request 51 includes at least one of the scale and area requested to be displayed as the map 25.

The user specifies the center coordinates and scale of the area that the user wants to display as map 25 by displaying the original map on the client terminal 20 with the area and scale that the user wants to display. The center coordinates of the area of the original map that the user has displayed on the client terminal 20 are the center coordinates of the area that the user wants to display as map 25. In addition, the scale of the original map that the user has displayed on the client terminal 20 is the scale of the map 25 that the user wants to display.

The feature editing information 31 or the map display request 51 may include information (layer information) specifying the type of feature to be displayed, or information specifying the attributes of the feature to be displayed. The layer information is information specifying the type of feature, such as utility poles, power lines, switches, and transformers. The layer information may specify the type of feature to be displayed, or may specify the type of feature not to be displayed. The information specifying the attributes of the feature to be displayed may specify, for example, features in an abnormal state, features in a normal state, etc.

The communication unit 11 also transmits the map information 56 created by the map information generation unit 13 to the terminal that transmitted the map display request 51, i.e., the client terminal 20. The map information 56 is information for displaying the map 25 on which the features have been thinned out.

The registration unit 12 registers the feature editing information 31 in the feature DB 60. Specifically, the registration unit 12 sends an update instruction to the feature DB 60 for the overall feature information 81, which is the overall information of the feature, based on the changed parts of the feature indicated by the feature editing information 31. This updates the overall feature information 81 stored in the feature DB 60. The overall feature information 81 includes position information (coordinates on the original map) of features such as utility poles, electric wires, switches, and transformers, feature attribute information, feature identification information 54, and the like. The feature identification information 54 is information for identifying features, and unique information is assigned to each feature.

The registration unit 12 obtains updated feature information 32 corresponding to the feature editing information 31 from the feature DB 60. That is, the registration unit 12 extracts updated feature information 32 indicating information on updated features from the overall feature information 81. The updated feature information 32 is part of the feature information included in the overall feature information 81. Therefore, the updated feature information 32 includes location information of features such as utility poles, electric wires, switches, and transformers, feature attribute information, feature identification information 54, etc.

The registration unit 12 creates the updated thinning information 33 based on the updated feature information 32. The registration unit 12 registers the created updated thinning information 33 in the thinning information DB 40. The updated thinning information 33 is information indicating which features are to be thinned (not displayed on the screen) for each scale. That is, the updated thinning information 33 indicates whether each feature is to be thinned for each scale. In the updated thinning information 33, for example, a list of identification information of features to be thinned is stored for each scale and for each area. The registration unit 12 creates the updated thinning information 33 in which whether or not to display a feature is set for each feature and for each scale so that the processing load of the display is equal to or less than a specific value. In this embodiment, a case where the scale is changed stepwise will be described, but the scale may be changed continuously. That is, an arbitrary scale may be set for the map 25. When the scale is changed continuously, the server 10 determines the features to be thinned while changing the scale. During this determination process, the server 10 determines up to what scale each feature should be displayed, and when determining whether or not to display it, it determines whether each feature is subject to thinning based on whether the current scale being requested is larger than the scale at which it should be displayed. This allows the server 10 to determine whether each feature is subject to thinning for each scale, even when the scale is changed continuously.

The map information generation unit 13 creates a request to acquire feature information (range feature acquisition request 52, described later) based on the map display request 51. The range feature acquisition request 52 is instruction information that requests feature information (range feature information 53, described later) for the area specified in the map display request 51.

The range feature information 53 is information about features located in the area specified in the range feature acquisition request 52. The range feature information 53 is part of the feature information included in the overall feature information 81. Therefore, the range feature information 53 includes location information (coordinates on the original map) of features such as utility poles, power lines, switches, and transformers, feature attribute information, feature identification information 54, etc.

The map information generation unit 13 sends the range feature acquisition request 52 to the feature DB 60, and reads out the range feature information 53 corresponding to the range feature acquisition request 52 from the overall feature information 81 stored in the feature DB 60.

The map information generating unit 13 obtains thinning information (request thinning information 55, described later) corresponding to the map display request 51 from the thinning information DB 40 based on the scale information 85 included in the map display request 51, the feature identification information 54 included in the range feature information 53 obtained from the feature DB 60, and the original map obtained from the feature DB 60.

The feature identification information 54 included in the range feature information 53 is identification information of features located in the area specified in the map display request 51. The request thinning information 55 acquired by the map information generation unit 13 from the thinning information DB 40 is thinning information corresponding to the scale information 85 and area included in the map display request 51. The scale information 85 is information on the scale specified in the map display request 51, and the client terminal 20 displays the map 25 at the scale indicated by the scale information 85. The request thinning information 55 includes a list of feature identification information 54 of the features to be thinned.

The map information generating unit 13 creates map information 56 corresponding to the map 25 using the range feature information 53, the request thinning information 55, and the original map. The map information 56 includes feature location information, feature attribute information, feature identification information 54, and the like. The map information generating unit 13 creates map information 56 corresponding to the map 25 by thinning out the features in the range feature information 53 that are set to be thinned out in the request thinning information 55. That is, the map information generating unit 13 thins out the point features 70 and the line features 80 using the request thinning information 55, and reconstructs the line features 80 at the locations where the point features 70 have been thinned out. In this case, the map information generating unit 13 reconstructs the line features 80 so that the connection relationships between the point features 70 that have not been thinned out are maintained. That is, the map information generating unit 13 reconstructs the line features 80 so that point features 70 that were connected via one or more line features 80 in the original map are still connected via the line features 80 after reconstruction.

Figure 4 is a diagram showing the configuration of a client terminal provided in a map display system according to an embodiment. The client terminal 20 has an input unit 21, an editing unit 22, a communication unit 23, and a display unit 24.

The input unit 21 accepts instructions from the user and sends them to the editing unit 22. The instructions that the input unit 21 accepts from the user include an instruction to create feature editing information 31 (an instruction to edit features), an instruction to send feature editing information 31, an instruction to create a map display request 51 (an instruction to display map 25), an instruction to send the map display request 51, etc.

When the editing unit 22 receives an instruction to create feature editing information 31 from the input unit 21, it edits the feature information in accordance with the instruction to create the feature editing information 31. The editing unit 22 creates the feature editing information 31 while displaying the original map of the map 25, the feature editing information 31, etc. on the display unit 24.

When the editing unit 22 receives an instruction to create a map display request 51 from the input unit 21, the editing unit 22 creates the map display request 51 according to the instruction. The editing unit 22 creates the map display request 51 while displaying the map display request 51 on the display unit 24.

When the editing unit 22 receives an instruction to send feature editing information 31 from the input unit 21, it sends the created feature editing information 31 to the communication unit 23. In addition, when the editing unit 22 receives an instruction to send a map display request 51 from the input unit 21, it sends the created map display request 51 to the communication unit 23.

The communication unit 23 transmits feature editing information 31, map display requests 51, and the like to the server 10. The communication unit 23 also receives map information 56 from the server 10 and sends the received map information 56 to the display unit 24.

The display unit 24 is equipped with a display device such as an LCD monitor, and displays the map 25 corresponding to the map information 56. The display unit 24 also displays the original map of the map 25, the feature editing information 31, the map display request 51, etc., according to instructions from the editing unit 22.

Figure 5 is a diagram for explaining the registration process of update thinning information registered by the map display system according to the embodiment. Figure 6 is a flowchart showing the registration process procedure of update thinning information registered by the map display system according to the embodiment.

The editing unit 22 of the client terminal 20 edits the information about the features in accordance with operations from the user. The communication unit 23 of the client terminal 20 transmits feature editing information 31 indicating the results of editing the features to the server 10 (step ST1).

The communication unit 11 of the server 10 receives the feature editing information 31. The registration unit 12 of the server 10 registers the feature editing information 31 in the feature DB 60 (step ST2). Specifically, the registration unit 12 of the server 10 registers the feature editing information 31 in the overall feature information 81 by transmitting the feature editing information 31 to the feature DB 60. In other words, the registration unit 12 of the server 10 updates the overall feature information 81 in the feature DB 60 based on the feature editing information 31.

The registration unit 12 of the server 10 acquires the updated feature information 32 from the feature DB 60 (step ST3). In this case, the registration unit 12 of the server 10 acquires the updated feature information 32 including not only information on the changed features but also information on the area in which the changed features exist. The updated feature information 32 acquired by the registration unit 12 of the server 10 from the feature DB 60 corresponds to the feature editing information 31 registered in the feature DB 60.

The registration unit 12 of the server 10 determines thinned features, which are features to be thinned, based on the acquired updated feature information 32 (step ST4). The registration unit 12 of the server 10 creates updated thinning information 33 corresponding to the determined thinned features. In this way, the registration unit 12 of the server 10 acquires updated feature information 32 including information on the changed features and information on the area in which the changed features exist, and recalculates new thinned features. The registration unit 12 of the server 10 registers the generated updated thinning information 33 in the thinning information DB 40 (step ST5).

The registration unit 12 may execute the aggregation process (the process of sending the feature editing information 31 to the feature DB 60) by batch processing. In this case, the feature editing information 31 of the newly added feature is not sent to the feature DB 60 until the batch processing. Therefore, the newly added feature is displayed as it is on the map 25 until the batch processing. The registration unit 12 may also execute the update process of the update thinning information 33 (the process of registering the update thinning information 33 in the thinning information DB 40) by batch processing. In this case, the registration unit 12 does not obtain the update feature information 32 corresponding to the feature editing information 31 of the newly added feature from the feature DB 60 until the batch processing. The registration unit 12 reads out the update feature information 32 collectively during the batch processing and updates the update thinning information 33 collectively.

Figure 7 is a diagram for explaining the map display process of the map displayed by the map display system according to the embodiment. Figure 8 is a flowchart showing the map display process procedure of the map displayed by the map display system according to the embodiment.

The editing unit 22 of the client terminal 20 creates a map display request 51 in accordance with operations from the user. This map display request 51 includes scale information 85, information indicating a specific area (area to be displayed) within the map 25, and the like.

The communication unit 23 of the client terminal 20 sends a map display request 51 to the server 10 (step ST11). The map information generation unit 13 of the server 10 creates a range feature acquisition request 52 based on the map display request 51. The map information generation unit 13 of the server 10 sends the range feature acquisition request 52 to the feature DB 60 (step ST12).

The map information generation unit 13 of the server 10 sends the range feature acquisition request 52 to the feature DB 60, and acquires the range feature information 53 corresponding to the range feature acquisition request 52 from the overall feature information 81 stored in the feature DB 60 (step ST13).

The map information generating unit 13 of the server 10 transmits the scale information 85 included in the map display request 51 and the feature identification information 54 included in the range feature information 53 to the thinning information DB 40 (step ST14). As a result, the map information generating unit 13 of the server 10 obtains the request thinning information 55 corresponding to the scale information 85 and the feature identification information 54 from the overall thinning information 82 stored in the thinning information DB 40 (step ST15).

The map information generation unit 13 of the server 10 creates map information 56 corresponding to the map 25 using the range feature information 53, the request thinning information 55, and the original map (step ST16). The communication unit 11 of the server 10 transmits the map information 56 to the client terminal 20 (step ST17). The communication unit 23 of the client terminal 20 receives the map information 56. Then, the display unit 24 of the client terminal 20 displays the map 25 corresponding to the map information 56 (step ST18).

Note that the processing by the server 10 described in Figures 5 and 6 and the processing by the server 10 described in Figures 7 and 8 may be executed by different servers 10.

Here, we will explain the registration process of the updated thinning information 33 by the registration unit 12 of the server 10. Figure 9 is a flowchart showing the registration process procedure of thinned features registered by the server according to the embodiment.

The registration unit 12 of the server 10 obtains the updated feature information 32 corresponding to the area specified in the feature editing information 31, i.e., the updated area, from the feature DB 60 (step ST21). The updated area specified in the map display request 51 is the area in which the feature information has been updated.

The registration unit 12 of the server 10 derives a thinning priority for each feature included in the updated feature information 32 (step ST22). The registration unit 12 derives a priority for each feature that is the subject of priority derivation (hereinafter, may be referred to as a target point feature). The registration unit 12 derives a thinning priority for each target point feature based on the following priority derivation elements (1) to (5).
(1) Attributes of the target point feature; (2) Whether the target point feature is a branch point of a line feature 80; (3) Whether the target point feature is an end point; (4) Distance from the branch point of the target point feature; (5) Distance from the line segment connecting the point features 70 on both sides of the target point feature to the target point feature.

For example, if the normal state of a utility pole is set as an attribute of a feature, the registration unit 12 increases the priority of thinning for this feature (target point feature). The registration unit 12 may increase the priority of thinning if an abnormal state of a utility pole is set. The registration unit 12 may also increase the priority of thinning if there is a power outage at the feature, or may increase the priority of thinning if there is no power outage at the feature. The user sets in the server 10 which attribute to increase the priority of.

The registration unit 12 also increases the priority of thinning when the target point feature is not a branch point. The registration unit 12 also increases the priority of thinning when the target point feature is not an end point. The registration unit 12 also increases the priority of thinning when the distance of the target point feature from the branch point is short. In this case, the distance from the branch point may be a straight line distance or the total distance when tracing the line feature 80 in order.

The registration unit 12 also extracts point features 70 located on both sides of the target point feature. The extracted point features 70 are point features 70 that are connected to the target point feature via a line feature 80. The registration unit 12 increases the priority of thinning when the distance from the line segment connecting the two extracted point features 70 to the target point feature is shorter than a specific value.

The registration unit 12 assigns weights to each of the above (1) to (5) and sets a thinning priority for each feature. The weights for (1) to (5) are set by the user in the server 10.

The registration unit 12 determines which features to thin out based on the priority set for each point feature 70 (step ST23). That is, the registration unit 12 sets priorities for thinning out for all features, and sets the point features 70 with the highest priority for thinning out as the features to be thinned out in order.

The registration unit 12 assigns a score indicating a priority to each point feature 70 based on the priority set for each point feature 70, for example. The registration unit 12 then sets each point feature 70 as a feature to be thinned out in descending order of score.

When the registration unit 12 thins out the point feature 70 at the end point, it sets the line feature 80 connected to the thinned point feature 70 as the feature to be thinned out. The registration unit 12 executes the thinning setting for the point features 70 and the line features 80 until the number of points 70 and the line features 80 is such that the processing load of the display when the client terminal 20 displays the map 25 is equal to or less than a specific value.

The display processing load when the map 25 is displayed is calculated by the registration unit 12 based on the number of point features 70 and the number of line features 80. Note that the registration unit 12 may also calculate the display processing load based on the number of point features 70 and the number of line features 80 when the map information generation unit 13 reconstructs the line features 80.

The specific value to be compared with the processing load may be registered in advance in the server 10, or a specific value requested by the client terminal 20 may be applied.

The registration unit 12 may also thin out the point features 70 and reconstruct the line features 80 so that the display processing time when the client terminal 20 displays the map 25 is less than or equal to a specific time. In this case, the registration unit 12 reconstructs the features based on the display processing capacity of the client terminal 20 so that the display processing time when the map 25 is displayed is less than or equal to a specific time.

The registration unit 12 registers the determined thinned features in the thinning information DB 40 (step ST24). That is, the registration unit 12 registers updated thinning information 33 indicating whether each feature is a target for thinning in the thinning information DB 40. Specifically, the registration unit 12 creates updated thinning information 33 in which the scale information 85, the feature's feature identification information 54, and information indicating whether the feature is a target for thinning are associated with each other, and registers the updated thinning information 33 in the thinning information DB 40.

The thinning information DB 40 stores overall thinning information 82 in which feature identification information 54 and information indicating whether the feature is a target for thinning are associated for each scale information 85, and updates the overall thinning information 82 using the updated thinning information 33.

The registration unit 12 determines whether thinned features have been determined for all update areas (step ST25). If the registration unit 12 has not determined thinned features for all update areas (step ST25, No), the registration unit 12 returns to the process of step ST21 and executes the processes of steps ST21 to ST24. If the registration unit 12 has determined thinned features for all update areas (step ST25, Yes), the registration process of the update thinning information 33 ends.

When the original map of map 25 is created for the first time, the entire original map becomes the update area. In this case, the registration unit 12 creates update thinning information 33 for each scale information 85 for all areas of the original map and registers it in the thinning information DB 40. At this time, the update thinning information 33 registered in the thinning information DB 40 becomes the overall thinning information 82, and when the map 25 is updated thereafter, the overall thinning information 82 is updated using the update thinning information 33.

In the embodiment, the registration unit 12 assigns weights to each of the above (1) to (5) and sets a thinning priority for each feature. However, the registration unit 12 may thin out features in order according to the above (1) to (5). In this case, the registration unit 12 thins out features in order until the processing load of the display falls below a specific value. The thinning process by the registration unit 12 in this case will be described below.

The registration unit 12 creates map 46 using map 41 shown in FIG. 2 as the original map by executing the first to fifth processes included in the thinning process in order. FIG. 10 is a diagram for explaining the first process performed when the server according to the embodiment makes a thinning decision. The registration unit 12 of the server 10 creates map 42 shown in FIG. 10 from map 41 shown in FIG. 2. Specifically, the registration unit 12 sets any feature on map 41 as a reference node. FIG. 10 shows the case where point feature 71A is set as the reference node.

The registration unit 12 extracts the path from the reference node, point feature 71A, to the farthest node (point feature 72). The point feature 72 farthest from point feature 71A is the point feature with the greatest number of line features 80 connections when tracing line features 80 from point feature 71A. In other words, the point feature 72 that is connected to point feature 71A via the greatest number of line features 80 is the point feature 72 farthest from point feature 71A.

The registration unit 12 extracts point feature 73 that is included in the path from point feature 71A to point feature 72. The first process is the process in which the registration unit 12 sets point feature 71A as the reference node and extracts point features 72 and 73. Figure 10 shows the state in which point feature 71A has been set and point features 72 and 73 have been extracted.

Fig. 11 is a diagram for explaining the second process performed by the server according to the embodiment when making a thinning decision. The registration unit 12 creates the map 43 shown in Fig. 11 from the map 42 shown in Fig. 10. Specifically, the registration unit 12 extracts, from among the point features 73, point features 73 that are branching points of line features 80. A point feature 73 that is a branching point of line features 80 is a point feature to which three or more line features 80 are connected.

The registration unit 12 extracts a point feature 74 that is a terminating point feature and has a shortest distance from the point feature 73 less than or equal to a reference value L from among the point features 70 that are connected to a point feature 73 that is a branch point of the line feature 80. Note that the distance from the point feature 73 may be the total distance of the path when the line features 80 are traced in order.

The second process is the process in which the registration unit 12 extracts point feature 73, which is a branch point, and point feature 74. Figure 11 shows the state in which point feature 71A has been set and point features 72 to 74 have been extracted.

FIG. 12 is a diagram for explaining the third process performed by the server according to the embodiment when making a thinning decision. The registration unit 12 creates the map 44 shown in FIG. 12 from the map 43 shown in FIG. 11. Specifically, the registration unit 12 deletes the point feature 74 extracted in the second process by setting it as a feature to be thinned. The registration unit 12 also deletes the line feature 80 connected to the deleted point feature 74 by setting it as a feature to be thinned. The line feature 80 connected to the point feature 74 is a line feature with one end connected to the point feature 73 and the other end to which no point feature is connected due to the deletion of the point feature 74. The third process is a process performed by the registration unit 12 to delete the point feature 74 extracted in the second process by setting it as a feature to be thinned and to delete the line feature 80 connected to the point feature 74 by setting it as a feature to be thinned.

The registration unit 12 also extracts branches that are connected to the point feature 73 that is the branching point of the line feature 80 and that extend from the point feature 73 farther than the reference value L. In other words, the registration unit 12 extracts branches that extend from the path from the point feature 71A to the point feature 72 and from which the point feature 74 has not been deleted.

The registration unit 12 executes the first process to the third process on the extracted branch. That is, the registration unit 12 sets the point feature 73, which is one end of the extracted branch, as the new reference node, point feature 71B. FIG. 12 shows a case where the point feature 73, which is located on the path from point feature 71A to point feature 72, is set as the new reference node, point feature 71B.

The registration unit 12 extracts point features 72 to 74 from the point feature 70 contained in the branch. FIG. 12 shows a state in which the registration unit 12 has set a point feature 71B for the extracted branch and extracted point features 72 to 74. The registration unit 12 deletes the extracted point feature 74 from the map 44 by setting it as a feature to be thinned out.

FIG. 13 is a diagram for explaining the fourth process performed by the server according to the embodiment when making a thinning decision. The registration unit 12 creates the map 45 shown in FIG. 13 from the map 44 shown in FIG. 12. Specifically, the registration unit 12 extracts, as a point feature 75, a target point feature whose distance from a line segment connecting the point features 70 on both sides of the target point feature to the target point feature is shorter than a specific value (reference value D1 described later). The process in which the registration unit 12 extracts the point feature 75 is the fourth process. FIG. 13 shows a state in which the registration unit 12 has extracted the point feature 75.

The registration unit 12 deletes the point features 75 extracted in the fourth process by setting them as features to be thinned out, and replaces the areas where the point features 75 have been deleted with a single line feature 80. The fifth process is the process in which the registration unit 12 deletes the point features 75 by setting them as features to be thinned out, and connects the adjacent point features 70 on both sides with a single line feature 80.

Figure 14 is a diagram for explaining the fifth process performed when the server according to the embodiment makes a thinning decision. Figure 14 shows a case where the target point feature is point feature 70B, and the point features on either side of point feature 70B are point features 70A and 70C.

Point features 70A and 70B are connected by line feature 80A, and point features 70B and 70C are connected by line feature 80B. The registration unit 12 extracts point feature 70B when the distance from line segment X1 connecting point features 70A and 70C on both sides of target point feature 70B to point feature 70B is equal to or less than reference value D1.

The registration unit 12 deletes the extracted point feature 70B and the line features 80A and 80B connected to the point feature 70B by setting them as features to be thinned out. Furthermore, the registration unit 12 connects the point features 70A and 70C on both sides of the point feature 70B with a new line feature 80C. The line feature 80C is a linear feature that connects the point features 70A and 70C at the shortest distance. Therefore, the line feature 80C is placed at the position of the line segment X1 that connects the point features 70A and 70C. In this way, the registration unit 12 thins out the point feature 70B, and places the line feature 80C in place of the line features 80A and 80B so that the point features 70A and 70C that were not thinned out are connected to each other. This maintains the connection relationship between the point features 70A and 70C.

The registration unit 12 may extract point features 70 that are not adjacent to the target point feature as point features 70A and 70C. In other words, point features 70A and 70C are not limited to point features 70 adjacent to point feature 70B, which is the target point feature. For example, the registration unit 12 may set point features 70A and 70C as point features that can be reached without passing through the point feature 70 that is a branch point when tracing the line feature 80 from point feature 70B. Furthermore, the registration unit 12 may set point feature 70B in order from any point feature 70 included in the original map.

There may be multiple point features 70 on the path from point feature 70A to point feature 70C. In this case, even if the registration unit 12 thins out all of the point features 70 on the path from point feature 70A to point feature 70C, point feature 70A and point feature 70C are connected by a line feature 80C.

The registration unit 12 creates a map 46 from the map 41 by executing the first to fifth processes described above for each scale and for each area of the original map. The map 46 here corresponds to the map 25 displayed on the client terminal 20.

The registration unit 12 creates a map 46 from the map 41, and sets some of the features included in the original map as features to be thinned based on the difference between the map 46 and the map 41. That is, the registration unit 12 creates updated thinning information 33 indicating the features to be thinned by comparing the features included in the map 46 with the features included in the map 41. In the updated thinning information 33, point features 70 included in the map 41 but not included in the map 46 are registered as point features 70 to be thinned. On the other hand, in the updated thinning information 33, point features 70 included in both the maps 41 and 46 are registered as point features 70 not to be thinned. In the updated thinning information 33, line features 80A and 80B to be deleted and line feature 80C to be added are also registered.

If the registration unit 12 can display the map 25 within a specific processing load between the first process and the fourth process, it ends the thinning determination process for the point features 70 at this point.

On the other hand, if the registration unit 12 cannot display the map 25 within the specific processing load even after executing the first process to the fifth process, it changes at least one of the reference value L and the reference value D1 described above to a larger value and executes the first process to the fifth process on the map 46. In this case, too, if the registration unit 12 can display the map 25 within the specific processing load between the first process and the fourth process, it ends the thinning determination process of the point features 70 at this point.

In other words, the registration unit 12 repeats the first to fifth processes while updating at least one of the reference value L and the reference value D1 to a larger value until the map 25 can be displayed within a specific processing load.

The server 10 creates map information 56 based on the map display request 51 received from the client terminal 20. That is, the server 10 creates map information 56 corresponding to a map 25 in which specific features have been thinned out from the original map based on the map display request 51. This map information 56 is information that allows the map 25 to be displayed in as much detail as possible within a specific processing load. This enables the client terminal 20 to display a map 25 in as much detail as possible within a specific processing load based on the map information 56.

Figure 15 is a diagram for explaining the map areas that the server according to the embodiment sets when creating update thinning information. When creating update thinning information 33 for each map area set on the original map, the registration unit 12 sets the map areas so that the map areas overlap.

Figure 15 shows a case where the registration unit 12 sets map areas 61 to 64. The map areas 61 to 64 are adjacent to each other and share overlapping areas. When the registration unit 12 determines that a target point feature is to be thinned in any of the map areas 61 to 64, it determines the target point feature as a thinned feature. In other words, the registration unit 12 determines that a feature determined to be thinned in at least one map area for an overlapping area is a thinned feature. That is, the registration unit 12 creates updated thinning information 33 in which a feature determined to be thinned in any of the map areas 61 to 64 is set as a thinning target. When a wide area is displayed at a small scale, the thinning rate is high, and at a medium scale, the thinning rate is to a certain extent. At a large scale such as 1/500, only a narrow area is displayed, and the registration unit 12 hardly needs to thin out. To accommodate changes in the thinning rate according to the scale, the registration unit 12 performs a process to determine the thinned features for each scale while changing the size of the display range.

Therefore, for the overlapping areas, the client terminal 20 causes the display unit 24 to display features that are determined not to be thinned in all map areas 61 to 64. In other words, for the overlapping areas, the client terminal 20 does not cause the display unit 24 to display features that are determined to be thinned in at least one map area.

In addition, in this embodiment, the case where the server 10 performs a thinning determination and creates the updated thinning information 33 when a change is made to the original map has been described, but the timing of the thinning determination process is not limited to this timing. That is, in this embodiment, the case where the server 10 does not perform the thinning determination process when the client terminal 20 actually displays the map 25 has been described, but the server 10 may perform the thinning determination when a map display request 51 is made.

In addition, in this embodiment, the server 10 creates map information 56 corresponding to the map display request 51 when a map display request 51 is received, but the timing for creating the map information 56 is not limited to this timing. That is, the server 10 may create map information 56 for each area and scale of the map 25 when creating the update thinning information 33. When the server 10 creates map information 56 before the map display request 51 is sent, the server 10 stores the created map information 56 in the thinning information DB 40.

When the client terminal 20 is displaying a map 25 and the user issues an instruction to change the display area (an instruction to scroll the screen), the client terminal 20 transmits a new map display request 51 corresponding to the scroll instruction to the server 10. As a result, the client terminal 20 receives new map information 56 corresponding to the scroll instruction from the server 10 and displays a new map 25 corresponding to the scroll instruction.

The map display system 1 may be applied to facilities other than power system facilities. The map display system 1 can also be applied to social infrastructure facilities (social infrastructure business) such as sewerage facilities and road facilities. When the map display system 1 is applied to sewerage facilities, the point features 70 are manholes, etc., and the line features 80 are pipes, etc. When the map display system 1 is applied to road facilities, the point features 70 are bridges, traffic lights, etc., and the line features 80 are roads, etc.

Next, the hardware configuration of the server 10 and the client terminal 20 will be described. Note that the hardware configuration of the server 10 and the client terminal 20 is similar, so the hardware configuration of the server 10 will be described here.

The server 10 is realized by a processing circuit. The processing circuit may be a processor and memory that executes a program stored in memory, or may be dedicated hardware such as a dedicated circuit. The processing circuit is also called a control circuit.

16 is a diagram showing an example of the configuration of a processing circuit when the processing circuit provided in the server according to the embodiment is realized by a processor and a memory. The processing circuit 90 shown in FIG. 16 is a control circuit and includes a processor 91 and a memory 92. When the processing circuit 90 is configured with the processor 91 and the memory 92, each function of the processing circuit 90 is realized by software, firmware, or a combination of software and firmware. The software or firmware is described as a program and stored in the memory 92. In the processing circuit 90, each function is realized by the processor 91 reading and executing the program stored in the memory 92. That is, the processing circuit 90 includes a memory 92 for storing a program that will result in the processing of the server 10 being executed. This program can also be said to be a program for causing the server 10 to execute each function realized by the processing circuit 90. This program may be provided by a storage medium in which the program is stored, or may be provided by other means such as a communication medium. The above program can also be said to be a program for causing the server 10 to execute various processes for creating and transmitting the map information 56.

Here, the processor 91 is, for example, a CPU (Central Processing Unit), a processing device, an arithmetic device, a microprocessor, a microcomputer, or a DSP (Digital Signal Processor). The memory 92 is, for example, a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an EPROM (Erasable Programmable ROM), an EEPROM (Electrically EPROM), or other non-volatile or volatile semiconductor memory, a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, or a DVD (Digital Versatile Disc).

FIG. 17 is a diagram showing an example of a processing circuit provided in a server according to an embodiment, configured with dedicated hardware. The processing circuit 93 shown in FIG. 17 corresponds to, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination of these. The processing circuit 93 may be partially realized with dedicated hardware and partially realized with software or firmware. In this way, the processing circuit 93 can realize each of the above-mentioned functions by dedicated hardware, software, firmware, or a combination of these.

The communication unit 11, the registration unit 12, and the map information generation unit 13 may each be realized using separate programs. That is, the processing circuits 90 and 93 may execute processing by the server 10 using a communication program corresponding to the communication unit 11, a registration program corresponding to the registration unit 12, and a map information creation program corresponding to the map information generation unit 13.

In addition, in the case of the client terminal 20, the editing unit 22, the communication unit 23, and the display unit 24 may each be realized using separate programs. That is, the processing circuits 90 and 93 of the client terminal 20 may execute processing by the client terminal 20 using an editing program corresponding to the editing unit 22, a communication program corresponding to the communication unit 23, and a display program corresponding to the display unit 24.

As described above, according to the embodiment, the map information generating unit 13 of the server 10 creates the map information 56 so that the display processing load when displaying the map 25, which is a thinned map of the original map, is equal to or less than a specific value, so that it is possible to create the map information 56 for displaying the detailed map 25 within a desired processing load. Also, the client terminal 20 is able to display the detailed map 25 within a desired processing load.

In the embodiment, the registration unit 12 of the server 10 obtains the updated feature information 32 corresponding to the feature editing information 31 from the feature DB 60, and creates the updated thinning information 33 using the updated feature information 32, in which whether or not to display the feature is set for each feature and for each scale so that the processing load is below a specific value. Then, the map information generation unit 13 obtains the feature information included in the display area from the feature DB 60 as range feature information 53 based on the map display request 51. Furthermore, the map information generation unit 13 obtains the thinning information corresponding to the feature included in the range feature information 53 from the thinning information DB 40 as request thinning information 55, and creates the map information 56 using the range feature information 53 and the request thinning information 55. As a result, when the server 10 receives the map display request 51, it can create the map information 56 in a short time using the request thinning information 55.

The map information generating unit 13 of the server 10 also uses the request thinning information 55 to thin out the point features 70 and line features 80, and reconstructs the line features 80 at the locations where the point features 70 have been thinned out. This enables the server 10 to create map information 56 for displaying the map 25 within the desired processing load while maintaining the overview of the original map.

In addition, the map information generating unit 13 of the server 10 acquires the request thinning information 55 from the thinning information DB 40 based on the feature identification information 54 included in the range feature information 53, so that the server 10 can easily acquire the request thinning information 55.

In addition, the registration unit 12 of the server 10 thins out features in order of priority, so the server 10 can easily keep the processing load when displaying the map 25 within the desired processing load.

The registration unit 12 of the server 10 also derives the thinning priority of each target point feature based on the priority derivation elements (1) to (5) described above, so that when displaying the map 25, it is possible to lower the thinning priority of features with high importance and to raise the thinning priority of features with low importance. This allows the server 10 to thin out features with low importance while retaining features with high importance.

The registration unit 12 of the server 10 also divides the display area on the map 25 into multiple map areas 61-64, and performs a thinning determination for each map area 61-64 as to whether or not to thin out features. This enables the server 10 to reduce the processing load when performing the update process for the overall thinning information 82.

The registration unit 12 of the server 10 also overlaps the map areas 61 to 64, and thins out the features when it determines that features should be thinned out in at least one of the overlapping map areas. This enables the server 10 to accurately extract the features to be thinned out.

The configurations shown in the above embodiments are merely examples, and may be combined with other known technologies. Parts of the configurations may be omitted or modified without departing from the spirit of the invention.

1 Map display system, 10 Server, 11, 23 Communication unit, 12 Registration unit, 13 Map information generation unit, 20 Client terminal, 21 Input unit, 22 Editing unit, 24 Display unit, 25, 41-46 Map, 31 Feature editing information, 32 Updated feature information, 33 Updated thinning information, 40 Thinning information DB, 51 Map display request, 52 Area feature acquisition request, 53 Area feature information, 54 Feature identification information, 55 Request thinning information, 56 Map information, 60 Feature DB, 61-64 Map area, 70, 70A-70C, 71A, 71B, 72-75 Point features, 80, 80A-80C Line features, 81 Overall feature information, 82 Overall thinning information, 85 Scale information, 90, 93 Processing circuit, 91 Processor, 92 memory.

Claims (11)

a communication unit that receives a map display request from a terminal, the map display request specifying at least one of a display area and a scale of the infrastructure facility on the map;
a map information generating unit that generates map information for displaying a thinned map in which some of the features included in the map are thinned out based on the map display request;
Equipped with
the map information generation unit acquires, based on the map display request, information on the features included in the display area from a first database that stores information on the features as range feature information, acquires, from a second database that stores thinning information that specifies whether each of the features is to be displayed on the thinned map, the thinning information corresponding to the features included in the range feature information as request thinning information, and creates the map information using the range feature information and the request thinning information ;
The communication unit transmits the map information to the terminal.
A map information creation device comprising: a registration unit that, when the communication unit receives feature editing information indicating editing content of the feature, obtains feature information that is information on the feature corresponding to the feature editing information from the first database , creates the thinning information set for each scale using the feature information, and registers the thinning information in the second database .
2. The map information generating device according to claim 1, the features include point features that are displayed as points on the map and line features that are displayed as lines on the map;
The map information generating unit
thinning out the point features and the line features using the request thinning information, and reconstructing the line features so that the connection relationships between the point features that were not thinned out are maintained;
3. The map information generating device according to claim 2. The information on the features and the thinning information include identification information for identifying the features,
The map information generating unit
acquiring the request thinning information from the second database based on the identification information included in the range feature information;
4. The map information generating device according to claim 2 or 3. A thinning priority is set for the feature,
The registration unit thins out the features in order of priority.
5. The map information generating device according to claim 2, wherein the map information generating device is a map information generating device. The infrastructure facility is a power system facility,
The point features include at least one of a utility pole, a transformer, and a switchgear;
The line feature includes an electric wire.
4. The map information generating device according to claim 3. The registration unit is
deriving the priority of thinning based on attributes set for the point feature, whether the point feature is a branching point on the map, whether the point feature is an end point, the distance from a point feature that is a branching point of the line feature on the map, or the distance from a line segment connecting the point features on both sides of the point feature to the point feature sandwiched between the point features on both sides;
4. The map information generating device according to claim 3. The registration unit divides the display area into a plurality of map areas, and executes a thinning-out determination as to whether or not to thin out the features for each of the map areas.
3. The map information generating device according to claim 2. the registration unit overlaps the map regions, and thins out the features when it is determined that the features should be thinned out in at least one of the map regions for the overlapping regions;
9. The map information generating device according to claim 8. a terminal that transmits a map display request specifying at least one of a display area and a scale of an infrastructure facility on a map;
a map information creation device that receives the map display request, creates map information for displaying a thinned map in which some of the features included in the map are thinned based on the map display request, and transmits the map information to the terminal;
Equipped with
the map information creation device acquires, based on the map display request, information on the features included in the display area from a first database that stores information on the features as range feature information, acquires, from a second database that stores thinning information that specifies whether or not each of the features is to be displayed on the thinned map, the thinning information corresponding to the features included in the range feature information as request thinning information, and creates the map information using the range feature information and the request thinning information ;
The terminal displays the thinned map based on the map information.
A map display system comprising: a map information generating step of generating map information for displaying a thinned map in which some of the features included in the map are thinned out based on a map display request received from the terminal, the map display request specifying at least one of a display area and a scale of the infrastructure facility on the map;
In the map information generating step, information on the features included in the display area is obtained as range feature information from a first database that stores information on the features based on the map display request, and thinning information corresponding to features included in the range feature information among the features is obtained as request thinning information from a second database that stores thinning information that specifies whether each of the features is to be displayed on the thinned map, and the map information is created using the range feature information and the request thinning information .
A map information creation program comprising:

Images