Layer use cases
- Lite Farm
- David Trapp
Layer name | Version / priority | Actions / interactions (session data) | Default on click behaviour | Description | Zone or location based | Manner of creation | Static, current, historical, forecast | Needs legend? | Static / Dynamic | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
Topography |
| View |
| Zone-based view of elevation ranges, e.g. (0 - 5 m, 6 - 10 m, 11 - 15 m). | Zone |
| Static | Yes | Static |
|
Soil texture | Irrigation | View |
| Zone-based view of soil texture including percent sand, clay, and silt per zone. For any given lat / long we want to know a soil texture to be able to understand how water will be stored. | Zone |
| Static | Yes | Static | Pre-requisite for understanding soil water content. |
Irrigation zones | Irrigation | View |
|
|
|
|
|
|
|
|
Irrigation prescription | Irrigation |
|
|
|
|
|
|
|
|
|
Organic, transitioning, and non-organic locations |
|
| Location details? | Location-based view of the organic status of each location on the farm. Likely statuses include:
| Location |
|
| Yes | Dynamic |
|
Crop group (e.g. cereals) |
|
|
| Location-based view of the crop groups grown on each location on the farm. In addition to each of the crop groups, we would need a “Not applicable” for non crop-enabled locations. | Location |
|
| Yes | Dynamic | Would need a way to show multiple crop groups being grown on the same location. Time lapse would need to define start / end date logic for crops. |
Crop type (e.g. apples) |
|
|
| Location-based view of the type of crops grown on each location on the farm. In addition to each of the crop groups, we would need a “Not applicable” for non crop-enabled locations. | Location |
|
| Yes | Dynamic | Would need a way to show multiple crop types being grown on the same location. Time lapse would need to define start / end date logic for crops. |
Task activity per location |
|
| View task homepage pre-filtered for that location and date or date range. | Number of tasks at that location on a specific date or during a date range. Include the ability to filter by task status and potentially task type. | Location |
|
| Maybe* | Dynamic | Could either use a heatmap treatment to show frequency or just show numbers similar to clustered points. LIkely need a onClick preview to show details about the task. |
Day planner |
|
|
| Show all locations where an incomplete task exists for the selected assignee or assignees for a selected date or date range. | Location |
|
| Maybe* | Dynamic |
|
Profitability by location |
|
|
| Calculate profitability based on either estimated harvest / actual harvest minus inputs and task hours. |
|
|
|
|
|
|
Crop enabled |
| View |
| Show the following location types with different visual treatment:
| Location |
|
| Yes | Dynamic |
|
Intercropping / Agribiodiversity level |
|
|
| Show via a heatmap the relative agribiodiversity of the location. | Location |
|
| Yes | Dynamic | Steps and criteria to be co-designed with Hannah, Lucas, and Illyas. |
Last pruning | Agroforestry |
|
| Last completed pruning task on this location |
|
|
|
| Dynamic | May need to add the ability to define how frequently pruning should happen. This could also be an attribute of the crop. |
Permaculture zones |
|
|
|
| Zone | User defined using zones |
|
|
|
|
Soil water deficit |
|
|
|
|
|
|
|
|
|
|
Water moisture target |
|
|
|
|
|
|
|
|
|
|
Soil water potential |
|
|
|
|
|
|
|
|
|
|
Active vs. fallow |
|
|
|
|
|
|
|
|
|
|
Weather |
|
|
|
|
|
|
|
|
|
|
Irrigation infrastructure |
|
|
| Only show things like water valves, pivots, waterways, drainage, drip tape, etc. |
|
|
|
|
|
|
Transportation / access |
| View |
| Only show locations related to transportation - e.g. gates, fences, roads, footpaths. | Location |
|
| No | Dynamic | Probably doesn’t need legend, but should have labels. |
Sunlight hours |
|
|
| Weather forecast or weather forecast and topography. |
|
|
|
|
|
|
Harvest forecast |
|
|
| Days to next harvest task. |
|
|
|
|
|
|
Nutrient balance |
|
|
| Some senstivity around how we display this in order to not push individuals towards the “NPK mentality”. |
|
|
|
|
|
|
Carbon stocks |
|
|
|
|
|
|
|
|
|
|
Soil analysis results |
|
|
|
|
|
|
|
|
|
|
Compaction |
|
|
|
|
|
|
|
|
|
|
Micronutrient balance |
|
|
|
|
|
|
|
|
|
|
Microbial content |
|
|
|
|
|
|
|
|
|
|
Biodiversity observations per zone / per location |
|
|
| Colour coding to specify |
|
|
|
|
|
|
Irrigation layer use cases
Layer name | Version / priority | Actions / interactions | Description | Zone or location based | Manner of creation | Current, historical, forecast | Needs legend? | Static / Dynamic | Notes |
|---|---|---|---|---|---|---|---|---|---|
Topography |
| View | Zone-based view of elevation ranges, e.g. (0 - 5 m, 6 - 10 m, 11 - 15 m). | Zone |
| Current: only 1 version | Yes | Static |
|
Soil texture | Irrigation |
| Zone-based view of soil texture including percent sand, clay, and silt per zone. For any given lat / long we want to know a soil texture to be able to understand how water will be stored. We know soil textures change across depths, e.g. 10 cm vs. 1m. | Zone |
| Current: only 1 version | Yes | Static | Pre-requisite for understanding soil water content. Will need to support multiple depths for each zone. |
Irrigation zones | Irrigation |
|
|
|
|
|
|
|
|
Irrigation prescription | Irrigation |
|
|
|
|
|
|
|
|
Soil water deficit | Irrigation |
|
|
|
|
|
|
|
|
Water moisture target | Irrigation |
|
|
|
|
|
|
|
|
Soil water potential | Irrigation |
|
|
|
|
|
|
|
|
Irrigation infrastructure | Irrigation |
| Only show things like water valves, pivots, waterways, drainage, drip tape, etc. |
|
|
|
|
|
|
Open questions:
Different types of layer history:
Some will change regularly and will be able to learn from changes over time
Some just need the ability to roll-back to previous, more correct versions
For layers with a time step functionality targeting locations, should locations appear / dissapear as their creation date is passed?