JP6664698B2 - Seismic intensity information providing device and seismic intensity information providing method - Google Patents

Description

  The present invention relates to a seismic intensity information providing device and a seismic intensity information providing method.

  Seismic intensity is a basic index for predicting the damage caused by earthquakes in an area or district. Also, disaster response organizations are often used as criteria for response actions. The seismic intensity of the area can be grasped if a seismic intensity meter is installed. However, seismometers are mainly installed at public institutions, research institutes, and large-scale facilities, and are not very common. In some cases, the seismic intensity cannot be determined due to going out.

  The Japan Meteorological Agency publishes an estimated seismic intensity distribution map on a website within about 30 minutes after the occurrence of an earthquake with a seismic intensity of 5 or less in Japan (Non-Patent Document 1). However, since this figure is a png (Portable Network Graphics) image file separated by seismic intensity class, the measured seismic intensity (or estimated data of seismic intensity) cannot be grasped. is there.

  The National Institute of Advanced Industrial Science and Technology (AIST) uses the Earthquake Ground Motion Map (Quick Report) / QuickMap to measure the seismic intensity when there are 10 or more data that are immediately available from the National Research and Development Agency for Disaster Prevention Science and Technology. It is published as a GeoTIFF (Geo Tagged Image File Format) file, a KML (three-dimensional geospatial information display management markup language) file, and the like (Non-Patent Document 2). However, since the measured seismic intensity values are displayed as gradations, the measured seismic intensity (or estimated seismic intensity data) at the site cannot be easily grasped visually.

  TG Information Network Co., Ltd. provides members with estimated seismic intensity data of 50m mesh for the Tokyo metropolitan area earthquake for a fee (Patent Document 1, Non-Patent Document 3). This 50m mesh seismic intensity can be scaled up and down on the map provided by the online map information service on the Internet, so that the seismic intensity class (estimated data) of the place can be grasped. I can't figure out.

  The seismic intensity is an index that quantifies the degree of the intensity of the ground motion. The seismic intensity class is a class indicating the intensity of the seismic motion. The Japan Meteorological Agency's seismic intensity class is "0", "1", "2", "3", "4", "low 5", "high 5", "low 6", "high 6" and "10". It is. The measured seismic intensity is a seismic intensity measured by the measuring seismic intensity meter, and is represented by an integer having a significant figure up to the first decimal place. The correspondence between the measured seismic intensity and the seismic intensity class is defined as, for example, seismic intensity "0" when the measured seismic intensity is less than 0.5, seismic intensity "less than 5" when 4.5 or more and less than 5.0, and "7" when the seismic intensity is 6.5 or more. Have been. The estimated seismic intensity data is a seismic intensity value estimated by performing seismic intensity interpolation estimation or liquefaction estimation calculation based on the ground basic data and raw data such as measured seismic intensity in the vicinity. Here, the raw data is information acquired by a sensor such as a measured seismic intensity meter, and includes information such as latitude and longitude, observation point name, measured seismic intensity, SI value, and maximum acceleration. The SI value is an index that quantifies how much a general building shakes due to an earthquake, and its unit is kine (cm / s).

JP-A-2002-250775

Japan Meteorological Agency, "Estimated seismic intensity distribution map", [online], [searched on December 22, 2015], Internet <URL: http: // www. data. jma. go. jp / svd / eew / data / suikei / index. html> National Institute of Advanced Industrial Science and Technology, “Earthquake Motion Map Immediate Estimation System”, [online], [searched on December 22, 2015], Internet <URL: https: // gbank. gsj. jp / QuiQuake / QuickMap / index. html> go. jp / svd / eew / data / suikei / index. html> TG Information Network Co., Ltd., “jishin.net”, [online], [searched on December 22, 2015], Internet <URL: http: /// jishin. net / point. html>

  The above-described background art of the present invention has a problem that it is sometimes difficult to grasp the measured seismic intensity (or estimated data of seismic intensity) at a target point. The present invention has been made in view of such circumstances, and provides a seismic intensity information providing apparatus and a seismic intensity information providing device that enable a user to easily grasp measured seismic intensity or estimated data of seismic intensity at a desired point. The aim is to provide a method.

  In order to solve the above-described problems, one embodiment of the present invention provides a storage unit that stores a plurality of tile image files, an earthquake ID that is an ID for identifying an earthquake, and a code that indicates any of a type of flash report, fixed, or earthquake distribution. And a plurality of fields for storing the data of the earthquake basic data, which is data including at least the data of the occurrence time of the earthquake, the epicenter position, the magnitude and the maximum seismic intensity class, and An earthquake information table having a plurality of records including at least a field for storing a storage position of the tile image file in the storage unit, a field for storing the earthquake ID type code, a field for storing a measured seismic intensity, At least one or more fields that store data representing the parcel whose seismic intensity is estimated An estimated seismic intensity distribution table having a plurality of records including: a field for storing the seismic ID type code; a field for storing the measured seismic intensity; and one or more fields for storing data representing observation points of the measured seismic intensity. A database including an observation point seismic intensity table having at least a plurality of records, seismic information data including the basic earthquake data relating to one earthquake, and an estimation including data representing a seismic intensity distribution estimated for the one earthquake When seismic intensity distribution data or observation point seismic intensity data including data representing an observation point and a measured seismic intensity measured when the one earthquake occurs is newly received, the newly received earthquake information data And, based on the estimated seismic intensity distribution data or the observation point seismic intensity data, the earthquake information table, A data registration unit that updates the contents of the measured seismic intensity distribution table or the observation point seismic intensity table, and based on the updated contents when the data registration unit updates the contents of the estimated seismic intensity distribution table or the observation point seismic intensity table A tile image file generating unit that generates a plurality of the tile image files and expands the tile image files in the storage unit; and when the earthquake information table is searched in response to an inquiry from an external user terminal and one or more earthquakes are extracted. An earthquake search unit that outputs data representing at least the earthquake ID type code and the storage location of the extracted earthquake to the user terminal; and the estimated seismic intensity distribution in response to an inquiry specifying at least the location from the user terminal. If one or more of the measured seismic intensity is extracted by searching the table or the observation point seismic intensity table, A seismic intensity information providing device comprising: a seismic intensity search unit that outputs, to the user terminal, at least data indicating the measured measured seismic intensity and the corresponding seismic ID type code.

  One embodiment of the present invention is the above-described seismic intensity information providing apparatus, wherein the tile image file has a north-south tile number or an east-west tile number of the tile image as a file name, and a directory name is the seismic ID type code. A directory name having a certain first directory as a parent directory and a second directory having a zoom level as a parent directory is stored in the third directory which is the east-west tile number or the north-south tile number, and a directory name of the tile image file is stored. A tile distribution information file including data relating to specifications is stored in the first directory, and the storage location is represented by a uniform resource locator of the tile distribution information file.

  Further, one aspect of the present invention is the above-described seismic intensity information providing device, wherein each of the records of the estimated seismic intensity distribution table stores the data representing a section in which the measured seismic intensity is estimated as the field. It includes a plurality of fields for storing the mesh code of the section, the longitude at the western end, the latitude at the southern end, the longitude at the eastern end, the latitude at the northern end, and data representing the geodetic system and the geometry in the geodetic system.

  Further, one embodiment of the present invention provides a storage unit that stores a plurality of tile image files, and an earthquake ID including an earthquake ID that is an ID for identifying an earthquake and a code that indicates any type of preliminary report, fixed, or earthquake distribution. A field for storing a type code, a plurality of fields for storing the respective data of the earthquake basic data which is data including at least the data of the occurrence time of the earthquake, the epicenter position, the magnitude and the maximum seismic intensity class, and the tile image file The earthquake information table having a plurality of records including at least a field for storing a storage position in the storage unit, a field for storing the earthquake ID type code, a field for storing the measured seismic intensity, and the measured seismic intensity are estimated. Records that include at least one or more fields that store data representing the parcels A record including at least an estimated seismic intensity distribution table, a field for storing the seismic ID type code, a field for storing the measured seismic intensity, and one or more fields for storing data representing observation points of the measured seismic intensity. Using a database including a plurality of observation point seismic intensity tables, seismic information data including the basic earthquake data for one of the earthquakes, and data representing a seismic intensity distribution estimated for the one earthquake, by a data registration unit When the estimated seismic intensity distribution data including or the observation point seismic intensity data including the data indicating the measured seismic intensity measured when the one earthquake occurs and the observation point is newly received, the newly received seismic intensity distribution data Based on the earthquake information data and the estimated seismic intensity distribution data or the observation point seismic intensity data, the earthquake information table And updating the contents of the estimated seismic intensity distribution table or the observation point seismic intensity table, and when the data registration unit updates the contents of the estimated seismic intensity distribution table or the observation point seismic intensity table by a tile image file generating unit, A plurality of the tile image files based on the updated contents are generated and developed in the storage unit, and the earthquake search unit searches the earthquake information table in response to an inquiry from an external user terminal to search for one or more earthquakes. Is extracted, data representing at least the earthquake ID type code and the storage location of the extracted earthquake is output to the user terminal, and the seismic intensity search unit responds to an inquiry specifying at least the location from the user terminal. The estimated seismic intensity distribution table or the observation point seismic intensity table is searched according to one or more of the measurement values. A method of providing seismic intensity information, wherein when seismic intensity is extracted, data representing at least the extracted measured seismic intensity and the corresponding seismic ID type code is output to the user terminal.

  According to the present invention, when the data registration unit updates the contents of the estimated seismic intensity distribution table or the observation point seismic intensity table, the tile image file generating unit generates a plurality of tile image files based on the updated contents and stores the tile image files in the storage unit. expand. Therefore, the user terminal can easily grasp the measured seismic intensity or the estimated seismic intensity distribution by performing image display using the tile image file stored in the storage unit. In addition, when the seismic intensity search unit searches the estimated seismic intensity distribution table or the observation point seismic intensity table in response to the inquiry specifying the position from the user terminal and extracts the corresponding measured seismic intensity, the seismic ID corresponding to the extracted measured seismic intensity. Information indicating at least the type code is output to the user terminal. Therefore, the measured seismic intensity or the estimated measured seismic intensity at the user terminal can be easily grasped.

It is a block diagram for explaining embodiment of the present invention. FIG. 2 is a diagram showing a configuration example of an input data file uploaded from the earthquake information registration server 4 shown in FIG. 1 to the seismic intensity information providing server 2. FIG. 3 is a diagram illustrating an example of a configuration of earthquake information data 43 illustrated in FIG. 2. FIG. 3 is a diagram illustrating a configuration example of an earthquake information data file 42 illustrated in FIG. 2. FIG. 3 is a diagram illustrating an example of a configuration of estimated seismic intensity distribution data 45 illustrated in FIG. 2. FIG. 3 is a diagram illustrating a configuration example of an estimated seismic intensity distribution data file 44 illustrated in FIG. 2. FIG. 3 is a diagram illustrating an example of a configuration of observation point seismic intensity data 48 illustrated in FIG. 2. FIG. 3 is a diagram illustrating a configuration example of an observation point seismic intensity data file 47 illustrated in FIG. 2. FIG. 2 is a diagram illustrating an example of a configuration of a tile image file generated by a tile image file generation unit 23 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an example of a tile image file generated by a tile image file generation unit 23 illustrated in FIG. 1. FIG. 2 is a diagram illustrating a storage example in a storage unit of a tile image file generated by a tile image file generation unit illustrated in FIG. 1. FIG. 12 is a diagram illustrating an example of a URL (uniform resource locator) used when the user terminal 3 illustrated in FIG. 1 acquires the tile image file 66 illustrated in FIG. 11. FIG. 12 is a diagram illustrating an example of a URL used when the user terminal 3 illustrated in FIG. 1 acquires the tile distribution information file 63 illustrated in FIG. 11. FIG. 2 is a diagram illustrating a configuration example of a database 27 illustrated in FIG. 1. FIG. 15 is a diagram illustrating a configuration example of records 11R to 14R included in tables 11 to 14 illustrated in FIG. 14. FIG. 2 is a diagram illustrating an example of input parameters to an earthquake search unit 25 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an example of output parameters of an earthquake search unit 25 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an input example to an earthquake search unit 25 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an output example of an earthquake search unit 25 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an example of input parameters to a seismic intensity search unit 26 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an example of output parameters of a seismic intensity search unit 26 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an example of output parameters of a seismic intensity search unit 26 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an example of input to a seismic intensity search unit 26 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an output example of a seismic intensity search unit 26 illustrated in FIG. 1. FIG. 2 is a diagram illustrating an output example of a seismic intensity search unit 26 illustrated in FIG. 1. 3 is a flowchart illustrating an operation example of the seismic intensity information providing server 2 illustrated in FIG. 1. FIG. 2 is a sequence diagram illustrating an operation example of the seismic intensity information providing system 1 illustrated in FIG. 1. FIG. 2 is a sequence diagram illustrating an operation example of the seismic intensity information providing system 1 illustrated in FIG. 1.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram for explaining an embodiment of the present invention. The seismic intensity information providing system 1 shown in FIG. 1 includes a seismic intensity information providing server 2, a user terminal 3, an earthquake information registration server 4, an earthquake information management server 51, a plurality of measured seismic intensity meters 52, and communication lines 53 to 56.

  The user terminal 3 is a terminal such as a personal computer, a tablet terminal, a smartphone, and a mobile phone, and accesses the seismic intensity information providing server 2 via the communication line 53 using a built-in or external communication device. The communication line 53 is a communication line configured in a wired or wireless private communication network, a public communication network, a mobile communication network, the Internet, or the like. The other communication lines 54, 55, and 56 have the same configuration as the communication line 53. The user terminal 3 communicates with the seismic intensity information providing server 2 by executing a dedicated application or application program on a predetermined OS (operating system), or by executing a general-purpose browser or mailer. Send and receive information. The user terminal 3 displays, for example, a tile image representing the seismic intensity obtained from the seismic intensity information providing server 2 on a map image obtained by accessing a map information providing server (not shown). Alternatively, the user terminal 3 accesses the seismic intensity information providing server 2 to search for an earthquake that satisfies a predetermined condition, or to search for a measured seismic intensity at a designated point or estimated data of the seismic intensity.

  The earthquake information management server 51 is a computer, receives information indicating the measured seismic intensity transmitted by a plurality of measurement seismometers 52 distributed and arranged in a certain area, and stores the information in the earthquake information management server 51. The information is stored and managed in a predetermined database not shown. Further, the earthquake information management server 51 calculates seismic intensity estimation data calculated and calculated for each tertiary mesh based on information representing the measured seismic intensity stored in a database (not shown) in the earthquake information management server 51 after the occurrence of the earthquake. It is distributed to a plurality of communication nodes such as the earthquake information registration server 4 within a predetermined time. In addition, the earthquake information management server 51 similarly converts the data indicating the measured seismic intensity measured by the measured seismic intensity meter 52 and the data specifying the observation point provided by the measured seismic intensity meter 52 (the code of the observation point, position information, etc.) The information is distributed to a plurality of communication nodes such as the information registration server 4. Here, the mesh means a section obtained by dividing a certain area into a mesh area. The tertiary mesh is a mesh that is obtained by dividing the primary mesh, which is the widest mesh in the standard area mesh system, into eight equal parts vertically and horizontally, and further dividing it into ten equal parts vertically and horizontally. . The tertiary mesh is also called a reference area mesh and is a section of about 1 km in length and width. The seismic intensity data measured at each observation point and the seismic intensity estimation data for each tertiary mesh are distributed in association with, for example, data representing an earthquake occurrence time, an epicenter location, a magnitude, a maximum seismic intensity class, and the like. You. In the present embodiment, information that specifies an earthquake of a certain size or more and indicates basic contents of the earthquake is referred to as earthquake basic data. In the present embodiment, it is assumed that the basic earthquake data includes at least information indicating an earthquake occurrence time, an epicenter position, a magnitude, and a maximum seismic intensity class. Hereinafter, the tertiary mesh is simply referred to as a mesh. The above data distributed from the earthquake information management server 51 to the earthquake information registration server 4 is collectively referred to as earthquake information.

  The earthquake information registration server 4 is a computer, and the seismic intensity data of the observation point, the seismic intensity estimation data for each tertiary mesh, and the seismic intensity data or the seismic intensity estimation received from the earthquake information managing server 51 via the communication line 55. An input data file in a predetermined format is generated based on the earthquake basic data associated with the data, and the generated input data file is uploaded to the seismic intensity information providing server 2 via the communication line. Here, an example of the configuration of an input data file that the earthquake information registration server 4 uploads to the seismic intensity information providing server 2 will be described with reference to FIGS.

  FIG. 2 shows two configuration examples of the input data file. The input data file 41 shown in FIG. 4A is a compressed file including a pair of earthquake information data files 42 and an estimated seismic intensity distribution data file 44. The earthquake information data file 42 includes earthquake information data 43 including basic earthquake data and the like regarding one earthquake. The estimated seismic intensity distribution data file 44 includes one or a plurality of estimated seismic intensity distribution data 45. Each estimated seismic intensity distribution data 45 includes estimated data of seismic intensity of each mesh and data specifying the position of the mesh. On the other hand, an input data file 46 shown in FIG. 4B is a compressed file including a pair of earthquake information data files 42 and an observation point seismic intensity data file 47. The observation point seismic intensity data file 47 includes one or more observation point seismic intensity data 48. Each observation point seismic intensity data 48 includes data for specifying the measured seismic intensity for each observation point and the observation point and its position. The input data file may have a configuration including only the earthquake information data file 42 in addition to the configuration example shown in FIG.

  FIG. 3 is a diagram for explaining an example (hereinafter, item example) 43F of items included in the earthquake information data 43 shown in FIG. 2A. FIG. 4 is a diagram showing a configuration example of the earthquake information data file 42 shown in FIG. The item example 43F shown in FIG. 3 is “earthquake ID + type”, “announcement time”, “earthquake time”, “epicenter name”, “JMA name”, “depth”, “magnitude”, “maximum seismic intensity class”. , “Maximum measured seismic intensity”, “Fixed additional sentence code”, “Tsunami presence”, “Longitude”, “Latitude”, and “Type” (preliminary report 1, seismic intensity distribution 2, confirmed 3). Here, the “earthquake ID + type” is data (hereinafter, referred to as an earthquake ID type code) including an ID (identification code) for uniquely identifying an earthquake and a type code representing the type of data. The “earthquake ID” can be composed of a combination of letters, numbers, or symbols, and is composed of, for example, a number representing the date and time of the earthquake. The “type” added to the “earthquake ID” is a file that is included in the same input data file (input data file 41 or 46 in FIG. 2) including the earthquake information data file 42 as a pair with the earthquake information data file 42. This is information indicating whether the estimated seismic intensity distribution data file 44 or the observation point seismic intensity data file 47 is used, and if it is the observation point seismic intensity data file 47, whether it is a preliminary report or a confirmed report (monthly report). In the present embodiment, the type “bnp” indicates the estimated seismic intensity distribution data file 44, the type “sok” or “kak” indicates the observation point seismic intensity data file 47, the type “sok” is a flash report, and the type “kak” is determined. Information. Note that "longitude" and "latitude" are data representing the position of the epicenter. In the example shown in FIG. 4, the earthquake information data file 42 is configured as a CSV (Comma Separated Value) file in which the items shown in FIG.

  FIG. 5 is a diagram for explaining an item example 45F included in the estimated seismic intensity distribution data 45 shown in FIG. FIG. 6 is a diagram showing a configuration example of the estimated seismic intensity distribution data file 44 shown in FIG. The item example 45F shown in FIG. 5 is “earthquake ID + type” (type: seismic intensity distribution bnp), “(third) mesh code”, “intensity class”, “measured seismic intensity”, “western longitude”, “southmost” , The longitude at the eastern end, the latitude at the northern end, and the type (seismic intensity distribution 2). The “(third) mesh code” is a code for identifying each mesh. The “longitude” at the west end or the east end and the “latitude” at the southern or northern end are data representing the positions of the corners of the mesh. In the example shown in FIG. 6, the estimated seismic intensity distribution data file 44 is configured as a CSV file in which the items shown in FIG. 5 are sequentially separated from the top by commas and arranged in one line for each mesh.

  FIG. 7 is a diagram for explaining an item example 48F included in the observation point seismic intensity data 48 shown in FIG. 2B. FIG. 8 is a diagram showing a configuration example of the observation point seismic intensity data file 47 shown in FIG. The item example 48F shown in FIG. 7 is “earthquake ID + type” (type: breaking bulletin sok, determined kak), “prefecture”, “municipalities”, “observation point name”, “observation point code”, “seismic intensity” Includes data of "class", "measured seismic intensity", "longitude", "latitude", and "type" (preliminary report 1, confirmed 3). Note that “longitude” and “latitude” are data representing the position of the observation point. In the example shown in FIG. 8, the observation point seismic intensity data file 47 is configured as a CSV file in which each data shown in FIG. 7 is sequentially separated from the top by commas and arranged in one line for each observation point.

  On the other hand, the seismic intensity information providing server 2 shown in FIG. 1 is a computer, which includes hardware such as a CPU (not shown), a storage device, and a communication device. The hardware and a storage device executed by the CPU. Each unit 21 to 28 shown in FIG. 1 is configured in combination with a stored predetermined program. The communication processing unit 21 connects to the user terminal 3 and the earthquake information registration server 4 via a communication line 53 or a communication line 54 by using a communication device (not shown), and performs an http (HyperText Transfer Protocol) or an ftp (File Transfer Protocol). ) Or data communication using e-mail. The communication processing unit 21 includes a communication device, and programs such as httpd (HyperText Transfer Protocol Daemon), ftpd (File Transfer Protocol Daemon), and a mail server. The communication processing unit 21 mediates access from the user terminal 3 to the earthquake search unit 25, the seismic intensity search unit 26, the storage unit 28, and the like, and mediates access from the earthquake information registration server 4 to the storage unit 28 and the like. .

  The data registration unit 22 uploads a new input data file (the input data file 41 or 46 shown in FIG. 2) from the earthquake information registration server 4 into a registration directory (also called a folder) set in the storage unit 28. It is monitored at a predetermined cycle whether or not it has been performed. The input data file 41 or 46 contains predetermined data on the above-mentioned earthquake. Then, when a new input data file 41 or 46 is uploaded to the registration directory, the data registration unit 22 updates the content of the database 27 via the database management unit 24 based on the content of the input data file 41 or 46. I do. The database 27 is a set of files including the earthquake ID management table 11, the earthquake information table 12, the estimated seismic intensity distribution table 13, and the observation point seismic intensity table 14 shown in FIG. It is stored in the device. Details of the configuration of the database 27 will be described later. The database management unit 24 is a program that performs processing such as searching, registering, adding, changing, and deleting files and data in the database 27. In the present embodiment, updating the content of the database 27 includes all processes such as registration, addition, change, and deletion of data in the database 27.

  The data registration unit 22 stores, for example, earthquake information data 43 including basic earthquake data relating to one earthquake, and estimated seismic intensity distribution data 45 including data representing the seismic intensity distribution estimated for the one earthquake, or the one earthquake. When the observation point seismic intensity data 48 including the data indicating the measured seismic intensity measured at the time of occurrence and the observation point is newly received, the newly received earthquake information data 43 and the estimated seismic intensity distribution data 45 Alternatively, based on the observation point seismic intensity data 48, the contents of the earthquake information table 12 and the estimated seismic intensity distribution table 13 or the observation point seismic intensity table 14 shown in FIG. The data registration unit 22 instructs the tile image file generation unit 23 to generate a tile image file in accordance with the content of the input data file 41 or 46 that has been uploaded, or stores the generated tile image file in the storage unit. 28 and store it. Further, the data registration unit 22 registers information indicating the position of the stored tile image file in the storage unit 28 in the database 27 via the database management unit 24.

  When the data registration unit 22 updates the contents of the estimated seismic intensity distribution table 13 or the observation point seismic intensity table 14, the tile image file generation unit 23 responds to an instruction from the data registration unit 22 to generate a tile based on the updated contents. A plurality of image files are generated, developed and stored in the storage unit 28. The tile image file is a file including data representing a tile image. In this embodiment, a tile image is an image created in the same tile format as a digital map image widely used on the Internet and the like, and is identified by a zoom level, an east-west tile number, a north-south tile number, and Is an image in which the measured seismic intensity and seismic intensity distribution are represented by numerals, colors, and the like. Since the numbers of the east-west tile number and the north-south tile number are assigned with the origin in the northwest corner, the position of each tile image can be grasped by a combination of the zoom level, the east-west tile number, and the north-south tile number. Each tile image can have, for example, a size of 256 pixels × 256 pixels and an image format of png. The tile image represented by the tile image file generated by the tile image file generation unit 23 can be displayed so as to be easily superimposed on the digital map image created in the tile format. Note that the tile image file generation unit 23 generates a tile image file representing a tile image. However, in the following description, the tile image file generation unit 23 may generate a tile image. Note that the position of each tile image file can be superimposed on a digital map image that is not created in a tile format by performing a predetermined coordinate conversion.

  In addition, the tile image file generation unit 23 stores the tile image file created in accordance with the layout specification 49F shown in FIG. That is, in the storage unit 28, each tile image file has a north-south tile number as a file name y, and an extension “.png” indicating an image format is added. Each tile image file is stored in the third directory x whose directory name is the east-west tile number. The parent directory of the third directory x is the second directory z whose directory name is the zoom level. The parent directory of the second directory z is the first directory whose directory name is the earthquake ID classification code. The parent directory name of the first directory is “eq”. The directory name “eq” and the directory name “earthquake ID type code” (= “earthquake ID + type”) constitute a directory for identifying an earthquake and a type. The file name y may be an east-west tile number, and the directory name of the third directory x may be a north-south tile number.

  Next, a tile image generated by the tile image file generation unit 23 will be described in detail with reference to FIG. The tile images generated by the tile image file generation unit 23 include the three types shown in FIGS. The tile image 60c shown in FIG. 10A is a color representing the value of the seismic intensity estimated for the range of each tile image (however, in FIG. 10, the difference in color is represented by the difference in shaded density). Is a tile image colored with. The tile image 60n illustrated in FIG. 10B includes a number representing the value of the seismic intensity at a position corresponding to the observation point when the observation point whose seismic intensity is observed is included in the range of the tile image. This is a tile image in which an elliptical figure 60t is drawn. The tile image 60 illustrated in FIG. 10C is a tile in which the tile image 60c illustrated in FIG. 10A and the tile image 60n illustrated in FIG. It is an image. The tile image 60 may be an image in which the tile image 60c and the tile image 60n are integrated on the same layer, or may be an image including the tile image 60c and the tile image 60n in different layers. Note that the tile image file generation unit 23 performs a process of calculating a seismic intensity corresponding to each tile image based on the seismic intensity estimated for each mesh, but this process may be performed by the data registration unit 22.

  Further, the tile image file generation unit 23 creates a tile distribution information file indicating the tile distribution information of the tile image file for each earthquake ID type code. The tile distribution information is data used when a tile image is overlaid on a map image in a tile format. The tile distribution information includes data relating to the specification of the tile image file, such as the specification name and version name indicating the specification of the corresponding map image, the code of the coordinate system, and the like. The tile image file generation unit 23 stores the created tile distribution information file in, for example, the first directory described with reference to FIG. 9 in which the directory name storing the tile image file is “earthquake ID type code”. FIG. 11 shows an example of the arrangement of the tile distribution information file in the storage unit 28. In this case, a plurality of first directories 62 whose directory names are earthquake ID classification codes are arranged below the directory 61 whose directory name is “eq”. Under one first directory 62, one tile distribution information file 63 and a second directory 64 having a plurality of directory names at a zoom level are arranged. A third directory 65 having a plurality of directory names of east and west tile numbers is arranged under one second directory 64. Under one third directory 65, a plurality of tile image files 66 whose file names are the north-south tile numbers are arranged. Note that, in the example shown in FIG. 11, the file name of the tile distribution information file 63 is “WMTSCapabilities”. The extension is xml. WMTS indicates OpenGIS Web Map Tile Service, and indicates that the tile distribution information file 63 is described in the WMTS specification. The extension xml indicates that the file format is XML (Extensible Markup Language). FIG. 12 shows an example of the URL of the tile image file 66 shown in FIG. FIG. 13 shows an example of the URL of the tile distribution information file 63 shown in FIG. 12 and 13, “example.com” is the domain name of the seismic intensity information providing server 2 (or the communication processing unit 21).

  Next, an example of the configuration of the database 27 shown in FIG. 1 will be described with reference to FIGS. As shown in FIG. 14, the database 27 includes the earthquake ID management table 11, the earthquake information table 12, the estimated seismic intensity distribution table 13, and the observation point seismic intensity table 14. The earthquake ID management table 11 includes a plurality of records 11R shown in FIG. Each record 11R includes a field 11F1 for storing an earthquake ID type code (= earthquake ID + type). The earthquake information table 12 includes a plurality of records 12R shown in FIG. Each record 12R includes fields 12F1 to 12F18. Fields 12F1 to 12F18 are, respectively, an earthquake ID type code (= earthquake ID + type), presentation time, earthquake time, epicenter name, JMA name, depth (km), magnitude, maximum seismic intensity class, maximum measured seismic intensity, and fixed addition. It stores sentence code, tsunami presence, longitude, latitude, type, geodetic system, tile URL, epicenter location, and data range. The tile URL stored in the field 12F16 is data indicating the storage position of the tile image file in the storage unit 28. For example, the field 12F16 may store the URL of the tile distribution information file shown in FIG. it can.

  The estimated seismic intensity distribution table 13 includes a plurality of records 13R shown in FIG. Each record 13R includes fields 13F1 to 13F11. The fields 13F1 to 13F11 are respectively an earthquake ID type code (= earthquake ID + type), a mesh code, a seismic intensity class, a measured seismic intensity, a west longitude, a south latitude, an east longitude, a north latitude, a type, a geodetic system, and Each data of geometry (latitude and longitude in the geodetic system concerned) is stored. The observation point seismic intensity table 14 includes a plurality of records 14R shown in FIG. Each record 14R includes fields 14F1 to 14F12. The fields 14F1 to 14F12 respectively contain an earthquake ID type code (= earthquake ID + type), prefecture, city, town, village, observation point name, observation point code, seismic intensity class, measured seismic intensity, longitude, latitude, geodetic system, type, and Each position data is stored.

  Next, the earthquake search unit 25 shown in FIG. 1 will be described with reference to FIGS. FIGS. 16 and 17 are diagrams illustrating examples of input and output parameters to the earthquake search unit 25, respectively. 18 and 19 are diagrams illustrating an example of input from the user terminal 3 to the earthquake search unit 25 and an example of output from the earthquake search unit 25 to the user terminal 3, respectively. The earthquake search unit 25 searches the earthquake information table 12 in the database 27 using the database management unit 24 in response to an inquiry from the external user terminal 3 via the communication processing unit 21 and searches for one or more earthquakes. This is a program that, when extracted, outputs data representing at least the earthquake ID type code of the extracted earthquake and the tile URL to the user terminal 3. The earthquake search unit 25 operates as an interface (also called an API (Application Programming Interface)) for using the search function for the database 27 from the user terminal 3.

  In the example shown in FIG. 16, the input parameters of the earthquake search unit 25 are “n”, “from”, “to”, “minmag”, “maxmag”, “minsi”, “maxsi”, “mindepth”, “mindepth”. “maxdepth”, “extent”, “epicenter”, “eqname”, “tsusunami”, “type”, “format”, “id”, “sort”, and “callback”. The contents of each parameter are as follows. “N” indicates the number of earthquakes to be searched. “From” indicates a search start date. “To” indicates a search end date. “Minmag” indicates to search for earthquakes of magnitude greater than or equal to minmag. "Maxmag" indicates to search for earthquakes of magnitude less than or equal to maxmag. “Minsi” indicates that an earthquake having a maximum measured seismic intensity equal to or greater than minsi is searched. “Maxsi” indicates that an earthquake having a maximum measured seismic intensity less than or equal to maxsi is searched. “Mindepth” indicates that an earthquake having a depth equal to or more than the mindepth is searched. “Maxdepth” indicates that an earthquake having a depth equal to or less than maxdepth is searched. “Extent” indicates a search range of an earthquake (central position). Designated by "xmin", "ymin", "xmax", "ymax". “Epicenter” indicates the epicenter name (partial match). “Eqname” indicates an earthquake name (partially coincident). “Tsunami” indicates the presence or absence of a tsunami (0 | 1). "Type" indicates a data type (all: 0 | observation point seismic intensity (breaking news): 1 | seismic intensity distribution: 2 | observation point seismic intensity (determined): 3). “Format” indicates an output format (GML | GeoJSON). “Id” indicates an earthquake ID (excluded from parameters other than format, type, and sort) (forward match). “Sort” indicates the sort order of the results (newest seismic time: 1 | largest magnitude: 2 | maximum seismic intensity: 3 | newest time: newest: 4) (reverse order if negative). “Callback” indicates a function for callback (when GeoJSON is specified). GML (Geography Markup Language) is an XML-based markup language for describing geographic features such as spatial data and position information. GeoJSON is a geospatial data exchange format.

  In the example illustrated in FIG. 17, the output parameters of the earthquake search unit 25 are “eqid”, “informed_time”, “occurred_time”, “epcinter_name”, “eq_name”, “depth”, “magnitude”, “max_si”, and “max_si”. “max_measured_si”, “additional_code”, “tsunami”, “type”, “tile_url”, “geometry”, and “extent”. The contents of each parameter are as follows. “Equid” indicates an earthquake ID type code (= earthquake ID + type). “Informed_time” indicates the announcement time. “Occurred_time” indicates the focal time. “Epcinter_name” indicates the epicenter name. “Eq_name” indicates the name of the Japan Meteorological Agency. “Depth” indicates a depth (km). “Magnitude” indicates the magnitude. “Max_si” indicates the maximum seismic intensity class. "Max_measured_si" indicates the maximum measured seismic intensity. “Additional_code” indicates a fixed additional sentence code. “Tsunami” indicates the presence or absence of a tsunami. “Type” indicates a type. “Tile_url” indicates a tile URL. “Geometry” indicates the epicenter longitude and latitude. “Extent” indicates a data range.

  As shown in FIG. 18, the inquiry from the user terminal 3 to the earthquake search unit 25 is performed by accessing the URL 73 that describes the input parameters after the domain name “example.com” and “/search/eq.php?”. be able to. If default values are set for some parameters, all input parameters can be omitted. FIG. 19 shows an example of a file 74 output from the earthquake search unit 25 to the user terminal 3. As shown in FIG. 19, the file 74 indicates data ““ eqid ”:“ 2011103111446618kak ”” indicating the earthquake ID type code, and a tile URL indicating a storage position in the storage unit 28 of the tile image file. "" Tile_url ":" http: $ / $ / example. com / eq / 20110311144618kak / WMTSCapabilities.com. xml "" is included.

  Next, the seismic intensity search unit 26 shown in FIG. 1 will be described with reference to FIGS. FIG. 20 is a diagram illustrating an example of input parameters to the seismic intensity search unit 26. FIG. 21 and FIG. 22 are diagrams illustrating an example of output parameters from the seismic intensity search unit 26. FIG. 23 is a diagram showing an example of an input from the user terminal 3 to the seismic intensity search unit 26. FIGS. 24 and 25 are diagrams illustrating an example of output from the seismic intensity search unit 26 to the user terminal 3. The seismic intensity search unit 26 is a program, for example, an estimated seismic intensity distribution table in the database 27 using the database management unit 24 in response to an inquiry specifying at least a position from the external user terminal 3 via the communication processing unit 21. 13 or the observation point seismic intensity table 14 is searched. The inquiry to the seismic intensity search unit 26 includes an inquiry about the estimated seismic intensity for the mesh including the designated position (this is referred to as an estimated seismic intensity distribution inquiry) and a measurement at the observation point closest to the designated position. There is an inquiry about the seismic intensity (including two types: breaking news and confirmation). In the inquiry to the seismic intensity search unit 26, for example, the seismic intensity corresponding to the designated position may be searched for a plurality of earthquakes. In addition, the search range of the observation point seismic intensity can have an upper limit in terms of distance. That is, when there is no observation point within, for example, 50 km from the designated place, data can not be output. The seismic intensity search unit 26 searches the estimated seismic intensity distribution table 13 for the inquiry of the estimated seismic intensity distribution, or searches the observation point seismic intensity table 14 for the inquiry of the observation point seismic intensity, and retrieves one or more measured seismic intensity (observed intensity). (Including the value and the estimated value), the data representing at least the extracted measured seismic intensity and the corresponding earthquake ID type code are output to the user terminal 3. It is not always necessary to specify the position when making an inquiry to the seismic intensity search unit 26 every time an inquiry is made. For example, it is possible to designate a position at the time of first use or registration of use, and to omit the position designation at the time of inquiry. The seismic intensity search unit 26 also operates as an interface (API) for using the search function for the database 27 from the user terminal 3, similarly to the earthquake search unit 25.

  In the example shown in FIG. 20, the input parameters of the seismic intensity search unit 26 are “lonlat”, “type”, “id”, “format”, and “callback”. The contents and default values of each parameter are as follows. “Lonlat” indicates the longitude / latitude (world geodetic system) of the search position (separated by a comma in the order of longitude and latitude), and there is no default value. “Type” indicates the data type (observation point seismic intensity (flash): 1 | seismic intensity distribution: 2 | observation point seismic intensity (determined): 3), and the default value is 2. “Id” indicates an earthquake ID (front match), and the default value is the latest earthquake ID. “Format” indicates the output format (GML | GeoJSON), and the default value is GeoJSON. “Callback” indicates a function for callback (when GeoJSON is specified), and there is no default value. In this case, the input parameter items to the seismic intensity search unit 26 are the same for the inquiry about the estimated seismic intensity distribution and the inquiry about the observation point seismic intensity. In addition, a plurality of earthquakes can be searched at once by designating several characters in front of an appropriate earthquake ID in the input parameter “id”.

  In the example shown in FIG. 21, the output parameters of the seismic intensity search unit 26 at the time of inquiring the estimated seismic intensity distribution are “eqid”, “si”, “measured_si”, and “geometry”. “Equid” is an earthquake ID type code (= earthquake ID + type), and the type is seismic intensity distribution “bnp”. "Si" indicates the seismic intensity class. “Measured_si” indicates the measured seismic intensity. “Geometry” indicates the point inquired, and the same data as “lonlat” specified by the input parameter is output.

  In the example illustrated in FIG. 22, the output parameters of the seismic intensity search unit 26 at the time of querying the observation point seismic intensity are “equid”, “pref”, “city”, “station_name”, “station_code”, “si”, and “measured_si”. , "Type", "distance", and "geometry". “Equid” indicates an earthquake ID type code (= earthquake ID + type), and the type is a bulletin “sok” or a fixed “kak”. “Pref” indicates a prefecture. “City” indicates a municipality. “Station_name” indicates an observation point name. “Station_code” indicates an observation point code. "Si" indicates the seismic intensity class. “Measured_si” indicates the measured seismic intensity. “Type” indicates the type, and is “1” or “3”. “Distance” indicates the distance (m) between the observation point and the input point. “Geometry” indicates the point inquired, and the same data as “lonlat” specified by the input parameter is output.

  As shown in FIG. 23, an inquiry from the user terminal 3 to the seismic intensity search unit 26 is performed by accessing a URL 75 describing an input parameter after the domain name “example.com” and “/search/si.php?”. be able to. FIG. 24 shows an example of a file 76 output from the seismic intensity search unit 26 to the user terminal 3 when inquiring about the observation point seismic intensity. As shown in FIG. 24, the file 76 includes data ““ equid ”:“ 2011103114144618kak ”” indicating the earthquake ID type code and data ““ mesured_si ”: 5.500000” indicating the measured seismic intensity. Have been. FIG. 25 shows an example of a file 77 output from the seismic intensity search unit 26 to the user terminal 3 when inquiring the estimated seismic intensity distribution. As shown in FIG. 25, the file 77 includes data ““ equid ”:“ 2011103114144640bnp ”” indicating the earthquake ID type code, and data ““ mesured_si ”: 5.300000” indicating the measured seismic intensity. Have been.

  Next, an operation example of the seismic intensity information providing server 2 shown in FIG. 1 will be described with reference to FIG. FIG. 26 is a flowchart showing the flow of processing when registering new data and generating a tile image file in the seismic intensity information providing server 2 shown in FIG. The process shown in FIG. 26 is executed at regular intervals. When the process shown in FIG. 26 is started, the data registration unit 22 determines whether a new input data file (input data file 41 or 46 (FIG. 2)) has been uploaded to a predetermined registration directory in the storage unit 28. It is determined whether or not uploading has been completed, and if the data has not been uploaded, the process ends (NO in step S101). On the other hand, if the input data file has been uploaded (YES in step S101), the data registration unit 22 decompresses and decompresses the newly uploaded input data file in a predetermined decompression directory in the storage unit 28, and decompresses it. The previous input data file is deleted (step S102).

  Next, the data registration unit 22 checks whether or not the expanded input data file includes the earthquake information data 43 (Step S103). If the earthquake information data 43 is included (YES in step S103), the data registration unit 22 registers the earthquake ID type code included in the earthquake information data 43 in the earthquake ID management table 11 via the database management unit 24. (Step S104). If the same earthquake ID type code has already been registered in the earthquake ID management table 11, the data registration unit 22 replaces the existing data with the existing data. Next, the data registration unit 22 registers each data included in the earthquake information data 43 in the earthquake information table 12 via the database management unit 24 (Step S105).

  Next, when the processing of step S105 is completed or when the earthquake information data 43 is not included (NO in step S103), the data registration unit 22 stores the estimated seismic intensity distribution data 45 in the expanded input data file. Is checked (step S106). If the estimated seismic intensity distribution data 45 is included (YES in step S106), the data registration unit 22 sends the earthquake ID type code included in the estimated seismic intensity distribution data 45 via the database management unit 24 to the earthquake ID management table 11. (Step S107). If the same earthquake ID type code has already been registered in the earthquake ID management table 11, the data registration unit 22 replaces the existing data with the existing data. Next, the data registration unit 22 registers each data included in the one or more estimated seismic intensity distribution data 45 via the database managing unit 24 in the estimated seismic intensity distribution table 13 (Step S108).

  Next, when the processing of step S108 is completed or when the estimated seismic intensity distribution data 45 is not included (NO in step S106), the data registration unit 22 stores the observation point seismic intensity data in the expanded input data file. It is checked whether or not 48 is included (step S109). If the observation point seismic intensity data 48 is included (YES in step S109), the data registration unit 22 sends the earthquake ID type code included in the observation point seismic intensity data 48 via the database management unit 24 to the earthquake ID management table 11 (Step S110). If the same earthquake ID type code has already been registered in the earthquake ID management table 11, the data registration unit 22 replaces the existing data with the existing data. Next, the data registration unit 22 registers each data included in the one or more observation point seismic intensity data 48 in the observation point seismic intensity table 14 via the database management unit 24 (Step S111).

  Next, when the processing of step S111 is completed, or when the observation point seismic intensity data 48 is not included (NO in step S109), the data registration unit 22 stores the estimated seismic intensity distribution data 45 or the observation point seismic intensity data. It is confirmed whether or not 48 has been registered in the database 27 (step S112). If the estimated seismic intensity distribution data 45 or the observation point seismic intensity data 48 has been registered in the database 27 (YES in step S112), the data registration unit 22 instructs the tile image file generation unit 23 to generate and arrange a tile image file. Then, the tile image file generation unit 23 generates and arranges the tile image file 66 (FIG. 11) (Step S113). Next, the data registration unit 22 instructs the tile image file generation unit 23 to generate and arrange the tile distribution information file, and the tile image file generation unit 23 generates and arranges the tile distribution information file 63 (FIG. 11) ( Step S114). Next, the data registration unit 22 registers the URL of the tile distribution information file 63 in the earthquake information table 12 via the database management unit 24 (Step S115). When the process in step S115 is completed, or when the estimated seismic intensity distribution data 45 or the observation point seismic intensity data 48 is not registered in the database 27 (NO in step S112), the process ends.

  Next, an operation example of the seismic intensity information providing system 1 shown in FIG. 1 will be described with reference to FIG. FIG. 27 is a sequence diagram showing a flow of processing when registering new data in the seismic intensity information providing server 2 and generating a tile image file in the seismic intensity information providing system 1 shown in FIG.

  When new earthquake information is distributed from the earthquake information management server 51 shown in FIG. 1 to the earthquake information registration server 4 (step S201), the earthquake information registration server 4 creates the input data file 41 or 46 (step S202). . Next, the earthquake information registration server 4 uploads the created input data file 41 or 46 to the registration directory of the storage unit 28 via the communication processing unit 21 in the seismic intensity information providing server 2 (Steps S203 to S204). Next, the data registration unit 22 detects the upload of the input data file 41 or 46 (Step S205). Next, the data registration unit 22 develops the input data file 41 or 46 (Steps S206 to S207).

  Next, the data registration unit 22 updates the contents of the database 27 via the database management unit 24 based on the contents of the expanded input data file 41 or 46 (Steps S208 to S209). Further, the data registration unit 22 instructs the tile image file generation unit 23 to generate and arrange the tile image file 66 and the tile distribution information file 63 based on the contents of the developed input data file 41 or 46, The file generation unit 23 generates and arranges the tile image file 66 and the tile distribution information file 63 (Steps S210 to S213). Next, the data registration unit 22 registers the URL indicating the storage location of the tile distribution information file 63 in the database 27 via the database management unit 24 (Steps S214 to S215).

  Next, another operation example of the seismic intensity information providing system 1 shown in FIG. 1 will be described with reference to FIG. FIG. 28 is a sequence diagram showing a flow of processing when information is provided from the seismic intensity information providing server 2 to the user terminal 3 in the seismic intensity information providing system 1 shown in FIG.

  In the case of searching for an earthquake (earthquake search input, step S301), when the user terminal 3 queries the seismic intensity information providing server 2 for the occurrence time of the earthquake, the epicenter location, the magnitude, the maximum seismic intensity, etc., the user terminal 3 The communication processing unit 21 that has received the inquiry from transmits the inquiry parameter to the earthquake search unit 25 (step S302). Next, the earthquake search unit 25 searches the database 27 via the database management unit 24 (Steps S303 to S304). Next, upon receiving the search result from the database management unit 24 (steps S305 to S306), the earthquake search unit 25 outputs an output file including the corresponding earthquake ID and data indicating its data based on the received search result. 74 is generated and transmitted to the user terminal 3 via the communication processing unit 21 (steps S307 to S308).

  When the seismic intensity is searched (seismic intensity search input, step S309), when the user terminal 3 inquires the seismic intensity information providing server 2 about the seismic ID and the latitude / longitude position as search parameters, the inquiry from the user terminal 3 is received. The communication processing unit 21 transmits an inquiry parameter to the seismic intensity search unit 26 (Step S310). Next, the seismic intensity search unit 26 searches the database 27 via the database management unit 24 (steps S311 to S312). Next, when the seismic intensity search unit 26 receives the search result from the database management unit 24 (steps S313 to S314), the measured seismic intensity of the specified earthquake of the tertiary mesh including the specified latitude and longitude position based on the received search result (Estimated data) or an output file 77 or 76 including data indicating the measured seismic intensity of the specified earthquake at the observation point closest to the specified latitude / longitude position is generated. The data is transmitted to the terminal 3 (steps S315 to S316).

  Further, when the tile distribution information file 63 is acquired (the tile distribution information file request, step S317), the user terminal 3 accesses the URL of the tile distribution information file 63 received in step S308, and It can be obtained (steps S318 to S320).

  Further, when the tile image file 66 is acquired (the tile image file request, step S321), the user terminal 3 determines the data and the user in the tile distribution information file 63 based on the URL of the tile distribution information file 63 received in step S308. The tile image file 66 can be obtained by accessing the URL of the desired tile image file 66 determined according to the instruction (steps S321 to S324).

  As described above, according to the embodiment of the present invention, when the data registration unit 22 updates the contents of the estimated seismic intensity distribution table 13 or the observation point seismic intensity table 14, the tile image file generating unit 23 updates the updated contents. A plurality of tile image files 66 based on the image data are generated and expanded in the storage unit 28. Therefore, the user terminal 3 can easily grasp the measured seismic intensity or the estimated seismic intensity distribution by displaying an image using the tile image file 66 stored in the storage unit 28. In addition, when the seismic intensity search unit 26 searches the estimated seismic intensity distribution table 13 or the observation point seismic intensity table 14 in response to an inquiry specifying a position from the user terminal 3 and extracts a corresponding measured seismic intensity, the extracted measured seismic intensity is used. Information indicating at least the corresponding earthquake ID type code is output to the user terminal 3. Therefore, the measured seismic intensity or the estimated measured seismic intensity in the user terminal 3 can be easily grasped.

  In the above-described embodiment, the tile image file 66 is a directory name having the north-south tile number or the east-west tile number of the tile image as a file name and the first directory 62 whose directory name is an earthquake ID classification code as a parent directory. Is stored in the third directory 65, which is the east-west tile number or the north-south tile number, with the second directory 64 having the zoom level as the parent directory, and the tile distribution information file 63 including the data related to the specification of the tile image file is stored. The location information represented by the URL of the tile distribution information file 63 is stored in a field 12F16 which is stored in the first directory 62 and stores the tile URL of each record 12R of the earthquake information table 12. Therefore, the user terminal 3 can easily access the plurality of tile image files 66.

  In the above-described embodiment, each record 13R of the estimated seismic intensity distribution table 13 includes, as fields for storing data representing the segment for which the estimated seismic intensity is estimated, the mesh code of the segment, the longitude at the western end, the latitude at the southern end, and the eastern end. And a plurality of fields for storing data representing the longitude, the latitude at the northern end, and the geodetic system and the geometry in the geodetic system (such as the latitude and longitude in the geodetic system). That is, a plurality of types of information representing the positions of the sections (mesh) are registered in the database 27. Therefore, in the user terminal 3, the position of the mesh, which is the estimation unit of the estimation data of the seismic intensity, can easily correspond to various use environments.

  The embodiment of the present invention is not limited to the above. For example, the seismic intensity information providing server 2 and the earthquake information registering server 4 may be integrally configured, or the seismic intensity information providing server 2 and the earthquake information registering server 4 may be servers that are virtually configured on a cloud. May be used.

  In the above-mentioned seismic intensity information providing system 1, the seismic intensity information providing server 2 automatically inquires from the user terminal 3 to the seismic intensity searching unit 25 and the seismic intensity searching unit 26, which are configured as APIs, and sends the result by e-mail. It is possible to perform automatic distribution by using the method described above. In this case, for example, as soon as an earthquake occurs and the estimated seismic intensity data is registered, the measured seismic intensity (estimated value) at the location can be quickly grasped without going through a complicated operation procedure of the browsing application. In addition, even if a seismic intensity meter is not installed, the measured seismic intensity (estimated value) at an arbitrary latitude and longitude position can be grasped. In addition, it is possible to grasp the measured seismic intensity (estimated value) at a remote place that is not present. Also, by appropriately combining the tile image of the estimated seismic intensity distribution map distributed by http with the seismic intensity search API (seismic intensity search unit 26), the estimated seismic intensity distribution map is displayed on the browsing application so as to be superimposed on the map information and enlarged. By scrolling down and clicking on any position, you can grasp the measured seismic intensity (estimated value) at that position.

1 Seismic intensity information providing system 2 Seismic intensity information providing server 3 User terminal 4 Earthquake information registration server 11 Earthquake ID management table 12 Earthquake information table 13 Estimated seismic intensity distribution table 14 Observation point seismic intensity table 21 Communication processing unit 22 Data registration unit 23 Tile image file generation Unit 24 database management unit 25 earthquake search unit 26 seismic intensity search unit 27 database 28 storage unit 51 earthquake information management server 52 measurement seismometer 60, 60c, 60n tile images 61, 62, 64, 65 directory 63 tile distribution information file 66 tile image File

Claims (4)

A storage unit for storing a plurality of tile image files,
A field for storing an earthquake ID type code consisting of an earthquake ID, which is an ID for identifying an earthquake, and a code indicating any type of preliminary report, confirmed or earthquake distribution, and a time, source location, magnitude, and maximum seismic intensity of the earthquake An earthquake having a plurality of records including at least a plurality of fields for storing the respective data of the earthquake basic data which is data including at least each class data, and a field for storing a storage position of the tile image file in the storage unit. An information table,
An estimated seismic intensity distribution table having a plurality of records including at least a field for storing the earthquake ID type code, a field for storing the measured seismic intensity, and one or a plurality of fields for storing data representing a section in which the measured seismic intensity is estimated. When,
An observation point seismic intensity table having a plurality of records including at least a field for storing the earthquake ID type code, a field for storing the measured seismic intensity, and one or more fields for storing data representing observation points of the measured seismic intensity; A database containing
Seismic information data including the basic earthquake data for one of the earthquakes, and estimated seismic intensity distribution data including data representing an estimated seismic intensity distribution for the one earthquake, or measured when the one earthquake occurs When the observation point seismic intensity data including the data indicating the measured seismic intensity and the observation point is newly received, based on the newly received earthquake information data and the estimated seismic intensity distribution data or the observation point seismic intensity data. A data registration unit that updates the content of the estimated seismic intensity distribution table or the observation point seismic intensity table,
When the data registration unit updates the contents of the estimated seismic intensity distribution table or the observation point seismic intensity table, a tile image file generating unit that generates a plurality of the tile image files based on the updated contents and expands the tile image files in the storage unit When,
When the earthquake information table is searched and one or more earthquakes are extracted in response to an inquiry from an external user terminal, the data representing at least the earthquake ID type code and the storage location of the extracted earthquake is stored in the user. An earthquake search unit that outputs to the terminal,
When the estimated seismic intensity distribution table or the observation point seismic intensity table is searched and at least one of the measured seismic intensity is extracted in response to an inquiry specifying at least a position from the user terminal, the seismic ID corresponding to the extracted measured seismic intensity. And a seismic intensity search unit that outputs data representing at least a type code to the user terminal. The tile image file has a north-south tile number or an east-west tile number of the tile image as a file name, a first directory whose directory name is the earthquake ID classification code as a parent directory, and a second directory whose directory name is a zoom level. Is stored in a third directory which is the east-west tile number or the north-south tile number,
A tile distribution information file including data relating to the specification of the tile image file is stored in the first directory,
The seismic intensity information providing device according to claim 1, wherein the storage location is represented by a uniform resource locator of the tile distribution information file. The records each having the estimated seismic intensity distribution table, as the field for storing the data representing the section for which the measured seismic intensity is estimated, the mesh code of the section, the west end longitude, the south end latitude, the east end longitude, the north end The seismic intensity information providing device according to claim 1, further comprising a plurality of fields for storing latitude and data representing a geodetic system and a geometry in the geodetic system. A storage unit for storing a plurality of tile image files,
A field for storing an earthquake ID type code consisting of an earthquake ID, which is an ID for identifying an earthquake, and a code indicating any type of preliminary report, confirmed or earthquake distribution, and a time, source location, magnitude, and maximum seismic intensity of the earthquake An earthquake having a plurality of records including at least a plurality of fields for storing the respective data of the earthquake basic data, which is data including at least each class data, and a field for storing a storage position of the tile image file in the storage unit. An information table,
An estimated seismic intensity distribution table having a plurality of records including at least a field for storing the earthquake ID type code, a field for storing the measured seismic intensity, and one or a plurality of fields for storing data representing a section in which the measured seismic intensity is estimated. When,
An observation point seismic intensity table having a plurality of records including at least a field for storing the earthquake ID type code, a field for storing the measured seismic intensity, and one or more fields for storing data representing observation points of the measured seismic intensity; Using a database with and
The data registration unit has generated the earthquake information data including the basic earthquake data and the estimated seismic intensity distribution data including the data representing the seismic intensity distribution estimated for the one earthquake, or the one earthquake has occurred. When the observation point seismic intensity data including the data representing the measured seismic intensity and the observation point measured at the time is newly received, the newly received earthquake information data, the estimated seismic intensity distribution data or the observation point Based on the seismic intensity data, update the contents of the earthquake information table and the estimated seismic intensity distribution table or the observation point seismic intensity table,
When the data registration unit updates the contents of the estimated seismic intensity distribution table or the observation point seismic intensity table, the tile image file generating unit generates a plurality of the tile image files based on the updated contents and stores the tile image file in the storage unit. Expand,
When an earthquake search unit searches the earthquake information table in response to an inquiry from an external user terminal and extracts one or more earthquakes, at least the earthquake ID type code and the storage position of the extracted earthquake are determined. Outputting data to the user terminal,
The seismic intensity search unit searches the estimated seismic intensity distribution table or the observation point seismic intensity table in response to an inquiry specifying at least the position from the user terminal and extracts one or more of the measured seismic intensities. A seismic intensity information providing method for outputting data representing at least the corresponding earthquake ID type code to the user terminal.

Images