S102 Grooming!

Recording link: Video Conferencing, Web Conferencing, Webinars, Screen Sharing

Passcode: R3Sf96P@

Agenda

  • Smart Irrigation / Sensor management

Discussion points

  • ProductBoard

    • engineering@litefarm can be used to add engineers

  • HistoricalData

    • Divya currently thinking max 6 month data storage of sensor data

    • Loic and others - the farmer wants to be able to see data much longer than that - minimum one season but preferable multiple seasons

    • What is approximate the cost per sensor?

    • Devs - tech constraints

      • Does Ensemble have a get endpoint for historical data? Can we choose to not store the data?

      • Architecture may depend on common sensor approaches:

        • Push data to us?

        • We pull data?

          • does it exist?

          • how long does ESci hold on to data?

        • User uploads data manually?

      • OpenWeather has limits more for historical data. What do we need from them?

  • Nested sensor under field

    • Mandatory to associate sensor with one field?

      • Likely sensor affects multiple areas, whole farm, nearby fields

    • One sensor per “irrigation zone”

    • Can we not calculate if a point is inside a polygon

      • yeah probably

  • Generic data?

    • using custom task as analogy , how can we reuse sensor for multiple sensors/data points (including manual eg mm rain graduated cylinder)

      • Can we input a unit of measurement?

      • Can we upload readings?

  • What happens when we delete a sensor?

    • delete → data is gone

    • retire → maybe data is retained for that point and passed on to successive sensor

TO DO

Task

Owner

Due date

Notes

Task

Owner

Due date

Notes