Integrate parts of Practical Plants database to powerplant
Why? For what purpose? Rise my motivation!
The Practical Plants database is a permaculture-oriented database that contains information about over 7000 edible plants.
Aim of this project is to integrate parts of Practical Plants database by identifying data that has a functional purpose in powerplant, and then implementing algorithms and UI components that use this data.
Examples of Practical Plants data:
- USDA hardiness zone is a classification of plants based on their capability of growing in a geographic location with specified average annual minimum temperature. Hardiness zone can be used to select plants that are capable of growing in a given geographic location.
- Nitrogen fixation is the ability of a plant to fix atmospheric nitrogen to soil. By tracking the nitrogen fixers of a garden bed over years, it is possible to plan a crop rotation schedule where the accumulated nitrogen is used by nitrogen consumers during successive growing seasons.
- Plant habit refers to a coarse type or shape of a plant. Habit can be used to (help) select plants that maximize the habitual diversity of a garden.
- Knowledge and interest about plants and gardening
- "USDA hardiness zone" integrated to powerplant
- Crop database schema extended with a field for hardiness zone
- Internal function (+ unit tests) for calculating the hardiness zone for a given location, utilizing geographic coordinates and temperature data
- HTTP API call (and CLI command) for searching crops that match the hardiness zone of the user's location
- "Nitrogen fixation" integrated to powerplant
- Database extended so that powerplant is able to track nitrogen fixers of a garden bed over time
- CLI administration commands for showing and modifying low-level database documents
- Internal function (+ unit tests) for calculating the amount of nitrogen in a garden bed at a given time, when the history of the bed is known
- UI component and HTTP API calls (+ corresponding CLI commands) for planning a long-term schedule for a garden bed that utilizes crop rotation
- "Plant habit"/*niche* integrated to powerplant
- Crop database schema extended with a field for plant habits
- Internal function (+ unit tests) for searching crops that increase the habitual diversity of the garden
- HTTP API call (and CLI command) for searching crops that increase the habitual diversity of the garden, combined with the HTTP API call for searching crops based on hardiness zone
- "About this plant" info screen
- Select fields from the Practical Plants database that might be useful in powerplant and/or otherwise important for the gardener
- There could be links to practicalplants.org, for full information about the plant
Identify another piece of data from Practical Plants database that is functional for powerplant, and plan, discuss and begin its implementation.