FieldSight is a tool to remotely monitor, supervise and manage your projects. Major objectives of FieldSight includes,
Assure quality and consistency throughout the project lifespan by returning to monitor a site with custom forms collecting 22 kinds of data even when offline and out of range.
Replicate the organization structure and assign user specific roles, with differentiated access and dialogue through several communication channels and supporting educational materials.
Track project progress with user friendly dashboards that visualize data in the form of interactive maps, charts and more with a donor viewing option. Export all data simply, for further custom reporting.
Clone the project locally. At the command line:
git clone https://github.com/fieldsight/fieldsight-mobile
If you prefer not to use the command line, you can use Android Studio to create a new project from version control using https://github.com/fieldsight/fieldsight-mobile
.
Maintainers keep a folder with a clean checkout of the code
Maintainers have a local.properties
file in the root folder with the following:
sdk.dir=/path/to/android/sdk
Maintainers have a secrets.properties
file in the collect_app
folder with the following:
// collect_app/secrets.properties
RELEASE_STORE_FILE=/path/to/collect.keystore
RELEASE_STORE_PASSWORD=secure-store-password
RELEASE_KEY_ALIAS=key-alias
RELEASE_KEY_PASSWORD=secure-alias-password
Maintainers also have a google-services.json
file in the collect_app/google-services.json
folder.
To generate official signed releases, you'll need the keystore file, the keystore passwords, a configured collect_app/secrets.properties
file, Then run ./gradlew assembleRelease
. If successful, a signed release will be at collect_app/build/outputs/apk
.
SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.
When cloning the project from Android Studio, click "No" when prompted to open the build.gradle
file and then open project.
We have seen this problem happen in both IntelliJ IDEA and Android Studio, and believe it to be due to a bug in the IDE, which we can't fix. As a workaround, turning off Instant Run will usually avoid this problem. The problem is fixed in Android Studio 3.5 with the new Apply Changes feature.
`