WebSAFE: Developing an Online Exposure and Risk Assessment Tool for the Philippines
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 183 | |
| Author | ||
| License | CC Attribution - NonCommercial - ShareAlike 3.0 Germany: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this | |
| Identifiers | 10.5446/31995 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language | ||
| Producer | ||
| Production Year | 2015 | |
| Production Place | Seoul, South Korea |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
00:00
Hazard (2005 film)Extension (kinesiology)Customer relationship managementPopulation densityWebsiteState of matterSoftware developerProjective planeBuildingExtreme programmingSubject indexingTexture mappingTraffic reportingMathematical analysisOpen sourceDenial-of-service attackCASE <Informatik>TrailModal logicObservational studyComputer programmingChannel capacitySound effectWeb applicationRevision controlAnalytic continuationFocus (optics)MappingVulnerability (computing)InformationNoise (electronics)Web 2.0Bus (computing)Form (programming)AverageBitComputer animation
07:08
MappingAreaBitHazard (2005 film)EstimatorDisk read-and-write headWeb 2.0Process (computing)Software frameworkAverageBootstrap aggregatingInstance (computer science)Different (Kate Ryan album)Open sourceUniform resource locatorTexture mappingServer (computing)Denial-of-service attackWeb browserCodeDatabaseSlide ruleWebsiteSubsetDependent and independent variablesRevision controlVarianceBuildingSoftware developeroutputElectric generatorProjective planeMenu (computing)Sound effectCurvatureCycle (graph theory)Drop (liquid)Right angleSoftwareCore dumpCalculationPopulation densitySampling (statistics)Traffic reportingConnectivity (graph theory)Phase transitionSoftware testingOverlay-NetzWeb applicationArithmetic meanDemo (music)Beta functionMereology
14:12
CalculationPattern languageTexture mappingCoordinate systemTelecommunicationConnectivity (graph theory)Presentation of a groupFood energyMultiplication signLevel (video gaming)DatabaseHazard (2005 film)MappingMereologyResultantInformationBuildingDifferent (Kate Ryan album)System callPopulation densityLimit (category theory)Server (computing)Front and back endsBitMathematical analysisGenderTraffic reportingMetreCustomer relationship managementGroup actionSoftware developerType theoryOnline helpRoundness (object)Computer animation
21:16
Computer animation
Transcript: English(auto-generated)
00:04
Good afternoon. First, let me introduce myself. You can see in the slide, I'm Ramon Aiko, Jr., but you can call me Ayo. I'm from the Philippines, and as our chair said, we are
00:20
colleagues. We work at the project funded by the Department of Science and Technology. We call it Project NOA. I'm going to talk about that a little bit, but actually there will be another session about Project NOA later in the next session. So, I have some interesting things
00:46
for you this afternoon. We are really proud of it. We call it Web Safe. We like to think of it as an online exposure and risk assessment tool. But before we go into the details of
01:02
that, I would like to give you a picture of what it's like in the Philippines when it comes to disaster management and mitigation. So here is an animation, a GIF, of all the tracks of typhoons from the 50s up to the 90s. So if we wait a little bit, we will see that
01:28
almost all of the country is covered by typhoons, and actually we have around 20 to 25 on the average typhoons per year. So disaster management is a big thing. I mean,
01:46
it's a necessity in our country. So disaster. What is disaster? So the question is, does having
02:00
typhoons automatically translate to having disaster? Well, studies show that no, typhoons are just natural hazards. Having these hazards does not mean there's going to be a disaster.
02:23
You also need the things that are going to be affected by the hazards. We call this exposure. Exposure could be us, humans, or the building's infrastructure. And also, another thing that
02:41
determines the disaster would be vulnerability. So how vulnerable are these things to the natural hazards? So these things all contribute to having a disaster. So that's why, so here's a quote from the World Risk Index report from 2013. It says here,
03:05
a country's risk of becoming a victim of a disaster is not determined solely by its exposure to natural hazards, but to a crucial extent also by the society's state of development. So
03:20
how ready are you when the hazards come? Okay, so here's a picture where we can see, so this explains what I've been talking about. There's a natural hazards fear to a disaster, and then there's that societal fear. So when it comes to natural hazard, we can't really do
03:47
anything, do much about it. We can't say to a typhoon that, well, you can't say it should postpone its arrival, just because we're not ready. But we can do something about the societal
04:02
fear. We can provide tools, we can educate the people, and make them more ready for the hazard. So by decreasing the vulnerability, we also decrease the possibility of having a disaster. That's why Project NOA was born. Project NOA, or Nationwide Operational Assessment of Hazards,
04:28
is a nationwide disaster management program which aims to improve the government and Filipino people's capacity to respond against impact and effect of extreme weather conditions.
04:42
So what we do at Project NOA is we actually gather all information, all data that we think will help when it comes to disaster management and mitigation. Also we empower stakeholders, we
05:01
educate them, we provide tools for them that they can access openly and freely. So one of the tools that we developed at Project NOA is WEBSAFE. So basically what WEBSAFE does is it
05:29
takes a hazard map which tells us where it's going to have, I mean, where it's going to have a hazard. For this example, this is a flood map. It tells us where it's going to have floods
05:47
in the case of extreme rain. And then it overlays that with another map, an exposure map. In this case, this is a population density map. It tells us where people live
06:01
and then intersects these two maps and gives us some analysis. That we think would be valuable when it comes to disaster management. Okay, so WEBSAFE stands for Web-based Scenario Assessment for Emergencies.
06:24
It is included in, it's one of the tools that we include in our website. We're actually working on the version two of the Project NOA website. This is a screenshot of it. So we have
06:40
the other features there, but WEBSAFE is this one. Later, we're going to have, as I said a while ago, there will be a talk in the next session. It's titled Continuous Improvement on the NOA Initiative. There will be more details regarding this website.
07:04
So for now, let's focus on WEBSAFE. WEBSAFE is built with free and open source software for Geospatial. It is a tool to calculate the needs of our immunity, considering the effects of a particular hazard. So let's go back to the last slide.
07:27
You can see here, it tells us what percentage of the population, of the total population, will be hit, will be affected by the flood. So out of 1,925,000 it says
07:46
606,000 will be affected. And then it tells us how many of these people will be in the different hazard areas. For this example, it's a flood map. It tells us
08:02
how many people will be in this flood height. These are different flood heights. So red means it's just above your jaw, average Filipino height. Orange means
08:22
just in your knee. So 197,000 will be flooded up to the knee. And then low hazard areas means it will be a little bit above your foot, 184,000. And then also it provides you with an estimation
08:41
of the needs that they'll be consuming when you evacuate them. So 1,696,800 kilograms of ice will be needed if you evacuate these people, and so on.
09:04
So Project NOA and the World Bank partnered in the development of WebSafe initially. After the funding from the World Bank, Project NOA initiated some other improvements for WebSafe, and it is now backed up by UNICEF. WebSafe aims to aid local government units in their response
09:31
to our disasters. So as I said, it's part of the version two website of Project NOA. So before we proceed with my slides, I would like to show you a demo.
09:57
So let's go take a look at the website. Yeah, okay. So we haven't officially launched this
10:10
version two, so it's in beta phase. You can access it for testing. It's beta.noa.ust.gov.ph.
10:20
Then you can access this website. So here, you can access WebSafe by clicking this icon. And to use it, you're going to have to choose two layers, the hazard layer and the exposure layer. So let's take a look at where I live in Manila. So we have, sorry, this drop down
10:49
gives you all the hazard layers that we have prepared. We're continuously generating hazard maps for this. Right now we only have flood hazard maps, but we're looking at also providing
11:05
hazard maps for storm surge and landslide. So let's take a look at Manila there. So
11:20
yeah, that's the flood map for Manila. Then let's overlay the population density map of Manila. These maps are all generated at Project NOA. We have components that are focused on doing the generation of these maps. So here's the sample report of WebSafe.
11:44
Sorry, showing you this a while ago in the screenshot. So that's how you use WebSafe, along with other features at the Project NOA website. So there. I would like to go through
12:05
the different technologies that we used in the development and maybe provide a brief explanation of what it does. So first, InnaSafe. It's a QGIS plug-in built with Python. The core calculation
12:25
capability of WebSafe uses the InnaSafe API. So you can check the code for this with this in GitHub. Next, we use TornadoWeb. It's a web server, but also built with Python.
12:45
It uses non-blocking asynchronous technology, which enables the web app to accommodate requests asynchronously. For the database, we use PostgreSQL, a database of the different
13:02
hazard maps available and the locations. Next, we have GeoServer to serve the maps that are being displayed. The hazard maps and the exposure maps are all stored in GeoServer.
13:22
We use OpenLayers 3 for displaying the maps in the browser. For building the web app, we use AngularJS as the framework and some Bootstrap for responsiveness.
13:43
Other technologies we use for the inputs. For the generation of hazard maps, we use Flow2D, and we extract data from OpenStreetMap for the building footprints. I don't think I have shown you the building footprints feature, so let's go to that.
14:08
So you can... So I'll show you the building footprints for Takloban. It's the place where
14:25
Super Typhoon Haiyan hit. So here it is. These are buildings, building footprints extracted,
14:42
let's wait for it to load, from OpenStreetMap. So the limitation here is that OpenStreetMap continuously updates its data, so we need to also regularly check for new data. So let's try it. So that's one of the limitations there. And as you can see,
15:10
there's a part of the place that does not have some buildings from it, so we have GIS specialists who regularly check OpenStreetMap for that. If you calculate it,
15:27
it will also give us an analysis when it comes to the infrastructure of Takloban.
15:47
So calculation for the building footprints takes a little bit longer than when using a population density map, but here it is. So it tells us that out of 30,416 buildings,
16:08
10,124 will be affected. 18 of those will be in high hazard, and so on. In the future, this is under development, as I said, it's still in beta phase, we will be able to
16:21
release the different building types so that disaster managers can see which buildings will be highly affected. So yeah, that's it. That's WebSafe. Thank you. Any questions for Mr. Eichel? Yes.
16:49
The roadmap for WebSafe in the future. I'm working in the World Bank with Vivian and everybody, and we're just working with Karthuza and Tim, and just curious what you guys have
17:02
coming up. Yeah, so right now, as I said a while ago, we are looking at providing more hazard types. Right now we have hazard maps for floodings, but we're generating more, even for storm surges and landslides. Also, we are integrating additional information
17:25
from the Philippine Statistical Authority regarding the census, so we can provide like age groups and gender groupings in the report, so we can see how many children are
17:43
affected by this hazard. And also, we're improving the user experience and reports so that it can be easily understood by the users. Thank you.
18:11
Some Canadian, through the Canadian NGO, how closely do you work with the actual local government level? Very close. So we regularly get visitations from local government leaders,
18:31
and also we conduct, I think twice every two weeks, some lectures to explain how they can
18:42
use it. Also, we have partnerships with the DILG, that's the Department of Internal... Interior and Local Government? Yeah, and that's why web-safe, when we release it,
19:00
we hope that DILG will be using it as one of the main tools for DRRM in the Philippines. Okay, that's helpful. I think a lot of times when I work there, I find there's a disconnect between the local level and the national government agencies. There's not enough coordination or communication, so I thoroughly encourage you to communicate with the local
19:27
governments. So we agree, we also noticed that, and we have a component that is dedicated for communicating the different information that we think will be necessary during disasters.
19:47
Is there any more questions for Mr. Aiko? Yes, ma'am. Hello, thank you for your interesting presentation, because I have also developed for my research, such kind of a similar tool. So I'm wondering when you calculate in the website, do you calculate risk on the fly?
20:08
Yeah. For example, when you choose the hazard layer and the exposure layer, do you calculate them interactively when you press the calculate button on the website? Yeah, the calculation happens in the backend. So we use InnoSafe for the calculation
20:25
capabilities. It's in Python. So when the user chooses the hazard map and the exposure map, this information is thrown to the backend server, and then the backend calculates it,
20:41
and then throws the result to the frontend server. Okay. So it's done within the PostGIS database? Yeah, we used a database for the database of the different hazard maps available. Yeah. Thank you.
21:02
Is there any more questions? Okay. So thank you, Mr. Aiko. Okay, let's give him a round of applause.