Skip to content

Gowrav-M/EchoShare

BranchesTags

Repository files navigation

EchoShare

EchoShare is a community-driven sustainability web app for reporting pollution near water bodies and turning those reports into visible local action.

This repository started from the hackathon concept of tackling pollution, biodiversity loss, and resource overuse in marine and freshwater ecosystems. The current codebase implements that idea as a full-stack Next.js MVP with Google auth, PostgreSQL, map-based reporting, community coordination, stakeholder discovery, AI-assisted enrichment.

Contest Problem Statement

Topic : Sustainability and Waste Management.
Create a technology driven solution to tackle pollution, biodiversity loss, and resources overuse in marine ecosystems.

Proposed solution

EchoShare - A community-driven sustainability web app for reporting pollution near water bodies and turning those reports into visible local action.

Stack

  • Next.js 16 App Router
  • React 19
  • Tailwind CSS 4
  • Supabase Postgres
  • Prisma 6.19
  • Supabase Storage
  • NextAuth.js with Google OAuth
  • Leaflet + OpenStreetMap + leaflet.heat
  • Gemini 2.5 Flash + Gemini embeddings via @google/genai
Fronted:
    1. Vite and React JS.
    2. Typescript.
    3. Tailwind CSS
Backend:
    1. Supabase
Database:
    1. PostgreSQL
User authentication:
    1. Google SSO

Local setup

npm install
npm run prisma:generate
npx prisma migrate dev --name init
npm run prisma:seed
npm run intelligence:sync
npm run dev

The app runs on:

http://localhost:8080

Verification commands

npm run typecheck
npm run lint
npm run build

for information related to env, read this

Samples

For output images of the project look inside Results/
For the powerpoint presentation and pdf look inside Presentation/

Members

Team BIT's o' MIT's (Number: 93)

  • Gowrav M (Gawrav-M)
  • Hemanth Shetty (team lead)
  • Mayura Krishna (KaoKsn, swiss-superman)
  • Mohit HJ

Problem framing

People regularly see litter, discharge, and waste buildup near lakes, rivers, canals, ponds, beaches, and wetlands, but the reporting path is fragmented and local coordination is weak.

EchoShare is designed to help communities:

  • post geo-tagged pollution evidence
  • visualize hotspots on a free interactive map
  • coordinate cleanup activity
  • discover NGOs and public stakeholders
  • keep AI outputs separate from raw user evidence

What the app includes

  • Geo-tagged pollution reporting with photo uploads
  • Free interactive map with markers and hotspot rendering
  • Google login for contributors
  • Community posts and cleanup coordination
  • Stakeholder directory
  • Gemini-powered AI enrichment stored separately from user evidence
  • Ollama-powered grounded assistant with optional live Google search via SerpAPI

Architecture diagram

flowchart LR
    U["Citizen / Community User"] --> W["EchoShare Web App<br/>Next.js 16 + React 19"]
    W --> A["Auth.js + Google OAuth"]
    W --> API["Server Actions + API Routes"]
    API --> DB["Supabase Postgres<br/>Prisma ORM"]
    API --> ST["Supabase Storage<br/>Report Images"]
    API --> MAP["Leaflet + OpenStreetMap"]
    API --> G["Gemini AI Enrichment"]
    API --> O["Ollama Assistant<br/>gpt-oss:120b-cloud"]
    O --> S["SerpAPI / Firecrawl<br/>Live Search Context"]
    API --> N["n8n Background Workflows"]
    N --> G
    DB --> R["Reports, Community, Directory,<br/>Dashboard, Intelligence"]
Loading

Repository map

echoshare/
├── prisma/
│   ├── schema.prisma
│   ├── migrations/
│   └── seed.ts
├── public/
│   ├── brand/
│   └── uploads/
├── scripts/
│   ├── sync-intelligence.ts
│   └── sync-real-directory.ts
├── src/
│   ├── app/
│   │   ├── api/
│   │   ├── assistant/
│   │   ├── community/
│   │   ├── dashboard/
│   │   ├── directory/
│   │   ├── intelligence/
│   │   ├── map/
│   │   ├── reports/
│   │   └── signals/
│   ├── components/
│   │   ├── assistant/
│   │   ├── layout/
│   │   ├── maps/
│   │   ├── reports/
│   │   └── ui/
│   └── lib/
│       ├── ai/
│       ├── assistant/
│       ├── automation/
│       ├── data/
│       ├── intelligence/
│       ├── supabase/
│       └── validation/
├── docs/
│   ├── architecture.md
│   ├── ai-automation.md
├── README.md
└── package.json

Environment

Create a local .env from .env.example.

Required:

  • DATABASE_URL

  • DIRECT_URL

  • AUTH_SECRET

  • AUTH_GOOGLE_ID

  • AUTH_GOOGLE_SECRET

  • SUPABASE_URL

  • SUPABASE_SERVICE_ROLE_KEY

  • GEMINI_API_KEY Optional:

  • SUPABASE_STORAGE_BUCKET

  • GEMINI_REPORT_MODEL

  • GEMINI_IMAGE_TRIAGE_MODEL

  • GEMINI_REVIEW_MODEL

  • GEMINI_EMBEDDING_MODEL

  • FIRECRAWL_API_KEY

  • FIRECRAWL_API_BASE_URL

  • FIRECRAWL_OFFICIAL_LIMIT

  • FIRECRAWL_NEWS_LIMIT

  • FIRECRAWL_MAX_AGE_MS

  • FIRECRAWL_SEARCH_LOCATION

  • OLLAMA_BASE_URL

  • OLLAMA_MODEL

  • OLLAMA_API_KEY

  • SERPAPI_API_KEY

  • SERPAPI_BASE_URL

  • SERPAPI_LOCATION

  • SERPAPI_RESULTS_LIMIT

  • SEARXNG_BASE_URL

  • SEARXNG_RESULTS_LIMIT

  • NOMINATIM_BASE_URL

  • OVERPASS_API_URL

  • NOMINATIM_EMAIL

Supabase + Prisma connection mode

For Supabase-hosted Postgres, use transaction pooling for DATABASE_URL and the direct socket for DIRECT_URL.

DATABASE_URL=postgresql://[DB_USER]:[PASSWORD]@db.[PROJECT_REF].supabase.co:6543/postgres?pgbouncer=true&connection_limit=5&connect_timeout=30&sslmode=require
DIRECT_URL=postgresql://[DB_USER]:[PASSWORD]@db.[PROJECT_REF].supabase.co:5432/postgres?connect_timeout=30&sslmode=require

This is the runtime split that keeps Prisma stable in Vercel/serverless execution while preserving a direct connection for migrations.

If your network cannot reach the direct Supabase host reliably, use the working Supavisor session pooler for both values locally until you have a stable direct path again.

AI model plan

EchoShare does not need a custom-trained ML model for the hackathon build.

  • gemini-2.5-flash is the default report-analysis model for multimodal report enrichment.
  • gemini-embedding-001 is used for duplicate-assist embeddings stored in pgvector.
  • gemini-2.5-pro is reserved as the heavier review model for future moderator escalation flows.

All AI outputs remain clearly separated from raw user-submitted evidence.

External intelligence layer

EchoShare now includes a separate Intelligence tab for official-site and news signals.

  • This layer does not write into Report.
  • It stores external signals in isolated intelligence tables.
  • It is intentionally credit-aware and syncs only a small curated India watchlist.
  • It prefers self-hosted Firecrawl when FIRECRAWL_API_BASE_URL points to your own deployment.
  • If self-hosted Firecrawl is unavailable, the intelligence layer falls back to free/public retrieval paths such as Google News RSS and optional SearXNG.
  • SerpAPI is reserved for the assistant's optional live web search and is not used by the intelligence feed.
  • Social-platform ingestion is excluded until an official API path is configured.

Grounded assistant layer

EchoShare now includes a separate Assistant tab.

  • The assistant uses Ollama for generation.
  • The default model is gpt-oss:120b-cloud.
  • It grounds answers in EchoShare reports, responders, cleanup events, and intelligence signals.
  • Optional live Google search uses SerpAPI and stays clearly separated from citizen-report truth.
  • If live search is off or unavailable, the assistant still answers from local app data only.

Firecrawl self-host + Vercel deployment

The EchoShare app can stay on Vercel while Firecrawl runs as a separate self-hosted service.

  • Deploy EchoShare on Vercel.
  • Point FIRECRAWL_API_BASE_URL at your self-hosted Firecrawl base URL.
  • Leave FIRECRAWL_API_KEY empty if your self-hosted Firecrawl instance does not require bearer auth.
  • Optionally set SEARXNG_BASE_URL for an open backup search path.

This keeps the Vercel app serverless while moving the crawler/search worker stack off the paid Firecrawl cloud path.

Evidence and location trust gates

EchoShare uses two validation layers before a report is accepted:

  • Gemini image triage rejects obviously unrelated uploads such as selfies, weapons, memes, screenshots, and non-evidence scenes.
  • Free OpenStreetMap services validate that the submitted pin is actually near a mapped water body and can reject clear water-body name mismatches.

This keeps obviously bad evidence out of the report pipeline without requiring a paid maps API.

Google OAuth note

For local development, the app can fall back to a client_secret_*.json file in the project root when AUTH_GOOGLE_ID and AUTH_GOOGLE_SECRET are not set.

Do not commit local .env files or Google OAuth client secret JSON files to a public repository.

You still need the exact Auth.js callback URI registered in Google Cloud:

http://localhost:8080/api/auth/callback/google

The existing origin http://localhost:8080 alone is not enough.

Data model highlights

  • Report stores citizen-submitted evidence metadata
  • ReportImage stores uploaded image references
  • ReportAIAnalysis stores AI-assisted summary, classification, duplicate hints, and recommendations
  • CleanupEvent and Participant manage turnout
  • Organization keeps a verification-ready stakeholder directory
  • StatusHistory and ModerationRecord support future admin workflows

Real vs demo

Real:

  • Auth flow
  • Route structure and protected pages
  • PostgreSQL schema
  • Supabase storage-backed report uploads
  • Typed Prisma queries
  • Report CRUD flow
  • Map rendering
  • Community feed and cleanup events
  • Stakeholder directory
  • Dashboard metrics
  • Gemini enrichment service

Demo-scoped:

  • Development seed data in prisma/seed.ts
  • Seed organizations and water bodies clearly labeled as development seed data

Docs

Project Checklist

  • Requirement Analysis.
  • Basic Workflow and Webpage design requirement analysis.
  • Mid hackathon presentation.
  • Login page configuration.
  • User authentication & email verification
  • Frontend responsive & accessible
  • Reporting & photo storage working
  • Basic Documentation

About

No description, website, or topics provided.

Resources

Readme

License

MIT license
Activity

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

 
 
 

Contributors

Languages