JP7668644B2 - Map Information System - Google Patents

Description

One aspect of the present disclosure relates to a computer system, a processing method, a program, and/or a data structure.

Patent Document 1 discloses a geographic information system that includes a map database and an attribute database. In this geographic information system, the map database stores the history of map data. The map data includes graphic shape data representing buildings and information on the time when the buildings existed. The attribute database stores the attributes of the buildings included in the map data. The attribute data is linked to the graphic shape data by location information.

JP 2009-58252 A

This disclosure provides a map information system that is effective in increasing the added value of map data.

A map information system according to one aspect of the present disclosure includes a feature database that accumulates feature information including coordinate information of features and a feature ID unique to the feature; an attribute database that accumulates utilization attribute information indicating addition, deletion, and content of utilization attributes assigned to features in association with the feature ID; and an attribute information registration unit that performs the following operations in the attribute database: generating utilization attribute information corresponding to a new utilization attribute corresponding to the feature ID of a specified feature when a new utilization attribute is assigned to the specified feature; registering information indicating the deletion in the utilization attribute information when a utilization attribute is deleted from the specified feature; and changing the content of the utilization attribute information when the content of the utilization attribute assigned to the specified feature is changed. the attribute information extraction unit extracts usage attribute information associated with the feature ID of the specified feature from the attribute database ; and an output unit outputs usage status information representing the addition, deletion, and content change history of the usage attribute assigned to the specified feature based on the usage attribute information extracted by the attribute information extraction unit, wherein if the magnitude of the change in the content of the usage attribute exceeds a predetermined level, the attribute information registration unit registers information indicating the deletion in the usage attribute information corresponding to the usage attribute and generates new usage attribute information corresponding to the changed usage attribute, and if the magnitude of the change in the content of the usage attribute does not exceed the predetermined level, changes the content of the usage attribute information corresponding to the usage attribute .

FIG. 1 is a schematic diagram illustrating a configuration of a map information system. FIG. 13 is a block diagram illustrating a configuration for outputting usage status information. 1 is a table illustrating an example set of feature information. 11 is a table showing variations of a set of feature information. 1 is a table illustrating an example of one set of attribute information. 11 is a table illustrating an example of a display of a usage status. 13 is a table showing a modified example of the display of the usage status. FIG. 2 is a block diagram illustrating a configuration for maintaining map data. FIG. 2 is a diagram illustrating an example of a hardware configuration of a map server. 4 is a flowchart illustrating a maintenance procedure for map data. 4 is a flowchart illustrating a maintenance procedure for map data. 4 is a flowchart illustrating a maintenance procedure for map data. 11 is a flowchart illustrating a procedure for displaying a usage status. 13 is a flowchart illustrating an example of an attribute information update notification procedure.

The following describes the embodiments in detail with reference to the drawings. In the description, the same elements or elements having the same functions are given the same reference numerals, and duplicate descriptions are omitted.

[Map Information System]
The map information system 1 shown in FIG. 1 is a system that manages and provides map data for displaying a map. If it were possible to easily aggregate various attributes that directly or indirectly indicate the usage status of features that make up a map and to indicate the usage status of the features, the added value of the map data would be increased. The attributes of features may be added, deleted, or changed over time. For this reason, many attributes are assigned to a feature from the time it is created until it disappears. If these attributes could be easily aggregated, it would be possible to accurately indicate the usage status of the feature.

However, changes may occur to the feature itself during the period from its creation to its disappearance. Specific examples of changes to the feature itself include an expansion or reduction in size. Even if no changes have occurred to the actual feature, changes may occur in the data representing the location and shape of the feature due to corrections to survey results, etc.

When a change occurs in the data of a feature due to the replacement of the entire feature with another feature, the attribute information of the feature data before the change and the attribute information of the feature data after the change must be associated with different features. Hereinafter, this is referred to as the "first case." On the other hand, when a change occurs only in existing feature data due to an extension, reduction, or data correction, the attribute information of the feature data before the change and the attribute information of the feature data after the change must be aggregated for the same feature. Hereinafter, this is referred to as the "second case." It is difficult to distinguish between the first and second cases based solely on the changes in the location and shape of the feature, and there are cases in which the attributes of the same feature cannot be appropriately aggregated.

In response to this, the map information system 1 includes a feature database that accumulates feature information including the coordinate information of the feature and its unique feature ID, an attribute database that accumulates attribute information of the feature in association with the feature ID, an ID selection unit that selects the feature ID of a target feature, an attribute information extraction unit that extracts attribute information associated with the feature ID of the target feature in the attribute database, and an output unit that outputs usage status information of the target feature based on the attribute information extracted by the attribute information extraction unit. With this configuration, a unique feature ID is assigned to the feature information itself, including the coordinate information of the feature, and the attribute information of the feature is accumulated in association with the feature ID. This makes it possible to clearly distinguish between changes in coordinate information due to the expansion or reduction of a building or correction of the map data itself, and changes in coordinate information due to replacement of the feature itself, and to aggregate various attribute information for each feature. Below, a detailed example of the configuration of the map information system 1 is shown.

As shown in FIG. 1, the map information system 1 has one or more map servers 100. Although only one map server 100 is shown in the figure, the map information system 1 may include two or more map servers 100. The map server 100 can communicate with a maintenance terminal 200 and an application terminal 300 via a network line 9. The map server 100 manages and provides map data.

The maintenance terminal 200 is a terminal of a worker who maintains the map data, and holds a maintenance program for maintaining the map data. The application terminal 300 is a terminal of a user of the map data, and holds an application program for using the map data.

The map server 100 is configured to hold a feature database that accumulates feature information including the coordinate information of the feature and the feature's unique feature ID, hold an attribute database that accumulates feature attribute information in association with the feature ID, extract attribute information associated with the feature ID of a specified feature from the attribute database, and output usage status information of the specified feature based on the attribute information extracted by the attribute information extraction unit.

Figure 2 is a block diagram illustrating the functional configuration of the map server 100. As shown in Figure 2, the map server 100 has, as its functional configuration (hereinafter referred to as "functional blocks"), a feature database 111, an attribute database 112, an area designation acquisition unit 113, a map data generation unit 114, a feature designation acquisition unit 115, an attribute information extraction unit 116, and a usage status output unit 117.

The feature database 111 accumulates feature information including the coordinate information of the feature and the feature's unique feature ID. A feature includes any object that exists in a fixed position in the global coordinate system. Specific examples of features include roads, lines and indicators on the road surface, signs and traffic lights installed on roads, roadside strips, land around roads, buildings on land, and administrative districts that group multiple land sites. The coordinate information of a feature is, for example, a sequence of coordinate points that represents the position and three-dimensional shape of the feature in the global coordinate system.

The feature ID is identification information generated for each feature so that it is a unique value. A unique feature ID means that there is only one feature to which the feature ID is assigned. In other words, the feature database 111 does not contain two or more pieces of feature information to which the same feature ID is assigned. There are no particular restrictions on the data format of the feature ID, so long as each piece of feature information can be identified from all other piece of feature information. The feature information may further include basic attributes that describe the nature of the feature itself.

Figure 3 is a table illustrating a set of feature information. As illustrated in Figure 3, the feature information may include the basic attributes of the feature, creation date information, and destruction date information in addition to the feature ID and coordinate information described above. The basic attributes of a feature are information that represents the nature of the feature itself. Specific examples of basic information include feature type and feature name. Specific examples of feature type include "office building," "warehouse," "factory," "detached house," "apartment building," and "store."

The creation date means the date on which a feature was created, for example through new construction. Creation date information is information that indicates the creation date. Indicating the creation date includes indicating the creation date with an error within an acceptable range for practical use. Thus, the creation date information may be information that indicates a period including the creation date. For example, the creation date information may be information that specifies the week, such as "Xth week of Xth month," or information that specifies the month, such as "Xth month." The creation date information may be information that specifies not only the creation date, but also the hour, minute, and second of creation.

The disappearance date means the date on which the building disappeared due to demolition or the like. The disappearance date information is information indicating the disappearance date. Indicating the disappearance date includes indicating the creation date with an error within the range permitted in practical use. Therefore, the disappearance date information may be information indicating a period including the disappearance date. For example, the disappearance date information may be information specifying a week such as "Xth week of Xth month" or information specifying a month such as "Xth month". The disappearance date information may be information specifying not only the disappearance date but also the disappearance hour, minute, and second. In the feature information of an existing feature, the disappearance date information is left blank. Therefore, whether or not the feature exists can be confirmed depending on whether or not the disappearance date information is blank. Note that instead of leaving the disappearance date information blank, the disappearance date information may include information indicating that the feature is currently existing (hereinafter referred to as "existing information"). In this case, whether or not the feature exists can be confirmed depending on whether or not the disappearance date information includes existing information.

Each feature may have a relationship with other features on the map. For example, a building standing on a site may be said to have a relationship with the site. A site included in an administrative district may be said to have a relationship with the administrative district. A road sign on a road may be said to have a relationship with the road. In order to clearly indicate such a relationship, the feature information may further include the ID of the other related feature ("related feature ID" in FIG. 4). Furthermore, the feature information may further include the type of relationship with the other feature (not shown). Specific examples of the type of relationship include an "inclusion relationship" such as the relationship between an administrative district and a site within the administrative district, a "loading relationship" such as the relationship between a site and a building on the site, and a "crossing relationship" such as the relationship between a road and a pedestrian bridge spanning the road.

The attribute database 112 stores the usage attribute information of features in association with the feature ID. Usage attribute information is information that indicates how a feature is used as a type of feature's property. Specific examples of usage attribute information include resident names and usage types. Usage type refers to the type of way a resident uses a feature. Specific examples of usage types include "office work," "manufacturing," "sales," "services," and "life."

Figure 5 is a table illustrating a set of usage attribute information. As illustrated in Figure 5, the usage attribute information is associated with a feature ID. In addition to the above-mentioned resident name and usage type, the usage attribute information may further include a unique attribute ID of the usage attribute. The attribute ID is identification information generated for each usage attribute information so that it is a unique value. A unique attribute ID means that there is only one set of usage attribute information to which the attribute ID is assigned. In other words, the attribute database 112 does not include two or more attribute information to which the same attribute ID is assigned. As long as each attribute information can be identified from all other attribute information, there is no particular restriction on the data format of the attribute ID. Note that the feature ID and the usage attribute information may be associated in the feature information. For example, instead of the usage attribute information including the corresponding feature ID, the feature information may include the corresponding attribute ID. In addition, correspondence information defining the correspondence between the feature ID and the attribute ID may be provided separately from the feature information and the usage attribute information.

Even if there is no substantial change in the usage attributes, the usage attribute information may change. For example, even if the occupant and type of usage have not substantially changed, a minor revision to the occupant's name may occur due to a company merger, etc. In such a case, if it is determined that the occupant has changed based on the minor revision to the name, the usage status of the feature cannot be properly indicated. By storing an attribute ID unique to the usage attribute in addition to the occupant name, which can change even for the same occupant, it is possible to accurately determine whether a change in usage attribute information is due to a substantial change in the usage attributes, and to properly indicate the usage status of the feature.

The usage attribute information may further include additional attribute information about the resident, addition date information, and deletion date information. Specific examples of additional attribute information about the resident include business hours, telephone number, etc.

The added date refers to the date on which a usage attribute was added, for example, due to a new resident moving in. Added date information is information that indicates the added date. Indicating the added date includes indicating the added date with an error within an acceptable range for practical use. Thus, the added date information may be information that indicates a period including the added date. For example, the added date information may be information that specifies the week, such as "Xth week of month X," or information that specifies the month, such as "Xth month." The added date information may be information that specifies not only the added date, but also the hour, minute, and second of the addition.

The deletion date means the date on which the usage attribute was deleted due to a resident moving out or the like. The deletion date information is information indicating the deletion date. Indicating the deletion date includes indicating the deletion date with an allowable margin of error in practical use. Therefore, the deletion date information may be information indicating a period including the deletion date. For example, the deletion date information may be information specifying a week such as "Xth week of Xth month" or information specifying a month such as "Xth month". The deletion date information may be information specifying not only the deletion date but also the deletion hour, minute, and second. In the usage attribute information of an ongoing usage attribute, the deletion date information is left blank. Therefore, it is possible to confirm whether the usage attribute is ongoing or not depending on whether the deletion date information is blank or not. Note that instead of leaving the deletion date information blank, information clearly indicating that it is ongoing (hereinafter referred to as "ongoing information") may be included in the deletion information. In this case, it is possible to confirm whether the usage attribute is ongoing or not depending on whether the deletion date information includes the ongoing information or not.

The attribute database 112 may include multiple sets of usage attribute information associated with the same feature ID. A specific example of multiple sets of usage attribute information associated with the same feature ID is shown below.
Example 1-1) Multiple sets of usage attribute information corresponding to multiple residents with different occupancy periods. Example 1-2) Multiple sets of usage attribute information corresponding to multiple residents who simultaneously reside in the same feature.

In the case of example 1-2 above, each of the multiple sets of usage attribute information may further include a floor number or room number, etc., that identifies the area in which each resident resides.

The area designation acquisition unit 113 acquires an area designation for map display from the application terminal 300. Hereinafter, the area designated by the area designation is referred to as the "display target area." For example, the area designation acquisition unit 113 acquires an area designation input by a user of the map data to the application terminal 300.

The map data generation unit 114 generates area map data for displaying a map of the display target area, and transmits it to the application terminal 300. For example, the map data generation unit 114 extracts feature information of all features to be displayed on a map of the display target area from the feature database 111 based on the coordinate information of each feature information, and generates area map data based on the extracted feature information. The application terminal 300 displays a map of the display target area (hereinafter referred to as the "area map") based on the area map data.

The feature designation acquisition unit 115 acquires the feature ID of a feature designated by a user on the area map displayed by the application terminal 300. Hereinafter, the designated feature will be simply referred to as the "designated feature." The attribute information extraction unit 116 extracts usage attribute information associated with the feature ID of the designated feature from the attribute database 112.

In some cases, the usage attribute information is not associated with the designated feature itself, but is associated with other features related to the designated feature. For example, if the designated feature is a site, usage attribute information may not be associated with the site itself, but is associated with buildings on the site. In some cases, if the designated feature is an administrative district, usage attribute information may not be associated with the administrative district itself, nor with a site within the administrative district, but is associated with buildings on a site within the administrative district. In such cases, the attribute information extraction unit 116 may extract usage attribute information of features related to the designated feature as usage attribute information of the designated feature.

The usage status output unit 117 (output unit) outputs usage status information of the designated feature based on the usage attribute information extracted by the attribute information extraction unit 116. For example, the usage status output unit 117 causes the application terminal 300 to display the usage status information of the designated feature. Displaying the usage status information of the designated feature on the application terminal 300 simply includes displaying the usage attribute information extracted by the attribute information extraction unit 116 on the application terminal 300. The usage status information is effective in improving the utilization efficiency of the feature. As an example, it is possible to check vacant rooms in a building based on the usage status information and make efficient use of the vacant rooms.

The usage status output unit 117 may output usage status information including a change history of the usage attributes of the target feature based on the addition and deletion dates of the usage attribute information extracted by the attribute information extraction unit 116. For example, in the case of the above example 1-1), the usage status output unit 117 may cause the application terminal 300 to display a list showing multiple sets of usage attribute information in chronological order based on the addition and deletion dates of each piece of usage attribute information (see FIG. 6).

Usage information including the change history of usage attributes is useful, for example, for investigating the usage of a feature retrospectively. Investigating the usage of a feature retrospectively is useful, for example, for evaluating the brand value of the feature. Investigating the usage of a feature retrospectively is also useful for quickly and accurately conducting PCB investigations or land contamination investigations, etc.

In the case of the above example 1-2), the usage status output unit 117 may cause the application terminal 300 to display a list showing multiple sets of usage attribute information extracted by the attribute information extraction unit 116, by floor number or room number (see FIG. 7). In this case, by showing the usage status information of the feature in more detail, it is possible to further improve the usage efficiency of the feature.

The map server 100 may be configured to send a push notification of the update to the application terminal 300 when the usage attribute information of the specified feature is updated. For example, the map server 100 may further include an update notification unit 121 and a monitoring target storage unit 122.

The update notification unit 121 acquires from the application terminal 300 a notification necessity designation that specifies whether or not a push notification of the update is required. For example, the update notification unit 121 acquires a notification necessity designation input by the user to the application terminal 300 for the specified feature. If it is designated that a push notification is required for the specified feature, the update notification unit 121 stores the feature ID of the specified feature in the monitored object storage unit 122. Thereafter, each time the stored contents of the attribute database 112 are updated, the update notification unit 121 checks whether the feature ID of the updated attribute information is stored in the monitored object storage unit 122. If the feature ID of the updated attribute information is stored in the monitored object storage unit 122, the update notification unit 121 transmits the update contents to the application terminal 300.

The map server 100 may be configured to extract feature IDs of features whose usage conditions satisfy extraction conditions from the attribute database 112, and output the extraction results. For example, the map server 100 may further include an extraction condition acquisition unit 131 and an ID extraction unit 132.

The extraction condition acquisition unit 131 acquires the extraction conditions from the application terminal 300. For example, the extraction condition acquisition unit 131 acquires the extraction conditions input by the user to the application terminal 300. Specific examples of the extraction conditions are shown below.
Example 2-1) Currently vacant.
Example 2-2) It is a new building.
Example 2-3) The building age must be greater than or equal to a specified number of years.
Example 2-4) The frequency of deletion/addition of usage attributes (for example, frequency within a specified period) is above a specified level.
Example 2-5) The frequency of disappearance and creation of buildings on the premises (e.g., frequency within a specified period) is above a specified level.

The ID extraction unit 132 extracts feature IDs of features (hereinafter referred to as "relevant features") whose usage conditions satisfy the extraction conditions acquired by the extraction condition acquisition unit 131 from the attribute database 112. For example, the ID extraction unit 132 extracts usage attribute information that satisfies the extraction conditions from the attribute database 112, and extracts feature IDs included in the extracted usage attribute information as feature IDs of the relevant features. The map server 100 may display the extraction results by the ID extraction unit 132 as a list on the application terminal 300, or may display the extraction results by the ID extraction unit 132 as a distribution on the area map displayed by the application terminal 300.

For example, the map data generation unit 114 generates map data indicating feature information whose usage status satisfies the extraction condition based on the feature ID extracted by the ID extraction unit 132 and the feature database 111. For example, the map data generation unit 114 extracts coordinate information corresponding to the feature ID extracted by the ID extraction unit 132 from the feature database 111, and regenerates the area map data so that the portion corresponding to the coordinate information is highlighted. This makes it possible to clearly show the distribution of features whose usage status satisfies the extraction condition within the display target area.

For example, according to the extraction conditions in Example 2-1) above, it is possible to display the distribution of currently vacant features. The distribution of vacant features is useful for planning redevelopment of the display area. In addition, since it is predicted that there will be a high demand for refreshing vacant features through renovation, the distribution of vacant features is also useful for efficiently selling renovations, etc.

According to the extraction conditions in Example 2-2), the distribution of newly constructed land features can be shown. The distribution of newly constructed land features is effective for efficiently selling infrastructure services such as city gas. The distribution of newly constructed land features is also effective for efficiently interpreting changes in fixed asset taxes. According to the extraction conditions in Example 2-3), the distribution of land features expected to deteriorate can be shown. The distribution of land features expected to deteriorate is effective for efficiently carrying out resilience construction work in the display area. The distribution of land features expected to deteriorate is also effective for efficiently selling remodeling or renovation.

The extraction conditions in Example 2-4) make it possible to show the distribution of features with a high turnover of tenants. The distribution of features with a high turnover of tenants is useful for planning the opening of chain stores, etc. The extraction conditions in Example 2-5) make it possible to show the distribution of sites with a high frequency of building renewal. The distribution of sites with a high frequency of building renewal is useful for estimating the growth rate of the area being displayed.

In this way, by setting the extraction conditions appropriately, it is possible to obtain various information that contributes to the efficient use of geographical features. It is also possible to combine several extraction conditions. For example, it is possible to extract geographical features where buildings are updated infrequently and which are vacant, and show the distribution of such geographical features. In display target areas where buildings are updated infrequently and there are many vacant geographical features, it is also possible to improve efficiency by reducing the scale of public facilities to suit the actual situation.

The map server 100 may be configured to update the map data in response to a maintenance input. For example, the map server 100 may be configured to add new usage attribute information including information indicating the date of addition to the feature ID in association with the feature ID in the attribute database 112 in response to an attribute addition input notifying the addition of a usage attribute of a feature. The map server 100 may be configured to add information indicating the date of deletion to the already registered usage attribute information indicating the usage attribute in question in association with the feature ID in association with the usage attribute information in the attribute database 112 in response to an attribute deletion input notifying the deletion of a usage attribute of a feature.

The map server 100 may be configured to generate a new feature ID for a feature in response to a generation notification input notifying the new generation of a feature, and store new feature information including the feature ID and coordinate information of the feature in the feature database 111. The map server 100 may be configured to store the new feature information including information indicating the generation date of the feature in the feature database 111. The map server 100 may be configured to add information indicating the destruction date to the feature information of the feature in response to a destruction notification input, and leave the information in the feature database 111.

For example, as shown in FIG. 8, the map server 100 further includes an area designation acquisition unit 141, a map data generation unit 142, a feature designation acquisition unit 143, an editing content selection unit 144, a feature information registration unit 145, and an attribute information registration unit 146.

The area designation acquisition unit 141 acquires the area designation for map display from the maintenance terminal 200. Hereinafter, the area designated by the area designation is referred to as the "maintenance target area." For example, the area designation acquisition unit 141 acquires the area designation input by the maintenance worker to the maintenance terminal 200.

The map data generation unit 142 generates maintenance map data for displaying a map of the maintenance target area, and transmits it to the maintenance terminal 200. For example, the map data generation unit 142 extracts feature information of all features to be displayed on a map of the maintenance target area (hereinafter referred to as "display target features") from the feature database 111 based on the coordinate information of each feature information, and generates maintenance map data based on the extracted feature information. Furthermore, the map data generation unit 142 may extract usage attribute information associated with the feature IDs of the display target features from the attribute database 112, and include the extracted usage attribute information in the map data. The maintenance terminal 200 displays a map of the maintenance target area (hereinafter referred to as the "maintenance area map") based on the maintenance map data.

The feature designation acquisition unit 143 acquires the feature ID of the feature designated by the maintenance worker on the maintenance area map displayed by the maintenance terminal 200. Hereinafter, the designated feature is referred to as the "maintenance target feature."

The editing content selection unit 144 acquires an editing content specification for the maintenance target feature from the maintenance terminal 200, and selects editing content for the maintenance target feature in accordance with the editing content specification. Specific examples of editing content are shown below.
Example 3-1) New registration of feature information related to the feature under maintenance.
Example 3-2) Changing the feature information of a feature subject to maintenance.
Example 3-3) Adding usage attribute information of the object to be maintained.
Example 3-4) Changing the usage attribute information of the maintenance target feature.

In response to a generation notification input notifying the new generation of a feature, the feature information registration unit 145 generates a new feature ID for the feature, and adds new feature information including the feature ID and coordinate information for the feature to the feature database 111. The feature information registration unit 145 may store the new feature information in the feature database 111 together with the feature's generation date information. In response to a deletion notification input for a feature, the feature information registration unit 145 may add deletion date information to the feature information for the feature and leave it in the feature database 111.

As described above, the creation date information may be information indicating the creation date with an error within an acceptable range for practical use, or may be information indicating a period including the creation date. The creation date information may be information specifying the creation date as well as the hour, minute, and second of creation. The destruction date information may be information indicating the destruction date with an error within an acceptable range for practical use, or may be information indicating a period including the destruction date. The destruction date information may be information specifying the destruction date as well as the hour, minute, and second of destruction.

For example, when the editing content of Example 3-1) above is selected by the editing content selection unit 144 as an example of a generation notification input notifying the new generation of a feature, the feature information registration unit 145 stores the new feature information in the feature database 111. At this time, the feature information registration unit 145 may include the feature ID of the maintenance target feature in the new feature information as a related feature ID.

When the editing content selection unit 144 selects the editing content of example 3-2) above, the feature information registration unit 145 changes the feature information of the maintenance target feature. When the change content is other than the disappearance of the maintenance target feature, the feature information registration unit 145 changes the feature information of the maintenance target feature based on the newly input basic attributes. When the change content is the disappearance of the maintenance target feature, the feature information registration unit 145 adds disappearance date information to the feature information of the maintenance target feature.

In response to an attribute addition input notifying the addition of a use attribute of a feature, the attribute information registration unit 146 adds new use attribute information including information indicating the addition date to the attribute database 112 in association with the feature ID. In response to an attribute deletion input notifying the deletion of a use attribute of a feature, the attribute information registration unit 146 may add information indicating the deletion date to already-registered use attribute information indicating the use attribute, and leave the use attribute information in the attribute database 112 in association with the feature ID.

As described above, the addition date information may be information indicating the addition date with an error within an acceptable range for practical use, or may be information indicating a period including the addition date. The addition date information may be information specifying the addition date as well as the hour, minute, and second. The deletion date information may be information indicating the deletion date with an error within an acceptable range for practical use, or may be information indicating a period including the deletion date. The deletion date information may be information specifying the deletion date as well as the hour, minute, and second.

For example, when the editing content selection unit 144 selects the editing content of Example 3-3 above, the attribute information registration unit 146 adds the new usage attribute information to the attribute database 112 in association with the feature ID of the maintenance target feature. At this time, the attribute information registration unit 146 may generate a new attribute ID and include the generated attribute ID in the new usage attribute information.

When the editing content selection unit 144 selects the editing content of example 3-4) above, the attribute information registration unit 146 changes the existing usage attribute information of the maintenance target feature. When the changing content is other than the deletion of the existing usage attribute information, the attribute information registration unit 146 changes the existing usage attribute information based on the newly input usage attribute. When the changing content is the deletion of the existing usage attribute information, the attribute information registration unit 146 assigns deletion date information to the usage attribute information.

Note that even if the change is other than the deletion of existing usage attribute information, if the magnitude of the change exceeds a predetermined level, the attribute information registration unit 146 may add deletion date information to the usage attribute information and add new usage attribute information to the attribute database 112 in association with the feature ID of the maintenance target feature based on the newly input usage attribute. At this time, the attribute information registration unit 146 may generate a new attribute ID and include the generated attribute ID in the new usage attribute information. An example of a case where the magnitude of the change exceeds a predetermined level is a case where the difference between the unique part of the resident name before the change and the unique part of the resident name after the change exceeds a predetermined level. The unique part is, for example, the part excluding "Co., Ltd." from "... Co., Ltd.".

If there is a large difference in the unique part, it is highly likely that the resident has essentially changed. On the other hand, if there is a high similarity in the unique part, it is highly likely that the resident is essentially the same, even if the resident's name has changed. Therefore, if the difference between the unique part of the resident's name before the change and the unique part of the resident's name after the change exceeds a predetermined level, the attribute information registration unit 146 may add deletion date information to the existing usage attribute information, and based on the newly input usage attributes, add new usage attribute information to the attribute database 112 in association with the feature ID of the maintenance target feature.

9 is a block diagram illustrating the hardware configuration of the map server 100. As shown in FIG. 6, the map server 100 has a circuit 190. The circuit 190 has at least one processor 191, a memory 192, a storage 193, and a communication port 194. The storage 193 has a computer-readable storage medium such as a hard disk. The storage 193 stores a program for causing the map server 100 to execute the following: holding a feature database that accumulates feature information including the coordinate information of the feature and the feature's unique feature ID; holding an attribute database that accumulates feature attribute information in association with the feature ID; extracting attribute information associated with the feature ID of the specified feature from the attribute database; and outputting usage status information of the specified feature based on the attribute information extracted by the attribute information extraction unit. The storage 193 stores a program for causing the map server 100 to configure each of the above-mentioned functional blocks.

The memory 192 temporarily stores the programs loaded from the storage 193 and the results of calculations performed by the processor 191. The processor 191 configures each functional block of the map server 100 by executing the above programs in cooperation with the memory 192. The communication port 194 communicates with the maintenance terminal 200 and the application terminal 300 via the network line 9 according to instructions from the processor 191.

The circuit 190 is not necessarily limited to configuring each function by a program. For example, the circuit 190 may configure at least some of its functions by a dedicated logic circuit or an ASIC (Application Specific Integrated Circuit) that integrates the dedicated logic circuit.

[Map information maintenance procedures]
Next, as an example of a method for maintaining map information, a maintenance procedure executed by the map information system 1 will be illustrated. As shown in Fig. 10, the map server 100 first executes steps S01, S02, S03, S04, S05, S06, and S07. In step S01, the area designation acquisition unit 141 waits for an area designation for map display to be transmitted from the maintenance terminal 200.

In step S02, the map data generation unit 142 generates maintenance map data for displaying a map of the area specified by the area specification (the maintenance target area). For example, the map data generation unit 142 extracts feature information of all features to be displayed on a map of the maintenance target area from the feature database 111 based on the coordinate information of each feature information, and generates maintenance map data based on the extracted feature information. Furthermore, the map data generation unit 142 may extract usage attribute information associated with the feature ID of the display target feature from the attribute database 112, and include the extracted usage attribute information in the map data.

In step S03, the map data generation unit 142 transmits the generated maintenance map data to the maintenance terminal 200. The maintenance terminal 200 displays a map of the area to be maintained (the above-mentioned maintenance area map) based on the maintenance map data.

In step S04, the feature designation acquisition unit 143 waits for the maintenance worker to designate a feature on the maintenance area map displayed by the maintenance terminal 200. In step S05, the feature designation acquisition unit 143 acquires from the maintenance terminal 200 the feature ID of the feature designated by the maintenance worker (the above-mentioned maintenance target feature).

In step S06, the editing content selection unit 144 acquires an editing content specification for the maintenance target feature from the maintenance terminal 200, and selects editing content for the maintenance target feature according to the editing content specification. In step S07, the feature information registration unit 145 checks whether the editing content selection unit 144 has selected new registration of a feature related to the maintenance target feature (example 3-1 above).

If the editing content selection unit 144 determines in step S07 that new registration of a feature related to the maintenance target feature has been selected, the map server 100 executes steps S08, S09, and S11. In step S08, the feature information registration unit 145 generates a new feature ID for the feature to be newly registered (hereinafter referred to as the "new feature"). In step S09, the feature information registration unit 145 adds new feature information including the newly generated feature ID and coordinate information of the new feature to the feature database 111.

In step S11, the area designation acquisition unit 141 checks whether or not a maintenance end instruction has been sent from the maintenance terminal 200. If it is determined that a maintenance end instruction has been sent from the maintenance terminal 200, the map server 100 ends the maintenance procedure.

If it is determined that a maintenance end instruction has not been sent from the maintenance terminal 200, the map server 100 executes step S12. In step S12, the area designation acquisition unit 141 checks whether or not an instruction to change the area of the map display has been sent from the maintenance terminal 200. If it is determined that an instruction to change the area of the map display has been sent from the maintenance terminal 200, the map server 100 returns the process to step S01. If it is determined that an instruction to change the area of the map display has not been sent from the maintenance terminal 200, the map server 100 returns the process to step S04.

If the editing content selection unit 144 determines in step S07 that new registration of a feature related to the maintenance target feature has not been selected, the map server 100 executes step S13, as shown in FIG. 11. In step S13, the feature information registration unit 145 checks whether the editing content selection unit 144 has selected changing the feature information of the maintenance target feature (example 3-2 above).

If the editing content selection unit 144 determines in step S13 that a change to the feature information of the maintenance target feature has been selected, the map server 100 executes step S14. In step S14, the feature information registration unit 145 checks whether the change to the feature information is the disappearance of the maintenance target feature.

If it is determined in step S14 that the change in the feature information is other than the disappearance of the maintenance target feature, the map server 100 executes step S15. In step S15, the feature information registration unit 145 changes the feature information of the maintenance target feature based on the newly input basic attributes.

If it is determined in step S14 that the change in the feature information is the disappearance of a maintenance target feature, the map server 100 executes step S16. In step S16, the feature information registration unit 145 adds disappearance date information to the feature information of the maintenance target feature. After steps S15 and S16, the map server 100 executes step S11.

If it is determined in step S13 that changing the feature information of the maintenance target feature has not been selected, the map server 100 executes step S21, as shown in FIG. 12. In step S21, the attribute information registration unit 146 checks whether the editing content selection unit 144 has selected adding the usage attribute information of the maintenance target feature (example 3-3 above)) or changing the usage attribute information of the maintenance target feature (example 3-4 above).

If it is determined in step S21 that adding use attribute information of the maintenance target feature has been selected, the map server 100 executes steps S22 and S23. In step S22, the attribute information registration unit 146 generates a new attribute ID for the use attribute to be added (hereinafter referred to as the "new attribute"). In step S23, the attribute information registration unit 146 adds new use attribute information including the newly generated attribute ID and information on the new attribute to the attribute database 112 in association with the feature ID of the maintenance target feature. The map server 100 then returns the process to step S01.

If it is determined in step S21 that a change to the use attribute information of the maintenance target feature has been selected, the map server 100 executes step S31. In step S31, the attribute information registration unit 146 checks whether the change to the use attribute information is the deletion of a use attribute.

If it is determined in step S31 that the change to the usage attribute information is not the deletion of a usage attribute, the map server 100 executes step S32. In step S32, the attribute information registration unit 146 checks whether the magnitude of the change is equal to or less than a predetermined level.

If it is determined in step S32 that the magnitude of the change is equal to or less than the predetermined level, the map server 100 executes step S33. In step S33, the attribute information registration unit 146 changes the existing usage attribute information based on the newly input usage attribute.

If it is determined in step S32 that the magnitude of the change exceeds a predetermined level, the map server 100 executes steps S34, S35, and S36. In step S34, the attribute information registration unit 146 adds deletion date information to the existing usage attribute information. In step S35, the attribute information registration unit 146 generates a new attribute ID for the newly input usage attribute. In step S36, the attribute information registration unit 146 adds new usage attribute information including the newly generated attribute ID and the newly input usage attribute to the attribute database 112 in association with the feature ID of the maintenance target feature.

If it is determined in step S31 that the change to the usage attribute information is the deletion of a usage attribute, the map server 100 executes step S37. In step S37, the attribute information registration unit 146 adds deletion date information to the existing usage attribute information. After steps S33, S36, and S37, the map server 100 executes step S11. The map server 100 repeats the above procedure.

[How to display usage status]
Next, as an example of a method for displaying the utilization status of features, a utilization status display procedure executed by the map information system 1 will be illustrated. As shown in Fig. 13, the map server 100 first executes step S41. In step S41, the area designation acquisition unit 113 checks whether or not an area designation for map display has been transmitted from the application terminal 300.

If it is determined in step S41 that the area specification for map display has been transmitted from the application terminal 300, the map server 100 executes steps S42, S43, S44, S45, S46, and S47. In step S42, the map data generation unit 114 generates area map data for displaying a map of the area specified by the area specification (the display target area). Based on the coordinate information of each feature information, the map data generation unit 114 extracts feature information of all features to be displayed on the map of the display target area from the feature database 111, and generates area map data based on the extracted feature information.

In step S43, the map data generation unit 114 transmits the generated area map data to the application terminal 300. The application terminal 300 displays a map of the display target area (the above-mentioned area map) based on the area map data. In step S44, the feature designation acquisition unit 115 waits for the user to designate a feature on the area map displayed by the application terminal 300. In step S45, the attribute information extraction unit 116 extracts from the attribute database 112 the usage attribute information associated with the feature ID of the feature designated by the user (the above-mentioned designated feature).

In step S46, the usage status output unit 117 outputs usage status information of the specified feature based on the usage attribute information extracted by the attribute information extraction unit 116. For example, the usage status output unit 117 causes the application terminal 300 to display the usage status information of the specified feature. In step S47, the update notification unit 121 acquires from the application terminal 300 a notification necessity designation that specifies whether or not a push notification of the above update is required for the specified feature, and confirms whether or not a push notification is required based on the notification necessity designation.

If it is determined in step S47 that a push notification has been requested, the map server 100 executes step S48. In step S48, the update notification unit 121 stores the feature ID of the specified feature in the monitored object storage unit 122 in association with the user's identification information. If it is determined in step S47 that a push notification has not been requested, the map server 100 omits step S48.

Next, the map server 100 executes step S55. Even if it is determined in step S47 that a push notification has not been requested, the map server 100 executes step S55. In step S55, the area designation acquisition unit 113 checks whether an instruction to end the display of the usage status has been sent from the application terminal 300.

If it is determined in step S55 that an instruction to end the display of the usage status has been sent from the application terminal 300, the map server 100 ends the usage status display procedure. If it is determined in step S55 that an instruction to end the display of the usage status has not been sent from the application terminal 300, the map server 100 executes step S56. In step S56, the area designation acquisition unit 113 checks whether or not an instruction to change the area of the map display has been sent from the application terminal 300. If it is determined that an instruction to change the area of the map display has been sent from the application terminal 300, the map server 100 returns the process to step S41. If it is determined that an instruction to change the area of the map display has not been sent from the application terminal 300, the map server 100 returns the process to step S44.

If it is determined in step S41 that the area designation for map display has not been transmitted from the application terminal 300, the map server 100 executes step S51. In step S51, the extraction condition acquisition unit 131 checks whether the feature extraction conditions have been transmitted from the application terminal 300.

If it is determined in step S51 that the feature extraction conditions have not been transmitted from the application terminal 300, the map server 100 returns the process to step S41. If it is determined in step S51 that the feature extraction conditions have been transmitted from the application terminal 300, the map server 100 executes steps S52, S53, and S54. In step S52, the extraction condition acquisition unit 131 acquires the feature extraction conditions from the application terminal 300. In step S53, the ID extraction unit 132 extracts, from the attribute database 112, the feature ID of a feature whose usage status satisfies the extraction conditions acquired by the extraction condition acquisition unit 131.

In step S54, the map data generation unit 114 generates map data indicating feature information whose usage status satisfies the extraction condition, based on the feature ID extracted by the ID extraction unit 132 and the feature database 111. For example, the map data generation unit 114 extracts coordinate information corresponding to the feature ID extracted by the ID extraction unit 132 from the feature database 111, and regenerates the area map data so as to highlight the portion corresponding to the coordinate information. The map data generation unit 114 transmits the regenerated area map data to the application terminal 300. The application terminal 300 displays an area map with the extraction result highlighted, based on the regenerated area map data.

Next, the map server 100 executes step S57. In step S57, the area designation acquisition unit 113 checks whether an instruction to end the display of the usage status has been sent from the application terminal 300.

If it is determined in step S57 that an instruction to end the display of the usage status has been sent from the application terminal 300, the map server 100 ends the usage status display procedure. If it is determined in step S57 that an instruction to end the display of the usage status has not been sent from the application terminal 300, the map server 100 returns the process to step S41.

Figure 14 is a flowchart illustrating an example of a procedure for notifying update of attribute information for features registered in the monitored object storage unit 122 in step S48. As shown in Figure 14, the map server 100 first executes steps S61 and S62. In step S61, the update notification unit 121 waits for an update of the contents stored in the attribute database 112. In step S62, the update notification unit 121 checks whether the feature ID of the updated attribute information (hereinafter referred to as the "notification target feature ID") is stored in the monitored object storage unit 122.

If it is determined in step S62 that the notification target feature ID is not stored in the monitored target storage unit 122, the map server 100 returns the process to step S61. If it is determined in step S62 that the notification target feature ID is stored in the monitored target storage unit 122, the map server 100 executes step S63. In step S63, the update notification unit 121 transmits the update contents to the app terminal 300 of the user associated with the notification target feature ID in the monitored target storage unit 122. Thereafter, the map server 100 returns the process to step S61. The map server 100 repeats the above process.

[Effects of this embodiment]
As described above, the map information system 1 comprises a feature database 111 that accumulates feature information including coordinate information of features and unique feature IDs of the features, an attribute database 112 that accumulates attribute information of features in association with the feature IDs, an attribute information extraction unit 116 that extracts attribute information associated with the feature ID of a specified feature from the attribute database 112, and a usage status output unit 117 that outputs usage status information of the specified feature based on the attribute information extracted by the attribute information extraction unit 116.

In this map information system 1, a unique feature ID is assigned to the feature information itself, including the coordinate information of the feature, and the attribute information of the feature is stored in association with the feature ID. This makes it possible to clearly distinguish between changes in coordinate information resulting from the expansion or reduction of a building or modifications to the map data itself, and changes in coordinate information resulting from the replacement of the feature itself, and to aggregate various attribute information for each feature. The attribute information aggregated for each feature is useful for the efficient operation of the features, etc. Therefore, this map information system 1 is effective in increasing the added value of map data.

Furthermore, a data structure in which feature information is assigned a unique feature ID is also effective in easily customizing map display. For example, by linking custom drawing data generated to emphasize a specific feature to the feature ID, the custom drawing data can be easily combined with the base map data. This makes it possible to provide more useful usage information. For example, even if a feature's coordinates change, if the feature's ID is the same, attribute information before the coordinate change and attribute information after the coordinate change can be linked to the same feature and stored, providing a history of consolidated attribute information for the same feature.

The map information system 1 may further include an attribute information registration unit 146 that, in response to an attribute addition input that notifies the addition of an attribute of a feature, adds new attribute information, including information indicating the date of addition, to the attribute database 112 in association with the feature ID. In this case, more useful usage information can be provided based on attribute information including the date of addition.

In response to an attribute deletion input notifying the deletion of an attribute of a feature, the attribute information registration unit 146 may include information indicating the deletion date in the already registered attribute information indicating the attribute, and may associate the attribute information with the feature ID and leave it in the attribute database 112. In this case, the history of attribute information for the feature can be appropriately managed, and more useful usage information can be provided.

The usage status output unit 117 may output usage status information including a change history of the attributes of the specified feature based on the addition and deletion dates of the attribute information extracted by the attribute information extraction unit 116. In this case, more useful usage status information can be provided.

The map information system 1 may further include a feature information registration unit 145 that, in response to a generation notification input notifying the new generation of a feature, generates a new feature ID for the feature and adds new feature information including the feature ID and coordinate information of the feature to the feature database 111. In this case, by generating a new feature ID each time a new feature is generated, it is possible to thoroughly manage feature information with feature IDs attached.

The feature information registration unit 145 may add new feature information to the feature database 111, including information indicating the date of creation of the feature. In this case, by basing the information on the feature information including the date of creation, it is possible to provide more useful usage information for higher-level features. For example, by basing the information on the feature information including the date of creation of a building (feature), it is possible to provide more useful usage information for the site on which the building is located (higher-level feature).

In response to input of a feature's disappearance notification, the feature information registration unit 145 may add information indicating the disappearance date to the feature information of the feature and leave it in the feature database 111. In this case, by appropriately managing the feature's history, it is possible to provide more useful usage information for higher-ranking features.

The map information system 1 may further include an ID extraction unit 132 that extracts feature IDs of features whose usage conditions satisfy the extraction conditions from the attribute database 112 based on a condition specification input that defines the extraction conditions for the usage conditions, and a map data generation unit 114 that generates map data indicating feature information whose usage conditions satisfy the extraction conditions based on the feature IDs extracted by the ID extraction unit 132 and the feature database 111. In this case, it is possible to easily provide bird's-eye view usage information for features over a wider area, such as administrative districts.

Although the embodiments have been described above, the present disclosure is not necessarily limited to the above-described embodiments, and various modifications are possible without departing from the spirit of the present disclosure.

The aspects described in all or part of the above embodiments solve any one of the following problems: control of movement paths, improvement of processing speed, improvement of processing accuracy, improvement of usability, improvement of functions using data or provision of appropriate functions, other improvement of functions or provision of appropriate functions, reduction of data and/or program capacity, miniaturization of devices and/or systems, provision of appropriate data, programs, recording media, devices and/or systems, and optimization of the production and manufacturing of data, programs, recording media, devices and/or systems, such as reduction of production and manufacturing costs of data, programs, devices or systems, simplification of production and manufacturing, and shortening of production and manufacturing time.

1...map information system, 111...feature database, 112...attribute database, 114...map data generation unit, 116...attribute information extraction unit, 117...usage status output unit (output unit), 132...ID extraction unit, 145...feature information registration unit, 146...attribute information registration unit.

Claims (9)

a feature database that stores feature information including coordinate information of features and unique feature IDs of the features;
an attribute database that stores attribute information indicating addition, deletion, and content of attributes of a feature in association with a feature ID;
an attribute information registration unit which performs the following operations in the attribute database: generating utilization attribute information corresponding to a new utilization attribute corresponding to the feature ID of a designated feature when a new utilization attribute is assigned to the designated feature; registering information indicating the deletion in the utilization attribute information when a utilization attribute is deleted from the designated feature; and changing the content of the utilization attribute information when the content of the utilization attribute assigned to the designated feature is changed;
an attribute information extraction unit that extracts, from the attribute database, utilization attribute information associated with a feature ID of a specified feature;
an output unit that outputs usage status information representing addition, deletion, and content change history of the usage attributes assigned to the designated feature based on the usage attribute information extracted by the attribute information extraction unit ;
the attribute information registration unit, when the change in the content of the usage attribute exceeds a predetermined level, registers information indicating deletion in the usage attribute information corresponding to the usage attribute, and generates new usage attribute information corresponding to the changed usage attribute;
If the change in the content of the usage attribute does not exceed a predetermined level, the content of the usage attribute information corresponding to the usage attribute is changed.
Map information system. 2. The map information system according to claim 1 , wherein the output unit outputs, as the usage status information , a plurality of pieces of usage attribute information of the specified feature arranged in chronological order based on the usage attribute information extracted by the attribute information extraction unit. The map information system according to claim 1 or 2, further comprising a feature information registration unit that generates a new feature ID for the feature in response to a generation notification input notifying the creation of a new feature, and adds new feature information including the feature ID of the feature and coordinate information of the feature to the feature database. 4. The map information system according to claim 3 , wherein the feature information registration unit adds new feature information to the feature database while including information indicating a date of creation of the feature in the new feature information. 5. The map information system according to claim 4 , wherein said feature information registration unit, in response to an input of a feature's disappearance notification, adds information indicating a disappearance date to the feature information of the feature and leaves the information in said feature database. The feature information includes basic attributes that represent the characteristics of the corresponding feature itself;
the feature information registration unit changes the feature information of the feature based on the newly input basic attributes of the feature;
The map information system according to any one of claims 3 to 5. The feature information includes a related feature ID, which is a feature ID of another feature having a relationship with the corresponding feature;
The feature information registration unit registers the related feature ID in feature information of the corresponding feature,
The attribute information extraction unit extracts, from the attribute database, utilization attribute information associated with a related feature ID included in the feature information of the specified feature, as utilization attribute information of the specified feature.
The map information system according to any one of claims 3 to 6. an ID extraction unit that extracts, based on a condition specification input that defines an extraction condition for a usage situation, from the attribute database, a feature ID of a feature whose usage situation satisfies the extraction condition;
a map data generating unit configured to generate map data indicating feature information whose usage status satisfies the extraction condition based on the feature ID extracted by the ID extracting unit and the feature database,
The map information system according to any one of claims 1 to 7. a monitoring target storage unit that stores a feature ID of a feature to be monitored in association with a user's identification information;
an update notification unit that transmits the update contents to a user terminal corresponding to the identification information associated with the feature ID stored in the monitoring target storage unit every time the usage attribute information in the attribute database is updated;
Equipped with
The map information system according to any one of claims 1 to 8.

Images