Disaster prevention map provision system and disaster prevention map creation device

Abstract

To obtain a disaster prevention map provision system and disaster prevention map creation device that can easily maintain the information on disaster prevention maps in an up-to-date state. [Solution] The disaster prevention map creation device 1 of the disaster prevention map provision system 1000 includes a request acquisition unit 110 that acquires modification requests, which are requests from users regarding the addition or modification of disaster prevention information in a disaster prevention map that includes a map and disaster prevention information, and a map modification unit 111 that modifies the disaster prevention information in the disaster prevention map based on the modification requests acquired by the request acquisition unit 110.

Description

Technical Field

[0004] ,

[0006] , ,

[0005] , ,

[0001] The present invention relates to a disaster prevention map providing system and a disaster prevention map creation device.

Background Art

[0002] In disaster prevention and mitigation measures, there is an idea of reducing damage through "self-help", "mutual assistance", and "public assistance". For example, in Patent Document 1, a disaster occurrence initial movement support kit that supports the initial response of local government officials responsible for "public assistance" during a disaster has been proposed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

[0007] This invention was made against the backdrop of the above-mentioned problems, and provides a disaster prevention map provision system and a disaster prevention map creation device that make it easy to maintain the information on disaster prevention maps in an up-to-date state. [Means for solving the problem]

[0008] The disaster prevention map provision system according to the present invention comprises: a request acquisition unit that acquires a modification request, which is a request from a user for adding or changing the disaster prevention information in a disaster prevention map that includes a map and disaster prevention information; a map modification unit that modifies the disaster prevention information in the disaster prevention map based on the modification request acquired by the request acquisition unit; and a display unit that displays the disaster prevention map including the modified disaster prevention information.

[0009] The disaster prevention map creation device according to the present invention comprises a request acquisition unit that acquires a modification request, which is a request from a user regarding the addition or modification of disaster prevention information in a disaster prevention map that includes a map and disaster prevention information, and a map modification unit that modifies the disaster prevention information in the disaster prevention map based on the modification request acquired by the request acquisition unit. [Effects of the Invention]

[0010] According to the present invention, disaster prevention maps can be modified based on modification requests from users regarding the addition or modification of disaster prevention information, making it easier to maintain the information on the disaster prevention map in an up-to-date state. [Brief explanation of the drawing]

[0011] [Figure 1]This is a system configuration diagram of the disaster prevention map provision system 1000 according to an embodiment. [Figure 2] This is a functional block diagram of Server 1 according to the embodiment. [Figure 3] This is an example of the data structure of the modification request data according to the embodiment. [Figure 4] This is an example of the data structure of the modified data according to the embodiment. [Figure 5] This is an example of the data structure of user data according to the embodiment. [Figure 6] This is an example of the data structure of regional data according to the embodiment. [Figure 7] This is an example of the data structure of evacuation route data according to the embodiment. [Figure 8] This is an example of the data structure of patrol route data according to the embodiment. [Figure 9] This flowchart shows an example of the process for modifying the disaster prevention map of Server 1 according to the embodiment. [Figure 10] This is an example of a screen displayed on the display unit 25 of terminal 2 during the disaster prevention map modification process according to the embodiment. [Figure 11] This flowchart shows an example of the notification process according to the embodiment. [Figure 12] This is an example of how disaster prevention information is displayed according to the embodiment. [Figure 13] This is a sequence chart showing an example of the process for creating a specific evacuation route according to the embodiment. [Figure 14] This is an example of a screen displayed on the display unit 25 of terminal 2 during the evacuation route creation process according to the embodiment. [Figure 15] This is a sequence chart showing an example of the certification process for a disaster prevention map according to the embodiment. [Figure 16] This is an example of a screen displayed on the display unit 25 of terminal 2 during the certification process of a disaster prevention map according to the embodiment. [Figure 17] This flowchart shows an example of the process for creating a security patrol route for Server 1 according to the embodiment. [Figure 18]It is a diagram showing an example of display before and after correction of a security patrol route according to an embodiment. [Figure 19] It is a sequence chart showing an example of verification processing of a disaster prevention map according to an embodiment. [Figure 20] It is a screen example of a verification result displayed on a display unit 25 of a terminal 2 according to an embodiment.

Mode for Carrying Out the Invention

[0012] Hereinafter, embodiments of the present invention will be described with reference to the drawings. The present invention is not limited to the following embodiments, and various modifications can be made without departing from the gist of the present invention. Further, the present invention includes all combinations of configurations that can be combined among the configurations shown in the following embodiments. In addition, the devices shown in the drawings are examples of the devices of the present invention, and the devices of the present invention are not limited by the devices shown in the drawings. In each figure, those with the same reference numerals are the same or corresponding ones, which is common throughout the entire specification.

[0013] Embodiment. (System Configuration) FIG. 1 is a system configuration diagram of a disaster prevention map providing system 1000 according to an embodiment. The disaster prevention map providing system 1000 of the present embodiment includes a server 1 and one or more terminals 2. The server 1 and the terminal 2 are communicably connected by a wired or wireless network 3. The disaster prevention map providing system 1000 is a system that electronically provides a disaster prevention map to a user who uses the terminal 2. Here, the disaster prevention map is a combination of a map and disaster prevention information. The disaster prevention information is information for supporting quick and safer evacuation, such as an evacuation place or a dangerous location. The disaster prevention information may include information for disaster prevention or rescue, such as the location of fire-fighting equipment such as fire hydrants, the location of life-saving equipment such as AEDs (Automated External Defibrillators) or life-saving vests, or a place of escape (a temple to rush into) for ensuring personal safety from suspicious persons.

[0014] Server 1 is a computer device that functions as a disaster prevention map creation device for creating disaster prevention maps. Server 1 comprises a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 is implemented by a processor such as a CPU (Central Processing Unit) that executes programs stored in memory, and by operating according to the program, it realizes various functions described later. The storage unit 12 is a non-volatile or volatile semiconductor memory such as RAM, ROM, flash memory, EPROM, EEPROM, or an external storage medium such as a memory card, or a combination thereof, and stores various data. The communication unit 13 is a communication interface that communicates with terminal 2 via network 3.

[0015] In this embodiment, an example is shown in which the disaster prevention map creation device is configured with one server 1, but two or more servers 1 may cooperate to configure the disaster prevention map creation device. Furthermore, the control unit 11, storage unit 12, and communication unit 13 may each be realized by the cooperation of one or more hardware components. In addition, the control unit 11, storage unit 12, and communication unit 13 may each be implemented on separate computer devices.

[0016] Terminal 2 is a computer device used by users to create, modify, or view disaster prevention maps. Terminal 2 is, for example, a smartphone, tablet, or personal computer. Terminal 2 comprises a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, and a display unit 25.

[0017] The control unit 21 is implemented by a processor such as a CPU that executes programs stored in memory. The storage unit 22 is a non-volatile or volatile semiconductor memory such as RAM, ROM, flash memory, EPROM, or EEPROM, or an external storage medium such as a memory card, or a combination thereof. The communication unit 23 is a communication interface that communicates with the server 1 via the network 3. The input unit 24 is an input device that receives input from the user, such as a touch panel, keyboard, mouse, or microphone that receives voice input. The display unit 25 is a device that performs graphic display, such as a liquid crystal display, organic EL display, or electronic paper.

[0018] Various processes, such as the display of the disaster prevention map described later, performed by terminal 2 are executed based on an application program run by control unit 21. The application program displays data transmitted from server 1 and received by communication unit 23 on display unit 25. The application program also transmits data or instructions input by input unit 24 to server 1 via communication unit 23. The application program may be a dedicated program or it may be embedded and executed in a web browser. Alternatively, the application program may be a web browser that displays data provided as an HTML file from server 1.

[0019] (Server 1 configuration) Figure 2 is a functional block diagram of Server 1 according to an embodiment. The control unit 11 includes, as functional units, a request acquisition unit 110, a map modification unit 111, an additional modification inquiry unit 112, an approval unit 113, an evacuation route creation unit 114, a patrol route creation unit 115, a verification unit 116, a notification unit 117, an output unit 118, and a management unit 119.

[0020] The request acquisition unit 110 acquires requests from terminal 2 for the addition or modification of disaster prevention information that constitutes the disaster prevention map. The request acquisition unit 110 stores the acquired requests in the modification request data storage unit 121 of the storage unit 12.

[0021] The map modification unit 111 modifies the disaster prevention information that constitutes the disaster prevention map based on the modification request acquired by the request acquisition unit 110. The map modification unit 111 stores the disaster prevention map, including the modified disaster prevention information, in the disaster prevention map storage unit 120. The map modification unit 111 also stores information related to the modification process in the modification data storage unit 122.

[0022] When the request acquisition unit 110 acquires a modification request, the additional modification inquiry unit 112 inquires with the user whether there is any disaster prevention information that needs to be modified in addition to the modification request. Specifically, the additional modification inquiry unit 112 extracts locations that meet the inquiry conditions from among the locations near the locations on the disaster prevention map included in the modification request, and outputs a notification from the notification unit 117 to terminal 2 inquiring whether or not the disaster prevention information for the extracted locations needs to be modified.

[0023] The certification unit 113 adds certification information to the disaster prevention information included in the disaster prevention map based on certification instructions from the user. Here, "certification" is like an endorsement of the disaster prevention information. When the validity of the disaster prevention information is confirmed by a user different from the user who created or modified the disaster prevention information, or at a different date and time than when the disaster prevention information was created or modified, a certification instruction is sent from terminal 2 based on the instructions of the user who made the confirmation. Then, based on this certification instruction, the certification unit 113 updates the certification information of the disaster prevention map stored in the disaster prevention map storage unit 120.

[0024] The evacuation route creation unit 114 receives evacuation route creation requests from users regarding the addition or modification of evacuation routes for each user, and creates or modifies evacuation routes based on the received evacuation route creation requests. Each user's evacuation route is, for example, a route from home to an evacuation shelter or a route home from work, and is a route used for evacuation or returning home in the event of a disaster. The evacuation route creation unit 114 stores the created or modified evacuation routes in the evacuation route storage unit 125.

[0025] The patrol route creation unit 115 creates or modifies a crime prevention patrol route. A crime prevention patrol route is the route taken when disaster prevention members, etc., who constitute a self-governing disaster prevention organization, conduct crime prevention patrols. The patrol route creation unit 115 creates or modifies a crime prevention patrol route based on a creation instruction from a user that specifies the points to be passed through and their order. In addition, the patrol route creation unit 115 in this embodiment creates or modifies a crime prevention patrol route based on information in the modification data storage unit 122, which stores information related to the modification of the disaster prevention map by the map modification unit 111. The patrol route creation unit 115 stores the created or modified crime prevention patrol route in the patrol data storage unit 126.

[0026] The verification unit 116 verifies the disaster prevention map stored in the disaster prevention map storage unit 120 based on the information stored in the modified data storage unit 122 and the verification conditions. The verification unit 116 verifies the disaster prevention map at predetermined timings or in response to instructions from terminal 2. The verification conditions are, for example, the maximum number of locations with registered disaster prevention information per unit area on the disaster prevention map. If the disaster prevention information is classified into multiple types according to the degree of impact on evacuation, etc., the maximum number of locations for each type may also be used. If there are too many locations with registered disaster prevention information, it can make the disaster prevention map difficult for users to view. Therefore, by verifying the disaster prevention map based on such verification conditions, the usability of the disaster prevention map is maintained.

[0027] The notification unit 117 inputs a notification containing information to be provided to the user into the communication unit 13, and the communication unit 13 transmits the notification to the terminal 2 via the network 3. The notification unit 117 sends the notification based on the notification availability time period for each user and the notification destination, which indicates the address to which the notification will be sent, stored in the user data storage unit 123.

[0028] The output unit 118 determines whether or not to output a notification to the user's terminal 2 when new information is added to or updated in the storage unit 12, and instructs the notification unit 117 to execute notification processing when it determines to output a notification. In this embodiment, when the output unit 118 detects that the disaster prevention map has been modified by referring to the modified data storage unit 122 (Figure 4), it extracts evacuation routes including locations corresponding to the modified disaster prevention information by referring to the evacuation route storage unit 125 (Figure 7). Then, the output unit 118 identifies the user associated with the extracted evacuation route by referring to the user data storage unit 123 (Figure 5), and instructs the notification unit 117 to process a notification to that user. In addition, when the output unit 118 detects that the disaster prevention map has been modified by referring to the modified data storage unit 122 (Figure 4), it extracts patrol routes including locations corresponding to the modified disaster prevention information by referring to the patrol data storage unit 126 (Figure 8). The output unit 118 then refers to the user data storage unit 123 (Figure 5) to identify the user who has administrator privileges to manage the patrol route, and instructs the notification unit 117 to send a notification to that user.

[0029] Furthermore, in this embodiment, the output unit 118 transmits the disaster prevention map and the like stored in the storage unit 12 to the user's terminal 2 via the communication unit 13 in response to a request from the terminal 2.

[0030] The management unit 119 manages information about terminal 2 and the users using it, regional information, and information on the electronic bulletin board. The management unit 119 stores user information transmitted from terminal 2 in the user data storage unit 123 and regional information transmitted from terminal 2 in the regional data storage unit 124. The management unit 119 also stores digital disaster prevention maps provided by local governments, etc., as initial disaster prevention maps in the disaster prevention map storage unit 120. The management unit 119 also transmits information from the electronic bulletin board stored in the bulletin board information storage unit 127 to terminal 2 via the communication unit 13 at predetermined timings or based on requests from terminal 2. The management unit 119 may also manage the read / unread status of bulletin board information on a per-user basis.

[0031] The memory unit 12 includes a disaster prevention map memory unit 120, a correction request data memory unit 121, a correction data memory unit 122, a user data memory unit 123, a regional data memory unit 124, an evacuation route memory unit 125, a patrol data memory unit 126, and a bulletin board information memory unit 127.

[0032] The disaster prevention map storage unit 120 stores disaster prevention map information, which combines maps and disaster prevention information. The disaster prevention map storage unit 120 can store disaster prevention maps for each designated area.

[0033] The correction request data storage unit 121 stores correction request data, which is correction request data related to the addition or modification of disaster prevention information in the disaster prevention map transmitted from terminal 2, as a history. Figure 3 shows an example of the data structure of correction request data according to the embodiment. The correction request data includes a request ID, location information, text information, an image, the person who requested the correction, whether or not the correction was performed, and a point. The request ID is information that uniquely identifies the correction request. The location information is information that identifies the location related to the correction request. The location information may be text such as a facility name or intersection name, or it may be location information that specifies longitude and latitude. The text information is a text representation of information about each location transmitted from terminal 2. The image is an image of each location transmitted from terminal 2. For correction requests that do not include an image, information indicating that there is no image is stored. The person who requested the correction is information that identifies the user of terminal 2 that sent the correction request, and is either a name or user ID (see Figure 5). Whether or not the correction was performed is information that indicates whether or not the disaster prevention map was actually corrected based on the correction request. In this embodiment, when the map modification unit 111 modifies the disaster prevention map, it changes the initial value "Do not implement" to "Implement".

[0034] Points are numerical values ​​awarded for correction requests. In this embodiment, the numerical value differs depending on whether the disaster prevention map has actually been corrected based on the correction request. When the map correction unit 111 corrects the disaster prevention map, it changes the initial value of "1" to "3". Note that the numerical value of the points and the conditions for awarding points are examples only. In this embodiment, the management unit 119 aggregates the points for each user over a predetermined period and outputs the aggregated results from the output unit 118 to the terminal 2 of the user with administrator privileges. The aggregated point results can be used when a local disaster prevention organization or the like gives users rewards corresponding to the points (e.g., awards or prizes such as disaster prevention goods). By awarding points to users in response to correction requests in this way, it is possible to increase the motivation of users to register correction requests. By enabling local residents to actively find disaster prevention information that needs correction and provide correction requests, the information on the disaster prevention map can be kept fresh and effective.

[0035] The correction data storage unit 122 stores correction data, which is a history of information related to corrections to the disaster prevention map based on correction requests, and information associated therewith. Figure 4 shows an example of the data structure of correction data according to the embodiment. In this embodiment, the correction data consists of one record for each combination of a location targeted by the disaster prevention information and the correction content. For example, if there is different disaster prevention information (two or more hazardous locations, etc.) for the same location, a record is created for each piece of disaster prevention information. Alternatively, one record may be configured for each location.

[0036] The correction data includes an ID, correction location information, correction information, initial registration date and time, latest correction date and time, correction count, image, impact level, and certification. The ID is information that uniquely identifies the target of the correction (location and correction content) of the disaster prevention information. The correction location information is information that identifies the location where the disaster prevention information was added or changed. The location may be text such as a facility name or intersection name, or it may be location information that specifies longitude and latitude. The correction information is a textual representation of the content of the disaster prevention information at the target location. The initial registration date and time is the date and time when the disaster prevention information was first registered. The latest correction date and time is the latest date and time when the disaster prevention information was corrected, and if it has not been corrected since initial registration, it is the same date and time as the initial registration date and time. The correction count is the number of times the disaster prevention information has been corrected, and in this embodiment, the initial registration is counted as the first time. The image is information on whether or not the correction information includes an image, and image data may be linked.

[0037] The impact level indicates the degree of impact on the user of the correction information. Here, the impact level is a numerical value with two or more levels set based on the degree of danger during normal times or during evacuation for disaster prevention information. For example, the impact level may be set in three levels, such as severely dangerous areas (areas under special warning for landslides, areas where large-scale floods are expected, etc.), moderately dangerous areas (areas where flood damage is possible, etc.), and mildly dangerous areas (areas with a risk of small-scale landslides). Furthermore, the impact level may be set based on region-specific information (for example, locations with a large number of registered evacuation routes, areas with high residential density, locations with narrow roads, locations with important infrastructure facilities, locations that have experienced significant damage in the past, etc.). The impact level may be set for each correction information based on instructions from terminal 2 of a user with administrator privileges. In addition, the impact level may be set using artificial intelligence. Specifically, one or more of the following are input to an artificial intelligence unit having a trained model running on server 1 or a device connected to server 1: location, correction information, and image, and the impact level is output from the artificial intelligence unit. The certification indicates whether or not certification has been granted by the certification department 113.

[0038] Here, we will explain the relationship between the correction request data shown in Figure 3 and the correction data shown in Figure 4. The correction data (Figure 4) is a compilation of the correction request data (Figure 3) that was actually used to correct the disaster prevention map, grouped by the target of the disaster prevention information correction. Multiple records in the correction request data (Figure 3) that indicate the same location and the same disaster prevention information are aggregated into a single record in the correction data (Figure 4). For example, in Figure 3, the first and fourth records are the same location, and the disaster prevention information indicated by the text information is substantially the same. The location information and text information in the correction request data (Figure 3) are analyzed for similarities and differences, for example using artificial intelligence, and those determined to be the same are recorded as a single record in the correction data (Figure 4). The functions of the artificial intelligence are executed on Server 1 or a device connected to Server 1 in a communicable manner.

[0039] The user data storage unit 123 stores user data, which is information about the user using terminal 2. Figure 5 shows an example of the data structure of user data according to this embodiment. The user data includes user ID, name, designated area, designated evacuation route, contactable time period, notification recipient, points held, and authority. The user ID is information that uniquely identifies the user. The name is the user's name. The designated area is the area designated as the area where the user resides from among the areas included in the disaster prevention map. In this embodiment, one of the areas included in the area data (see Figure 6) is designated. The designated evacuation route is information that identifies the evacuation route, and in this embodiment, one of the evacuation routes included in the evacuation route data (see Figure 7) is designated.

[0040] The contactable time slot is the time period during which the server 1 sends notifications to the user's terminal 2. Due to the diversification of lifestyles, the times when users are active vary. For example, if a notification from the server 1 arrives at terminal 2 during an active time such as bedtime, the notification may get lost and be difficult for the user to recognize. Therefore, in this embodiment, a contactable time slot is set for each user, and the notification unit 117 sends notifications to the user during the contactable time slot. This makes it easier for the user to recognize notifications from the notification unit 117 to terminal 2. The contactable time slot is stored as user data by the management unit 119 based on the information transmitted from terminal 2.

[0041] The notification recipient is information that identifies the recipient of notifications from the notification unit 117. The notification recipient may be, for example, an email address, or a destination used by a dedicated or general-purpose application executed on terminal 2. The points held are the total value of points held by the user. The permissions indicate the authority to view and edit various data stored in the storage unit 12. In this embodiment, there are two types of permissions: general and administrator. General users can, for example, view and edit their own user data, such as their name, designated area, designated evacuation route, contactable time slots, and notification recipient, and can also send correction requests and create evacuation routes. Administrators, for example, in addition to the permissions of general users, can certify corrected data and create crime prevention patrol routes.

[0042] The regional data storage unit 124 stores regional data, which is information about one or more regions included in the disaster prevention map. Figure 6 shows an example of the data structure of regional data according to the embodiment. The regional data includes a regional ID, a regional name, and a regional range. The regional ID is information that uniquely identifies a region. The regional name is the name of the region. The regional range is the range identified by location information consisting of longitude and latitude. One of the regions in the regional data is designated as the user's place of residence (see Figure 5).

[0043] The evacuation route storage unit 125 stores the evacuation route, which is the path taken during evacuation. Figure 7 shows an example of the data structure of evacuation route data according to this embodiment. In this embodiment, there are two types of evacuation routes: a general evacuation route used in common by a group, and a user's unique evacuation route. The general evacuation route is, for example, an evacuation route from a facility such as a school or hospital where multiple people reside to an evacuation site. The unique evacuation route is an evacuation route from the user's home to an evacuation site, and may include stops made during evacuation. As shown in Figure 7, the evacuation route includes an evacuation route ID and route information. The evacuation route ID is information that uniquely identifies the evacuation route and is configured to distinguish between general evacuation routes and unique evacuation routes. The route information is information in which location information is arranged in the order of waypoints.

[0044] The patrol data storage unit 126 stores the patrol route, which is the route taken for a crime prevention patrol. Figure 8 shows an example of the data structure of patrol route data according to the embodiment. The patrol route data includes a patrol route ID and route information. The patrol route ID is information that uniquely identifies the patrol route. The route information is information in which location information is arranged in the order of waypoints.

[0045] The bulletin board information storage unit 127 stores information to be provided to users as an electronic bulletin board. Bulletin board information includes, for example, information on changes in the head of a district or neighborhood association in the area covered by the disaster prevention map, information on local events such as boccia experience events, crime prevention information such as information on suspicious persons, and weather forecasts. The data stored in the bulletin board information storage unit 127 is, for example, data obtained via network 3 from an external server operated by a local government or an external organization. It is also possible to manage whether the information provided has been read or not for each user.

[0046] (Revision of disaster prevention map) Figure 9 is a flowchart showing an example of the disaster prevention map modification process on Server 1 according to the embodiment. Figure 10 is an example of the screen displayed on the display unit 25 of Terminal 2 during the disaster prevention map modification process according to the embodiment. The operation during disaster prevention map modification will be explained with reference to Figures 9 and 10.

[0047] The disaster prevention map modification process is initiated when terminal 2 issues a command to server 1 to begin modifying the disaster prevention map. Specifically, the display unit 25 of terminal 2 displays a disaster prevention map 200, as shown in Figure 10(a), based on information provided by server 1. The disaster prevention map 200 includes a map 201 and several icons 202 to 205. Icon 202 indicates evacuation shelters such as schools, icon 203 indicates a home, icon 204 indicates a location containing evacuation information added by the user, and icon 205 indicates the location of an AED, but these are just examples. When terminal 2, which is displaying such a disaster prevention map 200, specifies that it wants to add or change disaster prevention information by indicating the location with an arrow 300, an information input screen 400 for adding disaster prevention information is displayed, as shown in Figure 10(b). When adding disaster prevention information, it may be possible to refer to past modification request data stored in the modification request data storage unit 121. In this case, it is possible to add new information by referring to past situations, or to decide to stop adding information if the situation has not changed.

[0048] In Figure 10(b), the information input screen 400 includes a location name input field 401, a disaster prevention information text input field 402, an image file input field 403, and an input information transmission button 404 for sending the entered information to the server 1. Input to input fields 401 to 403 is performed using the input unit 24 of terminal 2. The location information of the location specified by the arrow 300 in Figure 10(a) is entered as an initial value in the location name input field 401, and can be edited by input from the input unit 24. When the input information transmission button 404 is pressed after input has been entered in input fields 401 to 403, the information entered in input fields 401 to 403 is sent to the server 1 as a request to correct disaster prevention information.

[0049] In Figure 9, the request acquisition unit 110 of server 1 acquires a request to correct disaster prevention information (step S1). The request acquisition unit 110 then stores the acquired correction request in the correction request data storage unit 121. Subsequently, the map correction unit 111 outputs a notification to terminal 2 via the communication unit 13 to confirm whether it is OK to correct the disaster prevention map based on the correction request acquired in step S1 (step S2). Then, as shown in Figure 10(c), a confirmation screen 410 is displayed on the display unit 25 based on the notification from server 1.

[0050] The confirmation screen 410 in Figure 10(c) includes a confirmation display field 411, a button 412, and a button 413. The confirmation display field 411 displays the information entered on the information input screen 400. Button 412 is a button for instructing the correction of the disaster prevention map, and when this button is selected, a correction execution instruction is sent from terminal 2 to server 1. Button 413 is a button for canceling the correction execution, and when this button is selected, a correction cancellation instruction is sent from terminal 2 to server 1.

[0051] In Figure 9, the map modification unit 111 determines whether or not it has received a modification execution instruction. If it has received one (step S3: YES), it modifies the disaster prevention map and stores the modified disaster prevention map in the disaster prevention map storage unit 120, and updates the information in the modification request data storage unit 121 and the modification data storage unit 122 (step S4). If the map modification unit 111 does not receive a modification execution instruction but receives a modification cancellation instruction (step S3: NO), it proceeds to step S5 without modifying the disaster prevention map. Note that the processing in steps S2 and S3 is optional.

[0052] In step S5, the additional modification inquiry unit 112 determines whether there are any locations among the locations included in the disaster prevention map modified in step S4 that are different from the modified locations but still meet the inquiry conditions. If there are locations that meet the inquiry conditions (step S5: YES), the additional modification inquiry unit 112 outputs a notification to terminal 2 inquiring about the necessity of modifying those locations (step S6). If there are no locations that meet the inquiry conditions (step S5: NO), the process proceeds to step S8.

[0053] Here, a location that satisfies the inquiry criteria is a location that falls under any of the following (a) to (c). (a) A point within a predetermined range from the point identified by the point information included in the correction request acquired by the request acquisition unit 110 in step S1. (i) A location that is within a predetermined range from the location identified by the location information included in the correction request acquired by the request acquisition unit 110 in step S1, and the date and time of the correction request stored in the correction request data storage unit 121 belongs to a predetermined period. (c) A location within a predetermined range from the location identified by the location information included in the correction request acquired by the request acquisition unit 110 in step S1, and the correction request data of the disaster prevention information stored in the correction request data storage unit 121 does not contain an image.

[0054] The locations within the predetermined range in (a) to (c) above refer to locations within a predetermined radius centered on the location included in the correction request in step S1, and are relatively close to the location included in the correction request. By inquiring with the user about the necessity of correcting disaster prevention information for such locations, if the user sends a correction request while walking around the area, the user can be prompted to update disaster prevention information for locations close to that location. Furthermore, the locations where the date and time of the correction request in (b) above falls within a predetermined period refer to, for example, locations where the date and time of the most recent correction request is old, i.e., locations where no correction request has been made for some time. By inquiring about the necessity of correcting disaster prevention information for such locations where disaster prevention information has not been updated recently, the user can be prompted to update the disaster prevention information. Furthermore, the locations where the correction request data in (c) above does not contain images refer to locations that contain only text information. By inquiring about the necessity of correcting disaster prevention information for locations that do not contain images, the user can be prompted to update disaster prevention information that includes images.

[0055] In Figure 9, if a correction request is received from terminal 2 (step S7: YES), the process returns to step S2 and continues. If no correction request is received (step S7: NO), the process proceeds to step S8. In step S8, the map correction unit 111 determines whether or not the disaster prevention map has been corrected. If the disaster prevention map has not been corrected (step S8: NO), the process ends. If the disaster prevention map has been corrected (step S8: YES), the notification process is executed (step S9).

[0056] In step S2 of Figure 9, a confirmation notification of the correction being implemented is output to terminal 2. However, if the correction request meets predetermined conditions (for example, the correction request data includes an image), server 1 may automatically correct the disaster prevention map without outputting a confirmation notification. Also, although Figure 9 shows an example where processing is performed each time a correction request for the disaster prevention map is received, the received correction requests may be accumulated, and if the accumulated correction requests meet predetermined conditions, server 1 may automatically correct the disaster prevention map. For example, if multiple correction requests are made for the same location or locations within a predetermined range, the disaster prevention map may be automatically corrected without outputting a confirmation notification. Furthermore, if correction requests with similar content are issued from multiple terminals 2, the disaster prevention map may be automatically corrected.

[0057] Figure 11 is a flowchart showing an example of notification processing according to the embodiment. Notification processing is performed by the notification unit 117 of server 1. The notification unit 117 refers to the data stored in the modified data storage unit 122 and the evacuation route storage unit 125 to extract evacuation routes that include points on the disaster prevention map modified by the map modification unit 111 (step S10). Subsequently, the notification unit 117 refers to the data stored in the user data storage unit 123 to extract users associated with the evacuation routes extracted in step S10 (step S11).

[0058] The notification unit 117 performs notification processing for each user (step S12). Specifically, based on the data in the user data storage unit 123, it determines whether the current time is within the contactable time period (step S121). If it is not within the contactable time period (step S121: NO), it waits. If it is within the contactable time period (step S121: YES), it outputs a notification to terminal 2 indicating that disaster prevention information for a point included in the evacuation route has been updated (step S122). Next, it determines whether it has received a confirmation signal from terminal 2 indicating that it has received the notification (step S123). If it has received confirmation (step S123: YES), it terminates the process. If it has not received confirmation (step S123: NO), it waits and then outputs the notification again (step S124). The waiting time in step S124 is not particularly limited, but it is desirable that the timing of outputting the notification again is also within the contactable time period. Also, if confirmation is not received even after outputting the notification again, it may wait again before outputting the notification again.

[0059] Figure 12 shows an example of the display of disaster prevention information according to the embodiment. Figure 12 shows an example of a screen displayed on the display unit 25 of terminal 2 based on information transmitted from the output unit 118 of server 1. On the disaster prevention map 200, disaster prevention information registered at the selected location is displayed in the disaster prevention information field 210, overlaid on the map 201. The disaster prevention information field 210 includes text information 211 and an image 212. The text information 211 is the text of the corrected information stored in the corrected data storage unit 122 or the text of a simplified version thereof. The image 212 is an image stored in the corrected data storage unit 122. If multiple images are registered, all of the multiple images may be displayed side by side, or one of them may be displayed as image 212, or any one of the multiple images selected by terminal 2 may be displayed.

[0060] The display on the display unit 25 of terminal 2 is controlled by the control unit 21, which acts as a display control unit. By overlaying the map 201 with disaster prevention information for the locations on the map 201, the user can easily grasp the information for each location. Note that the disaster prevention information section 210 displayed on the disaster prevention map 200 in Figure 12 only displays information for locations specified in the input unit 24. For example, clicking on icon 204 displays the disaster prevention information section 210. This simplifies the display compared to when the disaster prevention information section 210 for all locations is displayed simultaneously, making it easier for the user to grasp the information they need. The display unit 25 may also display only the information that satisfies the filter conditions specified in the input unit 24. In this case, the icon 204 itself may not be displayed, or the icon 204 may be displayed but the disaster prevention information section 210 may not be displayed. The display unit 25 may also display only information within a predetermined range based on location information acquired using positioning technology such as GPS by the positioning unit (not shown) of terminal 2.

[0061] (Create evacuation routes) Figure 13 is a sequence chart showing an example of the process for creating a unique evacuation route according to the embodiment. Figure 13 shows the processes of server 1 and terminal 2 that instructs the creation of a unique evacuation route, and the flow of processes for both.

[0062] First, an instruction to start creating an evacuation route is sent from terminal 2 to server 1 (step S20). This instruction includes the user ID of the user using terminal 2.

[0063] Server 1 searches the user data in the user data storage unit 123 using the user ID included in the acquired instruction as a key, and determines whether the user's designated evacuation route is a unique evacuation route (step S21). If it is not a unique evacuation route (step S21: NO), a new record for the unique evacuation route is created (step S22), and the process proceeds to step S24. If it is a unique evacuation route (step S21: YES), the evacuation route information in the evacuation route storage unit 125 is read based on the evacuation route ID of the designated evacuation route (step S23), and the process proceeds to step S24.

[0064] Next, Server 1 sends a request to Terminal 2 to specify a point to be added to or modified in the unique evacuation route (Step S24). At this time, if a new unique evacuation route is to be created, Server 1 sends a disaster prevention map of the area associated with the user to Terminal 2, and if a unique evacuation route already exists, it sends the unique evacuation route and the corresponding disaster prevention map to Terminal 2. Terminal 2 displays the acquired disaster prevention map, etc., on the display unit 25 (Step S25).

[0065] Figure 14 shows an example of a screen displayed on the display unit 25 of terminal 2 during the evacuation route creation process according to the embodiment. Figure 14(a) shows an example of a screen displayed in step S25 when a unique evacuation route exists. As shown in Figure 14(a), the existing unique evacuation route 220 is displayed overlaid on the disaster prevention map 200.

[0066] Terminal 2 then displays a screen (not shown) on the display unit 25 containing a message prompting the user to input locations to be added or modified, and accepts location input at the input unit 24. As shown in Figure 14(b), for example, locations that should not be passed through on the standard evacuation route 220, i.e., locations to be deleted, can be specified with arrows 300. Although not shown, locations that should be included in the standard evacuation route 220 can also be specified with arrows 300.

[0067] Furthermore, when creating a new custom evacuation route, the system may accept the specification of multiple points to be traversed from icon 203 (home) to icon 202 (shelter). Alternatively, in step S24, server 1 may provisionally create the shortest route from home to the shelter as an evacuation route and send it to terminal 2, and terminal 2 may display the provisionally created evacuation route. The user may then modify the provisionally created evacuation route using terminal 2.

[0068] In step S26 of Figure 13, terminal 2 transmits information about the specified location to server 1. Server 1 creates an evacuation route based on the specified location (step S27). Specifically, the evacuation route creation unit 114 of server 1 creates an evacuation route that includes the locations that have been added but excludes the locations that have been deleted. The evacuation route creation unit 114 may use information about the characteristics of each location on the disaster prevention map (e.g., dangerous locations) as input, in addition to the locations specified by the user, to create the evacuation route. For example, it may create an evacuation route that does not include locations that have been designated as dangerous locations. The evacuation route creation unit 114 may also use artificial intelligence to create the evacuation route. Server 1 outputs the created evacuation route to terminal 2 (step S28), and terminal 2 displays the acquired evacuation route on the display unit 25 (step S29).

[0069] Figure 14(c) shows an example of the screen displayed on the display unit 25 in step S29. The disaster prevention map 200 has the new evacuation route 221 overlaid on it.

[0070] Thus, according to this embodiment, users can create or modify unique evacuation routes that are suited to local conditions and their own living situations. The evacuation routes created in this way are easy for users to use and can help facilitate rapid evacuation. Furthermore, the disaster prevention map provision system 1000 of this embodiment provides users with the opportunity to consider their own evacuation routes through the evacuation route creation function, which also contributes to improving users' disaster prevention awareness.

[0071] While Figures 13 and 14 illustrate the process of creating specific evacuation routes, general evacuation routes can be created in the same manner. Since general evacuation routes are intended for use by multiple people, Server 1 may perform permission authentication so that, for example, only users with administrator privileges can create or modify them.

[0072] (Certification of disaster prevention information) Figure 15 is a sequence chart showing an example of the certification process for a disaster prevention map according to the embodiment. Figure 16 is an example of the screen displayed on the display unit 25 of terminal 2 during the certification process for a disaster prevention map according to the embodiment. Here, the operation of server 1 and terminal 2 will be explained using the example of a user using terminal 2 who performs a crime prevention patrol according to a crime prevention patrol route and certifies each point.

[0073] In Figure 15, terminal 2 sends a request to server 1 to display a crime prevention patrol route (step S30). Server 1 sends crime prevention patrol route information based on the request (step S31). Alternatively, server 1 may send terminal 2 a list of selectable crime prevention patrol routes in advance, and terminal 2 may select one of them in step S30. Alternatively, the display request in step S30 may include the location information of terminal 2, and server 1 may extract a crime prevention patrol route corresponding to the disaster prevention map that includes that location information and send it in step S31.

[0074] Terminal 2 displays the acquired crime prevention patrol route (step S32). As shown in Figure 16, the crime prevention patrol route 230 is displayed overlaid on the disaster prevention map 200. In Figure 16, icon 206 is a location that includes disaster prevention information added by the user and is a certified location. For example, a disaster prevention officer conducting a crime prevention patrol or a user participating in an event such as a disaster prevention map walk will display the crime prevention patrol route 230 on the display unit 25, conduct a crime prevention patrol according to the crime prevention patrol route 230, and at the uncertified actual location indicated by icon 204, confirm the disaster prevention information (see Figure 12) and the condition of the site to confirm whether the disaster prevention information is valid.

[0075] In Figure 15, a location is selected on terminal 2 (step S33), and an authentication instruction for the selected location is sent to server 1 (step S34). The authentication instruction includes either or both information that identifies the target location and information corresponding to the ID of the correction data (see Figure 4). The location selection in step S33 can be performed by selecting icon 204 on the disaster prevention map 200 shown in Figure 16.

[0076] When Server 1 receives an authentication instruction, it updates the authentication status of the corresponding location in the correction data storage unit 122 to "accepted" (step S35). Subsequently, Server 1 performs a notification process (step S36). The notification process in step S36 is the notification process explained in Figure 11. Through this notification process, users who have an evacuation route that includes an authenticated location can understand that the location information included in their evacuation route has been updated.

[0077] While this example shows the process when certification is granted to a location where disaster prevention information is registered, the process for revoking granted certification can be performed similarly. Furthermore, Server 1 may perform user permission authentication so that only terminal 2 of users with specific privileges (see Figure 5) can perform certification and revocation. Alternatively, all users may be allowed to perform certification and revocation, thereby giving more users the opportunity to obtain certification and improving the accuracy and timeliness of certification information.

[0078] Furthermore, while the request from terminal 2 in step S30 to display the crime prevention patrol route is based on user operation, a function to prompt the user to perform such operation may be provided. For example, if predetermined conditions are met, server 1 sends information to terminal 2 prompting a crime prevention patrol, and a user who decides to conduct a crime prevention patrol based on the information displayed on terminal 2 sends a crime prevention patrol route display request from terminal 2. In this case, predetermined conditions may include, for example, the number of disaster prevention information added by the user exceeding a predetermined number, or the number of disaster prevention information added by the user but not yet certified exceeding a predetermined number. The predetermined number may be aggregated within one region or across multiple regions. Also, server 1 may send information to terminal 2 prompting a crime prevention patrol at predetermined intervals, such as once a month.

[0079] (Creating crime prevention patrol routes) Figure 17 is a flowchart showing an example of the process for creating a security patrol route on Server 1 according to the embodiment.

[0080] In Figure 17, Server 1 receives an instruction to create a crime prevention patrol route (step S40). The instruction is sent from Terminal 2 and includes the user ID of Terminal 2. Server 1 determines whether the user of Terminal 2 who issued the instruction has the necessary permissions. If the user has the necessary permissions (step S41: YES), the process proceeds to step S42; otherwise, the process terminates (step S41: NO). In this embodiment, the process proceeds to step S42 if the user has administrator privileges.

[0081] Server 1 selects locations (also referred to as location X) that meet the conditions for adding to the crime prevention patrol route from the corrected data in the corrected data storage unit 122 (step S42). Here, the additional conditions in this embodiment are a combination of the date and time when the disaster prevention information was corrected (the latest correction date and time of the corrected data) and the number of corrections. For example, locations where the latest correction date and time is more than six months ago from the present and the number of corrections is one or less are selected as locations that meet the additional conditions. Note that the additional conditions may be only one of the two: the date and time when the disaster prevention information was corrected or the number of corrections. For example, the additional condition may be that the latest correction date and time is more than six months ago from the present, or that the number of corrections is two or less. Multiple locations may be selected in step S42, and if the number of locations that meet the additional conditions exceeds a predetermined upper limit, only locations included in a specific area may be selected.

[0082] Next, Server 1 determines whether there is a crime prevention patrol route that includes a point close to point X, which was selected in step S42, by referring to the crime prevention patrol routes in the patrol data storage unit 126. Here, "close" means that the straight-line distance or road-side distance between points is within a predetermined threshold range. Server 1 searches the crime prevention patrol route information (see Figure 8) and, if there is a crime prevention patrol route that includes a point close to point X (step S43: YES), adds point X to that crime prevention patrol route (step S44). If there are multiple crime prevention patrol routes in step S43, point X may be added to all of the crime prevention patrol routes, or it may be added to any one of the crime prevention patrol routes.

[0083] Figure 18 shows an example of the display of the crime prevention patrol route before and after modification according to the embodiment. In Figure 18(a), the crime prevention patrol route 230, shown as a dashed line, is superimposed on the disaster prevention map 200. Icon 204a indicates point X that satisfies the additional conditions. Point X is displayed in a way that distinguishes it from other points by icon 204a, which is a different form from the icons 204 that indicate other points. When point X is added to the crime prevention patrol route in step S44, the crime prevention patrol route 231 is modified to pass through point X, indicated by icon 204a, as shown in Figure 18(b).

[0084] Furthermore, if there is no crime prevention patrol route that includes a point close to point X (step S43: NO), server 1 creates a crime prevention patrol route by combining point X that satisfies the additional conditions with other points (step S45). The points that can be combined with point X here can be points included in at least one of the correction request data in the correction request data storage unit 121 and the correction data in the correction data storage unit 122. Specifically, points that were not corrected in the correction request data can be incorporated into the crime prevention patrol route. This makes it possible to incorporate points that users were concerned about but which were not previously registered as disaster prevention information into the crime prevention patrol route, which can, for example, lead to prior confirmation of dangerous areas.

[0085] After step S44 or step S45, server 1 performs a notification process for each user (step S46). The process in step S46 is the same process shown in step S12 in Figure 11.

[0086] (Verification of disaster prevention map) Figure 19 is a sequence chart showing an example of the verification process for a disaster prevention map according to the embodiment. Server 1 determines whether the current time is a predetermined verification timing. If it is a verification timing (step S50: YES), it proceeds to step S51. If it is not a verification timing (step S50: NO), it repeats step S50. Verification timings include, for example, when an instruction is received from terminal 2, at predetermined intervals, or when predetermined conditions are met. In this case, predetermined conditions include, for example, when the number of locations with registered disaster prevention information per unit area of ​​the map reaches the upper limit.

[0087] Server 1 performs verification processing of the disaster prevention map (step S51). The verification processing by the verification unit 116 is as described above. Here, the verification condition is explained as the maximum number of locations with registered disaster prevention information per unit area of ​​the map. If the number of locations with registered disaster prevention information per unit area does not exceed the maximum number, Server 1 determines that the verification condition is met (step S52: YES) and terminates the verification process. If the number of locations with registered disaster prevention information per unit area exceeds the maximum number, Server 1 determines that the verification condition is not met (step S52: NO) and notifies Terminal 2 of the verification result (step S53). The information sent to Terminal 2 as a verification result is information on the disaster prevention map that does not meet the verification condition and information on the locations included in the disaster prevention map.

[0088] Terminal 2 displays the verification results on the display unit 25 based on the information from server 1 (step S54). Figure 20 is an example of the verification results screen displayed on the display unit 25 of terminal 2 according to the embodiment. In the example in Figure 20, icons 204 indicating locations where disaster prevention information has been registered are displayed on the disaster prevention map 200, and an impact level 207 is displayed near the icon 204. The impact level 207 is a value included in the correction data of the correction data storage unit 122. Furthermore, a message 240 prompting the user to select a location to delete is overlaid on the disaster prevention map 200. Here, locations with an impact level of (1) are designated as candidates for deletion, and the user is asked to select one of them.

[0089] When a user selects one of the icons 204 with an impact level of (1) as shown in Figure 20 on terminal 2, a deletion instruction for the location corresponding to the selected icon 204 is sent from terminal 2 to server 1 (step S55). Upon receiving the deletion instruction, server 1 deletes the disaster prevention information for the location targeted by the deletion instruction (step S56). Alternatively, in step S55, the contents of the correction request data stored in the correction request data storage unit 121 or the correction data stored in the correction data storage unit 122 corresponding to the selected icon 204 may be displayed on terminal 2, and the deletion instruction may be sent from terminal 2 to server 1 when the user confirms the contents and performs the deletion operation.

[0090] This allows for the removal of disaster prevention information included in disaster prevention maps that do not meet the verification criteria. If there is too much disaster prevention information registered per unit area of ​​the map, it can be removed, reducing the amount of information on the disaster prevention map and improving its visibility.

[0091] The verification conditions may include, for example, conditions related to the last update date or number of updates of the disaster prevention map. For example, if the last update date of one or more disaster prevention information items included in the disaster prevention map is more than a predetermined period ago from the present time, it will be determined that the verification conditions are not met, and the items with the oldest last update dates will be shown to the user as candidates for deletion. Also, if the number of updates of one or more disaster prevention information items included in the disaster prevention map is one or less, it will be determined that the verification conditions are not met, and the items with one or fewer updates will be shown to the user as candidates for deletion. Furthermore, the number of times the user views the disaster prevention map may be counted on server 1, and those with a view count below a threshold may be determined not to meet the verification conditions. In addition, if none of the disaster prevention information items included in the disaster prevention map are certified, it will be determined that the verification conditions are not met, and the user may be asked whether to authenticate or delete the unnecessary disaster prevention information.

[0092] (modified version) Server 1 may include an input unit such as a keyboard and a display unit such as a screen. In this case, input from terminal 2 and display by terminal 2 are similarly realized by the input unit and display unit of server 1. [Explanation of Symbols]

[0093] 1 Server, 2 Terminal, 3 Network, 11 Control Unit, 12 Storage Unit, 13 Communication Unit, 21 Control Unit, 22 Storage Unit, 23 Communication Unit, 24 Input Unit, 25 Display Unit, 110 Request Acquisition Unit, 111 Map Modification Unit, 112 Additional Modification Inquiry Unit, 113 Certification Unit, 114 Evacuation Route Creation Unit, 115 Patrol Route Creation Unit, 116 Verification Unit, 117 Notification Unit, 118 Output Unit, 119 Management Unit, 120 Disaster Prevention Map Storage Unit, 121 Modification Request Data Storage Unit, 122 Modification Data Storage Unit, 123 User Data Storage Unit, 124 Regional Data Storage Unit, 125 Evacuation Route Storage Unit, 126 Patrol Data Storage Unit, 127 Bulletin Board Information Storage Unit, 200 Disaster Prevention Map, 201 Map, 202 Icon, 203 Icon, 204 Icon, 204a Icon, 205 Icon, 206 Icon, 207 Impact level, 210 Disaster prevention information section, 211 Text information, 212 Image, 220 Unique evacuation route, 221 Evacuation route, 230 Crime prevention patrol route, 231 Crime prevention patrol route, 240 Message, 300 Arrow, 400 Information input screen, 401 Input field, 402 Input field, 403 Input field, 404 Input information submission button, 410 Confirmation screen, 411 Confirmation display field, 412 Button, 413 Button, 1000 Disaster prevention map provision system.

Claims

1. A request acquisition unit that acquires a modification request, which is a request from a user regarding the addition or modification of disaster prevention information in a disaster prevention map that includes maps and disaster prevention information, A map modification unit modifies the disaster prevention information in the disaster prevention map based on the modification request acquired by the request acquisition unit, The system includes a display unit that displays the disaster prevention map, which includes the corrected disaster prevention information. Disaster prevention map provision system.

2. A correction request data storage unit stores location information indicating a location included in the correction request, disaster prevention information including either text and / or images, and the date and time of the correction request as a history of the correction request. When the request acquisition unit acquires the modification request, the additional modification inquiry unit extracts location information from the location information stored in the modification request data storage unit that is different from the location information included in the modification request acquired by the request acquisition unit, and outputs information to the user inquiring whether or not the disaster prevention information needs to be modified at the location indicated by the extracted location information. The disaster prevention map provision system according to claim 1.

3. The aforementioned additional modification inquiry unit, when extracting the location, The request acquisition unit extracts locations within a predetermined range from the locations identified by the location information included in the modification request acquired by the request acquisition unit. The request acquisition unit extracts locations that are within a predetermined range from the location identified by the location information included in the correction request acquired by the request acquisition unit, and whose date and time of the correction request stored in the correction request data storage unit falls within a predetermined period, or The request acquisition unit extracts locations that are within a predetermined range from the location identified by the location information included in the correction request acquired by the request acquisition unit, and where the disaster prevention information stored in the correction request data storage unit does not include the image. The disaster prevention map provision system according to claim 2.

4. A correction data storage unit stores correction location information indicating the locations corrected by the map correction unit, and certification information indicating whether or not certification has been granted, in association with each other. The system includes an authentication unit that obtains authentication for the correction location information of the correction data storage unit and updates the authentication information of the correction data storage unit. A disaster prevention map provision system according to any one of claims 1 to 3.

5. An evacuation route creation unit that obtains evacuation route creation requests from users regarding the addition or modification of evacuation routes for each user, and creates the evacuation routes based on the obtained evacuation route creation requests, A user data storage unit that stores information identifying the user and the evacuation route in association, The system includes a control unit that overlays the evacuation routes for each user onto the disaster prevention map based on the user data storage unit. A disaster prevention map provision system according to any one of claims 1 to 3.

6. The system includes a notification unit that sends a notification to the user's terminal associated with an evacuation route if a location included in the disaster prevention information corrected by the map correction unit is included in the evacuation route stored in the user data storage unit. The disaster prevention map provision system according to claim 5.

7. The user data storage unit stores information identifying the user, the evacuation route, and the time period during which the user can be contacted, in association with each other. The notification unit sends the notification to each user during their contactable time slot, based on the information stored in the user data storage unit. The disaster prevention map provision system according to claim 6.

8. A correction data storage unit stores correction location information indicating the locations corrected by the map correction unit, and either the date and time of the correction or the number of corrections, or both, in association with each other. The system includes a patrol route creation unit that selects one or more locations stored in the modified data storage unit based on either or both of the modified date and time and the number of times, and creates a crime prevention patrol route that includes the selected one or more locations. A disaster prevention map provision system according to any one of claims 1 to 3.

9. The system includes a display control unit that overlays the aforementioned crime prevention patrol route onto the disaster prevention map and displays one or more of the aforementioned locations in a manner different from other locations. The disaster prevention map provision system according to claim 8.

10. A correction data storage unit stores correction location information indicating the locations corrected by the map correction unit, and the degree of impact on the user, in association with each other. The system includes a verification unit that verifies the disaster prevention map based on the information stored in the modified data storage unit and the verification conditions, The verification conditions include an upper limit on the number of corrected point information items having an influence level below a threshold, per unit area in the map. A disaster prevention map provision system according to any one of claims 1 to 3.

11. The verification unit includes a notification unit that notifies the user's terminal of the verification result if the verification unit determines that the disaster prevention map does not meet the verification conditions. The map modification unit deletes the disaster prevention information corresponding to the modification location information that is determined not to satisfy the verification conditions, based on the deletion instruction output from the user's terminal in response to the notification from the notification unit, from the disaster prevention map. The disaster prevention map provision system according to claim 10.

12. A request acquisition unit that acquires a modification request, which is a request from a user regarding the addition or modification of disaster prevention information in a disaster prevention map that includes maps and disaster prevention information, The system includes a map modification unit that modifies the disaster prevention information in the disaster prevention map based on the modification request acquired by the request acquisition unit. Disaster prevention map creation device.

Images