Extra Features
The google map API has been implemented in Web and Android to allow the user to see the trees, and allow some features to interact with the map directly.
-
Two Taps to Add a Tree
When the map is tapped twice, with a small delay between each tap, there is the window to plant a tree that pops up. When filled and confirmed, the tree is added to the exact location that was specified by the users' taps. Please note that to see the tree on the map, you may need to wait for the confirmation message to pop up, and you may need to press the refresh button numerous times as data could take long to load.
-
Refresh
This feature refreshes the map and updates it with all the trees that were planted or cut down that were not there before.
Note: The user must back out of map page, reload it, and refresh the map to view any changes in the Info Window.
-
Mark Tree for Cut Down
This feature allows a citizen or a scientist to change the status of a tree to be marked for cut down for later surveying by a scientist.
Note: The user must back out of map page, reload it, and refresh the map to view any changes in the Info Window.
-
Viewing Trees
On the Web frontend, we have minimized the interaction with the Google Map, and only show the trees in their exact location.
-
Registering
In order to access the application any user needs to register in the system the first time they want to use it. The registration requires some simple entries, such as the person's name, their email address, a password that will be kept in private, and a selection between being a Resident or a Scientist. The selection of each of these will allow for a different kind of functionality for the system, that is, scientist will have access to more features than residents, due to the nature of their profession. Once this has been completed, the user will then be able to navigate the MonTREEal application.
-
Logging In
If someone wants to use the application and they have already registered, they will need to login using the same email address and password that they had registered with. Depending on the how the user has previously registered their role in the system, that is, whether they are a Resident or a Scientist, the user will have different access. The main page will then appear and the person will be able to use the application freely.
At the beginning of our project we mentioned the use of Slack. Slack is a useful tool for communication but it can even be more powerful then that. For our own usability, we connected Jenkins builds to our slack project, such that we receive notifications when a build is in progress, has been completed, or has failed. Thus, continuous updates and tracking on the project can be done.
