Abstract
AbstractProduction systems involving interplanted food crops are widespread in tropical latitudes, and interest in quantifying the productive potential of intercrops is high. Published data often suggest a sizable gain in land‐use efficiency by growing such crops in mixtures. Our thesis is that many of the large intercrop advantages reported in the literature are misleading because the conceptual basis on which the monoculture‐vs.‐intercrop comparisons were made is incomplete. In this paper, we review the various methods for estimating intercrop productivity, propose a concept which we believe will remove the principal limitation in conventional methodology, and test the new concept with intercrop data from the literature. The land equivalency ratio (LER) is the most‐used convention for intercrop‐vs.‐monoculture comparisons, but LER is frequently inappropriate because cropping‐system duration, i.e., time, is not included in its calculation. Duration of land occupancy by an intercrop is often longer than production‐cycle duration for one or more of the interplanted species. We propose an area‐×‐time equivalency ratio (ATER) and suggest that it will correct this conceptual inadequacy in LER. When published intercrop data were reevaluated via the ATER concept, large land‐use advantages ascribed to growing food crops in mixtures disappeared. We conclude that most crop mixtures utilize land area and time (area·time) at about the same efficiency as pure stands of the mixture's components.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.