Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Context

High level requirements doc for FarmOS to inform Aug 25 demo and help us take a call on whether to use FarmOS as a repository for storing farmer information for the Bihar MRV project. Prepared Aug 19

Overview

  1. We need a repository or "data wallet" where we can store a bunch of data about farms and practices followed on those farms. 

    1. This season we are recording data on 250 farmers, want to cover 1,600 farmers next season (Rabi or winter season; November 2021 to March 2022) and 25,000 farmers during the 2023 Kharif or Monsoon season (July to October) 

    2. Think of DG as a data steward, collaborating with the government extension system to capture and validate farmer practice data and hosting it on behalf of the farmers (and covering the cost of doing so for now)

  2. The individual farms are small, 0.5 to one hectare and for each season, we are capturing ~20 data datapoints related to practices followed which are collected via ~5 forms deployed over the course of the season. The data is captured via Kobo Collect by frontline extension workers (also called Village Resource Persons or VRPs), validated and then recorded. Over time, we may move to a model where farmers report data directly and VRPs validate it. See workflow below: 

3. An initial use case for this data is to it to generate emissions estimates; to do so, need to re-format the data to meet the input requirements of various models (CFT, DNDC, CENTURY). Some of the data required for this may come from third party sources like ISRIC Soilgrids and providers of weather data. In this case, I expect we would query those sources based on farmer lat/long and the farmer specific data could be added to their FarmOS repository.

4. We want to store derived values from these models like GHG emissions per hectare and yield scaled emissions in each farmers repository/wallet and share it back with the farmers and VRPs via some interface (TBD) and also publish this data to a dashboard

5. Looking ahead, want to build a workflow where farmers can grant consent to share certain data fields with various stakeholders. This could be facilitated via Farmstack and the consent workflow is something that lives outside of FarmOS.

Questions for FarmOS 

  1. How does hosting work?

  2. How do we create separation between farmer records? 

  3. How do we access this data once its recorded in FarmOS?

  4. Whats the status of the integration between FarmOS and CoolFarmTool and DNDC?

  5. How is FarmOS differentiated from some of the other open source farm management tools like Litefarm, Agrosense, Tania, etc.)

Additional stuff

  • Sample data file

  • Project overview doc

  • No labels