Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Recording link:

https://ubc.zoom.us/rec/share/9VDYwNldShJ9SnDrBTDDbAHRhTLI6oIpLyaTJLKHYAMmddfhuzsu7G9w3rdB1yDZ.7frsAyGtb3duOhp9

Passcode: H7dDJxc@

Agenda

...

Sensor data visualization

...

...

Irrigation prescriptions

Discussion points

...

Sensor array data

  • Latest Reading:

    • Capture the most recent reading time from all sensors.

Pivot

...

Form inputs:

  • Keep inputs minimal — name, rate, speed

  • Should we add "output format"?

  • Should confirm with Ensemble what data is required to generate irrigation prescriptions.

  • Retire "custom" pivots once we integrate with pivot manufacturers.

...

Benefits of integrating pivot manufacturers?

  • Potentially limited benefits but it would be interesting if we could mark the irrigation task as complete when the pivot finishes irrigating.

  • More reliable configuration data (eg. radius) compared to user inputs.

  • Accurate location

    • If a pivot is moved, the location must be updated.

Irrigation prescription

...

Users should specify the format (VRI/URI).

...

Should the irrigation recommendation be editable?

...

By approving the recommendation, the user is navigated to the task creation flow.

...

Where should "water allowance" belong? Farm settings?

...

Irrigation cycle

  • 1. When to trigger irrigation prescription generation?

  • 2. Upon approval, create both the prescription and corresponding irrigation task.

  • 3. Upon completing the task, adjust the water allowance.

...

How often do farmers want to update irrigation prescriptions?

Soil types (zones)

...

Requires further exploration.

...

Farm boundary etc. should be displayed on the map.

...

irrigation zones and soil zones don't match

...

This doesn't matter if recommendations aren't editable

...

TO DO

Task

Owner

Due date

Notes

...