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

Handle height allometries #19

Closed
teixeirak opened this issue Feb 8, 2018 · 8 comments
Closed

Handle height allometries #19

teixeirak opened this issue Feb 8, 2018 · 8 comments

Comments

@teixeirak
Copy link
Member

Some sites have local height allometries, which can be used to improve estimates.

We need to plan the structure for incorporating these in the database.

This is something that @gonzalezeb, @maurolepore, and @teixeirak should discuss in person.

@teixeirak teixeirak added this to Database - code structure in Big-picture planning Feb 8, 2018
@teixeirak teixeirak added this to Defining database structure in Database development Feb 8, 2018
@ErvanCH
Copy link

ErvanCH commented Feb 8, 2018

This is worth doing. Chave et al. 2014 are also providing a general equation to estimate height. I know that the group from O. Phillips is also computing local H-D model routinely, as part of the tools integrated in the Forestplots repository. There is a new paper related to that exploring the different generic models and approches to estimate H-D locally (see here)

@teixeirak
Copy link
Member Author

teixeirak commented Feb 27, 2018

The basic plan is to include height allometries in the allometries table, where height is entered as the independent variable (variable field in allodb_equations). The site-species table will have a new field that references the allometry ID for this calculation, when applicable, and applies it to calculate height before running the biomass allometry. To implement this:

  • add a height allometry ID field to allodb_site_species (@gonzalezeb).
  • revise code to deal with instances where a height allometry is available (@maurolepore).

Note: a biomass allometry that uses height should always be coupled to a height allometry.

@teixeirak teixeirak moved this from Database - code structure to wood density in Big-picture planning Feb 27, 2018
@teixeirak teixeirak removed this from wood density in Big-picture planning Feb 27, 2018
@maurolepore maurolepore changed the title Add structure to incorporate height allometries Handle height allometries Mar 12, 2019
@teixeirak
Copy link
Member Author

This is not necessary for the minimum viable product, but should be dealt with before publication of the paper.

@teixeirak
Copy link
Member Author

@gonzalezeb, this paper is the one I mentioned with height allometries.

@maurolepore
Copy link
Member

(Krista) revise code to deal with instances where a height allometry is available (@maurolepore)

(Ervan) Chave et al. 2014 are also providing a general equation to estimate height.

A branch of fgeo.biomass now wraps the BIOMASS package and provides a way to estimate height based on a region or on latitude and longitude. It does this internally (#54 (comment)). I believe this is appropriate for tropical species only.

Relates to #54 (comment)

@gonzalezeb
Copy link
Contributor

Now we only need:

  • decide if we need a height allometry ID field in site_species table in allodb
  • include a line in the code in fgeo.biomass to use height equations from allodb when height is needed to calculate biomass in a non tropical site.

@teixeirak
Copy link
Member Author

Now we only need:

* decide if we need a height allometry ID field in site_species table in allodb

Yes.

@gonzalezeb
Copy link
Contributor

Closing. Height allometries are now handle by the get_biomass function

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Database development
Defining database structure
Development

No branches or pull requests

4 participants