27.11.2012 Views

High Resolution 1:10,000 scale Mapping Strategy of Multi ... - NDMA

High Resolution 1:10,000 scale Mapping Strategy of Multi ... - NDMA

High Resolution 1:10,000 scale Mapping Strategy of Multi ... - NDMA

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

GIS DATABASE FOR DISASTER MANAGEMENT<br />

The data from different disciplines and agencies, as listed below, is required<br />

for disaster management process to obtain satisfactory results. Spatial and temporal<br />

data on the disastrous phenomena like landslides, floods, earthquakes their location,<br />

frequency, magnitude, etc. Data on the environment <strong>of</strong> the region like topography,<br />

geology, geomorphology, soils, hydrology, land use, vegetation etc. For more details<br />

, please refer to Annex- I.<br />

Data on elements in the region that might be affected by the disaster like<br />

infrastructure, settlements, population etc and the socioeconomic condition <strong>of</strong> the<br />

region. It can be seen that most <strong>of</strong> these data are <strong>of</strong> spatial nature, hence a GIS<br />

would not only be the most appropriate way to compile the data, but also the best<br />

platform to analyze them. A GIS database for disaster management would consist<br />

<strong>of</strong> several sets <strong>of</strong> information, as given below (Table 3.2).<br />

1 Base maps<br />

2 Remotely sensed imageries like Quickbird, IRS LISS III<br />

3<br />

4<br />

Thematic maps like, geology maps, geomorphology maps, Soil maps, Flood<br />

maps and digital terrain modeL<br />

Temporal data on disasters and their details, connectivity and<br />

communication infrastructure like roads, railways, ports, airports, helipads<br />

etc<br />

5 Hospitals and medical facilities<br />

22

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!