Requirements
- Lite Farm
Epics | Description | Versions |
|---|---|---|
The ability to add sensors, sensor reading types, and sensor readings to a farm via:
| V1, V2 | |
View sensor (https://lite-farm.atlassian.net/browse/LF-2507 amongst others) | V1 | |
V1 | ||
Add “Pivot irrigated field” to location types and build a creation flow for this. | V2 | |
View pivot | Needs to encompass:
| V2 |
View farm map layers | Needs to encompass:
| V2 |
Irrigation task supports depth based irrigation types (see https://lite-farm.atlassian.net/browse/LF-2794) | Support for both volume based and depth based irrigation types. | V1 |
Generate irrigation prescription | Potential scope:
| V2 |
View irrigation prescription |
|
|
|
|
|
Area | Epic | Details | Questions / Notes | Version |
|---|---|---|---|---|
Sensors |
| May or may not be needed, to be explored. | TBD | |
Sensors | Bulk add sensors via csv upload |
| V1 [DELIVERED] | |
Sensors | View sensor detail |
|
| V1 [DELIVERED] |
Sensors | Edit sensor |
|
| V1 [DELIVERED] |
Sensors | Retire sensor | Can’t retire if planned task associated with it? |
| V1 [DELIVERED] |
Farm map | List / tile view for all locations with limited filters |
|
| TBD |
Pivot irrigated field |
| Schedule is how frequently the irrigation prescription should be updated, always > 24 hours How do users upload kml? What do we need to check for here:
Is the assignee the system and LiteFarm does everything or is a human in the loop and responsible for marking something complete once the actual irrigation has taken place. | V2 | |
Pivot irrigated field | View Pivot irrigated field (via farm map) |
|
| V2 |
Pivot irrigated field | Edit Pivot irrigated field |
|
| V2 |
Pivot irrigated field | Retire Pivot irrigated field |
|
| V2 |
Pivot irrigated field | Designate existing location as irrigated |
| May or may not be needed, to be explored. | TBD |
Farm map filters | Filter Pivot irrigated field on farm map |
|
| V2 |
Farm map layers | View current moisture readings (via farm map layer + filter) |
| Likely best to just show point data overlaid on sensor. Try to generate a gradient? Should be overlaid over other locations? Filter vs. layer Need to investigate! | V2 |
Farm map layers |
|
| Will be imported via kml at the farm level or pulled and overlaid from Soilgrids. | TBD |
Irrigation tasks | Add irrigation task flow (user created) |
|
| V1 [DELIVERED] |
Irrigation tasks | View irrigation task (user created) |
|
| V1 [DELIVERED] |
Irrigation tasks | Mark irrigation task completed abandoned (user created) |
|
| V1 [DELIVERED] |
Irrigation tasks | Edit irrigation task (user created) |
|
| V1 [DELIVERED] |
Irrigation tasks | Add irrigation task (system created) |
| Important to document changes to the task | V2 |
Irrigation tasks | Automated completion of irrigation task (by system) |
| Should management be able to mark it complete manually?
| V2 |
Irrigation tasks | Edit system created irrigation task | Don’t allow? Link to irrigation prescription instead? |
| TBD |
Irrigation tasks | Automated abandonment of irrigation task (by system) |
| System marks as abandoned If the irrigation prescription was rejected Should management be able to mark it abandoned manually? If so, remove that irrigation prescription | TBD |
Notification | View irrigation prescription notification | Link to irrigation prescription |
| V2 |
Whole farm characteristics | Upload farm characteristics |
| May or may not be needed, to be explored. | TBD |
Insights | Temperature (whole farm or sensors) |
| May or may not be needed, to be explored. | TBD |
Insights | Soil moisture level by sensors over time |
| May or may not be needed, to be explored. | TBD |
Insights | Location history |
| May or may not be needed, to be explored. | TBD |
Iceboxed for V1
View irrigation prescriptions (list view)
View historical irrigation prescription
Filter irrigation prescriptions
View proposed irrigation prescription
Accept proposal
Roll-back to previous irrigation prescription
Reject and do not replace prescription