Field Task is an Android app that can be used for collecting data for Monitoring and Evaluation from outside the office including locations without data connectivity. It also has task management functionality which enables it to be used for work force management applications. Further details on installing and testing Field Task on an Android device can be found here. You will need to set up an account on the free hosted server to test the app.

• Dependencies
• Setting up your development environment
• Branches
• Variants
• Incorporating the latest upstream changes
• Changes in the Field Task fork
• Acknowledgements

Most dependencies are managed using gradle, however some Field Task functionality requires a modified version of JavaRosa(https://github.com/smap-consulting/javarosa). You will need to add this to your development environment in order to access these features.

1. Download and install Git if you don't have it already

2. Download and install Android Studio if you don't have it already

3. In Android Studio install the target SDK

4. Add Smap JavaRosa as a project in Android Studio

    Follow the readme instructions in the javarosa repository to build the latest production java rosa version. Currently tip of production branch.
    copy the generated jar file to fieldTask/collect_app/libs. You may need to create the libs folder
    The version of java rosa that you need is referenced in the application's build.gradle
   

5. Fork the Field Task project (why and how to fork)

6. Clone your fork of the project locally. At the command line type "git clone" and then the url provided by git hub.

    git clone https://github.com/YOUR-GITHUB-USERNAME/fieldTask4.git
   

7. Checkout the production branch

    git checkout production
   

8. Use Android Studio to import the project

9. Get a Google services json file

    Sign into the firebase console
    Add a project
    Select Android to add firebase to your Android app
    Specify the package as: org.smap.smapTask.android
    Register the app 
    Download the google-services.json file and place it in the fieldTas4/collect_app folder
   

10. Get a Google Maps API key. A credit card number is required however there a fairly significant number of requests available at no charge each month. Check how many map calls you expect to be using and the expected cost before signing up.

11. Enable Google Maps for your application. Your apk needs to be given acces to the google maps API key that you have created.

    Goto the google developers console
    Click enable APIs and services
    Select Maps SDK for Android
    Select Manage
    Select Credentials
    Add the package name and sha-1 signing certificate for your app to the google maps API key that you created in the previous step
    

12. Create a Mapbox account. Select the "Pay-As-You-Go" plan. Like Google, Mapbox provides free API usage up to the monthly thresholds documented at https://www.mapbox.com/pricing. You can find your access token on your account page.

13. Edit or create collect_app/secrets.properties and set the GOOGLE_MAPS_API_KEY and the MAPBOX_ACCESS_TOKEN property to your access keys. You should end up with two lines that looks like this:

     GOOGLE_MAPS_API_KEY=AIzaSyA9C_...
     MAPBOX_ACCESS_TOKEN=pk.eyJ1IjoibmFwMjAwMCIsImEiOiJja...
    

14. Select run to view fieldTask in an emulator

• production - The latest Field Task code
• master - The latest unmodifield code from the upstream repository

The variant in the github repository that you will want to start with is "standard". This contains some resources and Java code to handle customisable processing around location change. Background location recording can be enabled on FieldTask and by default this is used only for geo fencing and the location data is not stored. The register function in the LocationRegister file can be modified to do additional processing of location changes if you need that.

1. Update the master branch to the latest version. On the commnad line

    git checkout master
    git fetch upstream
    git merge upstream/master
   

2. Create a branch with the version you want to merge into Field Task

    git branch merge_master <tag name>
   

   is the tag in odk collect identifying the version that you want. merge_master is the temporary branch that will be created. You can name it as you wish.

3. Create a branch in which to merge the code

   git checkout production
   git checkout -b merge
   git merge --no-commit merge_master
   

   This creates a temporary branch called merge from the latest production branch and then merges code from merge_master without committing the changes

4. Fix merge issues.

   There are likely to be many of these. Smap changes from ODK are either in their own files or marked with the comment "smap". If there is a difference and no "smap" comment then you can generally accept the version from ODK. Otherwise a manual merge is required to preserve the smap functionality.

The following changes from the upstream implementation will need to be merged and then tested before releasing a new version that includes upstream updates/

• Login Page.
• One touch synchronisation
• Form List, Task List and Map Tabs on the home page.
• Automatic synchronisation when a form is changed on the server.
• Geofencing for showing and downloading of forms
• Chart Widget
• Form Launcher Widget
• NFC Widget
• Auto launching camera, barcode and other widgets
• Task Management
• Self Assigned Tasks
• Navigation to tasks using google maps
• Online lookup of choice values
• Online pulldata
• Online lookup of images for annotation
• Online lookup of labels in images
• Searching for choice values using "in" and "not in" functions
• pulldata acting on multiple records

This project:

• forks the odkCollect Library of (http:https://opendatakit.org/)
• includes the Android SDK from [MapBox] (https://www.mapbox.com/)