Description
As I add more and more crop models to PEcAn, it became an issue how to pass the management options to these models. Until now, I only dealt with passing harvest days to BASGRA and STICS for which I was using a simple text file format specifying cutting dates. BASGRA is a simple model, it only simulates cutting and fertilization for management but STICS has many many many options (fertilization composition, location of mineral nitrogen inputs, irrigation, location of irrigation, cutting height, mulch, thinning, pruning, sowing etc.). LPJ-GUESS agriculture simulations also have similar management settings. I suspect management in other models would also require a way of passing these options, e.g. https://github.com/PecanProject/pecan/issues/2122.
Proposed Solution
Although there are differences from models to models, the logic is not too different (all use some decision to do the harvest, fertilization amount/composition which could be nested etc.). Overall, I feel like we need a management workflow and/or a management standards file of sorts.
I need to apply these management scenarios soon. Before inventing ways for handling my use cases, I thought it would be helpful to have some design discussion.
istfer
All 8 comments
Also ED2 has anthropogenic disturbance. My understanding is that it takes an XML file that specifies PFTs, dates, and levels of disturbance.
ashiklom
on 22 Jan 2020
So Nell Campbell developed a couple small proposals (one to UNH, one to Brazil) about using PEcAn in an agronomic context, and part of that was to incorporate this sort of standardized management info. Looking quickly back over that text, it looks like this was going to be build off of things like http://farmos.org/ Nell is now at https://www.indigoag.com/ but this may still be very relevant to her, so I'd recommend reaching out
mdietze
on 27 Jan 2020
We should also look at how AgMIP encodes managements using the ICASA standard; I would recommend using this.
@KristinaRiemer is working on exporting data from BETYdb via the BrAPI to be ICASA compliant.
@eecampbell is this still relevant to your work?
dlebauer
on 27 Jan 2020
I'll drop this here for now https://docs.google.com/spreadsheets/d/1MYx1ukUsCAM1pcixbVQSu49NU-LfXg-Dtt-ncLBzGAM/pub?output=html#
istfer
on 3 Feb 2020
This issue is stale because it has been open 365 days with no activity.
![github-actions[bot] picture](https://avatars.githubusercontent.com/in/15368?v=4&s=40)
github-actions[bot]
on 3 Feb 2021
@KristinaRiemer do you have a go-to resource for ICASA standards? Main main source is the google sheet I shared above, but I was wondering whether there is a more official/up-to-date place I should be looking, e.g. maybe here https://github.com/agmip/VMapper/tree/develop/Data/ICASA?
istfer
on 18 May 2021
@istfer I am pretty sure that those CSVs are dumped from the google spreadsheet @MengZhang can confirm?
It is also worth noting that that 'VMapper' repository is a tool to help map fields from a bespoke spreadsheet or json file to the ICASA variables. The website is here http://vmapper-test.herokuapp.com/ and the Vmapper tool is here http://vmapper-test.herokuapp.com/tools/vmapper.
FYI @mengzhang @frostbytten and @chporter the PEcAn community was looking for standards for encoding managements / events etc so I pointed them to ICASA. Might be worth addressing at the next mini-hackathon (@istfer I'll contact you on slack w/ info).
dlebauer
on 18 May 2021
@dlebauer You are correct. The CSV files you mentioned are the local cache dumped from ICASA google site for performance and version control purpose.
MengZhang
on 19 May 2021
Related issues
tonygardella
·
11Comments
ayushprd
·
9Comments
serbinsh
·
38Comments
serbinsh
·
39Comments
serbinsh
·
27Comments
Most helpful comment
@dlebauer You are correct. The CSV files you mentioned are the local cache dumped from ICASA google site for performance and version control purpose.