this is for holding javascript data
Ritvik Sahajpal edited subsection_Method_Constraints_Should_be__.tex
almost 9 years ago
Commit id: 9a7102c3d76c618dd41cd74f4e668937a9be5d41
deletions | additions
diff --git a/subsection_Method_Constraints_Should_be__.tex b/subsection_Method_Constraints_Should_be__.tex
index e93a722..58e5dc6 100644
--- a/subsection_Method_Constraints_Should_be__.tex
+++ b/subsection_Method_Constraints_Should_be__.tex
...
* Should show changes in crop rotations: intensification
Our approach is based on the following concepts:
1.
Hub crop: \textbf{Hub crop}: Each crop rotation is organized around a hub crop which dominates the rotation, and provides the farmer a competitive edge in the market. E.g. corn is the hub crop in most of the US Midwest.
2.
Substituting \textbf{Substituting time by
space: space}: Crop rotations exist as a time-series of crops grown on the same parcel of land. At a coarser resolution (say 0.25 degree), we can substitute the temporal dimension of a crop rotation by looking at the relative acreage of different crops in the region. Greater the acreage, greater the share of that crop in the rotation.
3.
Using \textbf{Using fertilizer
data data} to infer monoculture versus rotation: Crop rotations reduce the amount of fertilizer needed to produce subsequent crops. Using information on fertilizer usage, we can deduce whether a crop is rotating or a monoculture.
4.
Local knowledge: \textbf{Local knowledge}: Information on historic and present crop rotations practiced in a region will be used to correct and inform the algorithm.
...