Content Comparison

Recording link:

https://ubc.zoom.us/rec/share/QuKtWFru8upd3SjAw7ygXz6nj0WKH-KBz1BlsYb5KlO-kxnrYebGZx1wS89KkEZm.rndZIt9gV2H5KivK9VDYwNldShJ9SnDrBTDDbAHRhTLI6oIpLyaTJLKHYAMmddfhuzsu7G9w3rdB1yDZ.7frsAyGtb3duOhp9

Passcode: #a?fM9egH7dDJxc@

Agenda

• Sensor data visualization

• Pivot manufacturers sent by partners

• Polish Institute of Aviation - Layers

• LiteFarm Update by Divya

• URL for addon sensors list

Discussion points

• Pivot manufacturers sent by partners

  • Sent back two companies today

  • (Divya) Preferences for communicating with pivot: 1) via cloud, 2) bluetooth, 3) manually

  • We need some time to look at the new information

• State of sensors

  • We need to get sensor data (not necessarily the visualization but at least the data)

  • We need to figure out which sensor types are included in the project

• Irrigation prescription

  • as of now we don’t have any information about how ESci is handling this or how they would to integrate inputs from us

• Polish Institute of Aviation - Layers

• Reviewed the document, got a sense for what was being proposed

• Loic Sans will create a simple map-based user flow as an alternative to the farm settings based input / table described in the document and get in touch with Richard

Larisse Cavalcante and David Trapp to bring up (via document and/or meeting next Wednesday) the importance of the .klm map file format for farmers

• 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

      • Override recommendations seems simpler than devs imagined

TO DO

...