Kenji SATO

Map Database Construction in Disaster Information System

In order to make prompt operations of the serious disasters which are caused by a large earthquake, storm, and flood, several Disaster Information Systems (DIS) have been introduced into different municipalities in Japan. And GIS function of DIS, especially, is helpful to visually support a good grasp of the emergency measures such as setting up the sheltered area and distributing medical supplies and emergency goods and so on. Therefore it is essential to construct a suitable map-data alignment into a DIS. Then map-data can be divided into a couple of categories from small-scale to large-scale in multiple stages. In terms of representation of the damage, each feature, e.g., facility point and road section, is given a code linking the data acquisition system where damage reports are summed. The character-based damage information are converted into tabular data that are retrieved at the displayed damage map. Consequently, the features are separated and attributed to the code related to the report unit such as jurisdiction. The overlaying processes are treated with precinct polygon layers and road line layers to make the road sections.

In this paper we illustrate the application examples and the map database construction for the DIS implemented ArcInfo.


INTRODUCTION

Japan has experienced several natural disasters which resulted in serious damages. The catastrophic tale of the grand earthquake in Kanto district (1923) has been passed down as the worst damage in the urban area, including the capital Tokyo. Furthermore the aftermath of the earthquake which took place on January 17th 1995 in Kobe, the largest trading port, made us to recognize the natural threat and the importance of emergency management.

To aim in an efficient decision making process for emergency operations such as monitoring of the damage, resource deployment and prioritizing recovery efforts, Disaster Information Systems (DIS) has been developed at several municipal governments. The system is designed to

  1. store/retrieve the basic information that provides the need data in emergency like the quantity of water supply and the capacity of hospital beds
  2. monitor the environmental circumstance including weather, water-level and seismic observations
  3. communicate from local offices to national agencies for gathering/conveying the disaster information
  4. collect/sum damage data using computer system to manipulate the information promptly.

It is important to have a proper grasp of the changing situation during a disaster. GIS has a capability to support emergency measures. It can make the situation maps combining stored location data and gathered disaster information. The maps displayed on the screen correspond to the time spans of a disaster, which are categorized as escape, rescue, emergency relief and continuing relief. In the relief period, for example, town tract and traffic regulated road layers would be selected to indicate damaged homes for each town and the route for transporting the needed materials. It would be utilized for emergency management decision making.

Although several abilities of GIS have been proposed for supporting emergency management, it is crucial for GIS to visualize the damage situation taking the numerous item into account. It is therefore necessary to display the damage maps reflected the latest information as quickly as possible in order to make a rapid recognition. This fundamental function depends upon not only hardware, but also map-data structure. For instance, subdivided tract layer like a parcel will be expected to increase a transaction process for linking to the damage data because of the number.

We have developed several GIS applications that were incorporated into DIS. Those applications called Map Information System (MIS) are based on the ArcInfo. It is a part of DIS and has focused on representing disaster situation visually. This paper will depict examples of the map database construction for the DIS.

MAP DATABASE

A good grasp of a regional situation shown on a computer screen can be displayed at multiple stages: whole prefecture, district, city/ward, and detailed map.
stage 1 - Prefecture level; scale is 1/100,000.
stage 2 - District level; scale is 1/25,000. It consists of several cities.
stage 3 - City/Ward level; scale is 1/10,000 to 25,000.
stage 4 - Map quadrangle; scale is 1/2500.

These can have effect on the following points:

  1. To make a grasp step by step those stages provide perception from macro point of view to micro point of view.
  2. Coverages can be weeded. It is important to catch a overview at upper stages so that layers can be extracted. In the road and administrative boundary layer, for example, major lines were selected and weeded.

There are two type of coverages which are stored into the MIS: Static and Active. The static coverages play a roll of showing a background. The active coverages can be changed considering attribute to reflect the damage situation data transmitted from the data acquisition system within the DIS.

The kinds of layers are different among each stage. Though some of them are common beyond stages (e.g., road line, local government office), layers are arranged to suffice needs that are depend upon the map-scale and emergency operations. School and hospital location layers, for instance, have been stored under stage 3 level because those are helpful for local response/recovery effort. The separation also results in a prompt and legible map avoiding to show the large number of those facilities (over one hundred per city/ward) on the screen.

The following is a list of the coverages implemented into the DIS.

Administrative boundary - polygon
This coverage is a basis on which disaster information map is illustrated. Each polygon in the coverage subdivided unit corresponding to each stage; stage 1 and 2, 3, 4 is city/ward/village, town tract and subdivided tract respectively. The active layer, which are upper than stage 3, represents the damage situation.

Road, River, Railway - line (polygon at stage 4)
These are static layer that makes map perceptual. Active layers were created based on these layers. Line features of the roads which will be regulated as routes for transporting emergency resource, major rivers under monitoring and railway were extracted and assigned the section linking to the data acquisition system.

Facility location - point
The following is the example type of facilities incorporated into the MIS. Facilities which are concerned in the emergency measures (e.g., bridge, school, hospital) have active attribute. The MIS can inform the status whether they are available or not.

Petrochemical complex - polygon
Like an administrative boundary layer this layer was also created to monitor the plant site.

Stage 4 maps are digital vector data derived from an urban planning division. They provide detailed perception showing house feature, symbol of land use and other topographic features. They are expected to have a household name for each house polygon. However, there are few data satisfied that condition because of their cost and time-consuming data processing. To remain the legible map on the monitor and get a good drawing performance, the displayed area at stage 4 is likely preferable less than 500m x 500m.

Prepared information for each facility and jurisdiction in DIS can have many items. The hospital data contained attributes such as name, address, phone numbers, type of consultation, the number of beds, and so on : those are over 20 items. There are also attributes that have to be updated every year. It makes database huge and needs a robust database management system with efficient transaction performance. Therefore, it is preferable to separate detail attribute from GIS database rather than contain all the attributes in each features. Consequently, each facility point and line feature in the MIS was assigned basic attributes (e.g., name, symbol number for display) and code which is common to detail attribute database.

SYSTEM FUNCTIONS

The disaster situation map can be illustrate on the computer screen with menu interface. Firstly, an area name related to stage is selected. Then damage status map like a ranking shade map representing the number of damaged houses and injured person can be displayed by clicking appropriate menu.

In each stage, it is possible to draw facility location mark and line feature over the damage status shading map so that it can make an organized damage map. For example, to prioritize rescue activity, facility location of socially weak such as a kindergarten in the school coverage, elderly and disable site in the welfare building coverage can be indicated over the shading map of home destruction.

The drawing functions are defined as follows:

Area selection: select a stage and an area name.

Background map: draw background feature and name.

Facilities location: draw mark of the location

Damage status: ranking shade map based on the report as a city/ward and subdivided town tract (detail report) unit. The damaged number of People (missing, injured), Homes (damaged, flooded, burn out) and Lifeline (power, gas, water, phone) are shaded on the administrative boundary coverage. In the detail report, damaged/recovered sections of the road/river/railway and facility points are displayed.

Recovery progress: The difference between damaged and recovered Lifeline number are shown as a ranking map on administrative boundary coverage.

In addition to those functions, the MIS has a retrieving function to identify the map feature on the screen. The name of the facility and the code can be obtained to retrieve more detail information from database.

DATA CONSTRUCTION

The damage status are reported according to jurisdiction units while those for facility are based on the name or code. They are complied into textural routine-form at city, ward, town, village government in charge at disaster time. For the road and rivers it is available to figure out the place with town tract address. This is because tract names are generally used to identify the location rather than intersection/subdivided reach names which are referred in the road/river management agency. That also makes reporting way consistent with the form using jurisdiction unit : "XXX road suffice damage from YYY town to ZZZ town"

An overlay process was treated with the administrative boundary coverage to create sections in the road/river coverage. Each section was assigned tract codes of the both sides that the section is adjacent to or through. The sequential numbers from the beginning section to the end can be illustrated using textural reports containing from/to tract name.

The road section divided by town
tract

REFLECT THE DAMAGE DATA

Active attributes which reflect the latest disaster situation were stored into a tabular data separated from map data. In other words, all active coverages have other INFO files that contains common code for connecting to each section/point feature and disaster status items. Moreover, each active coverage was assigned to each kind of the INFO file, namely Disaster Information Table (DIT), so that it could make an efficient control for manipulating the data:
  1. active coverages of different area could refer the same DIT
  2. updating process could be of easy to compare with each coverage that has the items in its PAT/AAT.

The set of DITs is also able to be stored in each directory/folder on computer disk. Actually to realize individual management for disaster several disk linking each disaster ID were created. This would be helpful to manage historically by changing a storage disk related to time periods.

For making rapid updates to the DITs, transaction modules written in FORTRAN were implemented into the MIS. The data acquisition system within DIS collects report data using town/facility name. It also synthesizes a text file that contains town/facility code extracted from the database and damage number/status. The MIS receives the file in a proper time span. Every time when the file is transmitted the modules start their task running within independent ArcInfo sessions. Hence, display task using AML/MENU can see the renewal DITs without waiting the transaction process.

In the indicating the status, RELATE function was adopted to join the DIT with active coverages. The aim to reflect the latest DITs was achieved by changing the direction to be related.

Configuration of data allocation

FUTURE WORK

We will have to explore more integrated/accurate systems adopting robust data management, GPS, color imagery viewing and other state-of-the-art tools surrounding GIS for accomplishing the goal of a comprehensive emergency management decision.

It is necessary, for instance, to maintain the freshness of socioeconomic data that are overlaid with the stricken area polygon for damage assessment. In the detail scale like stage 4, each stricken site location should be plotted in more actual position/area: an application example can be seen in the Disaster Prevention Information System of Tokyo Metropolitan Government using video imagery transmitted from helicopters. If the GPS/GIS running on the hand-held computer is applied, damage sites which are not distinguished from the sky can be gained at the field and sent into the system as quickly as possible.

GIS so far has been capable to view the imagery data. Urban planning and resource management agencies have started to combine vector map data used to be stored and aerial digital photography. For DIS as well, it is expected as the latest and rather cheap source in which decision makers can identify land cover like open space and densely built-up area at a glance. If sets of image data are used, the data store structure should be taken into account to get a tolerable speed because of the volume that might reach to gigabit order for one prefecture.

CONCLUSION

The GIS applications, incorporated into Disaster Information System, help to get a good grasp of disaster situation visually. To make a prompt operation for the system, it is available to
  1. categorize map data depend upon the scale for the indication in stages
  2. make map data sections corresponding to town tract unit
  3. separate active data with map data and
  4. manipulate active data concurrently without influence on displaying task.

We should explore the integrated system using GPS, imagery viewing and other state-of-the-art tools surrounding GIS to accomplish comprehensive emergency management decision making.

ACKNOWLEDGMENTS

The author would like to thank Mr. Masao Okajima, Dr. Mishra K. Kumar, Mr. Hideki Shimamura (PASCO Corporation) for their invaluable advice and help.

REFERENCES

Ed Biggs.(1993)"Developing a State-Wide Disaster Database For Emergency Management Planning, Response, and Recovery: Recommended Data Needs and Organizational Support structure", Proceedings of the Thirteenth Annual Esri User Conference.

Okajima,M. et al.(1991)"The Disaster Prevention Information System of Tokyo Metropolitan Government: Disaster Information and ArcInfo", Proceedings of the Eleventh Annual Esri User Conference.

Okajima Masao.(1994)"Application of Digital Aerial Photograph-Aerial Photo Retrieving System (kouku shashin kensaku system)", Journal of Japan Society of Photogrammetry and Remote Sensing, Vol 33, No 4.


Kenji SATO, System Engineer
PASCO CORPORATION, System Engineering Center
No.9-5, 4-Chome Yoyogi
Shibuya-ku, Tokyo 151, JAPAN
Telephone:+81-3-5351-5391
Fax:+81-3-3370-7817
E-mail:LDJ00701@niftyserve.or.jp