Page Comparison

Should LiteFarm be recommending the lat / long of collection points based on the area being sampled?

David Trapp to provide links here

• https://soiltesting.wvu.edu/sampling-texture/where-to-soil-sample

• https://play.google.com/store/apps/details?id=com.noframe.farmissoilsamples&hl=en_US

• https://play.google.com/store/apps/details?id=air.com.taplogic.soiltesting&hl=en

• https://www.scielo.br/j/sa/a/fBLJwHfsWs3kqNrPqDdgjMx/?format=pdf&lang=en

What soil collection task details are necessary to taking effective samples?

Should multi-point soil sample collection tasks be treated as one task or many?

Is there a particular type of soil sample collection types we’re looking to support?

Is there a particular type of soil sample analysis types we’re looking to support?

What format of soil analysis should we be supporting out of the box?

Should users be prompted for a follow-up timeframe to provide soil analysis results after collecting soil samples or should that be static (e.g. 2 weeks) or something else?

What is the best way to show farmers changes to soil health at the farm (versus point) level?

What attributes must and should be documented in each soil amendment task?

See API - Version 1 (current) (fertilisers, green_manure section)

(Assuming we document quantity) does it make sense to include a “Low inventory quantity” alert for products that are nearing depletion?

Duncan Brain Question about backfilling data. In SoilV1 we are looking to save percent_of_location_amended and total_area_amended_in_ha . Should data from previous tasks be backfilled with guidance from data/research team. (Based upon “location(s) total area” selected on tasks and/or crop plans “planted area” as a percent of selected locations area on tasks).

It would be nice to enforce non-null values at the db level