Vol.5 No.2 2012

43/66

Research paper : Information sharing platform to assist rescue activities in huge disasters (I. Noda)−117−Synthesiology - English edition Vol.5 No.2 (2012) geography markup language (GML),[10] XML Schema,[11] simple object access protocol (SOAP)[12] that are related to WFS, the areas that may be lacking in sharing the disaster information are defined as additional formats.These are widely used and standardized by ISO and others, and aim to enhance the compatibility with the existing and future systems. The employment of the standard has the advantage that the existing tools can be used as is, and linkages and application with the systems other than for disaster measures can be done. Downward scalability is achieved by maintaining simplicity that allows handling by systems without large computational ability such as the sensor system.The reasons for the employment of XML as the expression format are the same as the reasons for being employed in many systems recently, i.e., universality, flexibility and expandability of the data expression. There are four basic data types including numerals (integer, real number) and text, spatial/geographic expression (point, line, and plane defined by GML), and temporal expression necessary in disaster information.Note 2) It is possible to handle diverse data structure by defining the arbitrary combination using the XML Schema. That is, any fixed-structured data not limited to disaster information can be handled, and therefore the system can be utilized for normal time routines.The protocols of MISP are shown in Fig. 4. This example defines a type of feature called ‘RoadLink’. It shows that the feature data are composed of the elements of ‘representativePoint’ described in GML, the list of crossroads (‘nodeList’) and road width (‘roadWidth’), in addition to a structure declared as ‘misp:GeometryFeature’ (defines the information element ‘gml:GeometryProperty’ for position).2.3 Mitigation information sharing database DaRuMaDaRuMa is a database developed as the prototype implementation that operates in accordance with MISP explained in subchapter 2.2. It operates as a hub to link the modules in the mitigation information sharing platform. The design and implementation of DaRuMa were conducted under the following policy. Downward scalability and multi-platformThe required specification for the operating environment was kept simple as possible, to support a wide range of OS and hardware. Since the information and communication infrastructure may be damaged in a major disaster, high-performance servers and large-scale data centers may not be available. Therefore, one of the requirements was that it would operate in various and restricted computational environments. Utilization of existing software and open sourcingThe purpose of the proposed platform was to establish the framework for information sharing during a disaster, and it was not R&D for a new database technology. Therefore, the consideration was to maximize the use of existing software and not to spend much on the development itself. Also, to establish this information sharing framework and to make the diffusion smooth, it was assumed that the results would be provided as open source.The developed DaRuMa uses MySQL, an existing relational database, or PostGISNote 3) as its backend, as shown in Fig. 5, and has a structure where mediation and conversion of SQL and MISP is done by a middleware written in Java (MISP Processor). Therefore, DaRuMa can be operated on a wide range of OS and hardware that supports Java and MySQL or PostGIS, and it was shown to run on versions of Linux, FreeBSD, Windows, and Mac OS. Moreover, there is a middleware implemented by Ruby, though this is limited in function, and this enables run on portable terminals such as Linux Zaurus, and downward scalability is achieved. The system is light, and in the demonstration experiment that will Fig. 3 Basic functions of MISP ◆Description of service (GetCapability)◆Description of data structure (DescribeFeatureType)◆Registration of data structure (RegisterFeatureType) ◆Data registration (Insert)◆Data query (GetFeature)◆Data update and delete (Update・Delete)(Query conditions)(Update･delete conditions)Meta-functionDatabase basic functionsdatadataserviceschemaschema Fig. 4 Example of data structure definition of MISP (RegisterFeatureType)

※このページを正しく表示するにはFlashPlayer9以上が必要です