Map Information System

Abstract

To provide a map information system that is effective in improving the value added to map data.SOLUTION: A map information system 1 comprises: a feature database 111 that accumulates feature information including information on the coordinates of features and feature IDs unique to the features; an attribute database 112 that accumulates information on the attributes of the features in association with the feature IDs; an attribute information extraction unit 116 that extracts the attribute information associated with the feature ID of a designated feature from the attribute database 112; and a usage state output unit 117 that, based on the attribute information extracted by the attribute information extraction unit 116, outputs information on the usage state of the designated feature.SELECTED DRAWING: Figure 2

Description

Technical Field

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

Background Art

[0002] Patent Document 1 discloses a geographic information system including 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 indicating a building and information on the time when the building existed. The attribute database stores the attributes of the buildings included in the map data. The attribute data is associated with the graphic shape data by location information.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The present disclosure provides a map information system effective for improving the added value of map data.

Means for Solving the Problems

[0005] A map information system according to one aspect of the present disclosure includes a feature database that stores feature information including coordinate information of a feature and a unique feature ID of the feature, an attribute database that stores attribute information of the feature in association with the feature ID, an attribute information extraction unit that extracts attribute information associated with the feature ID of a specified feature from the attribute database, and an output unit that outputs usage status information of the specified feature based on the attribute information extracted by the attribute information extraction unit.

Brief Description of the Drawings

[0006] [Figure 1] This is a schematic diagram illustrating the configuration of a geographic information system. [Figure 2] This is a block diagram illustrating a configuration for outputting usage status information. [Figure 3] This is a table illustrating a set of feature information. [Figure 4] This table shows variations of a set of feature information. [Figure 5] This is a table illustrating a set of attribute information. [Figure 6] This is a table illustrating how usage status can be displayed. [Figure 7] This table shows variations in how usage status is displayed. [Figure 8] This is a block diagram illustrating an example of a configuration for maintaining map data. [Figure 9] This diagram illustrates the hardware configuration of a map server. [Figure 10] This is a flowchart illustrating the maintenance procedure for map data. [Figure 11] This is a flowchart illustrating the maintenance procedure for map data. [Figure 12] This is a flowchart illustrating the maintenance procedure for map data. [Figure 13] This is a flowchart illustrating the procedure for displaying usage status. [Figure 14] This flowchart illustrates the procedure for notifying users of attribute information updates. [Modes for carrying out the invention]

[0007] The embodiments will be described in detail below with reference to the drawings. In the description, the same elements or elements having the same function will be denoted by the same reference numeral, and redundant descriptions will be omitted.

[0008] [Map Information System] The map information system 1 shown in Figure 1 is a system that manages and provides map data for displaying maps. The added value of map data can be enhanced if various attributes that directly or indirectly represent the usage status of features constituting a map can be easily aggregated and the usage status of these features can be shown. Attributes of features can be added, deleted, or changed over time. Therefore, a large number of attributes are assigned to a feature during the period from its creation to its disappearance. If these attributes can be easily aggregated, the usage status of the features can be accurately shown.

[0009] However, changes can occur to the geographic feature itself during the period from its creation to its disappearance. Specific examples of changes to the geographic feature include additions or subtractions to the structure. Furthermore, even if no actual changes occur to the geographic feature, changes may occur in the data representing its location and shape due to corrections to survey results, etc.

[0010] When an entire feature is replaced by another feature, causing a change in the feature's data, the attribute information of the feature before the change and the attribute information of the feature after the change need to be associated with different features. This is hereinafter referred to as "Case 1". On the other hand, when the change in existing feature data is merely due to expansion, reduction, or data modification, the attribute information of the feature before the change and the attribute information of the feature after the change need to be aggregated for the same feature. This is hereinafter referred to as "Case 2". Distinguishing between Case 1 and Case 2 based solely on changes in the location and shape of a feature can be difficult, and it may not be possible to properly aggregate the attributes of the same feature.

[0011] In contrast, the map information system 1 includes a feature database that stores feature information including the coordinate information of features and unique feature IDs of features, an attribute database that stores the attribute information of features in association with the feature IDs, an ID selection unit that selects the feature ID of the target feature, an attribute information extraction unit that extracts the attribute information associated with the feature ID of the target feature from the attribute database, and an output unit that outputs the 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 stored in association with the feature ID. This makes it possible to clearly distinguish between changes in coordinate information caused by building extensions, demolitions, or modifications of the map data itself, and changes in coordinate information due to replacement of the features themselves, and to aggregate various attribute information for each feature. Hereinafter, the configuration of the map information system 1 will be illustrated in detail.

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

[0013] The maintenance terminal 200 is a terminal of an operator 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.

[0014] The map server 100 is configured to execute: holding a feature database that stores feature information including the coordinate information of features and the unique feature ID of each feature; holding an attribute database that stores the attribute information of features in association with the feature IDs; extracting the attribute information associated with the feature ID of a specified feature from the attribute database; and outputting the usage status information of the specified feature based on the attribute information extracted by the attribute information extraction unit.

[0015] FIG. 2 is a block diagram illustrating the functional configuration of the map server 100. As shown in FIG. 2, the map server 100 includes, as functional components (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.

[0016] The feature database 111 stores feature information including the coordinate information of features and the unique feature ID of each feature. Features include all objects that exist at fixed positions in the global coordinate system. Specific examples of features include roads, line indicators on the road surface, signs and signals installed on the road, road shoulders, sites around the road, buildings on the site, administrative divisions that group multiple sites, and the like. The coordinate information of a feature is, for example, a coordinate point sequence that represents the position and three-dimensional shape of the feature in the global coordinate system.

[0017] The feature ID is identification information generated for each feature so as to be a unique value. The fact that the feature ID is unique means that there is only one feature to which the feature ID is assigned. In other words, the feature database 111 does not include feature information of two or more features to which the same feature ID is assigned. As long as each feature information can be identified from all other feature information, there is no particular limitation on the data format of the feature ID. The feature information may further include basic attributes that represent the nature of the feature itself.

[0018] Figure 3 is a table illustrating a set of feature information. As illustrated in Figure 3, feature information may include, in addition to the feature ID and coordinate information mentioned above, the basic attributes of the feature, creation date information, and disappearance date information. 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 types include, for example, "office building," "warehouse," "factory," "detached house," "apartment building," and "shop."

[0019] The generation date refers to the date on which a feature is created through new construction or other means. Generation date information is information that indicates the generation date. Indicates the generation date includes indicating the generation date with an error within a range acceptable for practical use. Therefore, generation date information may also be information that indicates a period including the generation date. For example, generation date information may be information that specifies a week, such as "Xth week of month X," or information that specifies a month, such as "Xth month." In addition to the generation date, generation date information may also be information that specifies the hour, minute, and second of generation.

[0020] The date of disappearance refers to the date on which a building disappears due to demolition or other reasons. The date of disappearance information is information that indicates the date of disappearance. Indicates the date of disappearance includes indicating the creation date with an error within a range permissible in practical use. Therefore, the date of disappearance information may also be information that indicates a period including the date of disappearance. For example, the date of disappearance information may be information that specifies a week, such as "week X of month X," or information that specifies a month, such as "month X." In addition to the date of disappearance, the date of disappearance information may also specify the time, minute, and second of disappearance. In the feature information of existing features, the date of disappearance information is left blank. Therefore, whether or not a feature exists can be confirmed by whether or not the date of disappearance information is blank. Alternatively, instead of leaving the date of disappearance information blank, information that explicitly indicates that it is still existing (hereinafter referred to as "currently existing information") may be included in the date of disappearance information. In this case, whether or not a feature exists can be confirmed by whether or not the current existing information is included in the date of disappearance information.

[0021] Furthermore, each feature may have relationships with other features on a map. For example, a building standing on a plot of land can be said to have a relationship with that plot of land. Similarly, a plot of land included within an administrative district can be said to have a relationship with that administrative district. A road sign installed on a road can be said to have a relationship with that road. To clarify such relationships, feature information may further include the IDs of other related features (related feature IDs in Figure 4). Furthermore, feature information may further include the type of relationship (not shown) with the other features mentioned above. Specific examples of relationship types include "inclusion relationships," such as the relationship between an administrative district and a plot of land within that administrative district; "loading relationships," such as the relationship between a plot of land and a building on that plot; and "intersection relationships," such as the relationship between a road and a pedestrian bridge spanning that road.

[0022] The attribute database 112 stores the usage attribute information of a feature, associating it with the feature ID. Usage attribute information is a type of feature property that indicates how the feature is used. Specific examples of usage attribute information include the name of the occupant and the type of use. The type of use refers to the type of use the feature by the occupant. Specific examples of the type of use include "office work," "manufacturing," "merchandise sales," "services," and "living."

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

[0024] Even if there is no substantial change in the usage attributes, the usage attribute information may change. For example, even if the tenant and usage type remain essentially unchanged, a minor modification to the tenant's name may occur due to a company merger or similar event. In such cases, if the tenant is evaluated as having changed based on a minor modification to the name, it will be impossible to accurately represent the usage status of the property. By maintaining a unique attribute ID for each usage attribute, in addition to the tenant's name which may change even for the same tenant, 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 accurately represent the usage status of the property.

[0025] User attribute information may further include additional attribute information about the resident, information on the date of addition, and information on the date of deletion. Specific examples of additional attribute information about the resident include business hours and telephone number.

[0026] The "addition date" refers to the date on which usage attributes were added, such as when a new resident moves in. The addition date information is information indicating the addition date. Indicating the addition date includes indicating the addition date with an error within a range acceptable for practical use. Therefore, the addition date information may also be information indicating a period including the addition date. For example, the addition date information may be information that specifies a week, such as "Xth week of month X," or information that specifies a month, such as "Xth month." In addition to the addition date, the addition date information may also specify the time, minute, and second of the addition.

[0027] The deletion date refers to the date on which the usage attribute was deleted due to the tenant moving out, etc. The deletion date information is information indicating the deletion date. Indicating the deletion date includes indicating the deletion date with an error within a range permissible in practical use. Therefore, the deletion date information may also be information indicating a period including the deletion date. For example, the deletion date information may be information that specifies a week, such as "Xth week of month X," or information that specifies a month, such as "Xth month." In addition to the deletion date, the deletion date information may also specify the time, minute, and second of deletion. In the usage attribute information of an ongoing usage attribute, the deletion date information is left blank. Therefore, whether or not the usage attribute is ongoing can be confirmed by whether or not the deletion date information is blank. Alternatively, instead of leaving the deletion date information blank, information that explicitly indicates that it is ongoing (hereinafter referred to as "ongoing information") may be included in the deletion information. In this case, whether or not the usage attribute is ongoing can be confirmed by whether or not the continuing information is included in the deletion date information.

[0028] The attribute database 112 may contain 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 lengths of stay. Example 1-2) Multiple sets of usage attribute information corresponding to multiple residents who are simultaneously residing in the same property.

[0029] In the case of example 1-2) above, each of the multiple sets of user attribute information may further include the floor number or room number, etc., that identifies the area where each resident resides.

[0030] The area specification acquisition unit 113 acquires the area specification for map display from the application terminal 300. Hereinafter, the area specified by the area specification will be referred to as the "display target area". For example, the area specification acquisition unit 113 acquires the area specification entered by the map data user into the application terminal 300.

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

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

[0033] In some cases, the designated feature itself may not be associated with usage attribute information, but rather with other features related to the designated feature. For example, if the designated feature is a plot of land, the plot of land itself may not be associated with usage attribute information, but rather with buildings on the plot of land. If the designated feature is an administrative boundary, the administrative boundary itself may not be associated with usage attribute information, nor with plots of land within the administrative boundary, but rather with buildings on plots of land within the administrative boundary. In such cases, the attribute information extraction unit 116 may extract the usage attribute information of features related to the designated feature as the usage attribute information of the designated feature.

[0034] The usage status output unit 117 (output unit) outputs usage status information for the designated property based on the usage attribute information extracted by the attribute information extraction unit 116. For example, the usage status output unit 117 displays the usage status information for the designated property on the application terminal 300. Displaying the usage status information for the designated property on the application terminal 300 includes simply 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 property. For example, it becomes possible to check for vacant rooms in a building based on the usage status information and to efficiently utilize vacant rooms.

[0035] The usage status output unit 117 may output usage status information, including the history of changes to the usage attributes of the target object, 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 Example 1-1) above, the usage status output unit 117 may display a list on the application terminal 300 showing multiple sets of usage attribute information in chronological order based on the addition and deletion dates of each set of usage attribute information (see Figure 6).

[0036] Usage information, including a history of changes in usage attributes, is useful for, for example, investigating the usage of a geographical feature retrospectively. Investigating the usage of a geographical feature retrospectively is useful for, for example, evaluating the brand value of that feature. Furthermore, investigating the usage of a geographical feature retrospectively is also useful for conducting PCB surveys or land contamination surveys quickly and accurately.

[0037] In the case of Example 1-2) above, the usage status output unit 117 may display a list on the application terminal 300 showing the multiple sets of usage attribute information extracted by the attribute information extraction unit 116, for each floor number or room number (see Figure 7). In this case, by showing the usage status information of the features in more detail, it is possible to further improve the efficiency of using the features.

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

[0039] The update notification unit 121 obtains a notification requirement specification from the application terminal 300, which specifies whether or not a push notification of the above update is necessary. For example, the update notification unit 121 obtains the notification requirement specification entered by the user on the application terminal 300 for the above-mentioned feature. If it is specified that a push notification for the above-mentioned feature is necessary, the update notification unit 121 stores the feature ID of the specified feature in the monitored storage unit 122. Thereafter, each time the 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 storage unit 122. If the feature ID of the updated attribute information is stored in the monitored storage unit 122, the update notification unit 121 sends the update contents to the application terminal 300.

[0040] The map server 100 may be configured to extract feature IDs of features whose usage status satisfies the 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.

[0041] 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 entered by the user in the application terminal 300. A specific example of the extraction conditions is shown below. Example 2-1) It is currently available. Example 2-2) It is a new building. Example 2-3) The building's age must be at least the specified number of years. Example 2-4) The frequency of deletion and addition of usage attributes (e.g., frequency within a specified period) is above a specified level. Example 2-5) The frequency of building destruction and creation on the site (e.g., frequency within a specified period) is above a specified level.

[0042] The ID extraction unit 132 extracts the feature IDs of features (hereinafter referred to as "relevant features") whose usage status satisfies 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 the feature IDs included in each of the extracted usage attribute information as the 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 it may display the extraction results by the ID extraction unit 132 as a distribution on the area map displayed by the application terminal 300.

[0043] For example, the map data generation unit 114 generates map data showing feature information whose usage status satisfies the extraction criteria, 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 area map data so as to highlight the portion corresponding to that coordinate information. This makes it possible to clearly show the distribution of features whose usage status satisfies the extraction criteria within the display area.

[0044] For example, according to the extraction conditions in Example 2-1) above, it is possible to show the distribution of currently vacant properties. The distribution of vacant properties is useful for redevelopment plans for the area being displayed. Furthermore, since there is a high expectation of need for renovations and refreshment in vacant properties, the distribution of vacant properties is also useful for efficiently conducting sales of renovations and other related services.

[0045] According to the extraction conditions in Example 2-2), the distribution of newly constructed buildings can be shown. The distribution of newly constructed buildings is effective for efficiently selling infrastructure services such as city gas. Furthermore, the distribution of newly constructed buildings is also effective for efficiently interpreting changes in fixed asset tax. According to the extraction conditions in Example 2-3), the distribution of buildings that are expected to deteriorate can be shown. The distribution of buildings that are expected to deteriorate is effective for efficiently carrying out resilience construction work in the area to be displayed. Furthermore, the distribution of buildings that are expected to deteriorate is also effective for efficiently selling renovation or remodeling services.

[0046] According to the extraction criteria in Example 2-4), it is possible to show the distribution of properties with a high turnover of tenants. The distribution of properties with a high turnover of tenants is useful for planning the opening of chain stores, etc. According to the extraction criteria in Example 2-5), it is possible to show the distribution of sites with a high frequency of building renovations. The distribution of sites with a high frequency of building renovations is useful for estimating the growth rate of the area being displayed.

[0047] In this way, by appropriately defining extraction conditions, various information that contributes to the efficient use of geographical features can be obtained. It is also possible to combine several extraction conditions. For example, it is possible to extract geographical features that have a low frequency of building renovations and are vacant, and then show the distribution of such features. In areas where there are many geographical features that have a low frequency of building renovations and are vacant, it is possible to improve efficiency by reducing the scale of public facilities to suit the actual situation.

[0048] The map server 100 may be configured to update map data in response to 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 attribute database 112 in association with the feature ID, in response to an attribute addition input notifying the addition of a usage attribute for a feature. The map server 100 may also be configured to leave the usage attribute information, including information indicating the date of deletion, in the attribute database 112 in association with the feature ID, in response to an attribute deletion input notifying the deletion of a usage attribute for a feature.

[0049] The map server 100 may be configured to generate a new feature ID for a feature in response to a generation notification input that notifies of the creation of a new feature, and to store the new feature information, including the feature ID and the coordinate information of the feature, in the feature database 111. The map server 100 may also be configured to store the new feature information in the feature database 111, including information indicating the creation date of the feature. The map server 100 may also be configured to add information indicating the deletion date to the feature information of a feature and leave it in the feature database 111 in response to a feature deletion notification input.

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

[0051] 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 will be referred to as the "maintenance target area". For example, the area designation acquisition unit 141 acquires the area designation entered by the maintenance worker into the maintenance terminal 200.

[0052] 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 for all features to be displayed on the 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, 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 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 "maintenance area map") based on the maintenance map data.

[0053] 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 will be referred to as the "maintenance target feature".

[0054] The editing content selection unit 144 obtains the editing content specification for the maintenance target object from the maintenance terminal 200 and selects the editing content for the maintenance target object according to the editing content specification. Specific examples of editing content are shown below. Example 3-1) New registration of feature information related to a feature subject to maintenance. Example 3-2) Changing the feature information of a feature subject to maintenance. Example 3-3) Adding usage attribute information for properties subject to maintenance. Example 3-4) Changing the usage attribute information of a property subject to maintenance.

[0055] The feature information registration unit 145, in response to a generation notification input that notifies of the creation of a new feature, generates a new feature ID for the feature and adds the new feature information, including the feature ID and the coordinate information of the feature, to the feature database 111. The feature information registration unit 145 may also store the new feature information in the feature database 111, including the creation date information of the feature. The feature information registration unit 145 may also add the deletion date information to the feature information of the feature and store it in the feature database 111 in response to a feature deletion notification input.

[0056] 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 it may be information indicating a period including the creation date. In addition to the creation date, the creation date information may also specify the hour, minute, and second of creation. The expiration date information may be information indicating the expiration date with an error within an acceptable range for practical use, or it may be information indicating a period including the expiration date. In addition to the expiration date information, the expiration date information may also specify the hour, minute, and second of expiration.

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

[0058] The feature information registration unit 145 modifies the feature information of the feature to be maintained when the editing content selection unit 144 selects the editing content from Example 3-2) above. If the change is anything other than the deletion of the feature to be maintained, the feature information registration unit 145 modifies the feature information of the feature to be maintained based on the newly entered basic attributes. If the change is the deletion of the feature to be maintained, the feature information registration unit 145 adds deletion date information to the feature information of the feature to be maintained.

[0059] The attribute information registration unit 146, in response to an attribute addition input notifying the addition of a feature's usage attribute, adds new usage attribute information, including information indicating the addition date, to the attribute database 112, associating it with the feature ID. The attribute information registration unit 146 may also, in response to an attribute deletion input notifying the deletion of a feature's usage attribute, leave the previously registered usage attribute information indicating the usage attribute in the attribute database 112, associating it with the feature ID, and including information indicating the deletion date.

[0060] 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 it may be information indicating a period including the addition date. In addition to the addition date, the addition date information may also specify the time, minute, and second of addition. The deletion date information may be information indicating the deletion date with an error within an acceptable range for practical use, or it may be information indicating a period including the deletion date. In addition to the deletion date information, the deletion date information may also specify the time, minute, and second of deletion.

[0061] For example, when the Edit Content Selection Unit 144 selects the Edit Content from Example 3-3) above, the Attribute Information Registration Unit 146 adds the new usage attribute information to the attribute database 112, associating it with the feature ID of the maintenance target feature. In this case, the Attribute Information Registration Unit 146 may also generate a new attribute ID and include the generated attribute ID in the new usage attribute information.

[0062] The attribute information registration unit 146 modifies the existing usage attribute information of the maintenance target object when the editing content selection unit 144 selects the editing content from example 3-4) above. If the change is anything other than the deletion of existing usage attribute information, the attribute information registration unit 146 modifies the existing usage attribute information based on the newly entered usage attribute. If the change is the deletion of existing usage attribute information, the attribute information registration unit 146 adds deletion date information to the usage attribute information.

[0063] Furthermore, even if the changes are not the deletion of existing user attribute information, if the magnitude of the changes exceeds a predetermined level, the attribute information registration unit 146 may add deletion date information to the user attribute information and add the new user attribute information to the attribute database 112, associating it with the feature ID of the maintenance target feature, based on the newly entered user attribute. In this case, the attribute information registration unit 146 may generate a new attribute ID and include the generated attribute ID in the new user attribute information. An example of a case where the magnitude of the changes exceeds a predetermined level is when 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 of "...Co., Ltd." excluding "Co., Ltd." etc.

[0064] If there is a significant difference in the unique part, it is highly likely that the occupant has effectively changed. On the other hand, if there is a high degree of similarity in the unique part, it is highly likely that the occupant is essentially the same person, even if the occupant's name has changed. Therefore, if the difference between the unique part of the occupant's name before the change and the unique part of the occupant'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 add the new usage attribute information to the attribute database 112, associating it with the feature ID of the maintenance target feature, based on the newly entered usage attribute.

[0065] Figure 9 is a block diagram illustrating the hardware configuration of the map server 100. As shown in Figure 6, the map server 100 has a circuit 190. The circuit 190 has at least one processor 191, memory 192, storage 193, and communication port 194. The storage 193 has a storage medium that can be read by a computer, such as a hard disk. The storage 193 stores a program that causes the map server 100 to perform the following: hold a feature database that stores feature information including the coordinate information of a feature and the unique feature ID of a feature; hold an attribute database that stores attribute information of a feature associated 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 a specified feature based on the attribute information extracted by the attribute information extraction unit. The storage 193 stores a program that causes the map server 100 to configure each of the above-described functional blocks.

[0066] Memory 192 temporarily stores programs loaded from storage 193 and calculation results from processor 191. Processor 191 works in cooperation with memory 192 to execute the above programs, thereby configuring each functional block of the map server 100. Communication port 194 communicates with maintenance terminal 200 and application terminal 300 via network line 9 according to commands from processor 191.

[0067] Furthermore, the circuit 190 is not necessarily limited to those whose functions are configured by a program. For example, at least some of the functions of the circuit 190 may be configured by a dedicated logic circuit or an ASIC (Application Specific Integrated Circuit) that integrates such circuits.

[0068] [Map Information Maintenance Procedure] Next, as an example of a method for maintaining map information, we will illustrate the maintenance procedure performed by the map information system 1. As shown in Figure 10, the map server 100 first executes steps S01, S02, S03, S04, S05, S06, and S07. In step S01, the area specification acquisition unit 141 waits for the area specification for map display to be transmitted from the maintenance terminal 200.

[0069] In step S02, the map data generation unit 142 generates maintenance map data for displaying a map of the area specified by the area designation (the maintenance target area). For example, the map data generation unit 142 extracts feature information for all features to be displayed on the map of the maintenance target area from the feature database 111 based on the coordinate information of each feature, 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 feature to be displayed from the attribute database 112 and include the extracted usage attribute information in the map data.

[0070] In step S03, the map data generation unit 142 transmits the generated maintenance map data to the maintenance terminal 200. Based on the maintenance map data, the maintenance terminal 200 displays a map of the maintenance target area (the maintenance area map shown above).

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

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

[0073] In step S07, if the editing content selection unit 144 determines 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 "new feature"). In step S09, the feature information registration unit 145 adds new feature information, including the newly generated feature ID and the coordinate information of the new feature, to the feature database 111.

[0074] In step S11, the area designation acquisition unit 141 checks whether a maintenance completion instruction has been sent from the maintenance terminal 200. If it determines that a maintenance completion instruction has been sent from the maintenance terminal 200, the map server 100 terminates the maintenance procedure.

[0075] If the map server 100 determines that a maintenance completion instruction has not been sent from the maintenance terminal 200, it executes step S12. In step S12, the area specification acquisition unit 141 checks whether or not a map display area change instruction has been sent from the maintenance terminal 200. If it determines that a map display area change instruction has been sent from the maintenance terminal 200, the map server 100 returns to step S01. If it determines that a map display area change instruction has not been sent from the maintenance terminal 200, the map server 100 returns to step S04.

[0076] In step S07, if the editing content selection unit 144 determines that new registration of features related to the maintenance target feature has not been selected, the map server 100 executes step S13 as shown in Figure 11. In step S13, the feature information registration unit 145 checks whether the editing content selection unit 144 has selected to change the feature information of the maintenance target feature (Example 3-2 above).

[0077] In step S13, if the editing content selection unit 144 determines that a change to the feature information of the feature subject to maintenance has been selected, the map server 100 executes step S14. In step S14, the feature information registration unit 145 confirms whether the change to the feature information is the deletion of the feature subject to maintenance.

[0078] If step S14 determines that the changes to the feature information are other than the deletion of the feature subject to maintenance, the map server 100 executes step S15. In step S15, the feature information registration unit 145 modifies the feature information of the feature subject to maintenance based on the newly entered basic attributes.

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

[0080] If, in step S13, it is determined that changing the feature information of the feature to be maintained is not selected, the map server 100 executes step S21, as shown in Figure 12. In step S21, the attribute information registration unit 146 checks with the editing content selection unit 144 whether adding usage attribute information of the feature to be maintained (Example 3-3 above)) or changing the usage attribute information of the feature to be maintained (Example 3-4 above)) is selected.

[0081] If the map server 100 determines in step S21 that the addition of usage attribute information for the maintenance target object has been selected, it executes steps S22 and S23. In step S22, the attribute information registration unit 146 generates a new attribute ID for the usage attribute to be added (hereinafter referred to as the "new attribute"). In step S23, the attribute information registration unit 146 adds the new usage attribute information, including the newly generated attribute ID and the information for the new attribute, to the attribute database 112, associating it with the object ID of the maintenance target object. After that, the map server 100 returns to step S01.

[0082] If step S21 determines that a change in the usage attribute information of the maintenance target object has been selected, the map server 100 executes step S31. In step S31, the attribute information registration unit 146 checks whether the change in the usage attribute information is the deletion of a usage attribute.

[0083] In step S31, if it is determined that the change in the user attribute information is not a deletion of the user 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 below a predetermined level.

[0084] If the map server 100 determines in step S32 that the magnitude of the change is below a predetermined level, it executes step S33. In step S33, the attribute information registration unit 146 modifies the existing usage attribute information based on the newly entered usage attribute.

[0085] In step S32, if the map server 100 determines that the magnitude of the change exceeds a predetermined level, it 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 entered usage attribute. In step S36, the attribute information registration unit 146 adds the new usage attribute information, including the newly generated attribute ID and the newly entered usage attribute, to the attribute database 112, associating it with the feature ID of the maintenance target feature.

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

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

[0088] If the map server 100 determines in step S41 that the area specification for map display has been sent from the application terminal 300, it 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 above-mentioned display target area). Based on the coordinate information of each feature, the map data generation unit 114 extracts feature information for 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.

[0089] 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 area to be displayed (the area map shown above) 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 user attribute information from the attribute database 112 that is associated with the feature ID of the feature designated by the user (the designated feature shown above).

[0090] In step S46, the usage status output unit 117 outputs usage status information for the designated location based on the usage attribute information extracted by the attribute information extraction unit 116. For example, the usage status output unit 117 displays the usage status information for the designated location on the application terminal 300. In step S47, the update notification unit 121 obtains a notification requirement specification from the application terminal 300, which specifies whether or not a push notification of the above update is necessary for the designated location, and confirms whether or not a push notification is necessary based on the notification requirement specification.

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

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

[0093] In step S55, if the map server 100 determines that an instruction to end the display of usage status has been sent from the application terminal 300, the map server 100 terminates the usage status display procedure. In step S55, if the map server 100 determines that an instruction to end the display of usage status has not been sent from the application terminal 300, the map server 100 executes step S56. In step S56, the area specification acquisition unit 113 checks whether an instruction to change the area for map display has been sent from the application terminal 300. If the map server 100 determines that an instruction to change the area for map display has been sent from the application terminal 300, the map server 100 returns to step S41. If the map server 100 determines that an instruction to change the area for map display has not been sent from the application terminal 300, the map server 100 returns to step S44.

[0094] In step S41, if it is determined that the area specification for map display has not been sent from the application terminal 300, the map server 100 executes step S51. In step S51, the extraction condition acquisition unit 131 checks whether or not the extraction conditions for features have been sent from the application terminal 300.

[0095] In step S51, if the map server 100 determines that the feature extraction conditions have not been sent from the application terminal 300, it returns to step S41. In step S51, if the map server 100 determines that the feature extraction conditions have been sent from the application terminal 300, it 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 the feature IDs from the attribute database 112 for features whose usage status satisfies the extraction conditions acquired by the extraction condition acquisition unit 131.

[0096] In step S54, the map data generation unit 114 generates map data showing feature information whose usage status satisfies the extraction conditions, 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 area map data so that the portion corresponding to that coordinate information is highlighted. The map data generation unit 114 sends the regenerated area map data to the application terminal 300. The application terminal 300 displays an area map with the extraction results highlighted based on the regenerated area map data.

[0097] Next, the map server 100 executes step S57. In step S57, the area designation acquisition unit 113 checks whether or not a usage status display termination instruction has been sent from the application terminal 300.

[0098] In step S57, if the map server 100 determines that an instruction to end the display of usage status has been sent from the application terminal 300, the map server 100 terminates the usage status display procedure. In step S57, if the map server 100 determines that an instruction to end the display of usage status has not been sent from the application terminal 300, the map server 100 returns to step S41.

[0099] Figure 14 is a flowchart illustrating the procedure for notifying an update of attribute information for a feature registered in the monitored 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 the contents of the attribute database 112 to be updated. In step S62, the update notification unit 121 checks whether the updated attribute information feature ID (hereinafter referred to as "notified feature ID") is stored in the monitored storage unit 122.

[0100] In step S62, if the map server 100 determines that the notified feature ID is not stored in the monitored storage unit 122, the map server 100 returns to step S61. In step S62, if the map server 100 determines that the notified feature ID is stored in the monitored storage unit 122, the map server 100 executes step S63. In step S63, the update notification unit 121 sends the update content to the user's application terminal 300 associated with the notified feature ID in the monitored storage unit 122. After that, the map server 100 returns to step S61. The map server 100 repeats the above process.

[0101] [Effects of this embodiment] As described above, the map information system 1 includes a feature database 111 that stores feature information including the coordinate information of a feature and the unique feature ID of a feature; an attribute database 112 that stores feature attribute information associated with the feature ID; 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 a specified feature based on the attribute information extracted by the attribute information extraction unit 116.

[0102] In this geographic information system 1, each feature information, including its coordinate information, is assigned a unique feature ID, and the feature's attribute information is stored in association with this feature ID. This allows for a clear distinction between changes in coordinate information due to building additions or subtractions, or modifications to the map data itself, and changes in coordinate information due to the replacement of the feature itself. Various attribute information can then be aggregated for each feature. The attribute information aggregated for each feature is useful for the efficient use of the features. Therefore, this geographic information system 1 is effective in increasing the added value of map data.

[0103] Furthermore, a data structure in which feature information is assigned a unique feature ID is also effective for easily customizing map displays. For example, by linking custom drawing data generated to highlight specific features 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 the coordinates of a feature change, if the feature ID remains the same, the attribute information before and after the coordinate change can be linked to the same feature and stored, providing a consolidated history of attribute information for that feature.

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

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

[0106] The usage status output unit 117 may output usage status information, including the 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.

[0107] The map information system 1 may further include a feature information registration unit 145 that, in response to a generation notification input notifying the generation of a new feature, generates a new feature ID for the feature and adds the new feature information, including the feature ID and the 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, thorough management of feature information to which feature IDs are assigned can be ensured.

[0108] The feature information registration unit 145 may add new feature information to the feature database 111, including information indicating the creation date of the feature. In this case, by using feature information that includes the creation date, more useful usage information can be provided to higher-level features. For example, by using feature information that includes the creation date of a building (feature), more useful usage information can be provided to the site (higher-level feature) on which the building is located.

[0109] The feature information registration unit 145 may, in response to the input of a feature extinction notification, add information indicating the extinction date to the feature information of the feature and record it in the feature database 111. In this case, by appropriately managing the history of features, more useful usage information can be provided to higher-level features.

[0110] The map information system 1 may further include an ID extraction unit 132 that extracts feature IDs of features whose usage status satisfies the extraction conditions from the attribute database 112 based on condition specification input that defines the extraction conditions for usage status, and a map data generation unit 114 that generates map data showing feature information of features whose usage status satisfies 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 overview usage status information for features over a wider area, such as administrative divisions.

[0111] Although embodiments have been described above, this disclosure is not necessarily limited to the embodiments described above, and various modifications are possible without departing from its essence.

[0112] The embodiments described in whole or in part above solve 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, provision of appropriate data, programs, recording media, devices and / or systems such as reduction of data and / or program capacity, miniaturization of devices and / or systems, and optimization of data, programs, recording media, devices and / or systems such as reduction of production and manufacturing costs, simplification of production and manufacturing, and reduction of production and manufacturing time. [Explanation of Symbols]

[0113] 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

1. a feature database that stores feature information including coordinate information of features and feature IDs unique to the features; an attribute database that stores attribute information of features in association with feature IDs; an attribute information extraction unit that extracts attribute information associated with a feature ID of a specified feature from the attribute database; an output unit that outputs usage status information of a specified feature based on the attribute information extracted by the attribute information extraction unit.

2. 2. The map information system according to claim 1, further comprising an attribute information registration unit that adds new attribute information including information indicating the date of addition to the attribute database in association with the feature ID in response to an attribute addition input that notifies the addition of an attribute of the feature.

3. 3. The map information system according to claim 2, wherein the attribute information registration unit, in response to an attribute deletion input notifying deletion of an attribute of a feature, includes information indicating a deletion date in the already registered attribute information indicating the attribute, associates the attribute information with a feature ID, and leaves the attribute information in the attribute database.

4. 4. The map information system according to claim 3, wherein the output unit outputs 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.

5. A map information system as described in any one of claims 1 to 4, 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.

6. 6. The map information system according to claim 5, wherein said feature information registration unit adds new feature information to said feature database, including information indicating the date of creation of the feature.

7. 7. The map information system according to claim 6, wherein said feature information registration unit, in response to 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.

8. an ID extraction unit that extracts, based on a condition specification input that defines an extraction condition for a usage situation, feature IDs of features whose usage situation satisfies the extraction condition from the attribute database; The map information system according to any one of claims 1 to 7, further comprising a map data generation unit that generates map data indicating feature information whose usage status satisfies the extraction conditions based on the feature ID extracted by the ID extraction unit and the feature database.

Images