Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to determine the fertilizer application rate for each crop? #1257

Open
Tonyzhao610 opened this issue Oct 14, 2024 · 1 comment
Open

How to determine the fertilizer application rate for each crop? #1257

Tonyzhao610 opened this issue Oct 14, 2024 · 1 comment

Comments

@Tonyzhao610
Copy link

Which file is used to set the fertilization amount for each crop? In GCAM, will reducing fertilization lead to a decrease in yield, a reduction in fertilizer production, and a decrease in carbon emissions from fertilizer production?

@pkyle
Copy link
Contributor

pkyle commented Oct 14, 2024

Fertilizer input-output coefficients are indicated in kilograms of nitrogen per kilogram of crop produced, and are specified in the XML file ag_Fert_IRR_MGMT.xml.
There is no formal relationship between the fertilizer input-output coefficient and the yield in the model; as a default we hold this number constant over time. This effectively assumes constant fertilizer recovery efficiency over time, and that the fertilizer application rate per unit land area will scale 1:1 with future yield changes. Similarly the emissions rates of N2O_AGR, NH3_AGR, and NOx_AGR are also assumed to scale with production; emissions coefficients derived from base year inventory data are not changed over time.
These three sets of assumptions—kgN/kg crop, kg crop / m2 land area, kg nonco2s / kg crop--can all be changed independently of one another, so it is up to the model users and developers to make sure that the assumptions of any scenario are internally consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants