Mobile Applications Products for Disaster...

Mobile Application Products Playbook # RSC-06

i

Mobile Applications Products for Disaster Response

Naval Postgraduate School Earthquake Response Project

Playbook #: RSC-06

Revised – 10/15/2013

Approved for public release; distribution is unlimited


ii

Playbook Table of Contents

Executive Summary……………….………………………………………... iii Overview……………….……………………………………………………... 1 Purpose/Objectives……………….………………………………………… 1 Hardware Requirements……………….…………………………………… 1 Data Overview……………….……………………………………………….. 1 Product Descriptions…………….…………………………………………. 2 Software Required……………….………………………………………….. 2 Instructions……………….………………………………………………...... 2 Setting up Systems…………………………………………………… 2 Building Form in BUILD....……………………………………… ….. 4 Data Collection……………………………………………………….. 8 Data Analysis using Aggregate…………………………………… 26 Playbook Directory……….…………………………………………………. 44 Scientific Background and Additional Notes……………………………. 45 References……………………………………….……………………………. 46


iii

Executive Summary This playbook (Playbook #: RSC-06) describes a mobile application for form collection in support of damage assessment adapted by the NPS/DHS Earthquake Response Project for use during disaster events. Forms are filled out on-site in the field using an android tablet or phone and either sent back to a central server immediately using available internet connectivity or saved to be input into the server later. The playbook provides software installation and customization instructions, and operating instructions for the mobile application for use for post-earthquake damage assessment by 1st responders and emergency managers as part of Emergency Operations Center resources.

The NPS damage assessment mobile application product is based on the NPS Common Operational Research Environment (CORE) Lab mobile application “Lighthouse”. This is available as either an Android or Apple implementation and provides the ability to collect field data using mobile devices into forms that are customizable to meet the needs of any emergency management agency. This Playbook only covers the (no-cost) Android version of the Lighthouse application. The Apple version is a commercial (for fee) application. Lighthouse also provides a back-end database that allows for the analysis, display, and dissemination of this field data using an interactive web client. The NPS/RSC earthquake response project used Lighthouse to develop and demonstrate customized damage assessment forms for use within the project 3-tier framework. Responders enter data into simple forms and have the capability to transmit the forms along with supporting photos, video, and audio back to the mobile EOC if internet or cell phone capabilities exist. If a Tier-3 situation exists (no internet, no communications, and limited power), then the devices can download the data later when these are restored, or can locally download data at the EOC site to the Common Operating Picture. The Playbook Directory near the end of this document shows the NPS Earthquake Response Playbook sequence to help put this Playbook into perspective and give an overview of products resulting from this research and some aspects of practical implementation. The content of each Playbook is briefly described; however, users are referred to the specific named and numbered Playbooks for full product descriptions. These provide additional detailed product information, instructions on how to separately utilize the individual products, and how to combine them into an integrated system for improved earthquake response.


1

Overview Sponsored by the Department of Homeland Security (DHS) Science & Technology Directorate, the Remote Sensing Center (RSC) at the Naval Postgraduate School (NPS) has developed a series of instructional playbooks designed to assist 1st responders and emergency managers with the use of remote sensing technology for improving earthquake response.

This playbook (Playbook #: RSC-06) describes a mobile application for form collection in support of damage assessment during disaster events. Forms are filled out in the field using an android tablet or phone and either sent back to a central server immediately using available internet connectivity or saved to be input into the server later.

Lighthouse is an app developed by the NPS CORE lab using Open Data Kit for data collection using forms. The Remote Sensing Center used the Android version of Lighthouse to build forms

The major steps involved in the implementation of this mobile technology are collecting forms in the field, and sending them back to a server used for storing and manipulating submitted forms. The server can be either one owned and maintained by you, or a Google App Engine Server which Google will maintain for a fee.

Purpose/Objectives This playbook is meant to provide a guide to setting up and running an instance of the Lighthouse application and the server to support it. Lighthouse allows emergency management agencies to have customized damage assessment and other forms that can be filled out electronically, eliminating the need to transport and preserve paper forms. The forms can combine text, images, and video to provide a more accurate, visual picture of what is happening and what actions need to be taken at any given time during a disaster. Forms would be filled out by field teams doing initial damage assessment and sent back to the EOC to provide situational awareness and allow for a better plan for where to allocate resources based on better knowledge of the full situation.

Hardware Required Android tablets or phones for collecting the data, a computer with internet connection to manage and collect forms, and either a Google App Engine Account or a Tomcat server.

Data Overview The necessary starting data is the blank forms to be filled. Several of these forms come loaded into the instance of ODK Aggregate on the EOC in a Box and others can be created using the instructions in the Instructions section. The filled forms will be generated by users during an actual disaster and that data can be analyzed as it is created and submitted.


2

Product Description(s) The Lighthouse Application is an Android app that works on both tablets and phones to provide the ability to collect field data into forms that are customizable to meet the needs of any emergency management agency. Lighthouse also provides a back-end database in the form of either a Google App Engine instance or a local Tomcat server that allows for the analysis, display, and dissemination of this field data using an interactive web client. As implemented here, Lighthouse is used to build, collect, and analyze damage assessment reports.

Software Required On Android tablet and/or phone: either ODK Collect or Lighthouse app

On computer receiving forms: Web browser

If using a local server:

Java 6

Tomcat 6

MySQL or PostgreSQL

ODK Aggregate v1.N.N.

If using Google App Engine: ODK Aggregate v1.N.N.

Instructions

This section provides detailed instructions on how to access, install, and customize the Lighthouse application. The final section of these instructions provides details on use of the mobile application and data collection for post-earthquake damage assessment.

Setting Up Systems Download ODK Collect or Lighthouse

Download either ODK Collect or Lighthouse (not both) onto your Android device. This is the app you will use to fill in forms in the field.

Lighthouse download is in instruction 1 here: http://lhproject.info/install-odk/ o From your device's application drawer, choose Settings, then Applications. Make

sure “Unknown sources” is checked. Some operating systems are already set to allow installs from unknown sources, so don’t worry if the check box is not apparent.

o Keep the server settings for the default demo server until you get your server set up as explained later in this tutorial

ODK Collect download: Either download from market or from the web. o Downloading from Market:

In your app drawer choose Market or Play Store. (Some operating systems call it Market and some call it Play Store. They are the same thing.)

Search for ODK and select ODK Collect from Open Data Kit.

http://lhproject.info/install-odk/


3

Click install. Click OK after viewing the security settings. o Downloading from the web:

From your device's application drawer, choose Settings, then Applications. Make sure “Unknown sources” is checked. Some operating systems are already set to allow installs from unknown sources, so don’t worry if the check box is not apparent.

Return to the application drawer and choose Browser. Navigate to http://code.google.com/p/opendatakit and in the green Featured Downloads download ODK Collect vN.N.N.apk

In the download window, you will see ODK_Collect_vN.N.N.apk. Select it to install after you approve the security settings.

o More information on ODK Collect can be found here: http://opendatakit.org/use/collect/

Experiment with some forms from the ODK demo server to get a sense of how to fill in and send forms to the demo server.

Set up ODK Aggregate Server

This is the server that will house your blank forms and push them out to your android devices. It also stores and allows you to organize all your collected forms and data.

Once collected and sent to Aggregate, the data can be exported as CSV, JSON, and KML files

You can either install a local instance of Aggregate on a Tomcat server or install a Google App Engine instance. The App Engine is much easier to set up, but having your own Tomcat server provides more control over your data. More information comparing the two can be found at http://opendatakit.org/use/aggregate/deployment-planning/.

Make sure Java 6 or higher is installed on the computer you plan to use.

App Engine Installation: o You'll need to setup an App Engine account. These accounts are free (under

these terms). You will need to be able to receive a text message from Google to verify your account.

o Once you're logged into your App Engine account, click on the "Create Application" button, choose an application identifier (e.g., my-app-id) and application title, and click on "Save." The identifier determines your url and can never be changed.

o Download ODK Aggregate v1.N.N. from https://code.google.com/p/opendatakit/downloads/list. Select the latest Featured release for your operating system. These downloads are wizard-based installers for the various operating systems. If you are running OSX, you must unzip the downloaded file before running the installer within it. Consider using a non-Featured release during forms development (to help ODK identify issues prior to a production release).

o The installer will guide you through configuring ODK Aggregate for App Engine and then launch a script to upload this configured ODK Aggregate to App Engine.

Local Instance Installation: o Installation instructions can be found here:

http://opendatakit.org/use/aggregate/tomcat-install/

http://code.google.com/p/opendatakit

http://opendatakit.org/use/collect/

http://opendatakit.org/use/aggregate/deployment-planning/

http://appengine.google.com/

http://code.google.com/appengine/terms.html

http://code.google.com/appengine/terms.html

http://code.google.com/appengine/kb/sms.html

http://code.google.com/p/opendatakit/downloads/list

https://code.google.com/p/opendatakit/downloads/list

http://opendatakit.org/use/aggregate/tomcat-install/


4

Next, you need to create an ODK username and password and grant it Data Collector privileges. Do this on the Site Admin / Permissions tab. This username and password can then be entered into ODK Collect's settings page. Once you do that, you will be able to download forms to ODK Collect, fill them out, and submit the results back to ODK Aggregate. Alternatively, you can configure the anonymousUser to have Data Collector permissions to allow ODK Collect to interact with the server without any username or password (i.e., anonymously).

Get ODK Build Account

Go to http://build.opendatakit.org/ and click on “Don’t yet have an account?” on the Sign in screen. Create a username and password and provide your email.

This account does not need to have the same credentials as any of the Aggregate users.

Building Forms in BUILD

Go to http://build.opendatakit.org/ and log into your build account. An example form is shown on the next page.

Name your form by clicking rename at the top of the window and entering the new name.

Add fields to your form by clicking the field type that you want from the bottom of the screen. You can also drag the selected type to the desired spot in the order in the screen’s main panel. Some additional information about each field is on the next page.

The fields appear in the same order in ODK Aggregate as they do here as you create the form, so it is a good idea to put the most important fields first so that it is easier to find the important data in Aggregate later.

Fill in the Properties for each field at the right side of the screen.

Data Name is the field’s name in the .xml file and the name that will be displayed in Aggregate, so pick labels that are short, clear, and only include letters and underscores in this field.

It’s a good idea to add a multiple choice field for the priority of the form so that you can sort the forms later in Aggregate by importance.

Always go to File->Save Form As… or File->Save Form to File… so that you have a copy of the .odkbuild file before you log out of Build. You cannot reconstruct your Build from an .xml file. If you don’t have the .odkbuild file saved and you want to make any changes to the form you will have to edit the xml file directly or redo all the work you did in build.

Go to File->Export to XML… to create the .xml file that you will put into Aggregate.

http://build.opendatakit.org/

http://build.opendatakit.org/


5

Figure 1: Building a form.

Tips and tricks for filling in ODK Build field properties:

Text: Provides a textbox. The number of characters allowed can be changed by selecting the range. Always check Inclusive on your Minimum and Maximum when doing so.

Numeric: o Numeric only allows numbers to be entered, not letters or special characters. If

you want something like a phone number in the format xxx-xxx-xxxx, then use a Text field and specify the format you want used in the Hint portion. This is showed to your user after the field title in the form.

o To set a range on numbers keep in mind that the range is the numbers allowed, not the number of digits in the number. (E.g. To limit a zip code to 5 digits set your Minimum to 0 and maximum to 99999.) Always check Inclusive on your Minimum and Maximum when entering a range.

o The user input to Numeric fields can only be up to 9 characters long. For longer values use a text field.


6

Date: Displays the current date in the app. The date cannot be changed when filling in the form, so only use this when the current date is required. Changing the date causes the application to crash

Location: Records the GPS location of the device and the error on that measurement.

Media: Allows an image, video, or audio recording to be added. Image and Video work for this application - we have had technical difficulties with audio. See the ODK help files and user forums for more information.

Barcode: Requires that a barcode scanner be installed on your android device. These instructions are not included for this implementation of the application.

Choose One: Creates a multiple choice field in which only one option can be selected. You must add at least one Option in Properties for the form to work in Aggregate.

Select Multiple: Creates a multiple choice field in which more than one option can be selected. You must add at least one Option in Properties for the form to work in Aggregate.

Bulk edit: If you will be adding many Choose One or Select Multiple fields with the same set of options, you can save the options so that you don’t have to keep retyping them. Type them in for the first field, then click bulk edit. In the Options editor which appears click Save to Preset… then click Apply. To load the options in another field click bulk edit then in the Options Editor select the set you want, click Load Preset, then click Apply.

Metadata: This allows you to input the start and end time of the form’s completion. This will not show up in the form to be filled out, but the device will automatically record the information and it will show up when the form is sent back to the Aggregate server.

Group: Group is used to logically group fields together. Place other fields inside your group on the display. A check box in its properties lets you display multiple fields on the same page in your final form. Do this as much as possible to minimize the number of screens your user has to go through to answer all the questions without making them scroll too much on the same page. An appropriate balance will depend on the screen size of the devices that the form will be filled out on.

Branch: allows the logic of the form to branch depending on the answers to a given field. (e.g. Answering Yes to question 7 takes you to question 8, but No to question 7 takes you to question 10.)

Put Form into Aggregate

Log into your Aggregate account at the website created when you set up your server.

Go to the Form Management tab and click Add New Form.

IMPORTANT: Only click the “Add New Form” button once! Double clicking will send the server into a loop and make the whole site reset itself every few seconds.

Navigate to the .xml file that you exported from Build and click Upload Form.

The form is now available to be pulled into your android device.

If the form does not upload correctly go back into Build and edit it until it works. Pull Form to Android Device

On your android device open Lighthouse or ODK Collect.


7

Go to Change Settings. It should be one of the buttons on the bottom of your screen. The icon will vary based on your device.

Set your URL to the address of your Aggregate server, and Username, Password to your Aggregate account credentials.

Go back to the main screen of your app.

Download the form you created in the Get Blank Form Section. Check your work

You can now fill, save, send and delete forms.

Fill out a complete version of your form checking that all fields display as you want them to and that unexpected inputs to fields don’t crash the app. (e.g. if you have a Numeric field with a limit on the numbers allowed try a bigger number to see what happens.)

Make any necessary changes in Build and repeat the exporting to an .xml and putting it into Aggregate until the form is exactly as you want it. Don’t worry if it takes many tries on your first form. It gets faster the more familiar you are with ODK.

It is recommended that you save a new version of your form in Build every time you export to .xml. It’s easier to delete unnecessary forms later than to reconstruct a working version after changing fields.

Rename your build with different version numbers with each iteration exported to xml so that when you put it into Aggregate you don’t have to wonder which version is the most recent.

Adding additional fields

When you have the form working exactly as you want, you can go back to the .xml file to add some fields that Build did not provide. There are many things you can add to your forms depending on your familiarity with xml, and many code snippets are available on the internet.

To modify the .xml file open it in Notepad, Wordpad, or a similar program of your choosing. Add the desired code, and then save the finished .xml. Be sure to save the final product as an .xml file, not as a .txt file.

Finishing up

Upload the final version of your .xml into Aggregate. You’re ready to start collecting data!


8

Data Collection On your android device open the Lighthouse or ODK Collect app. The screenshots

show here will be from Lighthouse, but ODK Collect looks the same. Opening Screen:

If this is the first time you are filling in forms on this device, tap the icon located on the taskbar of your device. Your icon may look different depending on the device, but it should be in a similar location. Tap “Change Settings”.


9

Set the URL to the address of the ODK Aggregate server that you set up earlier. Set your username and password to the ones you selected in your ODK Aggregate account.


10

Return to the main menu using the back icon in the bottom corner of your taskbar.

If you already have the form on your device, then skip to the step for Fill Blank Form. If this is the first time you will be filling in a particular form tap “Get Blank Form”. You must be connected to the internet to complete this step.

The username and password should be automatically entered, but if it is not, type in the username/password from your ODK account. Tap “OK”.

Select the form that you would like to fill and tap “Get Selected”. You may download more than one form at a time. Here we will only be working with the DAF form. The DAF is modeled after the Monterey CERT Damage Assessment form.


11

Tap “OK” on the success dialog box.

Tap “Fill Blank Form”.

Tap on the form you want to fill


12

Go through filling in the form by swiping left and right to move forward and back. The keyboard will appear different depending on the type of input required.


13

To record GPS coordinates, tap the “Record Location” button.

Wait until your Android device achieves an accuracy level that is accurate enough for your needs, keeping in mind that it may be a few minutes. If the device is using GPS you will get more accurate results, but will take a bit longer than using a network. 10m accuracy is the best typical accuracy achieved with most Android devices.


14

.

Then tap “Record Location”.


15

To put a photo into the form you can either take one with your device’s camera or load in a previously taken photo. To take a picture, select “Take Picture”, making sure to take all pictures in landscape view. The + - slider zooms in and out; the blue button actually

takes the picture, and the button provides access to the various camera settings. Operation of the camera tool on your device may vary.


16

Tap “Done” if you are satisfied with your picture or if you would like to retake it. The Done button may be on top of the picture, so it may not be immediately obvious, but it is there in some form.


17

To instead pick an image tap “Choose Image”.

Select “Gallery” and tap on the image you want to select.

Once the photo is selected tap it again to put it into the form.


18

Some screens may have more fields than fit on the screen when the device is in

landscape orientation. Either scroll through them or rotate the device to the portrait orientation.


19

Some entries only allow numerical inputs.


20


21

After completing your form you can edit, send, or delete your form.


22

To change a completed form tap “Edit Saved Form”. Then tap the form you wish to change. If you have multiple copies of the same form, use the time and date stamp to determine which to edit.

You can tap on the field you would like to edit or use the “Go to Start” or “Go to End” buttons to navigate through the form.


23

While in the middle of a form, tap the icon in your taskbar to bring up some options. Tapping “Go To Prompt” will take you back to the list of fields so that you can edit another one. Save Form will save the form.

Exit the editing by either, going to the end of the form and tapping “Save Form and Exit”,

or by tapping the back button in your taskbar and tapping “Save Changes”.

You can delete a form by tapping “Delete Saved Form” on the main menu. Using the tabs at the top of the screen you can choose to either delete a saved completed form or a blank form.


24

Keep in mind that deleting a blank form will only delete it from the device. The master copy will still be available on the server for download. Deleting a saved form will only delete it form the device as well. Be sure to send completed forms before deleting them to ensure that they are on the server.

To send your completed form tap “Send Finalized Form” on the main menu. Then select the form or forms that you want to upload to the server and tap “Send Selected.” You must be connected to the internet for this step. Once a form has sent successfully it will no longer be stored on your device.

If there is not internet available in the field, the forms can be saved on the device until you are back within range of internet connectivity.


25


26

Data Analysis using Aggregate Once your data have been collected on your tablet/phone and sent back to the

Aggregate server, you can start to analyze your data.

Log into the Aggregate server you have created using the proper credentials.

Submissions

To display the form you are interested in select the form from the dropdown field titled Form.

All of the received copies of the form will appear in the main part of the display in the order they were submitted with the most recent forms on the bottom.

To delete a submission click the red ‘x’ at the far left of the fields.


27

To view a picture attached in a form double click the picture. This will enlarge it. If the picture is too large to view easily in the frame, right click the enlarged picture and select “Open image in new tab”


28

All of the data from each form is displayed. Depending on the number of fields in your form it may be difficult to fit them all on one monitor.

The fields appear in the order that they appeared in the form on the mobile device, so putting the most important fields first when you create the form will make it easier to find the important data in Aggregate.


29

In order to only display the most important data from each form or to only display the most important forms you can filter the data using the tools on the left of the screen.

To create a filter click “Add Filter”. o Display/Hide - Will you be selecting data to show or hide? o Rows/Columns - Choose whether you will be working with the rows or columns of

the table. The Rows selection lets you see entire entries that share the requested feature while Columns selection lets you see single features in all entries.

o If you selected Rows: Pick the column that you want to evaluate for all rows. Pick the operation you would like to use. Pick a value to use for the evaluation

o If you selected Columns: Pick the columns you want to either display or hide. You can select more than one filter at a time by holding the Ctrl key while

you click to select multiple single fields or holding the Shift key to select several in a row at once.

o Click "Apply Filter".


30


31

You can apply multiple filters at once. They can also be saved as either single filters or as a group.

To save your filter check “Display Metadata” then click “Save”. Name your filter and click “OK”. Unless you save it, the filter will disappear when you switch to a different form or close ODK Aggregate.

To apply your filter, select it in the Filter dropdown menu.


32

You can also visualize the data as different types of graphs by clicking the Visualize button in

the top bar.

Selecting Type: Pie Chart allows you to graph the different fields as a pie chart. The Column to

Visualize is the field that will be graphed. Selecting “COUNT” will graph only the relative

occurrences of the values of column to visualize. Selecting “SUM” will display the percentage of

the total number of occurrences of the field selected split up by the values in the column to

visualize.


33


34

Selecting Type: Bar Graph displays the same information as “Type Pie Graph”, but in bar graph form.


35


36

Selecting Type: Map and clicking Map allows you to see pins dropped at the GPS locations of

the submitted forms on the Google map. It does not allow you to display the pins over aerial or

satellite imagery.


37

Forms can be exported to CSV, KML, or JSON file formats for further analysis by clicking Export.

Choose the file type to which you would like to export the form data. You can also select a filter that you have previously created and saved if you only want a subsection of your data to be in the output file.


38

The file will appear at the top of the list in the submissions tab under the

Exported Submissions section.

The CSV file is an Excel spreadsheet of comma separated values that can be edited and analyzed.


39

When exporting a KML file the Geopoint will automatically select the GPS coordinate of each form. The Title dropdown allows you to select the field to use as the label for each point. Here is an example using priority.


40

Download the kml and open it in Google Earth. The form locations will appear as pins. Clicking on a pin will open a popup window with all of that form’s information. You may have to scroll in the popup to see all of the fields.


41

To make the photos visible, click View in one of the photos and then log into the ODK Aggregate screen that pops up with your Aggregate credentials. Then clicking “Back to Google Earth” in the top left corner of the window will take you back to the main map. All of the photos should display automatically when you click the pins.


42

The data can also be exported as a JSON file. The JSON is similar to an XML file and is used to share data quickly.

Your JSONs can be put into UICDS and then into WebEOC as described in Playbook#RSC-09.


43

Put Form into Aggregate

Log into your Aggregate account at the website created when you set up your server.

Go to the Form Management tab and click Add New Form.

IMPORTANT: Only click the “Add New Form” button once! Double clicking will send the server into a loop and make the whole site reset itself every few seconds.

Navigate to the .xml file that you exported from Build and click Upload Form.

The form is now available to be pulled into your android device.

If the form does not upload correctly go back into Build and edit it until it works.


44

Playbook Directory This Playbook is one of a series of Playbooks designed to cover the technical breadth of the NPS-DHS Earthquake Response Project. Each Playbook describes one series of products and its use. These Playbooks can be printed, transmitted electronically as Portable Document Format (PDF) documents, or stored locally on existing emergency management networks, workstations, or mobile devices. The following summarizes the individual Playbooks developed as part of this project and available to emergency responders. See the listed Playbook for specifics and details.

Playbook#RSC-01: NPS-DHS Remote Sensing Project/Products Overview

Playbook documenting project and scope and big picture for other Playbooks

Playbook#RSC-02: Monterey County Baseline Products and Pre-Event Data Processing

Playbook documenting baseline data, preprocessing, use/analysis of basic products

Playbook#RSC-03: Monterey (City) Infrastructure Products

Critical Infrastructure data (location, description, pre-event photos, geolocated imagery

frames and metadata)

Playbook#RSC-04A: Airborne Imagery Change Detection Products (SDSU) Monterey baseline imagery of critical infrastructure, Camp Roberts imagery, and selected

change detection example products. Full-Resolution NEOS imagery

Playbook#RSC-04B: NOAA Night Lights/Power Change Detection and Fire Detection Products Night lights/power and fire detections (NOAA)

Playbook#RSC-05A: Social Networking Products (Ushahidi)

Ushahidi implementation and instructions for Monterey City/County

Playbook#RSC-05B: Social Networking Products (Twitter)

Twitter implementation and instructions for Monterey City/County

Playbook#RSC-06: Mobile Application Damage Assessment Product Lighthouse damage assessment application download, install, configure, execute

Playbook#RSC-07: Post Event Processing Scenarios Products

LiDAR DEM, DSM, derived products, NAIP/WV-2 Change Detection Examples

Playbook#RSC-08: Soft and Hardcopy Output Products and Distribution

GeoPDF Products, Monterey Map Books, w/National Grid Index, PDF and Printed

Playbook#RSC-09: Common Operating Picture (COP) Products

Sensor Island Common Operating Picture, UICDS to WebEOC Link

Playbook#RSC-10: Systems Integration, Transition, and Training

Hardware/Software Installation Details, Coordination, and Integration


45

References

Brunette,Waylon. "Open Data Kit 2.0: Expanding and Refining Information Services for Developing Regions."2013. Web. 12 Mar. 2013. http://www.hotmobile.org/2013/papers/full/2.pdf

Brunette,Waylon. "ODK Tables: Building Easily Customizable Information Applications

on Android Devices." Bangalore, India: ACM, 2013. http://opendatakit.org/wp-content/uploads/2013/02/dev-final34.pdf

Brunette,Waylon. "Open Data Kit Sensors: A Sensor Integration Framework for Android

at the Application-Level .". Low Wood Bay, Lake District, UK: ACM, 2012. http://opendatakit.org/wp-content/uploads/2012/10/mobisys2012.pdf

Chaudhri, Rohit. "Open Data Kit Sensors: Mobile Data Collection with Wired and

Wireless Sensors.". Atlanta, Georgia: ACM, 2012.http://opendatakit.org/wp-content/uploads/2012/10/dev2012.pdf

Hong, YoonSung. "ODK Tables: Data Organization and Information Services on a

Smartphone.". Bethesda, Maryland: ACM, 2011. http://opendatakit.org/wp-content/uploads/2011/05/nsdr-tables-final.pdf

Kruse, F.A., Clasen, C.C., Kim, A.M., Runyon, S.C., Carlisle, S.C., Esterline, C.H.,

Trask, D.M., and Olsen, R.C., 2012, Tiered remote sensing and geographic information system (GIS) based map products for improved earthquake response: in Proceedings 34th International Geologic Congress (IGC), 5 -10 August, 2012, Brisbane Australia.

http://www.hotmobile.org/2013/papers/full/2.pdf

http://opendatakit.org/wp-content/uploads/2013/02/dev-final34.pdf

http://opendatakit.org/wp-content/uploads/2013/02/dev-final34.pdf

http://opendatakit.org/wp-content/uploads/2012/10/mobisys2012.pdf

http://opendatakit.org/wp-content/uploads/2012/10/dev2012.pdf

http://opendatakit.org/wp-content/uploads/2012/10/dev2012.pdf

http://opendatakit.org/wp-content/uploads/2011/05/nsdr-tables-final.pdf

http://opendatakit.org/wp-content/uploads/2011/05/nsdr-tables-final.pdf

Date post:	03-Jun-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Mobile Applications Products for Disaster...

Documents