Skip to content
Research Article Open access CC BY 4.0

Lotus Cultivation in Contaminated Water: Potential Risks and Solutions

Anup Gadekar, Disha Katre

International Journal of Environment and Climate Change · pp. 504–516 · Published 25 Feb 2025

10.9734/ijecc/2025/v15i24743

Abstract

This article explores the potential risks associated with lotus cultivation in polluted water sources and presents viable solutions to mitigate these challenges. Lotus cultivation plays a significant role in agriculture, providing economic, cultural, and medicinal benefits. However, the increasing contamination of water bodies due to industrial effluents, agricultural runoff, and domestic waste poses serious risks to the safety and productivity of lotus farming. Toxic chemicals such heavy metals, pesticides, and infections can accumulate in lotus plants due to contaminated water, which can then have an impact on soil quality, marketability, and human health. Strategies such as water quality monitoring, phytoremediation, sustainable farming practices, and policy interventions are discussed to ensure the long-term sustainability and safety of lotus production. Farmers can embrace environmentally friendly practices while preserving their financial viability by highlighting the significance of safe growing techniques.

Lotus cultivation water contamination heavy metals phytoremediation sustainable agriculture water quality monitoring

Cited by 0

No indexed citations yet.

Article metrics

Real usage data collected on this platform.

6

Page views

0

PDF downloads

0

Outbound clicks

0

Citations

Views over time

Views by country

Approximate, from request IP at view time — not citizenship or institution. Countries with fewer than 5 views are grouped as "Other".

Traffic sources

Referring site, by host.

Views and downloads exclude known bots/crawlers. Citations combines this platform's own DOI-resolved index with each external source's own reported total — see Cited by above for individually listed citing works. Last refreshed 0 seconds ago.