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

Improve Matching Variable: Agricultural Soil Suitability #90

Open
Jo-Schie opened this issue Apr 11, 2022 · 3 comments
Open

Improve Matching Variable: Agricultural Soil Suitability #90

Jo-Schie opened this issue Apr 11, 2022 · 3 comments
Assignees
Labels
3_Could This issue has third order priority. It just needs to be adressed if there is time Database

Comments

@Jo-Schie
Copy link
Collaborator

Jo-Schie commented Apr 11, 2022

Background:
Soil aptitude for agriculture is dependend on different factors, not solely clay as we have it in our model here. Textual factors comprise clay, silt and sand particles and an optimal mixture can be found e.g. here. Other variables are e.g. cation exchange capacity (CEC), total nitrogen as well as soil organic carbon density and soil organic carbon stock.

There are two approaches to create a better indicator:

  • create a better estimation based on the soilgrid data that the mapme.biodiversity package is able to process. This would require: Defining an adequate model, reprocessing the data and implementing a routine. It would also require working already on the raster level (i.e. changes to the package) because it does not make too much sense to do that within an AOI where mean values already distort the measures.
  • search for another dataset that already shows agricultural suitability. This might be conceptually easier but the routine is not implemented in the package so I would be not so easly reproducible and also technically more work.

As for the time being, I will only implement a routine that defines soil aptitude based on clay content within certain boundaries (i.e. from 10-40% as optimal to fair aptitude and beyond or below as low aptitutde.

Definition of Done.
A new indicator is defined and conceptually sound. Data is processed and integrated into the matching frames.

@Jo-Schie Jo-Schie added the enhancement New feature or request label Apr 11, 2022
@Jo-Schie Jo-Schie self-assigned this Apr 11, 2022
@Jo-Schie
Copy link
Collaborator Author

Jo-Schie commented Apr 11, 2022

fyi: @yotaae and @melvinhlwong . I think this issue will be more complicated. So as for the time beeing I will try to implement a better estimation based on the available data and later depending on ressources we should change this. I will also create a new issue in mapme.biodiversity for this.

image

Image Source

@Jo-Schie Jo-Schie changed the title Create a better approximation for agricultural aptitude from the soil grid data Improve Matching Variable: Agricultural Soil Suitability Apr 12, 2022
@Jo-Schie
Copy link
Collaborator Author

Probably it is easier and more sound to user another data-product with an estabilshed methodology see this issue in the biodiversity repo.

@Jo-Schie Jo-Schie added Database 2_Should This issue has second order priority and should be solved at some point and removed enhancement New feature or request labels Apr 12, 2022
@fBedecarrats
Copy link

This is an old reference(see Soil quality section) :
https://www.fao.org/soils-portal/data-hub/soil-maps-and-databases/harmonized-world-soil-database-v12/en/
But from what I've found, soilgrids 2.0 seems to be the state of the art right now (and I understand that it is not very satisfying). Just an idea: why not train a model to predict which soilgrids characteristics' combinations are the best predictors for deforestation?

@melvinhlwong melvinhlwong added 3_Could This issue has third order priority. It just needs to be adressed if there is time and removed 2_Should This issue has second order priority and should be solved at some point labels Jun 11, 2024
@melvinhlwong melvinhlwong added this to IE Jun 11, 2024
@melvinhlwong melvinhlwong moved this to To do in IE Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3_Could This issue has third order priority. It just needs to be adressed if there is time Database
Projects
Status: To do
Development

No branches or pull requests

3 participants