DEVELOPMENT OF ANDROID AND WEB APPLICATION FOR DISASTER RISK MANAGEMENT THROUGH CROWDSOURCING

1. DEVELOPMENT OF ANDROID AND WEB APPLICATION FOR DISASTER RISK MANAGEMENT THROUGH CROWDSOURCING Project Members: ArunBhandari Nishanta Khanal SUPERVISORS: MR. SHASHISH MAHARJAN MR. UMA SHANKAR PANDAY JULY 28 , 2014

2. introduction • Disasters: • Natural or human induced • Mostly inevitable • Risk reduction, safety and better rescue is what is necessary • Location Based Services (LBS): • Services that extract the location information of the people from GPS enabled devices • Popular, effective and easy to use • Provide the information on where a person is

3. background • Kathmandu valley faces the risk towards severe earthquake damage • Other disasters/ accidents also occur every once in a while • Rapid urban growth with unplanned settlements • Lack of efficient and sufficient emergency service providers But, The challenge of finding where a victim is trapped or where the rescue service is needed still prevails

4. objectives • To develop a system for communication between victims and rescue service operators/ non-victims in a post disaster scenario • Sub-objectives • To design and develop a database • To enable a system of communication with server containing database • To build a system enabling users to report, view map and call for emergency help • To design user interfaces (android and web) • To design and implement a proper administrative component

5. Methodology • PLANNING • RESEARCH • SYSTEM DEVELOPMENT • Database creation • Server backend development • Web application development • Android Application development • Testing and debugging

6. METHODOLOGY -> SYSTEM DEVELOPMENT Database creation • PostgreSQLwas used as DBMS • PGADMIN IIIwas used as frontend • Tables were created using PGADMIN IIIUI and writing SQL

7. METHODOLOGY -> SYSTEM DEVELOPMENT Server backend development • Server backend development was done by writing PHP scripts • Apache server was used to run the scripts • The scripts are designed to be supplied with data using post method • Scripts were written such that they returned data in JSON or GEOJSON format

8. METHODOLOGY -> SYSTEM DEVELOPMENT Server backend development ( Contd…) • Following tools were used • XAMPP to run/emulate and configure APACHE server on our pc • Notepad++ to write PHP scripts • Google chrome to test and debug scripts • Mozilla Firefox to test and debug scripts

9. METHODOLOGY -> SYSTEM DEVELOPMENT Web application development • Web application was developed using multiple languages • PHP • JS • Html5 • CSS 3 • Multiple files were created for different components to make it easy to add and edit components of the web site • CSS and JS were saved in separate files as well • External libraries were downloaded and used as well as referenced as required • Graphics and icons that were to be used were created • Testing and debugging

10. METHODOLOGY -> SYSTEM DEVELOPMENT Web application development (Contd…) • Following external libraries were used • Bootstrap 3 • jQuery • AJAX • Leaflet • Charts.js • Mapbox API • Google geocoding

11. METHODOLOGY -> SYSTEM DEVELOPMENT Web application development ( Contd…) • Following software and tools were used • XAMPP to run/emulate and configure APACHE server on our pc • Notepad++ to write scripts • Google chrome to test and debug web application • Mozilla Firefox to test and debug web application • Photoshop CS6 to create graphics and icons

12. METHODOLOGY -> SYSTEM DEVELOPMENT Android application development • Android application was developed using multiple languages • Java • XML • External libraries were downloaded and added to the build path • Multiple activities were created for the android application • Graphics and icons that were to be used were designed • Offline data to be used was acquired • Testing and debugging was done

13. METHODOLOGY -> SYSTEM DEVELOPMENT Android application development(Contd…) • Following external libraries were used • Mapsforge • Graphhopper • Following software were used • Eclipse • Java SDK • Android SDK

14. Results • Database • Server backend • Web application • Android Application

15. DATABASE RESULTS • FIVE TABLES: • user_auth: to store user information (username, contact, email address, type) • reports: to store information each report contains (type, level, description, location, date, etc. ) • likes: to store the report id, username and vote (yes or no) • report_types: to store the type of report • emergency: to store information about emergency request (username, location, date, time) Fig: Flow Database Schema Design

16. SERVER BACKEND RESULTS • Scripts written in PHP • Help in extracting required data from the database according to the client request Fig: Flow Diagram of Server Processing

17. WEB APPLICATION RESULTS • Clean and easy to use User Interface • Functionalities: • Map-view • News Feed • Submit new report • Search for nearest Hospital • Find shortest route • Admin components with privileges like manage users and reports, view statistics, etc. Fig: Website Homepage UI

18. ANDROID APPLICATION RESULTS • Application along with a widget for emergency service request • Six activities/ screens: • Login Page • Registration Page • News Feed • Map Screen • Disaster Report Page • Disaster Details Screen • Facility of routing and finding nearest hospital • Emergency service request possible through widget Fig: Android Application Splash Screen Fig: Android Application Map-view

19. discussion • Choice of OpenStreetMaps as the base map justifies data acquisition through crowd sourcing • One click for emergency reporting is helpful to victims • Users are responsible of validating the reports

20. Limitations • Android application is platform dependent • Error in GPS coordinates • We do not guarantee rescue services, a third party involvement is required

21. conclusion • The initial objectives have been achieved • The application can be of use to overall disaster resilience in Nepal • Addition of features such as alerting respondents in the vicinity

22. Recommendations • Proper marketing is required as crowd sourcing means nothing if crowd don’t use it • Working on how to mitigate the damages caused due to hazards • Involving responsible parties to manage the system and relay information to mass • Addition of features such as alerting respondents in the vicinity, broadcasting safety tips

23. Thank you!! visit our website www.banmedo.heliohost.org/disasteraid Android application download available in the site

24. METHODOLOGY -> SYSTEM DEVELOPMENT Server backend development (Contd…) • An example GEOJSON String { "type": "featurecollection", "features": [{ "type": "feature", "geometry": {"type": "point", "coordinates": [0.0, 0.0]}, "properties": {"name": "point1"} }, { "type": "feature", "geometry": {"type": "point", "coordinates": [10.0, 10.0]}, "properties": {"name": "point2”}] }