- 1 Project description - Android coordinate picker
- 2 List of group members
- 3 Summary of requirements
- 4 Time schedule
- 5 Task dividing
- 6 Delivery
- 7 Documented learning during project
- 8 Suggested improvements
- 9 Milestones
Project description - Android coordinate picker
The task description can be found here. They way we understand the project description, the problem we are going to solve is that currently the Tracker module of DHIS2 is only able to capture the coordinates of the current user. However, sometimes there is a need to capture coordinates of locations the user is not currently at, and this is what we are going to do. This is to be done by using a map and clicking on the position with the coordinates the user wishes to capture.
In other words, we are implementing new functionality in the Tracker module.
List of group members
Martin Kolbeinsvik - email@example.com
Jon-Robert Skårberg - firstname.lastname@example.org
Sebastian Søberg - email@example.com
Daniel Bugajski - firstname.lastname@example.org
Summary of requirements
Register location from a point-and-click on a map ind the Tracker module
Google maps API
Wiki pages will be updated continuously and is not mentioned in the week schedule below. Milestones as described on the wiki front page can be found in the section below this.
Week 45: Start project, write Wiki pages and familiarize with project (milestone 1).
Week 46: Familiarize with the DHIS2 system, testing and practicing with the system. Share experiences with each other, and start on the first bare-bone version (milestone two).
Week 47: Continue work with and finish the bare-bone version by November 22th. (This is a minimum, as we hope to have had more progression than this on the 22th.)
Week 48: Starting the work with "translating" our work from static HTML to a proper DHIS2 webapp (milestone three. We intend to fill the requirements by the end of this week, as we do not yet really know how demanding this will be.
Week 49: Continue the work from last week. If we are finished with milestone three by this time, we start finishing the app. If not, we continue with finishing milestone three by the deadline on December 4th.
Week 50: Finishing project and wrapping things up. Final delivery December 11th. Create and practice on presentation.
We work mostely together as a group, sitting in the same room while discussing and working. We all do our share in most parts of the project, while doing the programming itself on one or two computers at a time.
The static HTML-version is available on GitHub.
Our project is Android-based and the final delivery will not be in HTML. However, we have made a small HTML-version were it is possible to set and move a `marker` in a Google Map and the latitude and longitude is displayed on top.
Static stand-alone Android version
The Android version uses Google Maps.
DHIS android sdk project
Solution 1: Inline map
An inline Google Maps is displayed when the map icon button is pressed. The map's default view is over Africa (latitude and longitude 0) and can be moved, rotated and zoomed by the user.
A marker can be added by the user by touching anywhere on the map. It can also be moved and dragged around by pressing and holding the marker for a second. Any location change on the marker changes the `Latitude` and `Longitude` fields and is automatically saved by the app.
On view of existing patient entry with location data, as well any update to the location fields due to pressing the "I am here" button, places an appropriate marker on the map.
An issue with `fragment` and the `LayoutInflator` crashes the app the second time the `CoordinatesRow` is rendered.
Solution 2: Map with intent
New activity is started and Google Maps displayed when the map icon button is pressed. A marker is default placed over Africa (latitude and longitude 0) and can be moved and zoomed by the user. User can change the default location by touching anywhere on the map and the map view "follows" marker's location. Any location change on the marker, changes the `Latitude` and `Longitude` and is automatically saved by the app when <SET COORDINATES> or <GO BACK> button is pressed.
Starting a new Activity from CoordinatesRow.java on button click on the map icon.
Documented learning during project
Our most obvious learning is that the DHIS2 SDK is very complex and takes a lot of time to understand before one can start working on it. We have by far spent more time on reading classes and documentation, than we have spent on actual coding. The first challenge was to find out where to actually start, but when we after a while found out that the java class CoordinatesRow were the place to start, it all went a bit more smoothly.
We have also experienced that working with Android can be a bit cumbersome when two of the group members don't have any Android devices. Emulators have not always been very stable, and it would have been nice if this didn't take up as much of our time as it actually did.
Of course, the app crashing the second time CoordinatesRow is rendered is unacceptable and should be fixed. We are unable to to this, but feel that our solution is decent if just that particular error is fixed.
Another improvement related to the map would be to move the map viewport to center on the marker when location data already exist and when it is set by pressing the "I am here" location button.
Each group should follow these milestones:
- Milestone 1: 8th November
Document features and architecture on Wiki
Show understanding of DHIS2 web apps
- Milestone 2: 22th November
First bare-bone version - static HTML
Uploadable as DHIS2 web app
- Milestone 3: 4th December
- Finished, if applicable also with mobile app.
- Final delivery: 11th December
- Presentation: mid December