search

VincyaneBadouard / TreeData_broken

Harmonization and correction forest data tool.
https://vincyanebadouard.github.io/TreeData/
0 stars 1 forks source link

add options to deal with concatenated data at species level #43

Closed ValentineHerr closed 2 years ago

ValentineHerr commented 2 years ago

This is coming from a mail from Karina, and it sounds like Renato could use that too.

I was using the app with some sample data from the DRYFLOR network, which is a very simple database that does not gather individual tree data, only concatenated data at species level. So for this type of data matching the column names is not working very well. I guess that it is the same issue for Renato with TreeCo and the Amazon Tree Diversity Network (ATDN)

There are the fields that probably need to be included:

Plot info section: Coordinates (we do not have X and Y per tree) Min DBH (I saw it in the correction step, but maybe it is useful to have it in the inputs)

And at species level (no sure to include a new section for species info is needed or in the botanical information? )

abundance: Total number of individuals of the species recorded in this recorred per site (or sampling unit: plot/transect)

basal_area: Total cross-sectional area of all stems of the species in a stand measured at breast height per square meter\n. Σ Basal area m2 = pi * DBH(cm)^2/ 40000

I think it would be worthwhile to have the app handle this type of data.... and, for example, if DRYFLOR is selected as output profile but the input data is at stem level, the app should be aggregated info at the species level... @cpiponiot and @gabrielareto, what do you think?

VincyaneBadouard commented 2 years ago

I just saw this issue that had escaped from my main mailbox. Were you able to propose something for this species level?

ValentineHerr commented 2 years ago

not yet, I need to meet with Karina and Renato to make sure I get this right

ValentineHerr commented 2 years ago

@VincyaneBadouard, about this and related to the Correction functions, a few weeks ago, I added the option for the user to specify what the minDBH of their data is, which could be given as a column in their data (in case maybe it changes by plot) or manually given as numeric input (if not provided in a column). In the case where nothing is given by the user (no column indicated and no manual numeric input, the minDBH column is automatically calculated, looking at the Diameter column (and a warning is given to the user).

All that to say that the data should always have a minDBH column, and your functions could be looking at that instead of asking for it in the arguments

ValentineHerr commented 2 years ago

I added options for Species level measurements. I wan to add Plot level measurements too. but I am closing this, I'll open new issues as needed