Land feature management methods

Abstract

To efficiently provide a feature manager with information of a management feature.SOLUTION: A feature management system is provided by a system server 200 connected to both a feature management database 102 prepared by a feature manager and a map database 306 prepared by a cartographer. Information of the location, the type, or the like of a management feature stored in the feature management database 102 is associated with a feature ID for specifying feature data of the map database 306 and registered in a feature registration database 222. When the cartographer examines the feature for maintenance of the map database, examination information obtained by the feature examination is provided to a corresponding feature manager by referring to the feature registration database 222. On the other hand, change information, such as a new construction and abolition registered for the management feature by the feature manager is provided to the cartographer and utilized for maintenance of the map database.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention provides Feature management method Regarding. [Background technology]

[0002] There is a technology that recognizes road signs included in captured images and updates map information (Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2017-162356 Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present invention is to appropriately manage data on geographical features. [Means for solving the problem]

[0005] The present invention provides a feature management method executed by a feature management system connected to a map server having a map database and a system server that manages features, the method comprising: The features are managed with different identification information in the map database and in a feature management database in which a feature manager manages the features, The feature management system By linking the respective identification information, the information of the features stored in the map database and the information of the features stored in the feature management database are associated with each other for each feature, and are stored in a feature registration database; When change information indicating a change in the status of an arbitrary feature is registered in the feature management database from a terminal operated by the feature manager, To update the information of the features stored in the map database, Identifying the feature to be changed based on the identification information linked in the feature registration database, and transmitting the change information to the map database; evaluating the registered change information and / or evaluating the feature manager who registered the change information, and if the evaluation is above a predetermined level, updating the feature information stored in the map database with the change information; Execute.

[0006] In addition to the above-described feature management system, one embodiment of the present invention may also be configured as a feature management method for processing map data or feature data by a computer. It may also be configured as a computer program for realizing such processing, or as a computer-readable recording medium having the computer program recorded thereon. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is an explanatory diagram showing the configuration of a feature management system. [Figure 2] FIG. 2 is an explanatory diagram illustrating an example of a data structure. [Figure 3] FIG. 10 is an explanatory diagram showing an example of assigning IDs to linear features. [Figure 4] 10 is a flowchart of a feature registration process. [Figure 5] 10 is a flowchart of an information collection process. [Figure 6] 10 is a flowchart of an information selection process. [Figure 7] 10 is a flowchart of an information providing process. [Figure 8] FIG. 10 is an explanatory diagram showing an example of providing information. [Figure 9] 10 is a flowchart of an analysis process. [Figure 10] 10 is a flowchart of a sorting process. DETAILED DESCRIPTION OF THE INVENTION

[0008] As an embodiment of the present invention, a feature management system that provides survey information collected by a map database creator to a feature manager about features registered by the feature manager will be described below. A. System Configuration: B. Feature Registration Process: C. Information Collection and Processing: D. Information Selection and Processing: E. Processing of Information: F. Analysis Processing: G. Maintenance Treatment: H. Effects and Variations:

[0009] A. System Configuration: 1 is an explanatory diagram showing the configuration of a feature management system. In the figure, terminals 100, 100A, and 100B, a system server 200, and map servers 300, 300A, and 300B are connected to one another via a network such as the Internet.

[0010] The terminal 100 is a device used by a feature manager who manages features. The feature manager and the features under management (hereinafter also referred to as "managed features") may take various forms. For example, the feature manager may be a private company or individual, and the managed features may be facilities, equipment, and signs managed by a private company, or land and buildings managed by an individual. Alternatively, the feature manager may be a local government, and the managed features may be its facilities and equipment (for example, road signs, lanes, road markings, the road surface itself, guardrails, footbridges, bridges, railroad tracks, railroad crossings, rivers and levees, gutters, manholes, etc.).

[0011] A computer, tablet, smartphone, or other mobile terminal capable of communicating via a network can be used as the terminal 100. The number of terminals is not limited to one, and multiple terminals such as terminals 100, 100A, and 100B can be connected. The terminal 100 is installed with a browser 104, which serves as an interface for exchanging information with the system server 200. It also has a feature management database 102 that stores data on managed features. The data structure of this database will be described later. Note that the feature management database 102 is not necessarily required, and may be omitted if there are only a few managed features.

[0012] The map server 300 stores a map database 306. The map database 306 stores information about various features in the form of polygons, lines (straight lines, broken lines, curves, etc.), symbols, etc. It may also include information about links, nodes, etc. that are necessary for route searches. The map database 306 may also be a three-dimensional database that stores the three-dimensional shapes of features.

[0013] Each function of the map server 300 shown in the figure is configured as software by installing a computer program. Some or all of the functions may also be configured as hardware. Each function will be described below.

[0014] The survey information collection unit 304 collects survey information, which is the result of surveying the status of various features. Survey information includes image data of photographs of features (hereinafter also referred to as photographed images), comments on the status of features, etc. This information is provided by surveyors commissioned by the map creator, measurement vehicles, drive recorders, etc. Information may also be provided by the general public via social media, email, etc.

[0015] The information transmitting / receiving unit 302 transmits and receives various information to and from the system server 200 via the network. The system server 200 provides the map server 300 with information registered from the terminal 100, and the map server 300 provides the system server 200 with survey information on the status of features.

[0016] The maintenance unit 308 maintains the map database 306 by reflecting the survey information and information provided by the system server 200 in the feature data in the map database 306. It is not necessary to reflect all of this information, and the method of reflecting the information may be controlled depending on the credibility of the information, etc.

[0017] The feature management system can be configured in software form by installing computer programs for realizing the functions shown in the figure in the system server 200. Some or all of the functions may also be configured in hardware form.

[0018] Each function that constitutes the feature management system will be explained below. The main control unit 210 controls the overall processing. The user management unit 201 manages information about users who use the feature management system. Users include feature managers who manage features and map creators who create map databases. Multiple feature managers and map creators may be targeted. User information is stored in a user database 220, the data structure of which will be described later.

[0019] The display control unit 202 controls the display screens on the terminal 100. The display screens include an interface screen for registering information about features, and a screen for providing the terminal with information on surveyed features.

[0020] The feature registration unit 203 reads feature information that is registered individually from the terminal 100 or that is registered in the form of a feature management database, and registers the information by linking it to features in the map database 306. This linking is performed for each map database 306. In this way, the feature information registered from the terminal 100 or the feature management database 102 can be linked with the map database 306, and the latest information regarding features held by the feature manager and the map creator can be shared with each other. The registration results are stored in the feature registration database 222. The data structure will be described later.

[0021] The information providing unit 204 provides the terminal 100 with survey information and the like obtained from the map server 300 . The investigation information is stored in the investigation information storage unit 224. The data structure will be described later.

[0022] The change information providing unit 205 provides change information indicating the status or schedule of changes to features, etc., obtained from the terminal 100, to the map server 300. Change information includes, for example, information on the establishment, abolition, and modification of features.

[0023] The analysis unit 206 analyzes the presence or absence of changes over time for the features based on the survey information. Examples of changes over time include the construction or abolition of the feature, or partial or total destruction, damage, or destruction. In the case of features such as signs, fading of the markings is also included in changes over time. Changes in the surrounding environment of the feature itself, such as the accumulation of rain or snow, also fall under this category. All of these are meaningful information that the feature manager should manage, as they represent changes in the situation that may prevent the feature from performing its normal function. The analysis unit 206 may be provided in the terminal 100 or the map server 300, or may be provided in a server other than the terminal 100, the system server 200, or the map server 300.

[0024] The feature management system can have various configurations other than those shown in the figure. For example, one of the map servers 300 may be integrated with the system server 200. The functions provided in the system server 200 may be implemented by multiple servers, etc.

[0025] FIG. 2 is an explanatory diagram illustrating an example of a data structure. The user database 220 registers user information. As the ID, a manager ID, which is identification information of the feature manager, a map creator ID, which is identification information of the map creator, and the like are stored. Additionally, information such as the user's name and contact details is also stored. The type is information indicating whether the user is a feature manager or a map creator. The database is information indicating the location of a database managed by each user. For example, information indicating the URL or the like as the location of a feature management database used by a feature manager and a map database used by a map creator is stored.

[0026] The feature management database 102 stores the following information: The managed feature ID is identification information for the feature to be managed. The managed feature ID can be set arbitrarily by the feature manager. It is acceptable for multiple feature managers to have the same ID. As will be described later, the managed feature ID is managed together with the manager ID that set it, so that the managed feature can be uniquely identified. Furthermore, there is no need for the managed feature ID to match the identification information (feature ID) assigned to the feature in the map database 306. As will be described later, the managed feature ID is linked to the corresponding feature ID and managed in the feature registration database 222, so that the managed feature can be uniquely identified. The feature management database 102 also stores the names and locations of features. The names can also be set arbitrarily by the feature manager. The location can be the address of the feature or coordinate values ​​such as latitude and longitude. The classification indicates whether a feature is point-like, linear, or area-like. Point-like features are features whose location can be recognized as a point, such as railroad crossings and signs. Linear features are features with length, such as railway tracks and rivers. Area-like features are features with size, such as land, farmland, and administrative boundaries. However, whether each feature is a point feature, a line feature, or an area feature can be determined by the feature manager. For example, a feature such as a house can be treated as a point feature if the purpose is to manage the construction or demolition of the house itself, or as an area feature if the purpose is to manage the growth of weeds, trees, etc. around the house. The type is information that indicates the type of feature. For example, it is expressed as "railroad crossing," "signboard," "house," "railroad track," etc. The type may be specified from among predetermined types, or may be arbitrarily set. The setting is information indicating the status of the feature at the time of registration. Information such as "new" for a new feature, "existing" for an already existing feature, "changed" if an existing feature has been changed, or "abolished" if the feature has been removed or the like is stored. Any other information may also be used. The effective date is information that indicates the date and time when a change such as construction, modification, or abolition of a feature will occur. If such a change is scheduled to occur in the future, a future date and time will be stored. For example, if a new railroad crossing is constructed, the date on which the crossing will begin to be used is stored as the effective date. Also, if a store is a managed feature, the opening date may be used as the effective date. In the case of a road sign, the date on which the traffic regulation becomes effective may be used as the effective date.

[0027] The feature registration database 222 stores information linking the feature management database 102 and the map database 306 . The administrator ID is information that identifies the feature administrator registered in the user database 220, and thereby makes it possible to identify the feature management database 102. The managed feature ID is information that identifies the feature registered in the feature management database 102. Information such as name, location, classification, type, and valid date is information stored in the feature management database 102. The map link information is information for linking with the map database 306. For each map database 306, a map creator ID, a feature ID, location information, etc. are stored. The map creator ID is information for identifying the map creator stored in the user database 220, and is used to identify the map database 306. The feature ID is the feature ID of the map database 306. The location information can use information on the constituent points of the map database 306. Related data represents other data about the same feature that is registered in the feature registration database 222. For example, in the case of a linear feature, as will be described later, the feature may be subdivided and registered according to its position, and therefore multiple pieces of registered data may be generated for one feature in the feature registration database 222. In such cases, the other registered data are stored as related data. This makes it possible to easily refer to all data about one feature without omission. Such a registration method will be described in detail later using an example. Axis definitions are information that defines the axes used to identify positions within linear and area features. For example, for linear features, the start and end points can be registered as axis definitions. For area features, coordinate axes can be registered to identify internal positions.

[0028] The map database 306 stores information about features to be illustrated. A feature ID is identification information for a feature. By registering the feature ID in the feature registration database 222, it becomes possible to link the feature management database 102 and the map database 306. The map database 306 also stores information such as the name, constituent points, and attributes of each feature. Constituent points are data that represent the shape of the feature, and store the coordinate values ​​of the location for point-like features, the coordinate values ​​of each constituent point for linear features, and the coordinate values ​​of the vertices of polygons for planar features. As attributes, information such as the type of feature is stored.

[0029] The survey information storage unit 224 stores survey information about the status of features. The administrator ID, managed feature ID, map creator ID, and feature ID enable linking with information in the feature registration database 222. The date and time indicate the date and time when the survey information was acquired. Examples of survey information include photographed images of the feature and comments about the status of the feature. The poster is information that identifies the person who posted the survey information. Names, IDs, etc. can be used.

[0030] The above explanation is merely an example, and the database is not limited to this and can have various other structures.

[0031] Figure 3 is an explanatory diagram showing an example of assigning IDs to linear features. This example assumes that a railway company manages railroads, railroad crossings, and other features. The railroad crossing shown in the figure only needs to be registered as a point feature. This is because it is also managed as a point feature in the map database, and its position and shape are generally consistent. However, because railroad tracks are linear features with a length, even if they are managed as linear features in the map database, their start and end points may not necessarily match (i.e., they may not be separated by the same section), and their position and shape may differ. Therefore, the following two points must be considered. First, it is desirable to ensure that the settings of managed feature IDs are consistent with those of feature IDs in the map database. Second, it is desirable to register information that can identify a location within a feature. An example of registration that takes these points into consideration is shown below.

[0032] 3(a) shows an example in which the managed feature ID set by the feature manager is shorter than the feature ID in the map database. In other words, as shown in the figure, the feature manager sets managed feature IDs such as Section 1, Section 2, and Section 3 for each section of the railroad track separated by a railroad crossing, while in the map database, the railroad track is managed collectively with a single feature ID, "RW01." In this case, simply associating each managed feature ID (Section 1 to Section 3) with the feature ID "RW01" will result in a mismatch between the two corresponding features. Therefore, in such cases, information defining the start point (position 0 in the figure) and end point (position 100% in the figure) for the feature is registered as an "axis definition" (see Figure 2), and 0 to a (%) of the feature ID "RW01" is linked to the managed feature ID "Section 1," a to b (%) to "Section 2," and b to 100 (%) to "Section 3." This allows the positions and shapes of the two to be aligned. Furthermore, because the axis definitions have been created, it is possible to identify each point within each section.

[0033] Figure 3(b) shows the opposite case, where the managed feature ID is set to be longer than the feature ID. In other words, the managed feature ID is set to "between Station A and Station B" for the entire track, while the map database feature IDs are set to separate sections between railroad crossings, such as RWa1, RWa2, and RWa3. In this case, the managed feature ID "between stations A and B" is subdivided to match the feature ID. In other words, the managed feature ID is also divided into sections for each railroad crossing and registered with a sub-number such as "between stations A and B-1," "between stations A and B-2," and "between stations A and B-3." This makes it possible to match the feature management database with the map database. Even in this case, the start and end points may be defined for each section to identify each point within the feature. The subdivided managed feature IDs "A Station B Station-1," "A Station B Station-2," and "A Station B Station-3" shown in Figure 3(b) are generated for registration in the feature registration database 222 of the feature management system, and do not rewrite the feature management database 102. When information is provided from the feature management system to the feature manager, it will be provided as information relating to the original managed feature ID "A Station B Station."

[0034] Figure 3(c) shows a case where the managed feature ID and the feature ID are misaligned (i.e., they are not separated by the same section). As shown in the figure, the leftmost section is assigned a managed feature ID of "between stations C and D," and the other sections are assigned a managed feature ID of "between stations E and F." In contrast, the feature IDs are assigned "RWb1" to the two sections from the left, and "RWb2" to the rightmost section. In this case, the methods explained in Figures 3(a) and 3(b) are combined to ensure consistency between the two. First, the management feature ID "Between Stations E and F" assigned to the two sections on the right is subdivided into two management feature IDs, "Between Stations E and F-1" and "Between Stations E and F-2," to ensure consistency with the feature ID "RWb2." On the other hand, for the feature ID "RWb1," the information on the start and end points assigned in the same way as in Figure 3(a) is used to link 0 to a (%) of the feature ID "RWb1" to the management feature ID "Between Stations C and D," and a to b (%) to the management feature ID "Between Stations E and F-1." This allows consistency between the two. It is also possible to subdivide the feature ID "RWb1" into feature IDs "RWb1-1" and "RWb1-2" and associate them with the managed feature IDs.

[0035] Figure 3 shows an example of a linear feature, but it is also possible to associate area features with feature IDs by subdividing the managed feature ID and defining axes to identify their positions. In the case of area features, the axis definition to identify their positions is a two-dimensional coordinate.

[0036] The above explains the system configuration, data structure, etc. Next, we will explain examples of processing such as data registration and exchange of various information using these.

[0037] B. Feature Registration Process: 4 is a flowchart of the feature registration process, which is executed by the feature registration unit 203 of the feature management system, and is executed by the system server 200 in terms of hardware. The system server 200 executes a login process and reads the administrator ID, password, etc. (step S10).

[0038] Next, if the feature manager selects to register managed features individually rather than in a database (step S11), a registration screen is displayed on the terminal and the feature information entered by the feature manager is read (step S12). The items read here are the same as those shown in the feature management database 102. On the other hand, if the feature manager selects registration using a database (step S11), the database (feature management database) prepared by the feature manager is read (step S13). The registration method may be either individual registration or database registration.

[0039] Next, the system server 200 updates the existing registration contents in the feature registration database (step S14). This is because the information registered in steps S12 and S13 is not necessarily for a new feature, but may also be for an existing feature. If it is assumed that the managed feature ID will not be changed once it has been set, it is sufficient to search using the administrator ID and managed feature ID as keys to determine whether a feature is an existing feature. However, since the managed feature ID is an ID that is arbitrarily set by the feature manager, it may be changed by the feature manager. In this embodiment, taking this situation into consideration, whether a feature is an existing feature is determined based on information other than the managed feature ID, i.e., location, classification, and type. An example of a judgment is shown in the figure. When the input content from the feature manager is compared with the content already registered in the feature registration database, the managed feature ID and name are different. However, the location, classification, and type of the two are the same. In this case, the system server 200 determines that an already registered feature with the managed feature ID "Feature 1" and the name "** Signboard" has been replaced, and updates this already registered content based on the input content. If the "setting" information in the input contents is set to change or abolish, the system server 200 may take this into consideration. The above-mentioned (1) method using the managed feature ID, (2) method using the location, classification, and type, and (3) method using the "setting" information for change or abolition may be implemented by any one of them, or may be used depending on the conditions, or multiple methods may be used in combination. If it is determined that the information registered in steps S12 and S13 is not for an existing feature, the feature registration database will not be updated in step S14 (it will be newly registered as a new registered feature in step S16, which will be described later).

[0040] Next, if it is determined that the information registered in steps S12 and S13 does not correspond to a previously registered feature, the system server 200 searches the map database for a corresponding feature (step S15). In this case, as in step S14, a feature that matches the location, classification, and type is selected. However, since the location may contain errors, a deviation within a predetermined distance may be allowed.

[0041] Once the managed feature ID and feature ID have been associated in this way, the system server 200 associates them and registers the information in the feature registration database (step S16). During this registration, as explained in Figure 3, for linear features and area features, it may also be possible to perform processing such as matching the managed feature ID and feature ID and defining axes to identify positions within the features.

[0042] If a feature corresponding to the managed feature cannot be found, several methods can be considered. For example, the feature manager may be notified that there is no corresponding feature, and the process may be terminated without registering the feature in the feature registration database. Alternatively, a feature corresponding to the managed feature may be added to the map database through the maintenance process (Fig. 10) described below, and then registration may be performed.

[0043] The system server 200 sends the registration results to the map database (step S17) and ends the feature registration process. This allows the registration results to be used in the map server 300 (for example, by updating the map database using information about the newly registered feature). When registering features using a feature management database, the processes in steps S14 to S16 are performed for all managed features stored in the feature management database. Using a feature management database in this way has the advantage of enabling a large number of managed features to be registered efficiently. Furthermore, by executing the feature registration process, the feature management database and the map database can be linked, making it possible to use two databases created by different creators in conjunction with each other, thereby improving convenience and usefulness.

[0044] C. Information Collection and Processing: 5 is a flowchart of the information collection process, which is executed by the information provider 204 of the feature management system, and is executed by the system server 200 in terms of hardware. This process is a process in which the feature management system collects survey information on the status of features included in the map database. The timing of the process can be various, such as periodically, when the map server 300 obtains new survey information, or in response to a request from the feature manager.

[0045] When processing begins, the system server 200 reads survey information, etc. from the map server (step S20). An example of the information to be read is shown in the figure. For each target feature ID, survey information such as photographed images and comments, as well as information such as the acquisition date and time and poster, are included. The acquisition date and time refers to the date and time the survey information itself was obtained; for photographed images, it refers to the date and time the feature was photographed, and for comments, it refers to the date and time the comment was posted. The poster is information that represents the person who photographed the feature or posted the comment, and can be the name or poster ID. Including the acquisition date and poster information can be useful in evaluating the accuracy and reliability of the survey information.

[0046] Next, the system server 200 refers to the feature registration database and acquires the managed feature ID corresponding to the target feature ID (step S21). Then, the system server 200 stores the survey information in the survey information storage unit (step S22). The survey information stored in this way becomes an information source that is provided to the feature manager at an appropriate time.

[0047] The information collection process may end with the above content, but in this embodiment, a survey information refinement process is further executed (step S23). When a map creator frequently surveys features or receives survey information from many surveyors, measurement vehicles, drive recorders, SNS, etc., duplicate survey information about the same feature may be obtained at the same time, and saving all of the information may be wasteful. The information refinement process takes such situations into consideration and is a process for saving survey information efficiently and without waste.

[0048] D. Information Selection and Processing: Figure 6 is a flowchart of the information selection process. This process is executed by the information provider 204 of the feature management system, and in terms of hardware, it is executed by the system server 200. As mentioned above, this process is for efficiently storing the obtained survey information without waste.

[0049] When processing begins, the system server 200 reads the survey information, etc., to be processed (step S30). For example, a series of survey information stored in the survey information storage unit can be read using the target managed feature ID or feature ID as a key. Also, a flag indicating whether the information selection process has been completed or not can be set for the stored survey information, and information that has not yet been selected for selection can be read. This can reduce the amount of information and improve the efficiency of the information selection process.

[0050] The system server 200 evaluates the survey information based on the poster (step S31). Information from surveyors commissioned by the map creator can be evaluated as highly reliable, while information obtained from ordinary citizens via SNS or the like can be evaluated as lacking in reliability. A credibility rank can be set for each poster based on the content of survey information posted by the poster in the past, and the survey information can be evaluated based on this. The evaluation results can be used in various ways. For example, in step S31, survey information that does not meet a certain evaluation standard may be deleted from the target and not used in subsequent processing. Also, in step S31, the evaluation results may be stored as a credibility score for the survey information, and may be later considered together with evaluations based on other factors.

[0051] If the investigation information is a comment, the server 200 extracts keywords from it (step S32). Examples of comments are shown in the figure. For example, for the comment "The signboard at XX is fallen," the keyword is "fallen," which describes the state of the feature. For "The barrier at the railroad crossing at XX is broken," the keyword is "broken," and for "There is a fallen tree at the entrance to the XX parking lot," the keyword is "fallen." The keywords to be extracted can be registered in advance as a dictionary. It should be noted that "There is a cat at the entrance to the XX parking lot" does not include words that describe the state of a feature, that is, there are no keywords registered in the dictionary, so no keywords are extracted. This process allows the comments to be treated as simple information, with the main points extracted from the survey information. After the keywords are extracted, further processing may be performed to unify variations in spelling, etc.

[0052] Next, the system server 200 groups the captured images by date and time (step S339). An image of the grouping is shown in the figure. The horizontal axis represents time, and the state in which captured images P1 to P9 captured at each time is shown. This time axis is divided into G1 to G4 according to predetermined time intervals, and the captured images belonging to each are treated as a group. In the example shown in the figure, captured images P1 to P3 are classified into group G1, P4 and P5 into group G2, and so on.

[0053] By doing this, it becomes possible to treat images taken at relatively close dates and times as having the same shooting date and time conditions. The condition of an object changes depending on the date and time; for example, an object may be undamaged on one day, but then suffer some kind of collision and be damaged the next day. If one wishes to perform processing such as keeping only clear images or omitting duplicate images, it is necessary to target images that are considered to have the same shooting date and time conditions. The above grouping is performed from this perspective. Therefore, the time interval for grouping can be set arbitrarily, taking into account the possibility of changes occurring to features and the amount of survey information to be obtained. If the survey information is intended to capture relatively gradual changes, such as the fading of feature displays, the time interval can be set broadly, such as in days, weeks, or months. On the other hand, if damage due to incidents or accidents is also considered, the time interval can be set in minutes or hours, taking into account the possibility of such damage.

[0054] Next, the system server 200 evaluates the clarity of each captured image for each group (step S34). Various evaluation indices can be set. For example, as shown in the figure, the evaluation indices may be the area of ​​the target feature in the captured image, whether the target feature is hidden, the image quality of the captured image, whether the target feature is captured from close to the front, etc. Any one of these indices may be used, or multiple indices may be used. When multiple indices are used, for example, a method may be used in which the evaluation based on each indices is converted into a score and an overall evaluation is calculated.

[0055] Once the captured images have been evaluated in this way, the system server 200 deletes images that do not meet a predetermined evaluation standard (step S35). At this point, the evaluation by the poster in step S31 may also be taken into consideration. By deleting captured images based on the evaluation in this way, it is possible to eliminate unnecessary research information. In addition to or in addition to such evaluation, a process of retaining one of a plurality of photographed images that are evaluated as equivalent based on matching between the photographed images may be performed.

[0056] The information selection process may end with the above processing, but in this embodiment, a process of generating a composite image of the feature from multiple captured images is also performed (step S36). An image of the process is shown in the figure. For example, some of the captured images may have been taken with the bottom of the feature (in this case, a railroad crossing) hidden, while other captured images may have been taken with the top of the feature in low image quality. By combining these images, an image of the entire feature can be obtained, as shown on the right. Various well-known techniques can be applied to this image composition. Image compositing can be performed in various ways, such as performing it on captured images that were given a low rating in step S35, performing it on all captured images in the group regardless of their rating, or performing it on only the captured images that were not deleted in step S35.

[0057] E. Processing of Information: 7 is a flowchart of the information provision process. This process is executed by the information provider 204 of the feature management system, and in terms of hardware, it is executed by the system server 200. The process can be executed periodically, when a predetermined amount of survey information obtained from the map server is reached, in response to a request from the feature manager, or a combination of these, among other methods.

[0058] When the process starts, the system server 200 reads the administrator ID of the feature administrator (step S40). This information can be used to narrow down the features to be provided.

[0059] Next, the system server 200 sets the level of information provided to the feature manager (step S41). Information registered in the feature management system by the feature manager includes information useful to mapmakers, such as the establishment and abolition of features. In this embodiment, to increase the incentive to register such information, the content and amount of information provided to the feature manager are changed depending on the information obtained from the feature manager. The diagram shows an image of the process. The left side shows the evaluation criteria for the information registered by the feature administrator and provided to the map server. For example, the evaluation can be based on the amount of information, the number of features in question, the frequency of registration, and accuracy. On the other hand, the right side shows an example of the information provision level for feature managers. The provision level can be set using parameters such as the amount of information, the number of managed features, and frequency. For example, for feature managers who register a large amount of information, the information provision level can be set so that the amount and frequency of information provided is increased. The information provision level can be set as desired. Note that setting the provision level is an optional process, and step S41 may be omitted.

[0060] Next, the system server 200 reads the survey information etc. from the survey information storage unit (step S42). In this embodiment, information from multiple map servers is stored in the survey information storage unit, so as a result, survey information from multiple map servers is read (step S42). At this time, by narrowing down the information by the administrator ID, it is possible to read only the survey information related to the features managed by the feature administrator.

[0061] The read survey information may be provided to the feature manager as is, but in this embodiment, an information refinement process is performed (step S43). The details of the information refinement process are as explained in Fig. 6. By performing this process, it is possible to provide information to the feature manager efficiently without waste. The information selection process can be omitted because it is also performed in the information collection process (step S23 in Figure 5), but whereas the information collection process targets survey information obtained from one map server, step S43 of the information provision process can target survey information obtained from multiple map servers, which has the advantage of allowing for even more refined selection of survey information.

[0062] From the survey information thus obtained, the system server 200 selects information to provide to the feature manager according to the information provision level set in step S41 (step S44). Note that if step S41 is omitted, step S44 may also be omitted.

[0063] Once the survey information to be provided has been determined in this way, the system server 200 outputs and displays this information on the terminal 100 used by the feature manager (step S45). A display example will be shown later. The results of providing the information are saved as a log (step S46), and the information providing process ends. This log can be used to verify the content of the information provided to the feature manager after the fact, or for purposes such as managing the usage history by the feature manager.

[0064] Fig. 8 is an explanatory diagram showing an example of information provision. It is an example of a screen displayed on the terminal 100 used by the feature manager in step S45 of the information provision process. In this example, a railway company is assumed to be the feature manager. Information may be provided in the form of a list or the like for managed features, but in this embodiment, a method is adopted in which managed features and information are displayed on a map to make it easier to understand. In Figure 8, railways as managed features are divided into sections set by the feature manager and assigned managed feature IDs "R-1" to "R-5." Points displayed on the map represent the center positions of each section as representative points of the managed features. Railways correspond to linear features. In addition, in Fig. 8, managed feature IDs "P1" to "P5" are set. Of these, managed features P2 and P3 are railroad crossings. Managed features P1 and P4 are signs installed on land owned by a feature manager. These correspond to point-like features. The managed feature P5 is a site owned by a feature manager and corresponds to a planar feature.

[0065] Clicking on the icon corresponding to each managed feature on the displayed map will display survey information. For example, clicking on the icon for managed feature ID "R-1" will display photographed images in chronological order, as shown at the top of the image. By looking at these images, the feature manager can recognize that weeds are growing around the railroad tracks, which are managed features, and that some action is required. Here, we have shown the growth of weeds as an example, but various other information can be recognized from the photographed image, such as damage to the tracks or sleepers, the presence or absence of obstacles, etc. Comments may also be displayed together with the photographed image.

[0066] Similarly, clicking on the managed feature ID "P4" displays images of the sign installed there in chronological order. By looking at these images, the feature manager can see that the sign's display is faded and that the support pillar on the right side of the sign was damaged at time TT3.

[0067] In the figure, a warning is displayed for the managed feature ID "P1." This indicates that some kind of abnormality has been discovered through the analysis of survey information, which will be described later. By displaying a warning like this, feature managers can easily find the feature where an abnormality has occurred. The warning can be displayed in various ways, such as by making the icon blink, by displaying it in a different color, or by enlarging its size. The display of the survey information is not limited to the example shown in FIG. 8, and various other modes are possible.

[0068] F. Analysis Processing: 9 is a flowchart of the analysis process, which is executed by the analysis unit 206 of the feature management system, and in terms of hardware, by the system server 200. This process automatically determines whether there are any changes or abnormalities in the condition of the feature based on the survey information. There are various ways to execute this process, such as at the request of the feature manager, when the survey information is provided to the feature manager, or when a certain amount of survey information has been saved.

[0069] When processing begins, the system server 200 reads the survey information for each managed feature (step S50). Then, the degree of difference between the captured images is calculated (step S51). A method can be used in which the captured images are arranged in chronological order, and the degree of difference between the features is calculated by matching them with the images immediately before and after. This process may also utilize image recognition by artificial intelligence. For example, images of normal features photographed from various angles are trained in advance as training data, so that the target features can be recognized from the photographed images, and the extent to which the features in the photographed images differ from the features in the training data is calculated.

[0070] The figure shows an example of changes in the degree of difference. Changes that occur gradually over time, such as the growth of weeds or the fading of a signboard, as shown in Figure 8, tend to result in a generally continuous increase in the degree of difference, as shown in the figure for step S51. When this change exceeds a predetermined threshold, it can be determined that an abnormality has occurred. Furthermore, a change such as the broken support pillar shown in Figure 8 will cause the dissimilarity to change discontinuously at a certain point. In this case, too, if the dissimilarity exceeds the threshold value, it can be determined that an abnormality has occurred. In addition to this determination, it may also be possible to determine that an abnormality has occurred when the dissimilarity changes discontinuously.

[0071] If it is determined that an abnormality has occurred based on the calculated dissimilarity (step S52), the system server 200 outputs an alert (step S53) and ends the analysis process. As a result of the alert, a warning display such as that shown for the managed feature ID "P1" in Figure 8 can be displayed.

[0072] In this embodiment, the analysis process is performed by the system server 200, but it may also be performed by the terminal 100, i.e., the feature manager. It may also be performed by the map server 300, i.e., the map creator. Furthermore, it may also be performed by an analysis server separate from the system server, the terminal 100, and the map server 300.

[0073] G. Maintenance Treatment: 10 is a flowchart of the maintenance process. This process is executed by the change information providing unit 205 of the feature management system and the maintenance unit 308 of the map server, and in terms of hardware, by the system server 200 and the map server 300. This process is a process for updating the map database by reflecting information on features registered by the feature manager, such as information on new features, changes, and abolition of features (hereinafter referred to as "change information").

[0074] The left side of the figure shows the change information provision process. This process can be executed in various ways, such as when the feature administrator registers change information for the feature, when a certain amount of change information has been saved, or periodically.

[0075] In this process, the system server 200 sets the information provision level to the map server 300 (step S60). Information provided from the map server to the feature manager, i.e., survey information, is useful information for the feature manager. In this embodiment, to increase the incentive to register such survey information, the content and amount of information provided to the feature server are changed depending on the survey information provided from the map server to the feature manager. The provision level is set for each map creator. The diagram shows an image of the process. The left side shows the evaluation items for the survey information from the map server. For example, it can be evaluated based on the amount of information, the number of target features, the frequency of provision, and accuracy. On the other hand, the right side shows an example of the information provision level to the map server. The provision level can be set using parameters such as the amount of information, the number of managed features, frequency, and the period until the effective date. The effective date is information that indicates the effective date in the case of features that become effective from a specific date after being installed, such as road signs. For map creators, obtaining information as far into the future as possible is useful for maintaining the map database, etc. In this sense, in this embodiment, the period until the effective date is included in the parameters of the information provision level. Note that setting the provision level is an optional process, and step S60 may be omitted.

[0076] The system server 200 provides the change information to the map server 300 in accordance with the set provision level. If step S60 is omitted, the change information may be provided in accordance with a predetermined standard.

[0077] The map server 300 performs maintenance processing to reflect this change information. This processing can be performed in various ways, such as when the change information is received, when a certain amount of change information has been saved, or periodically.

[0078] The map server reads the target change information (step S70) and evaluates the change information based on the feature manager (step S71). In this embodiment, multiple feature managers are available, so the accuracy and reliability of the change information varies depending on the feature manager. If the feature manager's reliability is low, it is possible that a feature registered as "new" does not actually exist. If such information is reflected in the map database carelessly, it could damage the reliability of the map database. Feature managers can be evaluated based on whether they are sole proprietors or corporations, the scale of their business, past performance, etc. As mentioned above, a feature manager who has a history of registering changes to new features that do not actually exist will be evaluated lower. The feature manager's evaluation is an optional process and may be omitted.

[0079] Next, the map server 300 evaluates the read change information (step S72). If the change information clearly includes "settings" such as new establishment, change, or abolition, the evaluation can be increased. Also, if the change information matches with photographed images of the target feature or its surroundings, the evaluation can be increased. For change information on existing features, the evaluation can be increased because there is a low risk of it being incorrect. In addition to these, evaluation can be based on various other items. This assessment may also take into account assessments based on the feature manager.

[0080] Then, the map server 300 reflects the change information that has received a predetermined or higher evaluation in the map database (step S73), and ends the maintenance process. This makes it possible to efficiently develop a map database. The maintenance process can be modified in various ways. For example, the establishment of new features may be reflected only if they are confirmed visually by an inspector or by photographic images. The change information may be reflected in the map database or not depending on its content.

[0081] H. Effects and Variations: Traditionally, map makers have surveyed the state of features and compiled map databases based on the survey information. On the other hand, feature managers had no choice but to investigate the features under their management themselves, and when there were many features under their management or they were located far away, management became a huge burden. For example, if an individual owned a vacant house in a distant area, it was not easy to check the condition of the house and its surroundings. It was also not easy for a bus operating company to check the status of the many bus stops it had installed. In the past, while there was a high need for feature managers to check the status of the features under their management, no method had been found to reduce the burden. And although the survey information collected by cartographers could be effectively used for feature management, there was no established method for actually utilizing it.

[0082] In contrast, the feature management system of the present embodiment described above allows mapmakers to efficiently obtain survey information collected by the mapmakers for features registered by the feature manager, thereby reducing the burden of feature management. Conversely, this means that the survey information collected by the mapmakers can be used not only for developing the map database but also for feature management, thereby increasing its usefulness.

[0083] Furthermore, while conventionally, feature managers have plans for the establishment, modification, and abolition of managed features, mapmakers have no way of knowing this information, and so have had no choice but to reflect the establishment of new features in the map database based solely on their own survey information. Therefore, depending on the timing of the survey, there can be a delay between the establishment of a new feature and its reflection in the map database, making it impossible to update the map database in a timely manner, which has been an issue.

[0084] In contrast, the feature management system of this embodiment can provide change information provided by the feature manager to the map creator, so that the creation of new features, etc. can be reflected in the map database easily and in a timely manner, thereby improving the usefulness of the map database.

[0085] As mentioned above, the usefulness of information held by feature managers and map creators can be improved by linking them, but until now there has been no way to achieve this. In particular, because the information prepared by each party is prepared in a separate format, linking the information from both parties requires matching each piece of information one by one, which can be a huge burden and can be a challenge.

[0086] In contrast, the feature management system of this embodiment has the advantage that different databases prepared by different entities, such as the feature manager and the map creator, can be linked through the feature registration process, which has the advantage of enabling efficient linking of different databases with a light load. This feature registration process links based on information such as the location and type of features, so as long as the databases contain the corresponding information, they can be linked even if the databases prepared by different entities, such as the feature manager and the map creator, have different formats.

[0087] It is not necessary to have all of the various features described in the examples, and some of them may be omitted or combined as appropriate. Furthermore, the present invention is not limited to the examples, and various modifications can be made as described below without departing from the spirit of the present invention.

[0088] In this embodiment, various modifications can be made. For example, the basic configuration of this embodiment is as follows: A feature management system for managing features, a feature registration unit that manages the information on the features registered from the terminal by linking it with information on features included in a predetermined map database; When the feature management system includes an information providing unit that acquires survey information that indicates the actual status of the feature and provides it to the terminal, the modified example can be configured as follows. The terminals will be used by feature managers who manage the features, but feature managers are not limited to individuals or private companies. For example, if the features to be managed are municipal facilities, roads, etc., the feature manager may be the municipality. The features to be managed can include road signs, road lanes, crosswalks, and other road markings, and the person responsible for managing each of these can also be designated as a feature manager. Survey information can be image data (sometimes called photographed images) of features, comments about features posted via social media, email, etc. Survey information can be information obtained from surveyors commissioned by the creator of the map database, or information obtained from the general public.

[0089] In the feature management system, The feature registration unit may link the registered features to the map database based on location information and attributes of the features. This allows the above-mentioned linking to be performed quickly and accurately with a light load.

[0090] The location information may be, for example, coordinate values ​​such as an address or latitude and longitude. A map may be displayed on the terminal, and the location information of a feature may be easily specified by clicking on the map. Attributes can include, for example, the type of feature, such as a building, sign, or road sign, or the name of the feature. In the case of road signs, the content of the sign, such as speeding or one-way, may also be included. In addition to point-like features that exist at specific points, features can also be linear features with length, such as roads, rivers, and railroad tracks, or areal features with width, such as land such as farmland, parks, administrative boundaries, and intersection areas of wide roads.

[0091] In the feature management system, The feature registration unit may read from the terminal a feature management database that stores information on a plurality of the features, and perform the linking for the information on each of the features. This allows multiple features to be registered efficiently. This registration also makes it possible to link two types of databases, the feature management database and the map database, improving the convenience of both.

[0092] In the feature management system, The features may be classified into point features, line features, and area features and then linked together. In such cases, linear features and area features may be registered in a manner that allows the location within the feature to be specified. One such method is to divide a linear feature such as a road into sections of relatively short distances, even if the road is registered as a single road from a terminal. The division of the sections does not need to be a fixed distance, and can be determined by taking into account the correspondence with the map database. As another method, for a linear feature such as a road, a start point and an end point may be defined, and a virtual axis along the road may be defined, thereby making it possible to identify the position by the distance from the start point or a percentage (%) of the total distance. Similarly, for planar features, the feature may be divided into two-dimensional sections, or an axis or coordinate system may be defined that allows for identification of the position within the feature.

[0093] In the feature management system, The photographed images obtained as the survey information may be selected or synthesized according to a predetermined standard and provided to the terminal. By doing so, it is possible to suppress low-quality survey information, which could be called noise, and improve the accuracy and quality of the information provided. The criteria can be set in various ways, but for example, images taken at the same or similar times or directions may be grouped together. Images may also be selected that show clearly captured features that are not obscured by obstacles or out of focus. Furthermore, multiple captured images may be combined to generate a captured image of a feature.

[0094] In the feature management system, The information processing device may further include an analysis unit that analyzes whether or not there has been any change over time in the target feature or its surrounding environment based on the survey information. This makes it possible to recognize secular changes in features more objectively and efficiently. Examples of changes over time include damage, destruction, and wear to a feature, either partially or entirely. For example, in the case of a road sign, this would include a bent part, the road sign itself falling over, or the sign becoming faded. In the case of road markings, this would include damage caused by fading or the road itself collapsing. Changes over time also include the construction, removal, or alteration (replacement) of a feature itself. Changes over time in the environment surrounding the feature itself would include, for example, the growth of weeds around the feature or fallen trees near the feature. This also includes conditions such as the accumulation of rain or snow. The analysis unit may perform the analysis in response to a request from the terminal, or may perform the analysis when providing survey information to the terminal. The analysis unit may be provided as part of the feature management system, on the map database side, on the terminal side that manages the features, or externally independent of any of the above.

[0095] In the feature management system, Multiple map databases may be linked to registered features. This allows for the provision of survey information sourced from multiple map databases. In this case, the information provided to the terminal may be a logical sum of survey information obtained from multiple map databases, making it possible to provide a wider range of information. Alternatively, the survey information obtained from multiple map databases may be carefully selected to provide more accurate and high-quality information, thereby enabling the information provided to be used more effectively.

[0096] In the feature management system, The amount or content of information provided to a terminal may be changed depending on the amount or content of information about features registered from the terminal. This will increase the incentive for feature managers to provide information.

[0097] Conversely, the amount or content of information provided to the map database from the information on features registered from the terminal may be changed depending on the amount or content of information provided to the terminal. This increases the incentive to provide information from the map database to the terminal.

[0098] In the feature management system, a map server that stores a map database includes: The information processing device may further include a maintenance unit that reflects the information about the features registered from the terminal in the map database. By doing so, the information obtained from the feature manager can be efficiently reflected in the map database.

[0099] The processing by the maintenance department can be carried out in various ways. For example, if a registered feature does not exist in the map database, the feature may be newly added to the map database, thereby efficiently enriching the map database. Furthermore, information on new, abolished, or changed features may be received from the terminal, and the feature may be added, deleted, or changed in the map database accordingly. Since the processing is performed in response to instructions from the feature manager, the information can be accurately reflected in the map database. Furthermore, the person who registered the information about the features or the registered information may be evaluated, and if the evaluation is above a predetermined level, the information may be reflected in the map database. In this way, reliable information can be reflected in the map database.

[0100] The aspects described in all or part of the above embodiments solve any one of the following problems: appropriate processing of map data or feature data, improving processing speed, improving processing accuracy, improving usability, improving functions using data or providing appropriate functions, other improving functions or providing appropriate functions, reducing the data and / or program capacity, miniaturizing devices and / or systems, providing appropriate data, programs, recording media, devices and / or systems, and optimizing the production and manufacturing of data, programs, recording media, devices and / or systems, such as reducing the production and manufacturing costs of data, programs, devices or systems, facilitating production and manufacturing, and shortening production and manufacturing times. [Explanation of symbols]

[0101] 100, 100A, 100B terminals 102 Feature Management Database 104 Browser 200 System Server 201 User Management Department 202 Display control unit 203 Feature Registration Department 204 Information Provision Department 205 Change Information Department 206 Analysis Department 210 Main control unit 220 User Database 222 Feature Registration Database 224 Survey Information Storage Unit 300, 300A, 300B map server 302 Information Transmission and Reception Unit 304 Research and Information Collection Department 306 Map Database 308 Maintenance Department

Claims

1. A feature management method executed by a feature management system connected to a map server having a map database and a system server that manages features, comprising: The features are managed with different identification information in the map database and in a feature management database in which a feature manager manages the features, The feature management system By linking the respective identification information, the information of the features stored in the map database and the information of the features stored in the feature management database are associated with each other for each feature, and are stored in a feature registration database; When change information indicating a change in the status of an arbitrary feature is registered in the feature management database from a terminal operated by the feature manager, To update the information of the features stored in the map database, Identifying the feature to be changed based on the identification information linked in the feature registration database, and transmitting the change information to the map database; evaluating the registered change information and / or evaluating the feature manager who registered the change information, and if the evaluation is above a predetermined level, updating the feature information stored in the map database with the change information; Feature management method to perform.

2. The feature management system Obtaining survey information including date and time information and contributor information from the map server, obtaining identification information in the feature management database corresponding to the identification information in the map database of the feature that is the subject of the survey information based on the feature registration database, and storing the survey information in association with the obtained identification information; The feature management method of claim 1 , further comprising:

3. The feature management system Evaluating the stored survey information based on the credibility rank of the poster who posted the stored survey information, and deleting the survey information if it does not meet a predetermined rating; and evaluating the clarity of the captured images included in the stored survey information, and deleting the captured images if it does not meet a predetermined rating. The feature management method of claim 2 , further comprising:

4. The feature management system reading out the plurality of pieces of survey information stored for each of the features, arranging the captured images included in the read out survey information in chronological order, and calculating the degree of difference between the arranged captured images to determine whether or not there has been any change over time or abnormality in the condition of the features; The feature management method according to claim 3 , further comprising the steps of:

Images