River information management system, river information system, and river information management control method

Abstract

To provide a river information management system capable of improving efficiency of transmission of flood-protecting warnings.SOLUTION: According to an embodiment, a river information management system includes a telemeter monitoring device, a meteorological observatory system, a communication server, an outward provision server, and an inward provision server. The communication server transmits information related to flood protection to the outward provision server and the inward provision server on the basis of at least one of river data and meteorological data. The outward provision server transmits the information via the Internet to terminals connected to the outward provision server, receives, from the terminals, receipt confirmation data indicating that the information has been confirmed by users who use respectively the terminals, and transmits the receipt confirmation data to the inward provision server when transmission of the receipt confirmation data is requested by the inward provision server.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a river information management system, a river information system, and a river information management control method. [Background technology]

[0002] A river information system operated by a local government is used to notify officials and local stakeholders of increased risk of river flooding due to rising water levels. The local government may be, for example, a prefecture. Stakeholders may be, for example, city and town officials, fire department officials, and local flood prevention workers.

[0003] Specifically, the river information system collects observation data from external devices and systems, including, for example, the water level of the river and meteorological information.

[0004] Municipal officials determine the risk of river flooding based on the collected observation data and a pre-defined manual (flood prevention plan). Based on the results of their determination, the officials manually create a notice regarding the risk of river flooding. This notice is also called a flood prevention warning. The officials notify relevant local people of the flood prevention warning, for example, by facsimile (FAX). The officials also confirm, for example, by telephone, that relevant local people have received the flood prevention warning. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2001-250779 [Patent Document 2] Japanese Patent Application Laid-Open No. 2002-269656 [Patent Document 3] Japanese Patent Publication No. 2020-127125 [Patent Document 4] Japanese Patent Publication No. 2022-59747 Summary of the Invention [Problem to be solved by the invention]

[0006] This method of issuing flood warnings and then confirming receipt requires a lot of work for local government officials, making it difficult to respond quickly to situations in rivers that are at risk of flooding. It also raises the possibility of errors, such as missed notifications.

[0007] Therefore, the problem to be solved by the present invention is to provide a river information management system, a river information system, and a river information management control method that can efficiently transmit flood prevention warnings. [Means for solving the problem]

[0008] According to an embodiment, a river information management system includes a telemeter monitoring device, a weather station system, a communication server, an external provision server, and an internal provision server. The telemeter monitoring device transmits river data indicating the water level of a river to the communication server. The weather station system transmits weather data related to at least one of a weather advisory and a weather warning to the communication server. The communication server transmits information related to flood prevention to the external provision server and the internal provision server based on at least one of the river data and the weather data. The external provision server transmits the information to a terminal connected to the external provision server via the Internet. The external provision server receives receipt confirmation data from the terminal indicating that the information has been confirmed by a user using the terminal. When the internal provision server requests transmission of the receipt confirmation data, the external provision server transmits the receipt confirmation data to the internal provision server. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram showing the configuration of a river information management system including a river information system according to a comparative example. [Figure 2] FIG. 2 is a diagram showing an example of a notification destination of a flood warning in the river information system according to the embodiment. [Figure 3] FIG. 10 is a diagram showing an example of a notification message related to a flood warning created in a river information system according to a comparative example. [Figure 4] 1 is a block diagram showing an example of the basic configuration of a river information management system including a river information system according to an embodiment. [Figure 5] FIG. 2 is a diagram showing an example of the functional configuration of a communication server, an internal provision server, and an external provision server in the river information system according to the embodiment. [Figure 6] FIG. 2 is a diagram showing an example of the hardware configuration of a communication server in the river information system according to the embodiment. [Figure 7] FIG. 1 is a block diagram showing in more detail an example of the configuration of a river information management system including a river information system according to an embodiment. [Figure 8] FIG. 2 is a diagram showing an example of the functional configuration of an automatic notification unit included in the river information system according to the embodiment. [Figure 9] 1 is a diagram showing an example of the configuration of a network to which a river information system according to an embodiment is connected; [Figure 10] FIG. 10 is a diagram showing an example of the functional configuration of an automatic notification unit applied to a communication server, an internal provision server, and an external provision server in the river information system according to the embodiment. [Figure 11] FIG. 2 is a diagram showing an example of a reference value table used in the river information system according to the embodiment. [Figure 12] FIG. 4 is a diagram showing an example of a notification message used in a notification message generation unit of the river information system according to the embodiment. [Figure 13] FIG. 2 is a diagram showing an example of a notification destination list table used in the river information system according to the embodiment. [Figure 14] 10 is a flowchart showing an example of the procedure of a notification control process executed in a communication server in the river information system according to the embodiment. [Figure 15] 1 is a diagram showing a first example of a flood warning notified based on a time series of water levels and whether or not a heavy rain warning has been issued in the river information system according to the embodiment; [Figure 16]FIG. 10 is a diagram showing a second example of a flood warning that is notified based on the time series of water levels and whether or not a heavy rain warning has been issued in the river information system according to the embodiment. [Figure 17] FIG. 10 is a diagram showing a third example of a flood warning notified based on the time series of water levels and whether or not a heavy rain warning has been issued in the river information system according to the embodiment. [Figure 18] FIG. 10 is a diagram showing a fourth example of a flood warning notified based on the time series of water levels and whether or not a heavy rain warning has been issued in the river information system according to the embodiment. [Figure 19] FIG. 10 is a diagram showing a fifth example of a flood warning notified based on the time series of water levels and whether or not a heavy rain warning has been issued in the river information system according to the embodiment. [Figure 20] FIG. 10 is a diagram showing an example of an alert screen provided in the river information system according to the embodiment. [Figure 21] 1 is a diagram showing an example of a notification message list screen and a notification content screen provided in the river information system according to an embodiment; [Figure 22] FIG. 10 is a diagram showing an example of a receipt confirmation screen provided in the river information system according to the embodiment. [Figure 23] 10 is a diagram showing an example in which a receipt confirmation cannot be sent from an external provision server to an internal provision server in the river information system according to the embodiment. FIG. [Figure 24] FIG. 10 is a diagram showing an example of a receipt confirmation operation in the river information system according to the embodiment. [Figure 25] 10 is a flowchart showing an example of the procedure of a receipt confirmation process executed by an internal provision server in the river information system according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, each embodiment will be described with reference to the drawings. It should be noted that the disclosure is merely an example, and the invention is not limited to the contents described in the following embodiments. Modifications that a person skilled in the art can easily make are naturally included in the scope of the disclosure. For clearer explanation, the size, shape, etc. of each part may be changed from the actual embodiment and shown schematically in the drawings. Corresponding elements in multiple drawings may be given the same reference numerals, and detailed descriptions may be omitted.

[0011] First, a river information system according to a comparative example will be described. Fig. 1 is a block diagram showing the configuration of a river information management system 100 including a river information system 21 according to a comparative example.

[0012] The river information management system 100 of the comparative example includes a telemeter monitoring device 10, a Ministry of Land, Infrastructure, Transport and Tourism system 11, a Japan Meteorological Agency system 12, and a local government system 20. The local government is, for example, an administrative agency that has jurisdiction over a prefecture. In the following explanation, the case where the local government is a prefecture (prefectural office) will be exemplified.

[0013] The telemetry monitoring device 10 generates observation data on the condition of a river managed by a local government by monitoring (observing) the river. The observation data includes the water level and flow rate of the river. The telemetry monitoring device 10 transmits the collected observation data to the local government system 20 via the Internet, a dedicated line, or the like.

[0014] The MLIT system 11 collects observation data on rivers managed by the national government and rainfall data for each region. The MLIT system 11 transmits the collected observation data and rainfall data to the local government system 20 of each local government via the Internet or a dedicated line. Hereinafter, the observation data related to rivers collected by the telemetry monitoring device 10 and the MLIT system 11 will be referred to as "river data."

[0015] The Meteorological Agency system 12 manages weather station systems 22a installed in each region. The weather station systems 22a generate meteorological data related to weather. The meteorological data includes weather advisories, weather warnings, and AMeDAS (Automated Meteorological Data Acquisition System) rainfall. The weather advisories include heavy rain advisories. The weather warnings include heavy rain warnings. The Meteorological Agency system 12 transmits the collected meteorological data to each local government, including the local government system 20, via the Internet or a dedicated line, etc.

[0016] The local government system 20 is a system that collects and manages various data related to the local government. The local government system 20 is operated (used) by a local government employee U1. The local government system 20 includes a river information system 21 and a local government employee terminal 22.

[0017] The river information system 21 is a system that collects and manages river data and meteorological data. The river information system 21 transmits (notifies) information about flood prevention to local government officials U1 and related organizations 30 based on at least one of the river data and meteorological data.

[0018] "Flood prevention information" is information indicating the issuance of one of several levels of flood prevention warnings or the lifting of a flood prevention warning. Flood prevention warnings include, for example, information on rivers at increased risk of flooding, river water levels, and instructions on flood prevention measures by each agency. Flood prevention warnings are issued in stages according to the flood risk level when the risk of river flooding increases due to rainfall, etc. Flood prevention warnings are also lifted when the risk of flooding has sufficiently decreased. In the following explanation, notifying a flood prevention warning includes both sending information indicating the issuance of one of several levels of flood prevention warnings and sending information indicating the lifting of a flood prevention warning.

[0019] The local government employee terminal 22 is a terminal used by the local government employee U1. The local government employee terminal 22 is realized as, for example, a personal computer, a tablet terminal, a smartphone, or a mobile phone. The local government employee terminal 22 has a display unit (display).

[0020] The related organizations 30 are, for example, municipalities, fire departments, and flood prevention corps. Persons engaged in the work of the related organizations 30 are referred to as related parties U2. Based on the flood prevention warning, local government officials U1 and related parties U2 carry out flood prevention activities such as calling for evacuation to residents living in areas surrounding rivers.

[0021] Here, the internal configuration of the river information system 21 will be described. The river information system 21 has a data collection / distribution unit 21a and a screen providing unit 21b. The data collection / distribution unit 21a collects (receives) river data transmitted from each of the telemeter monitoring device 10 and the Ministry of Land, Infrastructure, Transport and Tourism system 11. The data collection / distribution unit 21a collects meteorological data transmitted from the Japan Meteorological Agency system 12.

[0022] The data collection / distribution unit 21a may collect river data and weather data from a system other than the system shown in Fig. 1 that is managed by a local government. The other system may be, for example, a dam management system. Data collected from the dam management system may include, for example, the amount of water stored in the dam and the amount of water discharged.

[0023] The data collection / distribution unit 21a also exchanges the collected river data and weather data with the telemeter monitoring device 10, the Ministry of Land, Infrastructure, Transport and Tourism system 11, the Japan Meteorological Agency system 12, and other systems. For example, the data collection / distribution unit 21a distributes the river data received from the telemeter monitoring device 10 to the Ministry of Land, Infrastructure, Transport and Tourism system 11 and the Japan Meteorological Agency system 12. The data collection / distribution unit 21a also distributes the river data received from the Ministry of Land, Infrastructure, Transport and Tourism system 11 and the weather data received from the Japan Meteorological Agency system 12 to the telemeter monitoring device 10.

[0024] In addition, the data collection / distribution unit 21a sends the collected river data and meteorological data to the screen providing unit 21b.

[0025] The screen providing unit 21b provides a confirmation screen for river data and weather data to the local government employee terminal 22. Specifically, when a request to display a confirmation screen is received from the local government employee terminal 22, the screen providing unit 21b provides the local government employee terminal 22 with the river data and weather data necessary to display the confirmation screen on the local government employee terminal 22.

[0026] In response to a predetermined operation by local government employee U1, local government employee terminal 22 requests screen provider 21b to display a confirmation screen. In response to the display request, local government employee terminal 22 receives the necessary river data and weather data from screen provider 21b, and displays a confirmation screen for the river data and weather data on the display unit.

[0027] Here, a procedure for issuing a flood warning or notifying the cancellation of a flood warning using the river information system 21 of the comparative example will be described. When a situation arises where a river may flood due to rainfall or the like, local government employee U1 checks river data and weather data by operating local government employee terminal 22. Based on the river data, weather data, and a predetermined manual (flood prevention plan), local government employee U1 determines the risk of river flooding and whether to issue a flood prevention warning.

[0028] If it is decided to issue a flood warning, the local government employee U1 manually creates a notice 24 regarding the flood warning using the local government employee terminal 22 and prints out the created notice 24 on paper. The flood warning notice 24 is also referred to as "flood warning announcement information." The format used to create the notice 24 is also referred to as "announcement format."

[0029] The local government employee U1 notifies the relevant local organizations 30 that should be notified of the flood warning of the issuance or cancellation of the flood warning by sending the created notification 24, for example by fax, to the relevant local organizations 30. After sending the fax, the local government employee U1 calls the relevant organizations 30 and confirms whether the relevant organizations 30's concerned U2 have received the notification. In the following explanation, notifying the flood warning and confirming whether the notification has been received will be referred to as "transmitting the flood warning."

[0030] As described above, in the comparative example, the local government employee U1 determines the risk of flooding. Based on the results of the risk determination, the local government employee U1 must also create a notification, notify the notification, and confirm receipt.

[0031] FIG. 2 is a diagram showing an example of the destinations to which a flood warning is notified. The prefectural government of A prefecture is a local government that operates the river information system 21 shown in Figure 1. The prefectural government of A prefecture manages multiple civil engineering offices (○○ civil engineering office, ◇◇ civil engineering office, ...△△ civil engineering office). The civil engineering offices are established in each region of A prefecture as branch offices of A prefecture. Each civil engineering office manages telemetry control devices (e.g., telemetry monitoring devices 10) installed on rivers, roads, waterways, etc. The prefectural government of A prefecture also distributes river data for each river collected by the river information system 21 to the terminals of employees of the prefectural government of A prefecture and the terminals of employees of multiple civil engineering offices.

[0032] Here, the flood warning must be notified to each city, town, and village in Prefecture A (General Affairs Division of City A, General Affairs Division of City B, Crisis Management Division of City B, ..., General Affairs Division of Town D) and the meteorological observatory. Upon receiving the notification, each city, town, and village and meteorological observatory will notify the flood warning to flood prevention workers and local residents in the area.

[0033] As mentioned above, flood warnings must be sent to many organizations related to the local government. Therefore, the comparative example of sending notifications by fax or confirming receipt by telephone requires a lot of man-hours.

[0034] FIG. 3 is a diagram showing an example of a notification message 24 related to a flood warning created in a river information system 21 according to a comparative example. For example, a flood warning indicates one of several types of information notifying the issuance or cancellation of a flood warning. Information indicating the issuance of a flood warning is one of three levels of information: "standby," which requests a flood defense unit to be on standby so that it can be mobilized; "preparation," which requests a flood defense unit to prepare for deployment; and "dispatch," which requests a flood defense unit to be mobilized. Information indicating the cancellation of a flood warning is "cancellation," which cancels a flood warning that has already been issued. Note that the multiple types of information that can be indicated as a flood warning are not limited to "standby," "preparation," "dispatch," and "cancellation," but can be set arbitrarily depending on the topography of the river and the surrounding environment.

[0035] The local government employee U1 determines the level of the flood warning based on the current water level of the river. Then, the local government employee U1 creates a notice 24 for the determined flood warning level, including the date and time, water level, and the target river.

[0036] Furthermore, local government employee U1 enters the information confirmed during the transmission of notice 24 into the "Transmission Record Table" provided in notice 24. The "Delivery Destination" field of the transmission record table lists the predetermined destination. When sending notice 24 to the destination by fax, local government employee U1 enters the date and time of transmission and the name of the sender (here, local government employee U1) in the "Transmission" field. Furthermore, when local government employee U1 confirms by phone that related party U2 has received notice 24, he or she enters the date and time of receipt and the name of the recipient (related party U2) in the "Receipt" field.

[0037] As mentioned above, if the notification 24 is created manually, there are many fields that the local government employee U1 must fill in, making it difficult to respond quickly. In addition, there is a possibility of mistakes such as omissions.

[0038] Therefore, one of the objectives of the river information system according to the embodiment is to efficiently notify and confirm receipt of information related to flood prevention.

[0039] Next, a river information system according to an embodiment will be described. 4 is a block diagram showing an example of the basic configuration of a river information management system 200 including a river information system 41 according to an embodiment. The river information management system 200 is a system that discloses information about rivers managed by the national or local government to prefectural residents. Specifically, the river information management system 200 provides information about rivers to terminals 50 used by prefectural residents (hereinafter referred to as prefectural residents terminals 50) via the Internet 1.

[0040] The river information management system 200 includes, for example, a telemeter monitoring device 13, a Ministry of Land, Infrastructure, Transport and Tourism system 14, a Japan Meteorological Agency system 15, and a local government system 40. The telemeter monitoring device 13, the Ministry of Land, Infrastructure, Transport and Tourism system 14, and the Japan Meteorological Agency system 15 each have the same configurations and functions as, for example, the telemeter monitoring device 10, the Ministry of Land, Infrastructure, Transport and Tourism system 11, and the Japan Meteorological Agency system 12 in the river information management system 100 of the comparative example.

[0041] The telemeter monitoring device 13 transmits the generated river data to a communication server 42 via the Internet or a dedicated line, etc. The Ministry of Land, Infrastructure, Transport and Tourism system 14 transmits collected river data and rainfall data managed by the government to the communication server 42. The Japan Meteorological Agency system 15 transmits weather data released by weather station systems 15a installed in various locations to the communication server 42 via the Internet or a dedicated line, etc.

[0042] The local government system 40 is a system for collecting and managing various data related to the local government. The systems operated in the local government system 40 include a river information system 41 and a local government employee terminal 45. The local government employee terminal 45 is a terminal used by employees of the local government.

[0043] The river information system 41 includes a communication server 42, an internal provision server 43, and an external provision server 44.

[0044] The communication server 42 is a server device that can communicate with the telemetry monitoring device 13, the Ministry of Land, Infrastructure, Transport and Tourism system 14, and the Japan Meteorological Agency system 15, and can also communicate with the internal provision server 43 and the external provision server 44 within the river information system 41.

[0045] The communication server 42 collects river data from each of the telemeter monitoring device 13 and the Ministry of Land, Infrastructure, Transport and Tourism system 14. The communication server 42 collects weather data from the Japan Meteorological Agency system 15. The communication server 42 provides (transmits) the collected river data and weather data to an internal provision server 43 and an external provision server 44.

[0046] The internal provision server 43 is a server device that provides the river data and weather data received from the communication server 42 to the local government employee terminal 45. The internal provision server 43 can be connected to the local government employee terminal 45 via, for example, a local network.

[0047] The internal provision server 43 also accepts input of correction data and update data from the local government employee terminal 45. Correction data is data indicating the correct value input to the local government employee terminal 45 in response to an operation by the local government employee U3 when an incorrect value is found in the river data, for example. Update data is data indicating new information notified to prefectural residents by an employee, for example. The internal provision server 43 displays information based on the update data as a "notice" on a web page made public to prefectural residents.

[0048] When the internal provision server 43 receives input of at least one of correction data and update data from the local government employee terminal 45, it transmits the correction data and / or update data to the communication server 42 and the external provision server 44. Based on the transmitted correction data and update data, the communication server 42 changes the stored data. Based on the transmitted correction data and update data, the external provision server 44 changes the web page within the external provision server 44.

[0049] The external provision server 44 is a server device that functions as a web server. The external provision server 44 stores data for providing web pages. The external provision server 44 accepts access requests to web pages in response to operations by resident users using a web browser running on the resident terminal 50. In response to this access request, the external provision server 44 transmits the data required to display the web page to the resident terminal 50. By displaying the web page on the screen of the resident terminal 50, the resident can refer to (check) river data and weather data.

[0050] FIG. 5 is a diagram showing an example of the functional configuration of a communication server 42, an internal provision server 43, and an external provision server 44 in a river information system 41 according to the embodiment.

[0051] The communication server 42 includes a data collection / distribution unit 42a, a data storage unit 42b, and a data calculation unit 42c.

[0052] The data collection / distribution unit 42a collects river data transmitted from the telemeter monitoring device 13 and the Ministry of Land, Infrastructure, Transport and Tourism system 14. The data collection / distribution unit 42a collects weather data from the Japan Meteorological Agency system 15. The data collection / distribution unit 42a also distributes the collected river data and weather data to the Ministry of Land, Infrastructure, Transport and Tourism system 14, the Japan Meteorological Agency system 15, the internal provision server 43, and the external provision server 44.

[0053] The data storage unit 42b stores the collected river data and meteorological data, and the river data and meteorological data processed by the data calculation unit 42c, in an arbitrary storage area (memory) within the communication server 42.

[0054] The data calculation unit 42c performs calculation processing on the collected river data and meteorological data. The calculation processing includes, for example, analysis and aggregation. The river data and meteorological data processed by the data calculation unit 42c may be distributed from the data collection / distribution unit 42a to the Ministry of Land, Infrastructure, Transport and Tourism system 14, the Japan Meteorological Agency system 15, the internal provision server 43, and the external provision server 44.

[0055] The internal provision server 43 includes a data collection / distribution unit 43a, a data storage unit 43b, and a screen provision unit 43c.

[0056] The data collection / distribution unit 43a collects (receives) river data and weather data transmitted from the communication server 42. The data collection / distribution unit 43a distributes the collected river data and weather data to the local government employee terminal 45. In addition, the data collection / distribution unit 43a distributes correction data and update data input from the local government employee terminal 45 to the communication server 42 and the external provision server 44.

[0057] The data storage unit 43b stores the collected river data, meteorological data, data input from the local government employee terminal 45, and the like in an arbitrary storage area within the internal provision server 43.

[0058] The screen providing unit 43c provides a confirmation screen for river data and weather data to the local government employee terminal 45. Specifically, when a request to display a confirmation screen is received from the local government employee terminal 45, the screen providing unit 43c provides the local government employee terminal 45 with the river data and weather data necessary to display the confirmation screen on the local government employee terminal 45.

[0059] The screen providing unit 43c provides an input screen for correction data and update data to the local government employee terminal 45. Specifically, when a request to display an input screen is received from the local government employee terminal 45, the screen providing unit 43c provides data necessary for displaying the input screen on the local government employee terminal 45. The screen providing unit 43c also receives at least one of the correction data and update data entered from the input screen of the local government employee terminal 45, and transmits it to the communication server 42 and the external provision server 44.

[0060] The external provision server 44 includes a data collection unit 44a, a data storage unit 44b, and a screen provision unit 44c.

[0061] The data collection unit 44 a collects river data and meteorological data transmitted from the communication server 42 .

[0062] The data storage unit 44b stores the collected river data and meteorological data in an arbitrary storage area within the external provision server 44.

[0063] The screen providing unit 44c generates a web page for displaying the collected river data and weather data. In response to an access request to the generated web page, the screen providing unit 44c provides (transmits) the data of the web page to the terminal that originated the access request (e.g., the resident terminal 50).

[0064] 6 is a diagram illustrating an example of the hardware configuration of a communication server 42 in a river information system 41 according to an embodiment. The communication server 42 includes, for example, a CPU (Central Processing Unit) 2, a storage 3, a RAM (Random Access Memory) 4, and a communication device 5.

[0065] The CPU 2 is at least one processor that executes various programs loaded from the storage 3 into the RAM 4.

[0066] The storage 3 is an auxiliary storage device. The storage 3 is realized as a storage device equipped with a nonvolatile storage medium, such as a hard disk drive (HDD) or a solid state drive (SSD). The storage area of ​​the storage 3 is allocated as a storage area for data saved by the data saving unit 42b, for example.

[0067] The RAM 4 is a storage medium used as a main storage device. The storage area of ​​the RAM 4 can be used as a temporary storage area for at least one of the data collected or distributed by the data collection / distribution unit 42a, the data stored by the data storage unit 42b, and the data used in calculations by the data calculation unit 42c.

[0068] The communication device 5 includes, for example, a transmitter that transmits data (signals) to the outside and a receiver that receives data from the outside. Specifically, the transmitter can transmit data to each of the telemeter monitoring device 13, the Ministry of Land, Infrastructure, Transport and Tourism system 14, the Japan Meteorological Agency system 15, the internal provision server 43, and the external provision server 44. The receiver can receive data from each of the telemeter monitoring device 13, the Ministry of Land, Infrastructure, Transport and Tourism system 14, the Japan Meteorological Agency system 15, the internal provision server 43, and the external provision server 44.

[0069] The functions of the data collection / distribution unit 42a, data storage unit 42b, and data calculation unit 42c are realized, for example, by the CPU 2 executing a predetermined program (software). This program may be stored in a computer-readable storage medium and distributed, or may be downloaded to the communication server 42 via a network. Note that some or all of the functions of the data collection / distribution unit 42a, data storage unit 42b, and data calculation unit 42c may be realized by dedicated hardware or the like, or by a combination of software and hardware.

[0070] The internal provision server 43 has a hardware configuration including a CPU, storage, RAM, and communication devices, similar to the communication server 42. The functions of the data collection / distribution unit 43a, data storage unit 43b, and screen provision unit 43c of the internal provision server 43 are realized, for example, by a CPU executing a predetermined program.

[0071] The external provision server 44 has a hardware configuration including a CPU, storage, RAM, and communication devices, similar to the communication server 42. The functions of the data collection unit 44a, data storage unit 44b, and screen provision unit 44c of the external provision server 44 are realized, for example, by a CPU executing a predetermined program.

[0072] With the above-described configuration, the river information system 41 can provide collected information to prefectural residents via the Internet 1. In addition to the basic configuration described above with reference to Figures 5 and 6, the river information system 41 of this embodiment further includes a configuration for streamlining the transmission of flood warnings. The configuration for streamlining the transmission of flood warnings includes, for example, a configuration for automating the notification and receipt confirmation of flood warnings.

[0073] 7 is a block diagram showing in more detail an example configuration of a river information management system 200 including a river information system 41 according to an embodiment. Detailed description of parts that are the same as the basic configuration described using FIG. 5 will be omitted.

[0074] The river information system 41 includes a data collection / distribution unit 41a, a screen providing unit 41b, and an automatic notification unit 41c.

[0075] Similar to the data collection / distribution unit 21a in the comparative example, the data collection / distribution unit 41a collects river data from the telemeter monitoring device 13 and the Ministry of Land, Infrastructure, Transport and Tourism system 14. The data collection / distribution unit 41a collects meteorological data from the Japan Meteorological Agency system 15.

[0076] The screen providing unit 41b provides the local government employee terminal 45 with a confirmation screen for river data and weather data, similar to the screen providing unit 21b in the comparative example.

[0077] The automatic notification unit 41c notifies the local government employee terminal 45 and the related party terminal 61 of the related organization 60 of a flood warning based on at least one of the river data and the meteorological data.

[0078] The automatic notification unit 41c also checks whether the notification of the flood warning has been received by each of the local government employee U3 and the concerned person U4.

[0079] The municipal system 40 further includes a warning light 46. The warning light 46 is controlled to be lit while a flood warning is issued. The warning light 46 is also controlled to be turned off when the flood warning is lifted. Specifically, the turning on and off of the warning light 46 is controlled by the municipal employee terminal 45 in response to notification of the flood warning. The municipal employee U3 can confirm the announcement of the flood warning by the notification on the municipal employee terminal 45 and the lighting of the warning light 46.

[0080] As described above, the river information management system 200 notifies not only local government officials U3 and prefectural residents but also relevant parties U4 of related organizations 60 of the announcement of a flood warning.

[0081] The relevant organization 60 is provided with a related party terminal 61 and a warning light 62. The warning light 62 is controlled to be on while a flood warning is issued. The warning light 62 is also controlled to be off when the flood warning is lifted. Specifically, the warning light 62 is turned on and off under the control of the related party terminal 61 in response to notification of the flood warning. The related party U4 can confirm the announcement of the flood warning by the notification on the related party terminal 61 and the lighting of the warning light 62. The related party U4 can also confirm the lifting of the flood warning by the notification on the related party terminal 61 and the lighting of the warning light 62.

[0082] 7 shows one local government employee terminal 45, the local government system 40 may have multiple local government employee terminals 45. Also, the related organization 60 may have multiple related party terminals 61.

[0083] Here, an example of a method for notifying a flood warning from the river information system 41 to the local government employee terminal 45 and the related party terminal 61 will be described.

[0084] A predetermined notification application program (hereinafter referred to as the notification application) is pre-installed on the local government employee terminal 45 and the related party terminal 61. The notification application has a display function and a warning light control function. The display function is a function that displays information indicating the issuance or cancellation of a flood warning, and receipt information of the flood warning notification, on the display unit of the terminal running the notification application. The receipt information is information that indicates whether the destination user (e.g., local government employee U3 or related party U4) has received the flood warning notification. The warning light control function is a function that controls the turning on and off of warning lights that can communicate with the terminal running the notification application. Hereinafter, any one of the local government employee terminal 45 and the related party terminal 61, without specifying the other, will be simply referred to as terminal 45, 61.

[0085] While the notification application is running, the terminal 45, 61 sends an inquiry regarding whether or not a flood warning notification has been sent to the automatic notification unit 41c at predetermined time intervals. This predetermined time is set arbitrarily by the user (municipal government employee U3 or related person U4) when the notification application is installed, for example.

[0086] When notifying a terminal 45, 61 of a flood warning, the automatic notification unit 41c responds to the inquiry and transmits information about flood warning to the terminal 45, 61. In order to enhance the security of protecting information used in the local government system 40, the automatic notification unit 41c may be configured to transmit information about flood warning to the terminal 45, 61 when authentication of the user using the terminal 45, 61 is successful.

[0087] Specifically, the automatic notification unit 41c receives the user ID and password entered into the terminal 45, 61 at a predetermined timing. The predetermined timing is, for example, when a notification application is started, when a predetermined operation is performed to display information indicating the issuance of a flood warning or the cancellation of a flood warning on the terminal 45, 61, or when a predetermined operation is performed to display information on receipt of a flood warning notification on the terminal 45, 61.

[0088] The automatic notification unit 41c determines that user authentication has been successful if the received user ID and password match the pre-registered user ID and password. On the other hand, if the user ID and password entered into the terminal do not match the pre-registered user ID and password, it determines that user authentication has failed. The pre-registered user ID and password are stored in the storage 3, for example.

[0089] Such user authentication can prevent information and screens related to flood prevention from being provided to unregistered users.

[0090] 8 is a diagram illustrating an example of the functional configuration of an automatic notification unit 41c included in the river information system 41 according to the embodiment. The automatic notification unit 41c includes a notification determination unit 411, a notification text generation unit 412, a screen provision unit 413, a notification unit 414, and a receipt confirmation unit 417.

[0091] The notification determination unit 411 determines whether to issue one of multiple levels of flood warnings based on at least one of river data and weather data. Specifically, the notification determination unit 411 determines whether at least one of the river water level and the weather advisory or weather warning satisfies one of multiple issuance conditions corresponding to each of multiple flood warning levels.

[0092] Furthermore, the notification determination unit 411 determines whether or not to notify the cancellation of the flood warning based on the river data and weather data. More specifically, the notification determination unit 411 determines whether the water level and at least one of the weather advisory and the weather warning satisfy the cancellation conditions corresponding to the cancellation of the flood warning. The announcement conditions and cancellation conditions will be described in detail later with reference to Figs. 14 to 19.

[0093] The notification generation unit 412 generates a notification (see FIG. 12 ) when the notification determination unit 411 determines that a flood warning should be issued or that a flood warning should be lifted. The notification generation unit 412 also generates notification destination information indicating information about a predetermined destination to which the notification should be sent. The notification generation unit 412 generates, for example, the IP address of the destination terminal as the notification destination information. The destinations of the notification message and the IP addresses of the destination terminals are stored, for example, in the storage 3.

[0094] The screen providing unit 413 displays the notification message list screen 27 (see FIG. 21), the notification content screen 28 (see FIG. 21), and the receipt confirmation screen 29 (see FIG. 22) on a terminal included in the notification destination information (for example, the local government employee terminal 45 or the related person terminal 61). More specifically, when the notification destination information includes the local government employee terminal 45, the screen providing unit 413 transmits information necessary to display the notification message list screen 27, the notification content screen 28, and the receipt confirmation screen 29 to the local government employee terminal 45 in response to a predetermined operation performed by the local government employee U3 on the local government employee terminal 45.

[0095] Furthermore, if the notification destination information includes the related party terminal 61, the screen providing unit 413 transmits to the related party terminal 61 information required to display the notification message list screen 27, the notification content screen 28, and the receipt confirmation screen 29 in response to the related party U4 performing a predetermined operation on the related party terminal 61. The predetermined operation includes inputting a user ID and password into the terminal 45 or 61 for user authentication. Furthermore, the screen providing unit 413 updates the receipt confirmation screen 29 based on the receipt confirmation data described below.

[0096] The notification unit 414 notifies the local government staff U3 and related parties U4 (related organizations 60) of the flood warning. The notification unit 414 includes a warning light control unit 415 and an alert screen display unit 416.

[0097] The warning light control unit 415 controls the turning on and off of the warning light 46 by the local government employee terminal 45. For example, when notifying the local government employee U3 of the announcement of a flood warning, the warning light control unit 415 transmits an instruction to turn on the warning light 46 to the local government employee terminal 45. In response to receiving this instruction to turn on the warning light 46, the local government employee terminal 45 turns on the warning light 46.

[0098] Furthermore, when notifying the local government employee U3 that the flood warning has been lifted, the warning light control unit 415 transmits an instruction to turn off the warning light 46 to the local government employee terminal 45. In response to receiving this instruction, the local government employee terminal 45 turns off the warning light 46.

[0099] Similarly, when notifying the relevant person U4 of the announcement of a flood warning, the warning light control unit 415 transmits an instruction to the relevant person terminal 61 to turn on the warning light 62. When notifying the relevant person U4 of the cancellation of the flood warning, the warning light control unit 415 transmits an instruction to the relevant person terminal 61 to turn off the warning light 62.

[0100] If multiple local government employee terminals are installed in the local government system 40, the warning light control unit 415 may turn on or off the warning light on each of the multiple local government employee terminals. Also, if the river information system 41 is connected to multiple related organizations via the Internet 1, the warning light control unit 415 may turn on or off the warning light on each of the related party terminals installed in the multiple related organizations.

[0101] The alert screen display unit 416 displays the alert screen 26 (see FIG. 20 ) on the local government employee terminal 45 and the related person terminal 61. In more detail, when notifying a local government employee U3 of a flood warning, the alert screen display unit 416 transmits information about flood warning and information necessary for displaying the alert screen 26 to the local government employee terminal 45. Furthermore, when notifying a related person U4 of the issuance of a flood warning, the alert screen display unit 416 transmits information about flood warning and information necessary for displaying the alert screen 26 to the related person terminal 61. Information necessary for displaying the alert screen 26 includes, for example, the name of the river for which the flood warning is to be issued, the serial number of the flood warning, and the level of the flood warning.

[0102] If the river information system 41 is connected to multiple local government employee terminals, the alert screen display unit 416 transmits to each of the multiple local government employee terminals information related to flood prevention and information necessary for displaying the alert screen 26. If the river information system 41 is connected to multiple related organizations via the Internet 1, it transmits to each of the related personnel terminals installed in the multiple related organizations information related to flood prevention and information necessary for displaying the alert screen 26.

[0103] The receipt confirmation unit 417 confirms whether or not the notification has been received by each of the local government employee U3 and the related person U4. A specific method for confirming whether or not the notification has been received will be described later with reference to Figures 23 to 25.

[0104] 9 is a diagram showing an example of a network configuration to which a river information system 41 according to the embodiment is connected. In the river information system 41 within the local government system 40, a local network 6 and an external network 7 are configured.

[0105] The local network 6 is a network in which communication with the outside via the Internet 1 is restricted in order to enhance security for protecting information used in the local government system 40. The local network 6 is, for example, a wired local area network (wired LAN) or a wireless local area network (wireless LAN). A communication server 42, an internal provision server 43, a local government employee terminal 45, and a warning light 46 are connected to the local network 6.

[0106] The external network 7 is a network communicably connected to an external related organization network 8 via the Internet 1. The external network 7 is provided between the local network 6 and the Internet 1 to prevent malware from invading the local network 6 or unauthorized access. The external network 7 is also called a DMZ (De-Militarized Zone). An external provision server 44 is connected to the external network 7.

[0107] In order to prevent attacks from devices connected to the Internet 1 on terminals connected to the local network 6, communication from the external network 7 to the local network 6 is restricted. Specifically, devices on the external network 7 (e.g., the external provision server 44) are restricted to be able to communicate with devices on the local network 6, for example, when using a predetermined protocol and when responding to a request from a device on the local network 6 (e.g., the internal provision server 43). The predetermined protocol is, for example, the HTTP protocol.

[0108] A related institution network 8 is configured in the related institution 60. The related institution network 8 may be a wired network (e.g., a wired LAN) or a wireless network (e.g., a wireless LAN). A related person terminal 61 and a warning light 62 are connected to the related institution network 8.

[0109] The related party terminal 61 can communicate with the external provision server 44 via the Internet 1. Although one related institution 60 is shown in FIG. 9, multiple related party terminals 61 provided in multiple related institutions 60 can communicate with the external provision server 44.

[0110] FIG. 10 is a diagram showing an example of the functional configuration of an automatic notification unit 41c applied to the communication server 42, the internal provision server 43, and the external provision server 44 in the river information system 41 according to the embodiment.

[0111] The communication server 42 includes an automatic notification unit 41c-1 in addition to a data collection / distribution unit 42a, a data storage unit 42b, and a data calculation unit 42c (see FIG. 5). The automatic notification unit 41c-1 corresponds to the notification determination unit 411 and the notification generation unit 412 included in the automatic notification unit 41c shown in FIG. 8. That is, in the communication server 42, the notification determination unit 411 determines whether to issue a flood warning of multiple levels based on at least one of river data and weather data. The notification determination unit 411 also determines whether to issue a notice of the lifting of a flood warning based on the river data and weather data. Then, the notification generation unit 412 generates a notice when the notification determination unit 411 determines to issue or lift a flood warning.

[0112] Specifically, the notification generator 412 generates a notification by selecting a format corresponding to the current flood warning level from a plurality of formats corresponding to the respective levels of flood warning. The plurality of formats includes formats for notifying information corresponding to each of the plurality of flood warning levels, such as the flood warnings announcing "standby," "preparation," and "mobilization" shown in FIG. 3. The plurality of formats also includes a format for notifying "cancellation" of the flood warning shown in FIG. 3. The plurality of formats are stored, for example, in the storage 3 of the communication server 42.

[0113] Furthermore, notification generation unit 412 generates notification destination information. The notification destination information is information indicating an organization to which the generated notification should be notified. Specifically, notification generation unit 412 generates the notification destination information based on a notification destination list table (see FIG. 13) described later.

[0114] The notification message generation unit 412 transmits the generated notification message and notification destination information to the internal provision server 43 on the local network 6. The notification message generation unit 412 also transmits the notification message and notification destination information to the external provision server 44 on the external network 7.

[0115] The internal provision server 43 has an automatic notification unit 41c-2 in addition to a data collection / distribution unit 43a, a data storage unit 43b, and a screen provision unit 43c (see FIG. 5). The automatic notification unit 41c-2 has a screen provision unit 413, a notification unit 414, and a receipt confirmation unit 417 for the local government employee terminal 45, which are included in the automatic notification unit 41c shown in FIG. 8. Hereinafter, the screen provision unit 413, the notification unit 414, and the receipt confirmation unit 417 for the local government employee terminal 45 will be referred to as the screen provision unit 413-1, the notification unit 414-1, and the receipt confirmation unit 417-1, respectively.

[0116] The screen providing unit 413-1 provides the data necessary to display the notification message list screen 27, the notification content screen 28, and the receipt confirmation screen 29 to the local government employee terminal 45. The notification unit 414-1 notifies the local government employee U3 of the flood warning by displaying the alert screen 26 on the local government employee terminal 45 and turning on or off the warning light 46. The receipt confirmation unit 417-1 confirms whether the local government employee U3 has received the notification.

[0117] The external provision server 44 has an automatic notification unit 41c-3 in addition to a data collection unit 44a, a data storage unit 44b, and a screen provision unit 44c (see FIG. 5). The automatic notification unit 41c-3 has a screen provision unit 413, a notification unit 414, and a receipt confirmation unit 417 for the related party terminal 61, which are included in the automatic notification unit 41c shown in FIG. 8. Hereinafter, the screen provision unit 413, the notification unit 414, and the receipt confirmation unit 417 for the related party terminal 61 will be referred to as a screen provision unit 413-2, a notification unit 414-2, and a receipt confirmation unit 417-2, respectively.

[0118] The screen providing unit 413-2 provides the data necessary to display the notification message list screen 27, the notification content screen 28, and the receipt confirmation screen 29 to the related party terminal 61. The notification unit 414-2 notifies the related party U4 of the flood warning by displaying the alert screen 26 on the related party terminal 61 and turning on or off the warning light 46. The receipt confirmation unit 417-2 confirms whether the related party U4 has received the notification.

[0119] The notification determination unit 411 and the notification message generation unit 412 may be provided in the internal provision server 43 and the external provision server 44, respectively, instead of in the communication server 42.

[0120] FIG. 11 is a diagram showing an example of a reference value table used in the river information system 41 according to the embodiment. The reference value table is a table showing multiple reference values ​​related to the water level of a river. Each of the multiple reference values ​​is a water level value used to determine whether or not the water level corresponds to a corresponding flood warning level. The reference value table is used in the notification control process executed by the automatic notification unit 41c-1 of the communication server 42. The reference value table is stored in the storage 3, for example.

[0121] The reference value table includes, for example, a plurality of entries corresponding to a plurality of rivers, each of which includes, for example, an "Issuing Civil Engineering Office" field, a "River Name" field, an "Observation Station Name" field, a plurality of "Water Level Reference Value" fields corresponding to a plurality of flood warning levels, and a "Levee Height" field.

[0122] In an entry corresponding to a river, the "Issuing Civil Engineering Office" field indicates the civil engineering office that has jurisdiction over the river. The "River Name" field indicates the name of the river. The "Observation Station Name" field indicates the name of the water level station (observation station) that measures the water level of the river.

[0123] The multiple "Reference Water Level" fields each indicate multiple reference values ​​set for the river. The multiple "Reference Water Level" fields are set with multiple reference values ​​for each flood warning level. For example, the higher the level (i.e., the larger the value) of the multiple flood warning levels, the higher the risk of flooding for the corresponding river. Specifically, for example, the "Reference Water Level" field corresponding to a level 1 flood warning indicates the reference value for the flood defense unit standby water level. The "Reference Water Level" field corresponding to a level 2 flood warning indicates the reference value for the flood warning water level. The "Reference Water Level" field corresponding to a level 3 flood warning indicates the reference value for the evacuation decision water level. The "Reference Water Level" field corresponding to a level 4 flood warning indicates the reference value for the flood danger water level. The number of "Reference Water Level" fields in which reference values ​​are set may vary depending on the river. Hereinafter, the reference value corresponding to a level X flood warning will also be simply referred to as the "reference water level for level X."

[0124] In the example shown in Figure 11, 1.20 m is set as the reference value for Level 1 for the XX River. 1.40 m is set as the reference value for Level 2 for the XX River. Note that no reference values ​​for Level 3 or Level 4 have been set for the XX River. This is because, for example, the surrounding environment of the XX River and the height of the levees make it unlikely that the river will flood even if the water level exceeds Level 2.

[0125] The "levee height" field indicates the height of the levee built on the corresponding river in the vicinity of the corresponding water level station (gauge station).

[0126] 12 is a diagram showing an example of a notification 25 used in the notification generation unit 412 of the river information system 41 according to the embodiment. Here, it is assumed that the notification generation unit 412 selects a notification format corresponding to a level 1 flood warning in response to the water level of the river exceeding the reference value for level 1.

[0127] The format corresponding to a level 1 flood warning is, for example, a format for generating a notification requesting the flood defense unit to "prepare." This format includes multiple items a1 to a6 in which the specific content of the flood warning to be notified is set.

[0128] The notification generation unit 412 generates the notification 25 by inputting (setting) character strings corresponding to the content of the flood warning to be notified into the items a1 to a6 in the selected format.

[0129] Item a1 indicates the river name (XX River) and the sequence number (XX) of the flood warning during one rainfall. The river name is entered as the name of the river that is the subject of the flood warning. The flood warning sequence number is entered as the consecutive number assigned in order to multiple flood warnings issued during one rainfall. Note that a "one rainfall" is the period from the issuance of the first flood warning at a certain observation station until the flood warning is lifted.

[0130] Specifically, for example, if a flood warning indicating "standby" is issued for the first time during a rainfall, "No. 1" is entered as the flood warning sequence number. If a flood warning indicating "preparation" is issued next during that rainfall, "No. 2" is entered. If the flood warning is then lifted, "No. 3" is entered. If a flood warning is issued again after being lifted, a new sequence number is assigned, so "No. 1" is entered as the flood warning sequence number.

[0131] Item a2 indicates the date and time of the flood warning announcement (Reiwa year, month, day, hour, minute). For example, the current date and time is input as the date and time of the flood warning announcement.

[0132] Item a3 indicates the issuing civil engineering office (XX civil engineering office). The issuing civil engineering office is the civil engineering office that has jurisdiction over the river that is the subject of the flood prevention warning. The name of the issuing civil engineering office is entered in item a3. The name of the issuing civil engineering office is obtained, for example, from the "issuing civil engineering office" field in the reference value table shown in Figure 11.

[0133] Item a4 indicates the water level observation point (□□ point), the observation date and time (as of XX day, XX:XX minute), and the observed value (XX m).

[0134] The observation point is the point where the civil engineering office observed the water level (i.e., the point where the water level was observed to determine whether or not a flood warning was required) entered in item a3. The points where the civil engineering office observed the water level are stored in advance in storage 3, for example.

[0135] The observation date and time is the date and time when the river water level used by the notification determination unit 411 to determine whether or not a flood warning notification is necessary is acquired (observed). The observation value is the river water level used by the notification determination unit 411 to determine whether or not a flood warning notification is necessary.

[0136] Item a5 indicates a preparation area for a flood defense unit. For example, a preparation area for a flood defense unit that is predetermined according to the issuing civil engineering office and the observation point is input as the preparation area for a flood defense unit.

[0137] Item a6 indicates the reference value of the water level. In the example of Fig. 12, the reference value of the flood defense unit standby water level corresponding to a flood prevention warning of level 1 (see Fig. 11) is input.

[0138] The notification generation unit 412 may add other supplemental information to the notification 25, such as attribute information managed for each civil engineering office (observatory).

[0139] 13 is a diagram showing an example of a notification destination list table used in the river information system 41. The notification destination list table is a table that indicates organizations to which a flood warning should be notified. The notification destination list table is used when the notification message generation unit 412 generates notification destination information. The notification destination list table is stored in the storage 3, for example.

[0140] The notification destination list table includes, for example, a plurality of entries corresponding to a plurality of observation stations (water level stations). Each of the plurality of entries includes, for example, an "issuing civil engineering office" field, a "river name" field, an "observation station" field, a "location" field, and a plurality of "notification destination" fields.

[0141] In an entry corresponding to a certain observation station, the "Issuing Civil Engineering Office" field indicates the name of the civil engineering office that has jurisdiction over the observation station. The "River Name" field indicates the name of the river on which the observation station is installed. The "Observation Station" field indicates the name of the observation station (e.g., water level bureau). The "Location" field indicates the city, town, or village where the observation station is located.

[0142] The multiple "Notification destination" fields correspond to multiple organizations, respectively. The multiple organizations include, for example, a prefectural office, multiple civil engineering offices, multiple city / town / village departments, and meteorological observatories. Each of the multiple "Notification destination" fields indicates whether the corresponding organization is set as a notification destination for flood warnings for the observation station. If an organization is set as a notification destination for flood warnings for a certain observation station, for example, "O" is set in the corresponding "Notification destination field." If an organization is not set as a notification destination for flood warnings for a certain observation station, for example, no value is set in the corresponding "Notification destination field." Therefore, an organization with "O" set in the "Notification destination field" is an organization associated with the corresponding observation station as a notification destination for flood warnings.

[0143] Specifically, the multiple "notification destination" fields include multiple "prefectural office / civil engineering office" fields and multiple "related organizations (city / town, meteorological observatory)" fields. The multiple "prefectural office / civil engineering office" fields indicate notification destinations connected to the local network 6. The "related organizations (city / town, meteorological observatory)" field indicates notification destinations connected to the external network 7 via the Internet 1.

[0144] In the example of the notification destination list table shown in Figure 13, for example, if a flood warning is issued based on the water level at Water Level Station A of the XX River under the jurisdiction of Civil Engineering Office A, the notification destinations for the flood warning are shown to be the prefectural government office, the general affairs department of A1 City, and the meteorological observatory.

[0145] 14 is a flowchart showing an example of the procedure of a notification control process executed by the automatic notification unit 41c-1 of the communication server 42 in the river information system 41 according to the embodiment. The automatic notification unit 41c-1 repeatedly executes the notification control process for each of a plurality of observation stations (water level stations), for example, at regular intervals. The following describes an example in which the automatic notification unit 41c-1 executes the notification control process for one observation station (hereinafter referred to as the target observation station).

[0146] In step S11, the notification determination unit 411 acquires the latest river data of the target observation station stored by the data storage unit 42b. The river data is stored in the storage 3, for example.

[0147] In step S12, the notification determination unit 411 refers to the reference value table (FIG. 11) and determines whether the river water level indicated in the latest acquired river data (hereinafter also referred to as the current river water level) exceeds any of the multiple reference values ​​corresponding to the target observation station. The multiple reference values ​​correspond to, for example, multiple levels of flood warnings.

[0148] If the acquired current river water level exceeds any of the reference levels (YES in step S12), the notification determination unit 411 proceeds to the processing in step S13.

[0149] In step S13, the notification determination unit 411 determines whether a heavy rain warning has been issued for the area including the target observation station. For this determination, for example, the latest weather data for the area including the target observation station, stored in the storage 3, is used. Note that instead of determining whether a heavy rain warning has been issued, the notification determination unit 411 may determine whether another weather warning or weather alert, such as a heavy rain warning, has been issued. Weather warnings and weather alerts are issued by the weather station system 15a and notified to the river information system 41 from the Japan Meteorological Agency system 12. In the following explanation, a case where whether a heavy rain warning has been issued is used for the determination by the notification determination unit 411 in step S13 will be exemplified.

[0150] If a heavy rain warning has been issued (YES in step S13), the notification determination unit 411 proceeds to the process of step S14.

[0151] In step S14, the notification determination unit 411 determines whether a flood warning of the same level or higher has already been issued during one rainfall. Specifically, for example, consider a case where the water level of a river exceeds the reference value for Level 2, and the announcement of a Level 2 flood warning is issued, and then the water level drops. In this case, even if the dropped water level rises again due to subsequent rainfall and exceeds the reference value for Level 1 or Level 2, the notification determination unit 411 determines that a flood warning of the same level or higher has already been issued during one rainfall.

[0152] If a flood warning of a level equal to or higher than the reference value exceeded in step S12 has already been issued during one rainfall (YES in step S14), the automatic notification unit 41c terminates the notification control process without issuing a flood warning. In other words, the automatic notification unit 41c-1 does not issue a flood warning. In other words, the automatic notification unit 41c-1 does not issue a flood warning of the same level more than once during one rainfall.

[0153] On the other hand, if a flood warning of the same level or higher has not yet been issued during one rainfall (NO in step S14), the automatic notification unit 41c-1 proceeds to the process in step S15.

[0154] In step S15, the notification generation unit 412 generates a notification (first announcement information) based on the flood warning level (hereinafter referred to as the current flood warning level) corresponding to which of multiple reference values ​​the current river water level has exceeded, and generates notification destination information for the notification. That is, the notification generation unit 412 generates a notification indicating the announcement of a flood warning of the current flood warning level. Furthermore, the notification generation unit 412 generates notification destination information indicating one or more notification destinations set for the target observation station, based on the notification destination list table shown in FIG. 13.

[0155] In step S16, the automatic notification unit 41c-1 transmits the notification message and the notification destination information to the internal provision server 43 and the external provision server 44, and ends the notification control process. As a result, the notification unit 414-1 of the internal provision server 43 and the notification unit 414-2 of the external provision server 44, which have received the notification message from the notification message generation unit 412 of the communication server 42, notify the notification destinations indicated in the notification destination information attached to the notification message of the announcement of a flood warning.

[0156] If the current water level of the river exceeds the reference value (YES in step S12) and a heavy rain warning has not been issued (NO in step S13), the notification determination unit 411 proceeds to the process in step S17.

[0157] In step S17, the notification determination unit 411 determines whether the current water level of the river has exceeded a reference value of level 3 or higher.

[0158] If the current water level of the river is lower than the reference value of Level 3 (NO in step S17), the automatic notification unit 41c-1 ends the notification control process without issuing a flood warning notification.

[0159] If the current water level of the river exceeds the reference value of level 3 or higher (YES in step S17), the notification determination unit 411 proceeds to the process of step S18.

[0160] In step S18, the notification determination unit 411 determines whether or not a flood warning of a level equal to or higher than the reference value exceeded in step S12 has already been issued during one rainfall. If a flood warning of a level equal to or higher than the reference value exceeded in step S12 has already been issued during one rainfall (YES in step S18), the automatic notification unit 41c-1 ends the notification control process without issuing a flood warning.

[0161] On the other hand, if a flood warning of a level equal to or higher than the reference value exceeded in step S12 has not yet been issued during a single rainfall (NO in step S18), the automatic notification unit 41c-1 proceeds to the processing of step S15. The processing of steps S15 and S16 is as described above.

[0162] If the current water level of the river does not exceed any of the reference values ​​(NO in step S12), the automatic notification unit 41c-1 proceeds to the process in step S19.

[0163] In step S19, the notification determination unit 411 determines whether a flood warning is currently being issued. "Flood warning is currently being issued" means that the cancellation of the flood warning has not been notified after it was issued.

[0164] If a flood warning is not being issued (NO in step S19), the automatic notification unit 41c-1 ends the notification control process without issuing a flood warning notification.

[0165] On the other hand, if a flood warning is being issued (YES in step S19), the notification determination unit 411 proceeds to the processing of step S20. In step S20, the notification determination unit 411 determines whether or not the heavy rain warning has been lifted. If the heavy rain warning has not been lifted (is being issued) (NO in step S20), the automatic notification unit 41c-1 ends the notification control processing without issuing a flood warning notification. On the other hand, if the heavy rain warning has been lifted (YES in step S20), the notification determination unit 411 proceeds to the processing of step S21.

[0166] In step S21, the notification generator 412 generates a notification (cancellation information) indicating the cancellation of the flood warning, and generates notification destination information for the notification. Specifically, the notification generator 412 selects, for example, a format for notifying "cancellation" from multiple formats, and generates a notification indicating the cancellation of the flood warning. Furthermore, the notification generator 412 generates notification destination information indicating one or more notification destinations set for the target observation station, based on the notification destination list table (FIG. 13).

[0167] Then, in step S22, the automatic notification unit 41c-1 transmits a notification message indicating the cancellation of the flood warning and notification destination information to the internal provision server 43 and the external provision server 44, and ends the notification control process.

[0168] Through the above notification control process, the automatic notification unit 41c-1 can control notifications of the issuance or cancellation of flood warnings using river data and meteorological data corresponding to the target observation station.

[0169] Specific examples of how a flood warning is issued or canceled will be described below with reference to Figures 15 to 19. In the following description, the step numbers in Figure 14 will be used as appropriate.

[0170] 15 to 19 are diagrams showing examples of flood warnings notified based on time-series water levels and whether or not a heavy rain warning has been issued in an embodiment. Here, the time-series water levels are assumed to be water levels observed at a target observation station. The presence or absence of a heavy rain warning refers to whether or not a heavy rain warning has been issued for an area including the target observation station. It is also assumed that four reference values ​​have been set corresponding to flood warnings from level 1 to level 4. The four reference values ​​are the flood defense unit standby water level, which is the reference value corresponding to a level 1 flood warning, the flood caution water level, which is the reference value corresponding to a level 2 flood warning, the evacuation decision water level, which is the reference value corresponding to a level 3 flood warning, and the flood danger water level, which is the reference value corresponding to level 4.

[0171] In the figure, times t11 to t18, t21 to t31, t41 to t48, t51 to t58, and t61 to t70 indicate the times when water levels were observed. Of these times t, the times when the corresponding water levels are indicated by black circles indicate the times when the river information system 41 issues or notifies the announcement of a flood warning. Furthermore, the times when the corresponding water levels are indicated by white circles indicate the times when the river information system 41 does not issue or notify the announcement of a flood warning.

[0172] First, the example in Fig. 15 will be described. At time t11, the water level of the river exceeds the reference value for Level 1. However, a heavy rain warning has not yet been issued. Furthermore, the water level of the river does not exceed the reference value for Level 3 (corresponding to step S11 → YES in step S12 → NO in step S13 → NO in step S17 in Fig. 14). In this case, the river information system 41 does not notify the issuance of a flood warning.

[0173] After that, at time t12, a heavy rain warning is issued while the river water level remains above the reference value for Level 1. Furthermore, the river information system 41 has not issued a flood warning related to the reference value for Level 1 during one rainfall (corresponding to step S11 → YES in step S12 → YES in step S13 → NO in step S14 in FIG. 14). In this case, the river information system 41 issues a flood warning of Level 1.

[0174] Next, at time t13, the river water level exceeds the reference value for Level 1, and a heavy rain warning is issued. However, the river information system 41 has already issued a Level 1 flood warning at time t12 (corresponding to step S11 → YES in step S12 → YES in step S13 → YES in step S14 in FIG. 14). In this case, the river information system 41 does not notify the issuance of a flood warning. In other words, the river information system 41 does not notify the issuance of a flood warning of the same level more than once during one rainfall. The same is true from time t14 to time t16.

[0175] The water level of the river gradually drops from time t15, and falls below the reference value of Level 1 at time t17. Also, at time t17, a flood warning is in effect, and the heavy rain advisory has not yet been lifted (corresponding to step S11 → NO in step S12 → YES in step S19 → NO in step S20 in FIG. 14). In this case, the river information system 41 does not notify the lifting of the flood warning.

[0176] Then, at time t18, the river water level falls below the reference value of Level 1, and the heavy rain warning is lifted (corresponding to step S11 → NO in step S12 → YES in step S19 → YES in step S20 in FIG. 14). In this case, the river information system 41 notifies the lifting of the flood warning.

[0177] 15, when the conditions that the water level of the river exceeds a certain reference value and a heavy rain warning has been issued are first met during one rainfall, the river information system 41 issues a notice to issue a flood warning corresponding to that level. After issuing a flood warning, the river information system 41 also issues a notice to cancel the flood warning when the conditions that the water level is below the reference value and the heavy rain warning has been cancelled are met.

[0178] Next, an example of Fig. 16 will be described. At time t21, the water level of the river exceeds the reference value of Level 1, and a heavy rain warning has been issued. Furthermore, the river information system 41 has not issued a flood warning related to the reference value of Level 1 during one rainfall (corresponding to step S11 → YES in step S12 → YES in step S13 → NO in step S14 in Fig. 14). In this case, the river information system 41 issues a notice of issuing a flood warning of Level 1.

[0179] After that, at time t22, the river water level drops below the reference value of Level 1. However, the heavy rain warning is not lifted (corresponding to step S11 → NO in step S12 → YES in step S19 → NO in step S20 in FIG. 14). In this case, the drop in the river water level may be temporary, so the river information system 41 does not notify the lifting of the flood warning.

[0180] After that, at time t23, the water level of the river rises again and exceeds the reference value for Level 1. Furthermore, a heavy rain warning is being issued. However, the river information system 41 has already issued a Level 1 flood warning at time t21 (corresponding to step S11 → YES in step S12 → YES in step S13 → YES in step S14 in FIG. 14). In this case, the river information system 41 does not notify the issuance of a flood warning.

[0181] After that, at time t24, the water level of the river rises further and exceeds the reference value for Level 2. A heavy rain warning is still being issued. Furthermore, the river information system 41 has not yet issued a Level 2 flood warning (corresponding to step S11 → YES in step S12 → YES in step S13 → NO in step S14 in FIG. 14). In this case, the river information system 41 notifies the issuance of a Level 2 flood warning.

[0182] Then, at time t25, the water level of the river rises further and exceeds the reference value for Level 3. A heavy rain warning is being issued. Furthermore, the river information system 41 has not yet issued a Level 3 flood warning (corresponding to step S11 → YES in step S12 → YES in step S13 → NO in step S14 in FIG. 14). In this case, the river information system 41 notifies the issuance of a Level 3 flood warning.

[0183] At time t26, the water level of the river has risen further and exceeds the reference value for level 4. A heavy rain warning is currently being issued. Furthermore, the river information system 41 has not yet issued a level 4 flood warning (corresponding to step S11 → YES in step S12 → YES in step S13 → NO in step S14 in FIG. 14). In this case, the river information system 41 notifies the issuance of a level 4 flood warning.

[0184] After that, at time t27, the water level of the river drops above the reference value for Level 3, but falls below the reference value for Level 4. However, the river information system 41 has already issued a flood warning of Level 3 at time t25 and a flood warning of Level 4 at time t26. In other words, the river information system 41 has already issued a flood warning of the same level (Level 3 in this case) or higher (corresponding to step S11 → YES in step S12 → YES in step S13 → YES in step S14 in FIG. 14). In this case, the river information system 41 does not notify the issuance of a flood warning. The same is true at time t28.

[0185] Next, at time t29, the water level of the river drops below the reference value of Level 1. However, a heavy rain warning is still being issued (corresponding to step S11 → NO in step S12 → YES in step S19 → NO in step S20 in FIG. 14). In this case, the river information system 41 does not announce the cancellation of the flood warning.

[0186] After that, at time t30, the river water level rises again and exceeds the reference value for Level 1. However, a heavy rain warning has not been issued (it has been lifted). Furthermore, although the river water level has risen, it has not exceeded the reference value for Level 3 (corresponding to step S11 → YES in step S12 → NO in step S13 → NO in step S17 in FIG. 14). In this case, since the rise in the river water level may be temporary, the river information system 41 does not issue a flood warning.

[0187] After that, at time t31, the river water level drops again to below the reference value of Level 1. Also, the heavy rain warning is lifted (corresponding to step S11 → NO in step S12 → YES in step S19 → YES in step S20 in FIG. 14). In this case, the river information system 41 notifies the lifting of the flood warning.

[0188] Next, the example of Fig. 17 will be described. At time t41, the water level of the river exceeds the reference value for Level 2, and a heavy rain warning is issued. Furthermore, a flood warning related to the reference value for Level 2 has not been issued during one rainfall (corresponding to step S11 → YES in step S12 → YES in step S13 → NO in step S14 in Fig. 14). In this case, the river information system 41 notifies the issuance of a Level 2 flood warning.

[0189] Thereafter, at time t42, the dropped water level of the river exceeds the reference value for Level 1 but is below the reference value for Level 2. Furthermore, at time t41, the river information system 41 has already issued a flood warning of Level 2, which is higher than Level 1 (corresponding to step S11 → YES in step S12 → YES in step S13 → YES in step S14 in FIG. 14). In this case, the river information system 41 does not notify the announcement of a flood warning of Level 1. Similarly, at time t43, the river information system 41 does not notify the announcement of a flood warning of Level 2 because it has already issued a flood warning of Level 2 at time t41.

[0190] After that, at time t44, the water level of the river rises and exceeds the reference value for level 3, and a heavy rain warning is issued (corresponding to step S11 → YES in step S12 → YES in step S13 → NO in step S14 in FIG. 14). In this case, the river information system 41 issues a notice to issue a level 3 flood warning.

[0191] Next, at time t45, the water level of the river rises further, exceeding the reference value for level 4, and a heavy rain warning is issued (corresponding to step S11 → YES in step S12 → YES in step S13 → NO in step S14 in FIG. 14). In this case, the river information system 41 issues a notice to issue a level 4 flood warning.

[0192] Thereafter, the water level of the river drops below the reference value for Level 4 at time t46, and below the reference value for Level 3 at time t47. At times t46 and t47, the river information system 41 makes the same judgment as at times t27 and t28 in FIG. 16, and therefore does not issue a flood warning.

[0193] At time t48, the water level of the river drops below the reference value of Level 1. Also, at time t48, the heavy rain warning has not been issued (has been lifted) (corresponding to step S11 → NO in step S12 → YES in step S19 → YES in step S20 in FIG. 14). In this case, the river information system 41 notifies that the flood warning has been lifted.

[0194] As explained in Figures 16 and 17, the river information system 41 issues a flood warning corresponding to the second level when the following conditions are met for the first time during a rainfall: the river water level exceeds a second level reference value that is higher than the first level reference value that was previously exceeded; and a heavy rain warning has been issued. That is, the river information system 41 may issue a flood warning every time the river water level exceeds a higher level reference value. Furthermore, the river information system 41 will not issue a flood warning of a level lower than the level issued during a rainfall.

[0195] Next, the example in Figure 18 will be described. At time t51, although a heavy rain warning has not been issued, the water level has risen sharply and exceeded the reference value for level 3. Also, a level 3 flood warning has not yet been issued during one rainfall (corresponding to step S11 in Figure 14 → YES in step S12 → NO in step S13 → YES in step S17 → NO in step S18). In this case, the river information system 41 notifies the issuance of a level 3 flood warning.

[0196] From time t52 to t54, the water level of the river exceeds the reference value for Level 3, but does not exceed the reference value for Level 4. Therefore, the river information system 41 does not issue a Level 3 flood warning, as in the case of times t13 to t16 in FIG.

[0197] After that, at time t55, the water level of the river rises and exceeds level 4. In addition, a heavy rain warning is issued (corresponding to step S11 in FIG. 14 → YES in step S12 → YES in step S13 → NO in step S14), and the river information system 41 notifies the issuance of a level 4 flood warning.

[0198] The subsequent determinations at time t56 and time t57 are similar to the determinations at time t27 and time t28 shown in FIG.

[0199] Thereafter, at time t58, the dropped river water level falls below the reference value of Level 1. Also, at time t58, the heavy rain warning has not been issued (it has been lifted) (corresponding to step S11 → NO in step S12 → YES in step S19 → YES in step S20 in FIG. 14). In this case, the river information system 41 notifies that the flood warning has been lifted.

[0200] 18, when the water level of a river exceeds the reference value of Level 3 or higher, the river information system 41 issues a flood warning even if a heavy rain advisory has not been issued. This allows the river information system 41 to issue a flood warning without waiting for the issuance of a heavy rain advisory when there is a sudden change in water level, such as a sudden downpour.

[0201] Next, an example will be described in Fig. 19. At time t61, a heavy rain warning has been issued, but the water level of the river has not exceeded the reference value of Level 1 (corresponding to step S11 → NO in step S12 → NO in step S19 in Fig. 14). In this case, the river information system 41 does not issue a flood warning.

[0202] Here, it is assumed that river data including the river water level was missing at time t62. Hereinafter, the water level of the missing river data will be referred to as "missing data." In Figure 19, the missing data is indicated by a dashed white circle.

[0203] For example, if the river information system 41 has not received river data observed at a certain time (for example, if the river data at that time has not been saved in the storage 3) when determining whether or not to issue a flood warning for that time, or if the water level indicated in the received river data is inappropriate, such as exceeding a predetermined range, the river information system 41 determines that the water level of the river data is missing data. In this case, the river information system 41 uses the water level of the river data acquired immediately before that time to determine whether or not to issue a flood warning. Here, the river water level at time t61 is used as the river water level at time t62. Although a heavy rain advisory has been issued at time t62, the river information system 41 does not issue a flood warning because the river water level (i.e., the river water level at time t61) does not exceed the reference value for Level 1.

[0204] Next, at time t63, the river water level exceeds the Level 1 reference value, and a heavy rain warning is issued. Also, a flood warning related to the Level 1 reference value has not been issued during the rainfall (step S11 → YES in step S12 → YES in step S13 → NO in step S14). In this case, the river information system 41 notifies the issuance of a Level 1 flood warning.

[0205] Assume that the river water level data was missing at time t64. Therefore, the river information system 41 uses the water level indicated in the river data at time t63, which was acquired immediately before time t64. The water level in the river data at time t63 exceeds the reference value for Level 1. A heavy rain warning is also being issued. However, the river information system 41 has already notified the issuance of a Level 1 flood warning at time t63 (corresponding to step S11 → YES in step S12 → YES in step S13 → YES in step S14 in FIG. 14). In this case, the river information system 41 does not notify the issuance of a Level 1 flood warning.

[0206] Next, at time t65, the water level of the river exceeds the reference value for Level 1. However, a Level 1 flood warning has already been issued (corresponding to step S11 → YES in step S12 → YES in step S13 → YES in step S14 in FIG. 14). In this case, the river information system 41 does not issue a Level 1 flood warning.

[0207] The processing by the river information system 41 from time t66 to time t70 is the same as the processing from time t44 to time t48 in Fig. 17. Therefore, detailed explanation will be omitted here.

[0208] 19, when river data including water level is missing, the river information system 41 uses the water level of the most recently acquired river data to determine whether to issue a flood warning. This allows the river information system 41 to prevent inappropriate notifications based on missing data.

[0209] 14 to 19, in the embodiment, the risk of river flooding is determined not by the local government employee U3 but by the river information system 41. This unifies the criteria for determining whether or not to issue a flood warning, and allows the issuance of a flood warning to occur without relying on the experience and know-how of multiple local government employees U3.

[0210] Next, the screen configuration in the embodiment will be described. The screens shown in Fig. 20 to Fig. 22 below are displayed on the display units of the local government employee terminal 45 and the related party terminal 61 by, for example, the above-mentioned notification application.

[0211] 20 is a diagram showing an example of the alert screen 26. The alert screen 26 displays the name of the river for which a flood warning is to be issued, the sequence number of the flood warning, the level of the flood warning, and the like.

[0212] The alert screen 26 is displayed, for example, as a pop-up on the foreground of the display unit of each of the local government employee terminal 45 and the related person terminal 61. By displaying such an alert screen 26, the local government employee U3 and the related person U4 can easily understand that a flood warning has been issued (or canceled) even if they are performing other work on the local government employee terminal 45 and the related person terminal 61.

[0213] Fig. 21 shows examples of a notification message list screen 27 and a notification content screen 28. The notification message list screen 27 shown in the upper part of Fig. 21 shows a list of one or more flood warnings (notification messages). The notification content screen 28 shown in the lower part of Fig. 21 shows the specific notification content of one of the flood warnings.

[0214] 21 shows an example of a notification list screen 27 and a notification content screen 28 displayed on a local government employee terminal 45. The notification list screen 27 displayed on a local government employee terminal 45 shows a list of flood warnings notified to the local government employee terminal 45. The flood warnings notified to the local government employee terminal 45 are flood warnings for rivers (water level stations) managed by the corresponding local government. More specifically, the notification list screen 27 displayed on the local government employee terminal 45 may show, for example, flood warnings for water level stations for which "prefectural office" is set as the notification destination, as shown in the notification destination list table of FIG. 13.

[0215] Meanwhile, the notification list screen 27 displayed on the relevant person terminal 61 shows a list of flood warnings notified to the relevant person terminal 61. In other words, the notification list screen 27 displayed on the relevant person terminal 61 can show flood warnings for which the corresponding relevant organization 60 is the notification recipient.

[0216] The notification message list screen 27 includes multiple entries corresponding to multiple flood warnings that have been notified (more specifically, multiple flood warnings that have been issued or canceled). When a flood warning is issued, one entry is added to the notification message list screen 27. When a flood warning is canceled, one entry is added to the notification message list screen 27.

[0217] As described above, the notification list screen 27 shown in Fig. 21 shows an example displayed on the local government employee terminal 45. The notification list screen 27 displayed on the local government employee terminal 45 includes entries of flood warnings for all rivers (water level stations) managed by the corresponding local government. On the other hand, the notification list screen 27 displayed on the related party terminal 61 includes entries of flood warnings notified to the related party terminal 61 (i.e., flood warnings to which the corresponding related organization 60 is notified).

[0218] Each of the multiple entries includes fields such as "announcement date and time," "notification method," "announcement civil engineering office," "river name," "observation station name," "location," "announcement content," and "notification destination confirmation status."

[0219] In an entry corresponding to a flood warning, the "announcement date and time" field indicates the announcement date and time of the flood warning.

[0220] The "Notification Method" field indicates whether the corresponding flood warning notification was made automatically by the automatic notification unit 41c or manually by a local government employee U3. Examples of manual notification include reissuing a flood warning of the same level or modifying the content of a flood warning that has already been issued.

[0221] The "Issuing Civil Engineering Office" field indicates the civil engineering office that issued the corresponding flood warning. More specifically, the "Issuing Civil Engineering Office" field indicates the civil engineering office that has jurisdiction over the observation station (water level station) that observed the river data used to determine whether or not to issue the corresponding flood warning.

[0222] The "river name" field indicates the river that is the subject of the corresponding flood warning.

[0223] The "observation station name" field indicates the water level station that observed the river data used to determine whether or not a corresponding flood warning notice is required.

[0224] The "Location" field indicates the location of the water level station indicated in "Observation Station Name." For example, the city, town, or village where the water level station is located is set in the "Location" field.

[0225] The "Announcement Content" field indicates the content of the corresponding flood warning. For example, the "Announcement Content" field contains an outline of the flood warning (notification), such as the name of the river and the level of the flood warning.

[0226] The "Notification destination confirmation status" field indicates whether the corresponding flood warning notification destination has received the flood warning notification. If all notification destinations to which the corresponding flood warning notification was sent have received the flood warning notification, the "Notification destination confirmation status" field is set to, for example, "Completed." On the other hand, if at least some of the notification destinations to which the corresponding flood warning notification was sent have not received the flood warning notification, the "Notification destination confirmation status" field is set to, for example, "Incomplete." Whether the notification destinations to which the corresponding flood warning notification was sent have received the flood warning notification is determined by whether the internal provision server 43 or the external provision server 44 has received the receipt confirmation data, which will be described later, from the notification destination.

[0227] Furthermore, when an entry is selected in the notification list screen 27, details of the flood warning (notification) corresponding to the selected entry are displayed. The lower part of Fig. 21 shows an example of a notification content screen 28 that is displayed when an entry with an announcement date and time of "2023 / 04 / 18 12:00" is selected from the notification list screen 27.

[0228] Although not shown, when an entry with "Incomplete" set in the notification destination confirmation status is selected, a list of local government employee terminals 45 and / or related organizations 60 that have not received the corresponding flood warning is displayed. This allows local government employee U3 to notify related organizations 30 that have not confirmed receipt of the flood warning despite having notified them of the flood warning by another means, such as by telephone.

[0229] 22 is a diagram showing an example of the receipt confirmation screen 29 according to this embodiment. The receipt confirmation screen 29 is a screen for inputting that a flood warning has been received. The receipt confirmation screen 29 is displayed on the local government employee terminal 45 and the related party terminal 61 to which the flood warning has been notified.

[0230] The receipt confirmation screen 29 includes multiple entries corresponding to each of the multiple notification destinations to which a certain flood warning will be notified. Note that Fig. 22 shows an example of the receipt confirmation screen 29 displayed on the local government employee terminal 45. The receipt confirmation screen 29 displayed on the local government employee terminal 45 includes multiple entries corresponding to all notification destinations to which a certain flood warning will be notified. On the other hand, the receipt confirmation screen 29 displayed on the related party terminal 61 includes an entry corresponding to that related party terminal 61, but does not include entries corresponding to other notification destinations.

[0231] Each entry includes fields for, for example, "announcement office," "notification destination," "date and time of receipt confirmation," "receipt confirmation person," and "receipt confirmation person registration."

[0232] In an entry corresponding to the notification destination of a certain flood warning, the "issuing office" field indicates the civil engineering office that issued the flood warning.

[0233] The "Notification destination" field indicates the notification destination of the corresponding flood warning.

[0234] The "date and time of receipt confirmation" field indicates the date and time when the user confirmed the flood warning notification. The user who confirmed the flood warning notification is also called the "receiver." The "receiver" may be, for example, a local government employee U3 or a related person U4. The "date and time of receipt confirmation" field may be automatically populated with the date and time when the user confirmed receipt of the flood warning.

[0235] The "receipt confirmer" field indicates the person who confirmed the receipt. If the notification destination is the prefectural office (specifically, the local government employee terminal 45), the name of the local government employee U3 is entered in the "receipt confirmer" field. If the notification destination is the related organization 60 (specifically, the related person terminal 61), the name of the related person U4 is entered.

[0236] A registration button is placed in the "Receipt confirmation person registration" field. When the registration button is pressed, information including the receipt confirmation date and time entered in the "Receipt confirmation date and time" field and the receipt confirmer entered in the "Receipt confirmation person" field is sent to the river information system 41. Hereinafter, information including the receipt confirmation date and time in the "Receipt confirmation date and time" field and the receipt confirmer in the "Receipt confirmation person" field will be referred to as "receipt confirmation data." The receipt confirmation data may further include information about the notification destination indicated in the "Notification destination" field.

[0237] Specifically, for example, when the registration button in the “Register Receipt Confirmer” field is pressed on the receipt confirmation screen 29 displayed on the local government employee terminal 45, the local government employee terminal 45 transmits the receipt confirmation data to the internal provision server 43. Also, when the registration button in the “Register Receipt Confirmer” field is pressed on the receipt confirmation screen 29 displayed on the related party terminal 61, the related party terminal 61 transmits the receipt confirmation data to the external provision server 44.

[0238] Next, the receipt confirmation process by the receipt confirmation unit 417 will be described with reference to FIGS.

[0239] FIG. 23 is a diagram showing an example in which receipt confirmation data cannot be transmitted from the external provision server 44 to the internal provision server 43 without a request from the internal provision server 43 in the river information system 41 according to this embodiment.

[0240] The local network 6 is connected to an external network 7 via a firewall 9. The firewall 9 has the function of protecting information (data) used by devices on the local network 6. The external network 7 is connected to, for example, a related organization network 8 via the Internet 1. The related organization network 8 is a network to which related party terminals 61 are connected.

[0241] A communication server 42 and an internal provision server 43 are connected to the local network 6 .

[0242] Each of the communication server 42 and the internal provision server 43 can transmit data (for example, a flood warning notification) to the external provision server 44 via the firewall 9.

[0243] The internal provision server 43 also receives receipt confirmation data from a local government employee terminal 45 connected to the local network 6. If multiple local government employee terminals are connected to the local network 6, the internal provision server 43 receives receipt confirmation data from each of the multiple local government employee terminals.

[0244] The internal delivery server 43 includes a receipt result database (receive result DB) 70. The receipt result DB 70 is a database that stores receipt confirmation data received from the local government employee terminal 45. For example, a storage area of ​​a storage provided in the internal delivery server 43 is allocated as the receipt result DB 70. Alternatively, the receipt result DB 70 may be stored in a storage device (not shown) on the local network 6, for example. The internal delivery server 43 stores, for example, the receipt confirmation data received from the local government employee terminal 45 in the receipt result DB 70 together with information indicating the notification destination (here, the prefectural office) corresponding to the local government employee terminal 45. Note that the information indicating the notification destination may be included in the receipt confirmation data.

[0245] In response to receiving the receipt confirmation data, the internal provision server 43 determines that the local government employee U3 using the local government employee terminal 45 that sent the receipt confirmation data has confirmed the flood warning notification. Then, the internal provision server 43 updates the "Receipt confirmation date and time" field and the "Receipt confirmer" field corresponding to this local government employee terminal 45 on the receipt confirmation screen 29 (FIG. 22) to indicate that the flood warning notification has been confirmed.

[0246] An external provision server 44 is connected to the external network 7 . The external provision server 44 is restricted so as not to transmit data to a server on the local network 6 without a request from a server on the local network 6 (i.e., the communication server 42 or the internal provision server 43). Specifically, for example, the external provision server 44 cannot transmit receipt confirmation data to the internal provision server 43 without a request from the internal provision server 43. This is to prevent, for example, malware transmitted to the external provision server 44 via the Internet 1 from invading a server on the local network 6, and to prevent a virus-infected external provision server 44 from gaining unauthorized access and leaking information stored in a server on the local network 6.

[0247] The external provision server 44 is capable of transmitting data to the related party terminal 61 via the Internet 1, and is capable of receiving data from the related party terminal 61. Data transmitted from the external provision server 44 to the related party terminal 61 is, for example, a flood warning notification. Data transmitted from the related party terminal 61 to the external provision server 44 is, for example, receipt confirmation data. Note that, when the external provision server 44 is connected to a plurality of related organizations 60 via the Internet 1, it is capable of transmitting data to each of the related party terminals of those plurality of related organizations 60, and is capable of receiving data from each of them.

[0248] The external provision server 44 includes a receipt result DB 71. The receipt result DB 71 stores receipt confirmation data received from the related party terminal 61. For example, a storage area of ​​a storage provided in the external provision server 44 is allocated as the receipt result DB 71. Alternatively, the receipt result DB 71 may be stored in a storage device (not shown) on the external network 7, for example.

[0249] As mentioned above, access from the external network 7 to the local network 6 is restricted to prevent the intrusion of malware via the Internet 1 or the leakage of information due to unauthorized access. Therefore, the external provision server 44 cannot transmit the receipt confirmation data of the related party terminal 61 to the internal provision server 43 without a request from the internal provision server 43. In other words, the internal provision server 43 cannot know whether the related party terminal 61 has received the flood warning (i.e., whether the related party U4 has confirmed the flood warning). Therefore, the internal provision server 43 cannot update the information set in the "Receipt confirmation date and time" field and the "Receipt confirmer" field corresponding to the related party terminal 61 on the receipt confirmation screen 29 (FIG. 22) using the receipt confirmation data from the related party terminal 61.

[0250] Therefore, the river information system 41 of this embodiment is configured to enable data transmission (access) from the external provision server 44 to the internal provision server 43 in communication conforming to a specific protocol. The specific protocol is, for example, HTTP (Hypertext Transfer Protocol). HTTP is a protocol for transmitting (sending) an HTML file (web page) on a server to a client in response to a request from the client. Hereinafter, transmitting a web page in response to a request for transmission of the web page will be referred to as "accessing" the web page.

[0251] In HTTP-compliant communications, for example, it is possible to restrict the rewriting of data on the server and the sending of files to the server, so HTTP-compliant communications may be permitted even in communications from the external provision server 44 to the internal provision server 43 via the firewall 9 as described above.

[0252] Furthermore, in the river information system 41, when a server on the local network 6 requests a server on the external network 7 (for example, the external provision server 44) to send data, the server on the external network 7 can send a response to the request to the server on the local network 6. Specifically, for example, when the internal provision server 43 requests the external provision server 44 to send receipt confirmation data, the external provision server 44 sends the receipt confirmation data to the internal provision server 43.

[0253] 24 is a diagram showing an example of a receipt confirmation operation in the river information system 41 according to this embodiment. This receipt confirmation operation is an operation in which the internal provision server 43 receives receipt confirmation data from the external provision server 44 and confirms receipt of the flood warning notification by the concerned party terminal 61. Note that the operation in which the internal provision server 43 receives receipt confirmation data from each of one or more local government employee terminals 45 and stores the receipt confirmation data in the receipt result DB 70 has been described above with reference to FIG.

[0254] For the receipt confirmation operation, the internal provision server 43 further includes a receipt confirmation Web page WP, a log DB 73, and a receipt result DB 70. The internal provision server 43 functions as a Web server that provides at least the receipt confirmation Web page WP.

[0255] The receipt confirmation web page WP is a web page that should be accessed by the external provision server 44 that receives the receipt confirmation data from the related party terminal 61. The receipt confirmation web page WP is, for example, a file (data) created using HTML (Hypertext Markup Language) or CSS (Cascading Style Sheets). The receipt confirmation web page WP may be configured so that the internal provision server 43 can detect that it has received an access request to the receipt confirmation web page WP from the external provision server 44. The receipt confirmation web page WP may be, for example, a web page with content that does not display anything on the screen of the external provision server 44 that sent the access request. The receipt confirmation web page WP is stored, for example, in storage within the internal provision server 43.

[0256] The log DB 73 is a database that stores at least a log (hereinafter also referred to as an access log) related to access to the receipt confirmation web page WP. For example, a storage area of ​​the storage in the internal provision server 43 is allocated as the log DB 73. Alternatively, the log DB 73 may be stored in a storage device (not shown) on the local network 6.

[0257] As described above, the external provision server 44 can receive receipt confirmation data from each of one or more related party terminals 61. The external provision server 44 stores the received receipt confirmation data in the receipt result DB 71 together with information indicating the notification destination (e.g., related organization 60) corresponding to the related party terminal 61 that sent the receipt confirmation data. Note that the information indicating the notification destination may be included in the receipt confirmation data.

[0258] Next, a description will be given of an example of a receipt confirmation operation in the river information system 41. The receipt confirmation operation is performed by the receipt confirmation unit 417-1 of the internal provision server 43 and the receipt confirmation unit 417-2 of the external provision server 44, for example.

[0259] In step S1, the external provision server 44 (receipt confirmation unit 417-2) receives receipt confirmation data from the concerned party terminal 61 via the Internet 1, and then transmits an access request to the internal provision server 43 for the receipt confirmation Web page WP. The access request to the receipt confirmation Web page WP is, for example, an access request conforming to HTTP.

[0260] In step S2, the internal provision server 43 (receipt confirmation unit 417-1) stores a log related to access to the receipt confirmation Web page WP in the log DB 73 in response to the access request received from the external provision server 44. Specifically, the internal provision server 43 stores information capable of identifying the device that sent the access request to the receipt confirmation Web page WP (here, the external provision server 44) together with the date and time when the access request was received in the log DB 73. The information capable of identifying the device that sent the access request is, for example, an IP address assigned to that device.

[0261] In step S3, the internal provision server 43 periodically refers to the log DB 73 to determine whether there has been a new access to the receipt confirmation web page WP from the external provision server 44. If there has been a new access to the receipt confirmation web page WP from the external provision server 44, in step S4 the internal provision server 43 requests the external provision server 44 to transmit receipt confirmation data. Note that the request to transmit the receipt confirmation data may include the date and time of the new access to the receipt confirmation web page WP.

[0262] In step S5, in response to the request to transmit the receipt confirmation data, the external provision server 44 reads out from the receipt result DB 71 the receipt confirmation data that has not yet been transmitted to the internal provision server 43. Specifically, the external provision server 44 reads out from the receipt result DB 71 the receipt confirmation data that has been received within a specific period that includes, for example, the date and time when the receipt confirmation web page WP was accessed.

[0263] Then, in step S6, the external provision server 44 returns (transmits) the read receipt confirmation data to the internal provision server 43. Note that the communications in steps S4 and S6 are communications compliant with, for example, TCP / IP (Transmission Control Protocol / Internet Protocol).

[0264] In step S7, the internal delivery server 43 stores the received receipt confirmation data in the receipt result DB 70. The internal delivery server 43 (screen providing unit 413-1) displays the receipt confirmation screen 29 based on the receipt confirmation data stored in the receipt result DB 70. The internal delivery server 43 also updates the receipt confirmation screen 29 based on the receipt confirmation data newly stored in the receipt result DB 70.

[0265] 25 is a flowchart showing an example of the procedure of the receipt confirmation process executed by the internal provision server 43. The internal provision server 43 repeatedly executes the receipt confirmation process, for example, at regular intervals.

[0266] In step S31, the internal provision server 43 refers to the access log of the receipt confirmation Web page WP (hereinafter simply referred to as the access log). Specifically, the internal provision server 43 reads the access log from the log DB 73, for example. Alternatively, the internal provision server 43 may read a portion of the access log stored in the log DB 73 that has been newly added since the last time it was referenced (hereinafter referred to as the added log portion).

[0267] In step S32, the internal provision server 43 determines whether or not a new access from the external provision server 44 has been recorded in the access log of the receipt confirmation web page WP. Specifically, the internal provision server 43 determines, for example, whether or not the access log newly includes the IP address of the external provision server 44. Alternatively, the internal provision server 43 may determine whether or not the IP address of the external provision server 44 is included in the additional log portion.

[0268] If no new access by the external provision server 44 is recorded in the access log (NO in step S32), the internal provision server 43 ends the receipt confirmation process.

[0269] If a new access by the external provision server 44 is recorded in the access log (YES in step S32), the internal provision server 43 proceeds to the process of step S33.

[0270] In step S33, the internal provision server 43 requests the external provision server 44 to transmit receipt confirmation data.

[0271] In step S34, the internal provision server 43 receives the receipt confirmation data from the external provision server 44.

[0272] In step S35, the internal provision server 43 saves (stores) the received receipt confirmation data in the receipt result DB 70.

[0273] In step S36, the internal provision server 43 (screen provision unit 413-1) may display the receipt confirmation screen 29 (see FIG. 22) based on the stored receipt confirmation data, or may update the receipt confirmation screen 29 that is already displayed.

[0274] Through the above-described receipt confirmation process, when the external provision server 44 acquires new receipt confirmation data, the internal provision server 43 can acquire the receipt confirmation data from the related party terminal 61 (related party U4) by requesting the external provision server 44 to transmit the receipt confirmation data. In other words, under the constraint that data cannot be transmitted from the external provision server 44 to the internal provision server 43 without a request from the internal provision server 43, the internal provision server 43 can efficiently acquire the receipt confirmation data from the related party terminal 61 from the external provision server 44. As a result, the internal provision server 43 can efficiently confirm that the related party terminal 61 has received the flood warning notification, while maintaining security in communication with the external network 7 via the firewall 9.

[0275] As described above, the river information system 41 according to the embodiment includes a communication server 42, an external provision server 44, and an internal provision server 43. The communication server 42 transmits a flood warning notification (flood warning information) to the external provision server 44 and the internal provision server 43 based on at least one of river data indicating the water level of a river and weather data related to at least one of a weather advisory and a weather warning. The external provision server 44 transmits the flood warning notification to a related party terminal 61 (first terminal) connected to the external provision server 44 via the Internet 1. The external provision server 44 receives, from the related party terminal 61, receipt confirmation data indicating that the flood warning notification has been confirmed by a related party U4 (user) using the related party terminal 61. When the internal provision server 43 requests transmission of the receipt confirmation data, the external provision server 44 transmits the receipt confirmation data to the internal provision server 43.

[0276] With this configuration, the river information system 41 can efficiently transmit flood warnings. In other words, the river information system 41 can automatically notify flood warnings and confirm receipt of the notifications.

[0277] Specifically, for example, in the river information system 41, local government employee U3 does not need to create or notify a flood warning. Furthermore, the river information system 41 automatically generates a receipt confirmation screen 29. This allows local government employee U3 to confirm receipt of the flood warning notification without directly contacting the relevant organization 60. Furthermore, the river information system 41 can prevent mistakes that occur when local government employee U3 creates a notification, such as incorrect entry of the notification message or failure to select the notification recipient (failure to transmit the message).

[0278] Furthermore, the internal provision server 43 receives, from the external provision server 44, receipt confirmation data indicating that the related organization 60 has received the flood warning notification in response to the external provision server 44 accessing the web page WP stored in the internal provision server 43. This allows the internal provision server 43 to obtain the receipt confirmation data from the related organization 60 even under the security constraint that data cannot be sent from the external provision server 44 to the internal provision server 43 without a request from the internal provision server 43.

[0279] According to at least one of the above-described embodiments, it is possible to provide a river information management system, a river information system, and a river information management control method that can improve the efficiency of transmitting flood warnings.

[0280] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention described in the claims and their equivalents. [Explanation of symbols]

[0281] 1...Internet, 2...CPU, 3...storage, 4...RAM, 5...communication device, 6...local network, 7...network, 7...external network, 8...related organization network, 9...firewall, 13...telemetry monitoring device, 14...Ministry of Land, Infrastructure, Transport and Tourism system, 15...Japan Meteorological Agency system, 15a...meteorological station system, 25...notification, 40...local government system, 41...river information system, 41c...automatic notification unit, 411...notification determination unit, 412...notification generation unit, 413...screen provision unit, 414...notification unit, 415...warning light control unit, 416...alert screen display unit, 417...receipt confirmation unit, 42...communication server, 43...internal provision server, 44...external provision server, 45...local government employee terminal, 46, 62...warning light, 50...prefectural resident terminal, 60...related organization, 61...stakeholder terminal, 200...river information management system.

Claims

1. A river information management system including a telemeter monitoring device, a meteorological station system, a communication server, an external provision server, and an internal provision server, the telemetry monitoring device transmits river data indicating the water level of the river to the communication server; the weather station system transmits weather data relating to at least one of a weather advisory and a weather warning to the communication server; the communication server transmits information on flood prevention to the external provision server and the internal provision server based on at least one of the river data and the meteorological data; The external provision server transmitting the information to a terminal connected to the external provision server via the Internet; receiving, from the terminal, confirmation data indicating that the information has been confirmed by a user using the terminal; When the internal provision server requests transmission of the receipt confirmation data, the internal provision server transmits the receipt confirmation data. River information management system.

2. A river information system including a communication server, an external provision server, and an internal provision server, The communication server transmits information relating to flood prevention to the external provision server and the internal provision server based on at least one of river data indicating the water level of a river and weather data relating to at least one of a weather advisory and a weather warning; The external provision server transmitting the information to a first terminal connected to the external provision server via the Internet; receiving, from the first terminal, receipt confirmation data indicating that the information has been confirmed by a user using the first terminal; When the internal provision server requests transmission of the receipt confirmation data, the internal provision server transmits the receipt confirmation data. River information system.

3. In response to receiving the receipt confirmation data, the external provision server accesses the internal provision server through communication conforming to a specific protocol; The internal provision server is In response to the external server accessing the internal provision server, requesting the external provision server to transmit the receipt confirmation data; receiving the receipt confirmation data from the external server; The river information system according to claim 2.

4. The external provision server accessing the internal provision server includes accessing a specific web page in the internal provision server. The river information system according to claim 3.

5. the internal provision server transmits the receipt confirmation data to a second terminal connected to the internal provision server via a local network; the second terminal displays information based on the receipt confirmation data. The river information system according to claim 2.

6. the external provision server further transmits the information to the first terminal if the authentication of the user is successful. The river information system according to claim 2.

7. The communication server determining whether to notify the information based on at least one of the river data and the weather data; When notifying the information, generate the information; transmitting the information to the external provision server and the internal provision server; The river information system according to claim 2.

8. The information indicates the issuance of any one of a plurality of levels of flood warnings or the cancellation of the flood warnings; The communication server When the water level and at least one of the weather advisory and the weather warning satisfy a first announcement condition among a plurality of announcement conditions corresponding to the plurality of levels, a first announcement information indicating the flood warning of a first level corresponding to the first announcement condition is generated; transmitting the first announcement information to the external provision server and the internal provision server; The river information system according to claim 7.

9. The communication server generating cancellation information indicating the cancellation of the flood warning in response to the water level and at least one of the weather advisory and the weather warning satisfying a cancellation condition corresponding to the cancellation of the flood warning; transmitting the release information to the external provision server and the internal provision server; The river information system according to claim 8.

10. The communication server generating second announcement information indicating the flood warning of the second level in response to the water level and at least one of the weather advisory and the weather warning satisfying a second announcement condition corresponding to a second level higher than the first level during the period from when the first announcement information is transmitted to when the cancellation information is transmitted; transmitting the second announcement information to the external provision server and the internal provision server; The river information system according to claim 9.

11. the first announcement condition is a condition that the water level is equal to or higher than a first reference value and a heavy rain warning has been issued, the second announcement condition is a condition that the water level is equal to or greater than a second reference value that is higher than the first reference value, and the heavy rain warning has been announced; The cancellation condition is a condition that the water level is less than the first reference value and the heavy rain warning has been cancelled. The river information system according to claim 10.

12. the first announcement condition is a condition that the water level is equal to or greater than a first reference value; the second announcement condition is a condition that the water level is equal to or greater than a second reference value that is higher than the first reference value, and a heavy rain warning has been announced; The cancellation condition is a condition that the water level is less than the first reference value and the heavy rain warning has been cancelled. The river information system according to claim 10.

13. If the water level and at least one of the weather advisory and the weather warning satisfy a third announcement condition corresponding to a third level lower than the first level during the period from when the first announcement information is transmitted to when the cancellation information is transmitted, the communication server does not generate third information indicating the flood warning of the third level. The river information system according to any one of claims 9 to 12.

14. the river data includes a first water level measured at a first observation station; the external provision server transmits the information to each of one or more third terminals, including the first terminal, that are associated with the first observation station and connected to the Internet; the internal provision server transmits the information to each of one or more fourth terminals, including the second terminal, that are associated with the first observation station and connected to a local network; The river information system according to claim 5.

15. the external provision server receives, from each of the one or more third terminals, the receipt confirmation data indicating that the information has been confirmed by a user of each of the one or more third terminals; the internal provision server receives, from each of the one or more fourth terminals, the receipt confirmation data indicating that the information has been confirmed by a user of each of the one or more fourth terminals; The river information system according to claim 14.

16. A river information management control method for controlling a river information system including a communication server, an external provision server, and an internal provision server, comprising: transmitting information relating to flood prevention from the communication server to the external provision server and the internal provision server based on at least one of river data indicating the water level of a river and weather data relating to at least one of a weather advisory and a weather warning; transmitting the information from the external provision server to a terminal connected to the external provision server via the Internet; The external provision server receives, from the terminal, receipt confirmation data indicating that the information has been confirmed by a user using the terminal; When the internal provision server requests transmission of the receipt confirmation data, the external provision server transmits the receipt confirmation data to the internal provision server. River information management and control method.

Images