Soil Limitiations

[ltseng]

User Story

• As a user with permissions to edit a site, I can contribute soil limitations data in various areas (specific values found in the spec doc)
  • Salt on soil surface
  • Flooding
  • Lime requirements
  • Surface stoniness
  • Water table depth
  • Soil depth

### Design
- [ ] https://github.com/techmatters/terraso-product/issues/379

### Front end
- [ ] https://github.com/techmatters/terraso-client-shared/issues/111
- [ ] https://github.com/techmatters/terraso-mobile-client/issues/472

### Back end
- [ ] https://github.com/techmatters/terraso-backend/issues/861
- [ ] https://github.com/techmatters/terraso-backend/issues/915

Acceptance criteria

• I can only contribute soil limitations data at various depths to sites I have contributor/manager access to.
• I can add soil limitations data to sites where I am a contributor/manager
• I can delete all soil limitations data that I have previously provided.
• Authenticated users who contribute soil limitations data should have their actions logged in the site-level audit log.
• Analytics should be collected according to the spec doc.

Resources

Soil Limitations

[ltseng]

There were requests for us to add Mottling and Soil Smell as additional submethods to Soil Limitations because they could be useful inputs to Soil ID in the future. My answer is for us to focus on this core set of Soil limitations submethods for now for MVP so that we can deliver what is needed to calculate LCC, and worry about those other ones when it becomes relevant.

[CourtneyLee333]

Per Laura: The help text question marks are actually pretty decent in this section. We discussed that having a “beginner mode” like we were discussing for soil color would be helpful here, where we would show all the diagrams and explanations that are currently hidden in the question mark help text.