Page Comparison

Recording link: https://ubc.zoom.us/rec/share/XJIVFE3_fpJJJ3gdmcJDm9YTyLujzVqAGBfUmFKkZFkgCGBFlJcWU1UEt3NVZyyzY6uj6k8pfdhWRWGWNW-v8QtePmzvmxNSJUt7jw037k8xzUgewfVNc9UP8ZH7YWy.IpqE1-2me0f3jz2BF0FJNcdsXTlOXyHQ

Passcode: k39n!F!K

Agenda

...

Adding animals to custom tasks

...

R3Sf96P@

Agenda

• Smart Irrigation / Sensor management

Discussion points

...

Adding animals to custom tasks

• Anto, Loïc: Should be designed properly

• Divya: There is a lot of energy around animals that we should take advantage of

• Could be done with more time – should we scope it for January?

  • If designs get done could it be slotted in now?

...

Task completion

• Editing location and animals would be a new pattern

• We might not want to be beholden to the old pattern of e.g. not editing crops on task completion

• Divya: editing animals is more important than editing locations

• Decision:

  • Bug bash has not yet been communicated externally; we can therefore push it back as needed

  • We will scope custom tasks such that it can be completed in ONE WEEK extension

  • We will discuss what is done with location ASAP

  • Further discussion was done with dev team + Loïc:

    • Devs will investigate the feasibility of optional locations on custom tasks and report back on Monday; in the same time Loïc will create new screens for custom task creation and for task creation

    • Editable locations on movement (only) definitely in scope

    • Adding animals to custom tasks and editing animals in task completion definitely in scope

...

• 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

...