S108 Grooming!

Recording link:

Passcode:

Agenda

• Irrigation prescription based on farmer interviews

•  

Discussion points

• Only 1 farmer with VRI, the rest have URI pivot

  • They manually adjust the application depth based on personal experience

  • URI

    • one application depth ?

  • Currently only approve or disapprove

• Opportunities

  • Whatsapp to communicate with team + water board

  • Tasks for workers

• Trusting technology and readings values is an issue

  • fluent with technology but their experience shows it is not quite accurate

  • fluency with technology is not the issue with these farmers

• How are we choosing the farmers participating this year?

  • are they open to using this technology that we are building?

    • Lewis mentioned vri users hard to find

  • are any of the participants using vri?

    • just the 1

• One farmer uses fieldnet to start pivots

  • any fieldnet updates?

    • currently low priority to develop FieldNet relationship

• What did farmers say about water usage?

  • Before 2pm day before to request water

  • 13-16” per year allowance (13-16” ? how is that measured?)

  • Drought only 8” allowance - had to pick least valuable crop to die

  • Making a case to the district about how much actual water they use

  • In our app choosing the task if it is included in the district water usage calculation

    • only on pivots

    • optional

    • connect technology/irrigation method to a water source? (well or pond or water district?)

  • confirm what pivot and water usage information ESci gets?

    • probably not sending estimation (but sends zones, area, and water application per zone)

  • Water usage task specific and not irrigation prescription specific?

  • Task creation changes the IP status?

    • yes

• Weather station sensor

  • sensor view is current in KPI

  • IP is forecast in KPI

    • Need to ask ESci if they are sending this forecasted info?

      • Or are we getting tomorrows weather forecast from our api?

  • Do we want to show which forecast data where?

    • dynamic vri prescription

• Layers is out of scope right?

  • yes it is nice to have

• Importing pivot information?

  • in scope or nice to have?

  • send along with IP or as a device like sensors?

    • ideally as device like sensors

• Keeping old custom sensor flow?

  • don’t worry about it for now

• Does ESci want data back on implementation of IP?

  • yes

• IP - do we need to store status information?

  • approved, declined, pending

  • Loic doesnt feel the need to keep declined IP

  • ESci - do they want to store status or not?

  • Why keep declined? Why have a declined action at all?

    • approved and pending only

• UI - figma watching topics

  • approve / abandon buttons

  • LEwis questions

  • uri/vri

    • single flow rate pivots could have uri or vri (sectional) plans ?

    • multi flow rate pivots can have uri, vri (sectional) and vri (advanced polygons)

  • Where would we edit IP ? On IP page or on task page or both?

    • We are not editing, not even date and time

TO DO