User Stories

This application has two main use cases: mapping (different ways) and analysis.

Mapping (new trees)

This is a process of adding new trees to the database. This mostly happens in the field, using a phone. The user needs to be able to quickly locate themselves on the map, select precisely where a tree is located, add some basic tree description and measurement, upload a photo or a few of them, then repeat the whole cycle. Multiple photos might need to be uploaded, especially when a tree is damaged in multiple places and needs to be pictured from different angles. It would be best to have an option to pick the main image for a tree.

The user should be able to repeat this cycle with as little actions as possible.

Note that when adding new trees, mappers typically go street by street, and streets have little variation in tree species. Normally it's 1, rarely more than 3 species of trees combined. So, on the new tree page, it would be great to have a list of a few recently added tree species to avoid typing the same thing over and over again. Other attributes, like height or circumference, typically differ and need not be auto-filled.

Some conclusions:

• The map UI should follow best practices established by other map-centered applications, such as Google, Apple or Yandex.

Mapping (updates)

This is a process of updating the data using live survey. This mostly happens in the field, using a phone. The user selects one of the following options:

• List trees without photos.
• List trees with basic parameters missing. (Might require measuring tools so a different case.)
• List trees updated more than 6 months ago.

They then get a map with pointers of trees to check. When the tree is updated, photos and measurements are added, the tree is removed from the list, the user can pick another tree on their way to go and check. This is a kind of gaming procedure, where the user is encouraged to clean up the map around them from incomplete trees.

The process should also be very straight-forward, with a minimalist UI: click a tree, quickly access photo uploads or basic parameters editor, save changes, get back to the original UI.

Analysis (research)

This is when a user is at a fixed location, using a device with a bigger screen, to search for the trees, browse them, review photos and comments, occasionally make corrections to the existing data. Like, move trees to make a straight line (which is hard to accomplish on the go), fix or add latin names (because on the go one typically just enters something like "oak").

Analysis (moderation)

This is when a user reviews updates made by other users. When adding data on the go, it is easy to make typos. It should be possible to list recent updates and quickly edit them, if necessary.