Implementation of Semantic Web GIS-based Platform in

Project NOAH Emergency Management System

An Application of Software Reuse and Service Oriented Architecture Concepts

A-Jay N. Galiza
University of the Philippines
Diliman, Quezon City, Philippines
ajngaliza@gmail.com
1st Semester, A.Y. 2017-2018

Abstract — An emergency management system based on GIS web services is a tool designed to handle disasters such as
flood, earthquake, landslides, etc. which helps in visualizing affected areas and provide necessary response. During these
scenarios, timing is critical and proper coordination and collaboration of services is a necessity. Currently, Project NOAH
is a tool used in disaster preparedness and mitigation by combining real-time sensor data, weather forecast, and hazard maps
to visualize areas that need to be closely monitored. Developments in semantic web services show an opportunity to add
higher semantic levels to this existing framework, providing services focusing in emergency response. This paper outlines
a semantic web GIS implementation of Project NOAH in which data sources and services are made available through
semantic web services, described by ontologies, to create comprehensive response based on user needs and goals.

1 Introduction
In a crisis, relevant information of an affected area becomes critically important and speedy access to that data becomes a
matter of life and death. Multiple agencies have to collaborate and coordinate data and information regarding actions to be
performed. Unfortunately, many emergency relevant resources are not available on the network and interactions between
agencies usually occur on a personal/phone basis. The resulting interaction is therefore limited and slower, contrary to the
nature of the need for information access during emergencies. The digital maps and spatial information from Geographic
Information Systems (GIS) offer a template on which all diverse nature data for disaster management can be quickly
visualized and analyzed, resulting in more well-informed decisions. Functionality of GIS can be core in each of the five
traditional stages of disaster management: Identification and Planning, Mitigation, Preparedness, Response, and Recovery.
Emergency relevant data is often spatial-related, and Spatial-Related Data (SRD) is traditionally managed with the help of
GIS. GIS support decision making by simplifying the integration, storage, querying, analysis, modeling, reporting, and
mapping of this data. Unfortunately, GIS are often centralized and isolated systems, and heterogeneity arises in the way
different organization gather and manage data. This inefficiency can lead to devastating consequences in an emergency
situation.
To solve this problem, service-oriented architectures are becoming widespread in the implementation of e-government
programs; combined with recent advances in web services and the semantic web they can enable the creation of agile
networks of collaborating applications distributed within and across public organization boundaries. Using web services,
SRDs can be shared on the internet via services which become autonomous and platform-independent computational
elements.

1.1 Project NOAH

The Philippines has launched a responsive program for disaster management, prevention and mitigation called the
Nationwide Operational Assessment for Hazards (Project NOAH), to provide a 6-hour forecast or warning to vulnerable
communities against imminent floods and to use innovative technologies to enhance current geo-hazard vulnerability maps
[1]. It is being developed with the help of the National Institute of Geological Sciences and the College of Engineering of
the University of the Philippines; the Philippine Institute of Volcanology and Seismology (PHIVOLCS); the Philippine
Atmospheric, Geophysical and Astronomical Services Administration (PAGASA); Science and Technology Information
Institute (STII) and the Advanced Science and Technology Institute (ASTI).
Initial efforts of Project NOAH include: deployment of weather-related sensors such as rain gauges and water-level sensors;
use of state-of-the-art methods to construct high-resolution flood and landslide hazard maps; and integration of disaster
efforts by the national government, academe, civil society organizations and private sector.
To spread such critical information in a wider scale, a web-based GIS using mashups of available source codes and APIs
was developed. This tool is now heavily used by LGUs in disaster prevention and mitigation efforts to address impacts of
natural hazards.

1.2 Semantic Web Services

However, even with the acceptance of web service description and publishing standards, syntactic definitions do not fully
describe the capability of a service and cannot be interpreted by software programs; human intervention is always required
to interpret the meaning of input and output data, applicable constraints as well as the context in which services can be used.
The benefit of web services is that users now only need to think of services instead of the raw data they wish to receive. But
the major disadvantages of the web service technologies are their inability to permit automatic discovery, selection,
composition and therefore human intervention and effort is required. Adding semantic web technologies to the web services
solves the said problems of web services.
Particularly, Semantic Web Services (SWS) provide infrastructure in which new services can be added, exposed and
composed constantly, and the organization processes automatically updated to reflect new forms of cooperation [2], by
combining the flexibility, reusability, and access that usually characterizes a web service, with the expressivity of semantic
reasoning. This allows the invocation, composition, mediation, and execution of complex services with multiple paths of
execution, and levels of process nesting.
Government service such as Project NOAH is an ideal test bed for Semantic Web research due to the heterogeneity of
information space with the challenge to achieve interoperability and process integration.

1.3 Purpose of the Study

Currently, Project NOAH focuses on disaster prevention and mitigation program. It maintains a disaster management
platform, providing meteorological information available for everyone to use [3]. Its interface provides weather data and
shows real-time information from ground-based sensors which serves as flood early warning system. It also gives
information about the location of critical facilities such as schools, health facilities, police stations, and fire stations. This
service can be extended to cases like earthquake, fire, and other calamities.
On the other hand, it has been observed that there is no accurate system that has been providing any kind of quick response
services to affected individuals. Such systems mainly work in a way that the affected person will call rescue service team’s
helpline from his/her mobile or landline and will tell them his/her position. With an emergency management system,
historical data such as hazard maps and forecasts can be integrated to real-time sensor data to provide agencies information
where to focus various emergency services. Also in a wider scale, the lack of coordination among national and local
government agencies was evident [4]. This is demonstrated by delayed distribution of relief goods and delayed retrieval of
casualties.
In this paper, an emergency response system integrated to the current functionality of Project NOAH is proposed to be
implemented as a Semantic Web GIS Emergency Management System (EMS) relying on semantic web services. The EMS
assists the disaster management and response team in the task of retrieving, displaying, and interacting with emergency
relevant information. This can include, according to the kind of emergency, weather forecasts, available rescue team,
evacuation procedures, available evacuation centers, supply providers, categories of affected and vulnerable people, nature
and location of damaged or endangered facilities, access of critical spots, etc.
As a result, involved agencies are able to extend their knowledge about the emergency situation by making use of diverse
functionalities based on data held by other agencies which otherwise might not be accessible to them or slow to obtain
manually.

2 Proposed Framework
The use of Semantic Web Services (SWS) increases the speed and adaptability of process execution in various situation.
On the basis of available semantic descriptions, SWS allow the automatic selection, composition and mediation of the most
adequate Web services to accomplish a specific process activity [5]. It joins the innovation of Web administration (WSDL,
SOAP, UDDI) with Semantic Web advances. In GIS, the use of semantic layers, although not yet firmly established, is
being investigated in a number of research studies [6], [7], [8]. Spatial data repository and its functionality described in an
ontology is believed to make cooperation with other systems easier and to better match user needs.
An SWS framework called Web Service Modelling Ontology (WSMO), is used to reference ontologies for describing the
various aspects of heterogeneous Web services. On the other hand, the activities such as processing and executing the user
goal; discovering web services; selecting the most appropriate one; resolving any mismatches at the ontological level;
invoking the relevant set of Web Services satisfying any data, and control flow and invocation requirements are mainly
supported by IRS-III infrastructure [9].

2.1 WSMO
Different to other SWS approaches, WSMO defines the ontologies and explicitly captures both the user (goals) and
provider (web services) perspectives, as well as the mappings between them (mediators) [5].
Ontologies provide the foundation for describing domains semantically. Ontologies are the key elements in WSMO, they
provide the terminology used by other elements, allow to link machine and human terminologies and define the information
formal semantics [9].
Web service descriptions represent the behavior of a given service in terms of their capabilities and how to use it (interface).
The description also indicates web service choreography, or how the services communicate, and orchestration, how they
are composed. Goals define the tasks that a service requester expects the web service to fulfill. Basically, they tend to specify
the service user’s intent.
Mediators are employed to handle issues of data and process interoperability that arise between heterogeneous systems.
Mediation services realizes this functionality by providing mapping rules from a source entity (usually the one used by the
service requester) to the target entity (the one used by the service provider), i.e. mediators link the ontologies, goals, and
web services. There are four types of mediators in WSMO [10]:

• ggMediators that link two goals. This link represents the refinement of the source goal into the target goal or state
equivalence if both goals are substitutable.
• ooMediators that import ontologies and resolve possible representation mismatches between ontologies.
• wgMediators that link Web services to goals, meaning that the Web service fulfills the goal to which it is linked.
wgMediators may explicitly state the difference between the two entities and map different vocabularies (through
the use of ooMediators).
• wwMediators that link two Web services.

2.2 IRS-III in Semantic Web Services

The Internet Reasoning Service (IRS-III) is a framework and implemented infrastructure supporting the creation of semantic
web service based applications. Following the WSMO framework, the term choreography is used to describe the IRS-III
component which deals with web service interaction [11]. It is a platform which allows the description, publication and
execution of Semantic Web Services.
Based on a distributed architecture communicating via XML or SOAP messages [12], it offers an execution environment
for SWS; ontologies are stored by the server, and used in WMSO descriptions to support discovery, invocation, composition
and orchestration of web services.
IRS-III supports one-click publishing of ‘standard’ program code, i.e. it automatically transforms programming into a web
service, by automatically creating an appropriate wrapper. Therefore, it is very easy to make existing standalone software
available, as web services. By extending the WSMO goal and web service concepts, clients of IRS-III can directly invoke
web services via goals-that is IRS-III supports capability-driven service invocation [9].

2.3 GIS Web Service

GIS data is mostly present in the form of spatial sources, which includes scale/resolution, dimension (2D, 3D), schemas,
geodata, geo location, geo references etc. [13]. In order to share data between services, an international organization, the
Open Geospatial Consortium (OGC), established some standards that these services have to follow, and OSM satisfies all
these standards [14]. GIS allows the creation and management of objects composed of spatial attributes (nodes, polygons,
maps, etc.) as well as descriptive ones (names, numeric values, etc.)
Maps available on the web, used for locating an address or getting transportation information, do not allow simple queries.
Meanwhile, new mapping systems released, are highly responsive mapping frameworks that provides an API (e.g. Google,
Yahoo, Bing, etc.). API allow developers to fill online mapping services with custom data by collecting information from
standard documents in RDF format, or simply by ad hoc “web scraping” of HTML resources. These embryonic but very
agile Web GIS, called mashups, can merge more than one data sources and add functionality such as filtering and search
features.

2.4 Project NOAH development

Programmers of Project NOAH developed mapping platform mashups to tailor fit the web application for disaster response
and mitigation purposes. These mashups combine public domain web information with open APIs to simplify
communication between different data sources and mapping platform. OpenLayers, an open-source dynamic mapping
platform is used to embed the web map service of Google and other online mapping services such as OpenStreetMap on a
webpage [1]. Using this platform, sensor data and hazard maps are overlain to achieve the end product of which is a web-
based disaster GIS used to aid in addressing Philippine disaster mitigation problems.
A part of the project, nababaha.com is a website that has a flood reporting option for the public. Data gathered from the
reports help verify the flood hazard maps. For local governments, these flood hazard maps can be used for localized
emergency response - evacuation and access routes, road closures, location of key rescue facilities - and for urban planning.
However, web GIS like this do not avoid traditional issues attached to non-semantic applications. Because of this, handling
information heterogeneity still requires considerable manual work, the lack of semantics limits the precision of queries, and
limited expressiveness usually drastically limits functionality.

2.5 Semantic Web GIS proposal

A multi-layered architecture was proposed for a semantic web GIS [15]. This system answers geographically oriented
queries while adding the functionality of multiple and heterogeneous sources of information. Its notable elements include a
Data and Web Services Layer, Semantic Web Services Layer, User Ontology Layer, and the Mediation Layer.

• Data and Web Services Layer. This layer allows distributed datasets to be retrieved through the network. This layer
abstracts underlying relational access interface to provide simpler but well-defined queries.
• Semantic Web Services Layer. The operations provided by the preceding layer can be described semantically by
the WSMO framework.
• User Ontology Layer. Although conventional GIS exhibit various levels of GUI complexity, as well as custom
query languages, accessing the underlying data level is often the only way to express complex queries. Indeed, GIS
usage can hardly be called intuitive and often requires technical knowledge of the user, or even programming skills.
However, in a semantic web context, simplicity of objects should be achieved. In semantic web GIS, attaching goals to
objects as described in an ontology, and using the sequence of goal invocation as well as the location of the query as a
context may help simplifying the task of query specification. Moreover, to efficiently support an activity such as emergency
planning, precision is essential; only goals and data related to the emergency have to be displayed. Therefore, an appropriate
user ontology must capture the decision-making process in terms of goals and relevant information. Generic concepts have
to be used in specifying the domain asked for. For example, a request for “evacuation center” will only include shelters
situated outside the affected area in flooding context, but will have a different extension elsewhere.

3 Proposed Prototype Design

Semantic Web Services will be used to provide an improvement to the existing functionality of Project NOAH. Project
NOAH was the Department of Science and Technology’s (DOST) integrated disaster prevention and mitigation program.
It is designed to generate accurate data and address the conditions needed to make informed decisions for disaster mitigation,
through government agencies, partners in the private sector and the academe. The project also uses advanced technologies
to improve current geo-hazard vulnerability maps [16].
The Project NOAH web portal provides critical information for disaster prevention based on near real-time weather data,
flood and landslide hazard maps, storm surge inundation maps, and the identification of local critical facilities. The web
portal also includes the WebSAFE application, which allows for smarter and more comprehensive preparation of resources
in the case of an incoming severe weather event [17]. For mobile users, Project NOAH is also accessible as a mobile app,
providing the weather monitoring tools from the web portal such as satellite and Doppler radar data, information from the
automated weather stations and the 4-hour forecast. Additionally, the Arko app, allows viewing of relevant hazard data for
floods, landslides and storm surges in an area. This would enable them to locate safe locations nearby in the event of future
hazards.
This program focuses on the early phases of disaster management. In order to focus on scenarios regarding emergency
response, additional services will be integrated to the project. Existing components of the Project NOAH [16] will be reused
in acquisition of critical sensor data and hazard maps. The Local DRRM Offices (LDRRMOs) at the provincial, city and
municipal levels and the Barangay Development Councils shall design, program and coordinate DRRM activities consistent
with the NDRRMP [18]. This office shall maintain a directory and database of human resource, equipment, directories and
local of critical infrastructures and their capacities such as hospitals, schools, fire stations and evacuation centers. These
will be used in making decisions regarding contact with rescue teams and voluntary associations, or actions necessary to
provide refuge, services, and supplies to affected communities.

Fig. 1 Package diagram of a typical emergency response system

This development will provide a decision support system, which assists the disaster management team. This design can also
be extensible to other agencies such as fire service, police, ambulance service, etc. in gathering data related to a certain type
of event, faster and with increased precision.
3.1 Architecture
The proposed improvement in the architecture is based on the semantic web GIS framework discussed in Section 2.5. The
prototype architecture based on [15] is modified to fit the current services offered by Project NOAH.
Different web services expose the data and functionalities of external information sources, including the major components
of the program [16]. The ontologies semantically describe those services and are made accessible to the users through the
Emergency Management Service Client of Project NOAH which is a web interface using the web map service of Google
and other online mapping services such as ArcGIS Online or OpenStreetMap API. The IRS-III is used to publish the
semantic web services. This system is designed to handle service, environment, and presence related goal invocations,
discovering the semantic web service that fits the goals, managing its orchestration and mediation, executing the web
service, and releasing the results.

Fig. 2 Architecture of the Project NOAH EMS based on [15].

3.2 Data and Components

The emergency management service aggregates information from these sources:

• Emergency Planning and Facilities Database. Project NOAH currently enumerates critical facilities (e.g. schools,
health institutions, police stations, fire stations) based on OpenStreetMap data and World Health Organization
records. Other establishments like accommodation, supermarkets and government offices can be included. In
coordination with local disaster management councils this can be achieved.
• BuddySpace. An instant messaging client providing lightweight communication and collaboration means. It is an
enhanced Jabber client providing secure presence management, web services and instant messaging. It extends the
'buddy list' idea with improved and customizable visualization of presence (incl. maps, logical layouts) and
automated contact list generation which administers access to a community, and scalability. It also allows users to
find relevant people (functional role and location) in a given emergency situation, and to easily communicate with
them through calls or chat. This can also be accessed using smartphones and other mobile devices.
• Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA). PAGASA provides
environmental data such as weather forecasts. Data are used for warnings (such as rainfall) through Project NOAH
since June 2012 [19].
 This also involves major components of Project NOAH which provide data to the program:

• Distribution of Hydrometeorological Devices in hard-hit areas in the Philippines (Hydromet). Automated rain
gauges and water level monitoring stations in major river basins and flood-prone areas.
• Disaster Risk Exposure Assessment for Mitigation – Light Detection and Ranging (DREAM-LIDAR) Project.
Accurate three-dimensional flood inundation and hazard maps for the country’s flood-prone areas.
• Enhancing Geohazards Mapping through LIDAR. Use of LIDAR technology and computer-assisted analyses to
identify landslide-prone areas.
• Coastal Hazards and Storm Surge Assessment and Mitigation (CHASSAM). Generate wave surge, wave refraction,
and coastal circulation models to understand and recommend solutions for coastal erosion.
• Flood Information Network (FloodNET) Project. Timely and accurate information for flood forecasts.
• Landslide Sensors Development Project. Sensor-based early monitoring and warning system for landslides, slope
failures, and debris flow.

3.3 Services
The data services refer to the given data sources discussed in the previous section and are exposed by means of web services.
The emergency planning services provides information about critical facilities. Each web service requires a query are as
input and returns a list of important facilities in that area, together with their properties, such as address, telephone number,
etc. The query area is a circle represented by the coordinates and a radius. For example, the ‘getHospitals’ Web service
returns a list of relevant hospitals.
The meteorological services, through PAGASA, provide weather information either nationwide or in specific areas. Also,
nababaha.com is a website which merges flooding reports from ordinary citizens with scientific flood simulation data based
on rainfall from past major typhoons.
The BuddySpace messaging service allows emergency planning officers to connect to the Jabber network, and retrieve the
list of necessary presences. Various sensor data through Project NOAHs programs also provide real-time information, these
return readings together with the coordinates of the deployed sensors and gauges.
Services are orchestrated in IRS-III and communicates through XML/SOAP messages. To get the information up to the
semantic level, IRS-III creates instances of the relevant ontologies by lifting information from the XML output of a web
service. Also, XML data inputs of web services are also created from ontology instances. These are all converted into XML
which can be understood by the interface.

3.4 Domain Ontologies and WSMO Description

The following ontologies were presented in [15] which is designed to support an emergency management system through a
semantic web GIS discussed in Section 2.5:

• Weather, Emergency Planning and BuddySpace Domain Ontology. Represents the concepts used to describe the
services attached to the data sources, such as flood and rain for PAGASA, schools and hospitals for NDRRMC
Emergency Planning, session and presences for Jabber. The services, composed of the data types involved as well
as its interface, have to be described in an ontology usually at a level low enough to remain close from the data.
• HCI Ontology. Part of the user layer, this ontology is composed of HCI and user-oriented concepts. It allows to
lower from the semantic level results for the particular interface which is used.
• Archetypes Ontology. Part of the user layer, this is an ontology aiming to deliver a cognitively expressive insight
into the nature of a specific object; for example, by conveying the cognitive feeling that for example a hospital, as
a “container” of people and provider of “shelter” can be conformed to the more universal idea of “house”, which is
considered an archetypal concept.
• Spatial Ontology. Being part of mediation layer, it describes GIS concepts of location, such as points, coordinates,
polygonal areas, and fields. It also allows describing spatial objects as entities with a set of attributes, and a location.
The goals, mediators, and Web services descriptions of our application link the PAGASA, environmental data, Emergency
Planning, and the messaging services to the user interface. Correspondingly, the Web service goal descriptions use the SGIS
spatial, meteorology, Emergency Planning and Jabber domain ontologies whilst the goal encodings rely on the HCI and
archetypes ontologies. Mismatches are resolved by the defined mediators.

Fig. 3 Structure of the WSMO description of the design

A workflow represented in terms of SWS descriptions is shown. Get-Polygon-GIS-data-with-FiIterGoal represents a request

for available evacuation shelters within the area. The client specifies the requirements as a target area, radius, and a shelter
type (e.g. hospitals, hotels, schools). As mentioned above, the set of emergency planning web services each return potential
shelters of a specific type with a circular query area. The given results are filtered in order to return only shelters correlated
to emergency-specific requirements (a storm, for example). From a SWS point of view the problems to be solved by this
particular portion of the SWS layer includes discovering the appropriate Emergency Planning Web service and composing
the retrieve and filter data operations. Below, how WSMO representations address these problems are shown.

• Web service discovery. Each web service description of an emergency service defines the specific class of shelter
that the service provides. Each definition is linked to the Get-Circle-GIS-Data-Goal by means of a unique WG-
mediator (wgM). The inputs of the goal specify the class of shelter, and the circular query area. At invocation, IRS-
III discovers through the WG-mediator all associated Web services, and chooses one on the basis of the specific
class of shelter described in the Web service capability.
• Area mediation and orchestration. The Get-Polygon-GIS-data-with-Filter-Goal is associated with a unique Web
service that orchestrates, by simply invoking three sub-goals in sequence. The first gets the list of polygon points
from the input; the second is Get-Circle-GIS-Data-Goal described above; finally, the third invokes the smart service
that filters the list of GIS data.

4 Example Usage
The application user interface is based on Web standards. One of the main components of the interface is a map, which uses
the ArcGIS Online API to display polygons and objects, custom images, at specific coordinates and zoom level. Goals and
attributes are attached to such objects; they are displayed in a pop up window or in a hovering transparent region above the
main interface.
A user defines a flooding hazard, which offers a specific goal, before trying to contact relevant agents. The procedure is as
follows:
1. Based on external emergency information or a critical alarm from one of the deployed flood sensors, validated
by the flood hazard map from the database, an officer draws a polygon (red, indicating that the flood is 1-m or
higher), then assigns a type of emergency to the region. Here, a neck-high flood.
 Fig. 4a, 4b Polygon designating the affected area

2. Described in the ontology, the new instance has attached features and goals. Here the goals are as follows: since
it is a neck-high flood, one gets shelters at distance from the area outside the red region, two others connect to
BuddySpace and get relevant presences.

Fig. 5 Defined area present goals which can be queried to provide objects and allow added interactions
3. First, the user requests all possible evacuation centers inside the region, they are retrieved with their features and
attached goals.

Fig. 6a, 6b Goals and features attached

4. With that information the officer logs into BuddySpace, then contacts the relevant persons to request action or
information e.g. AFP for mobilization of stranded individuals and/or DSWD for relief support.

Fig. 7 Relevant presences are provided and the emergency personnel contacts them for relevant information.
5 Conclusion
The emergency response system discussed in this paper, as an example of Semantic Web GIS, provides a service oriented
tool for emergency personnel. By using existing components of an existing system, efforts of future development can be
minimized. The framework described in the previous sections can also be used in other applications like traffic management
or extensions in airport authorities.

6 References
[1] A. Lagmay, B. Racoma, K. Aracan, J. Alconis-Ayco and I. Saddi, "Disseminating near-real-time hazards information
and flood maps in the Philippines through Web-GIS", Journal of Environmental Sciences, vol. 59, pp. 13-23, 2017.
[2] A. Gugliotta, L. Cabral, J. Domingue, and V. Roberto, “A Semantic web service-based architecture for the
interoperability of e-Government services”, In Proceeding of the International Workshop on Web Information Systems
Modeling, Sydney, Australia, 2005.
[3] G. de la Cruz, “How does Project NOAH contribute to PH's disaster management?,” Rappler. [Online]. Available:
https://www.rappler.com/newsbreak/iq/159975-project-noah-contribute-ph-disaster-management. [Accessed: 11-Dec-
2017].
[4] “Assessment of Disaster Risk Reduction and Management (DRRM) at the Local Level.” Commission on Audit, 2014.
[5] A. Gugliotta, S. Dietze and J. Domingue, "A Situations & Goals Semantic Model for Designing and Implementing
Semantic Web Services-based Processes," 2008 IEEE International Conference on Services Computing, Honolulu, HI,
2008, pp. 581-582.
[6] Y. Yang, Z. Gan, H. Chen and X. Tang, "An Ontology-Based General Multi-scale Conceptual Model and its 3D GIS
Application," 2009 Second International Symposium on Information Science and Engineering, Shanghai, 2009, pp. 239-
245.
[7] J. Shen, A. Krishna, S. Yuan, K. Cai and Y. Qin, "A Pragmatic GIS-Oriented Ontology for Location Based Services,"
19th Australian Conference on Software Engineering (ASWEC 2008), Perth, WA, 2008, pp. 562-569.
[8] Wei Cui and Hao Wu, "Using ontology to achieve the semantic integration and interoperation of GIS," Proceedings.
2005 IEEE International Geoscience and Remote Sensing Symposium, 2005. IGARSS '05., 2005, pp. 3
[9] J. Domingue, S. Galizia and L. Cabral, "The Choreography Model for IRS-III," Proceedings of the 39th Annual Hawaii
International Conference on System Sciences (HICSS'06), 2006, pp. 62c-62c.
[10] S. Zhou and Z. Sun, "Using WSMO to Enable Mediation of Heterogeneous Services and Semi-automation of Service
Discovery and Execution in Semantic SOA," 2009 International Conference on Web Information Systems and Mining,
Shanghai, 2009, pp. 638-642.
[11] L. Cabral and J. Domingue, “Ontology Based Discovery of Semantic Web Services with IRS-III,” Semantic Web
Services, pp. 191–202, 2012.
[12] A. Saeed et. al., “Android, GIS and Web Base Project, Emergency Management System (EMS) Which Overcomes
Quick Emergency Response Challenges,” Advances in Intelligent Systems and Computing Advances in Information Systems
and Technologies, pp. 269–278, 2013.
[13] L. Descamps-Vila, J. Conesa and A. Perez-Navarro, "How Can Semantic Be Introduced in GIS Mobile Applications:
Expectations, Theory and Reality," 2012 Fourth International Conference on Intelligent Networking and Collaborative
Systems, Bucharest, 2012, pp. 477-482.
[14] Tanasescu, V., Gugliotta, A., Domingue, J., Davies, R., Gutierrez-Villarias, L., Rowlatt, M., Richardson, M., and
Stincic, S. (2006). A semantic web services GIS based emergency management application. 5th International Semantic Web
Conference, pages 959–966, Athens, GA, USA.
[15] “Project NOAH (Philippines),” Wikipedia, 11-Dec-2017. [Online]. Available:
https://en.wikipedia.org/wiki/Project_NOAH_(Philippines). [Accessed: 11-Dec-2017].
[16] “Project NOAH (Nationwide Operational Assessment of Hazards) Implementing Agency,” Center of Excellence on
Public-Sector Productivity. [Online]. Available: https://dap.edu.ph/coe-psp/innovation/noah/. [Accessed: 12-Dec-2017].
[17] “The National Disaster Risk Reduction and Management Plan.” Department of Interior and Local Government (DILG),
December 2011.
[18] “PAGASA,” Wikipedia, 11-Dec-2017. [Online]. Available: https://en.wikipedia.org/wiki/PAGASA. [Accessed: 11-
Dec-2017].