...
V2
...
V1
...
Reading list
An introduction to soil moisture and the bucket concept
Pivot irrigated location: https://lucid.app/lucidchart/f712a83a-ec8a-4382-8da4-94a61a5f33f8/edit?viewport_loc=1217%2C345%2C2219%2C1041%2C0_0&invitationId=inv_13649814-34a2-4ef6-afd4-8eb2f7bcf415#
Very rough requirements: Requirements
Figma sketches: https://www.figma.com/file/1Izd87rqbOH1eSFoyOmOTo/Irrigation?node-id=420%3A17106
Technical resources
Soilgrids API: https://rest.isric.org/soilgrids/v2.0/docs#/default/query_layer_properties_properties_query_get
Rosetta (webapp): https://www.handbook60.org/rosetta/
Rosetta (Github): https://github.com/ncss-tech/ROSETTA-docs
Quote from an Alberta farmer:
Effective remote sensing of soil moisture would likely help increase water use efficiency, by helping detect either "underwatering" conditions (water delivery problems, water scarcity/distribution problems, plant stress due to high evapotranspiration rates, high winds/temperatures, etc.) or "overwatering" conditions (plant stress from flooding/poor drainage, elevated energy costs for water delivery eg. electricity/natural gas, excessive soil leaching causing nutrient removal or excess gasification, etc.). We anticipate that for many established irrigation operations, overwatering is more prevalent than underwatering. Water "prescriptions" are endlessly dynamic due to changes in the external environment (relative humidity, wind, temperature, etc), so remote sensing alternatives featuring soil moisture sensors, plant stress sensors/surveillance, and weather stations are technologies requiring evaluation for Southern Alberta applications. On our farm, we have automated pivot control on the majority of our 100+ pivots, but still rely on an irrigation team to evaluate moisture conditions and plant stress to make adjustments. Smart irrigation management technologies using the technologies mentioned above would help us reduce electricity (pumping) costs, optimize water usage, and reduce endless truck traffic to the fields through the irrigation season.
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Summary
...
Description
...
Fix Version
Sensor model work
...
Build out database to support tables for:
Sensors (location)
Sensor reading types (see ESCI doc)
Sensor readings
...
MVP
Bulk or individual?
...
v2
Upload screen with template and front-end validation
...
v1
Bulk sensor creation and outcome splash
...
v1
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Summary
...
Description
...
Fix Version
Sensor model work
...
Build out database to support tables for:
Sensors (location)
Sensor reading types (see ESCI doc)
Sensor readings
...
MVP
Bulk or individual?
...
v2
Upload screen with template and front-end validation
...
v1
Bulk sensor creation and outcome splash
...
v1
Questions:
Assignments for pivot or other system based irrigation that is automated?
Will need to be able to mark complete if you’re not the assignee.
...
Area
...
Epic
...
Details
...
Questions / Notes
...
Stories
...
Sensors
...
Add sensor via farm map
...
Add sensor to farm map sections under “Add”
Drop a pin flow
Sensor detail flow
Need to be able to multi-select type of sensor (e.g. Temperature, Moisture)
...
MVP:
Sensor model work
V1:
Bulk upload
V2:
Individual upload
...
Sensors
...
Bulk add sensors via csv upload
Where does this live? Could live on the default “+” on the farm map with a modal to differentiate individual vs. bulk.
At the end of the flow, what does the user see? Farm map? Filtered only for sensors?
...
High
...
Sensors
...
View sensor detail
...
Standard view / edit / retire pattern
Two tabs:
Readings
Details
...
Default readings ranges by sensor type? Pre-defined? e.g. 24 hours, 7 days, 30 days? If longer term, maybe goes to insight
Need to know the types of sensors, e.g. temperature, soil moisture, precipitation, wind speed
Could each of the types be at different depths? Different lat / long, something else?
For sensors that had multiple readings types, how would you display them? Stacked? Choosable with a picklist / tab
...
Medium
...
Sensors
...
Edit sensor
...
Location
Details
Type
Other attrs
...
Do we need to persist history of the sensor location and attributes or is the current state sufficient?
...
Medium
...
Sensors
...
Retire sensor
...
Can’t retire if planned task associated with it?
...
How to view retired sensors? Could have something like a farm map history insight where you drag a timeline and locations appear / disappear.
Probably should be closer to an archive than a traditional retire so that the reading history is still available. What’s the best way to do this?
...
Low
...
Farm map
...
List / tile view for all locations with limited filters
...
Tab between farm map and tile view
Tile view similar to crop management plan tile view
Categories for each location?
Filter for active / retired
...
Low
...
Pivot / Irrigated location
...
Add irrigated location (via farm map)
...
Drop pin
Define radius
Add pivot details
Define irrigation prescription settings:
Assignee?
Full auto vs. notify vs. manual
Schedule
Define contact for water district
...
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:
Correct location?
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.
...
High
...
Pivot / irrigated location
...
View irrigated location (via farm map)
...
Tabs:
Crops
Details
Irrigation prescriptions
View and filter irrigation prescription history
Export prescription
View / modify schedule
For proposed prescriptions:
Accept proposal (export)
Keep current (export)
Reject and do not replace prescription (no export)
...
Pivot / irrigated location
...
Edit irrigated location
...
Standard edit / retire pattern
Update irrigation prescription settings
...
Pivot / irrigated location
...
Retire irrigated location
...
Check for planned tasks
Automatically turn off irrigation prescription
...
Pivot / irrigated location
...
Designate existing location as irrigated
...
Farm map filters
...
Filter pivot / irrigated location on farm map
...
Farm map layers
...
View current moisture readings (via farm map layer + filter)
...
.
...
Try to generate a gradient?
Should be overlaid over other locations? Filter vs. layer
Need to investigate!
...
Farm map layers
...
View soil types / zones
...
Should be a layer to allow locations to overlap
...
Will be imported via kml at the farm level
...
Irrigation tasks
...
Add irrigation task flow (user created)
...
Select irrigation enabled location or select crop plan(s)
Add irrigation task details
Assign to user
...
Low
...
Irrigation tasks
...
View irrigation task (user created)
...
Low
...
Irrigation tasks
...
Mark irrigation task completed abandoned (user created)
...
Low
...
Irrigation tasks
...
Edit irrigation task (user created)
...
Edit irrigation task
Edit irrigation task details (prior to when it’s pushed to pivot)
...
Irrigation tasks
...
Add irrigation task (system created)
...
Automatically assigned to irrigation enabled location
Has link / attachment for irrigation prescription
Assigned to …
...
Important to document changes to the task
...
Irrigation tasks
...
Automated completion of irrigation task (by system)
...
Should management be able to mark it complete manually?
For now: If irrigation prescription was accepted
Future: Based on positive ack from pivot
...
Irrigation tasks
...
Edit irrigation task (system created)
...
Don’t allow?
Link to irrigation prescription instead?
...
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
...
Notification
...
View irrigation prescription notification
...
Link to irrigation prescription
...
Whole farm characteristics
...
Upload farm characteristics
...
Upload soil types map of farm
Page where user would upload should allow user to download kml template
...
Insights
...
Temperature (whole farm or sensors)
...
Low
...
Insights
...
Soil moisture level by sensors over time
...
Could be based on inputs from readings or soil lab results.
...
Low
...
Insights
...
Location history
...
Low
Logic:
Understanding various types of readings:
Temperature (component based)
Soil moisture
Data needs:
Crop stages for wheat
Water needs for wheat
Iceboxed:
View irrigation prescriptions (list view)
...
View historical irrigation prescription
...
Filter irrigation prescriptions
View proposed irrigation prescription
...
Accept proposal
...
Roll-back to previous irrigation prescription
...