How kelemi90/trash_heatmap works
Trash Heatmap records event trash-bin emptying and turns those records into operational views. The main workflow is a worker scanning a bin’s QR code, selecting an approved username, and submitting a timestamped emptying; the server validates the user and enforces a ten-minute per-bin cooldown before storing the record. Dashboards summarize bin locations, recent activity, and usage. Administrators manage users, bin positions, QR labels, and log resets behind session authentication. The README documents capabilities and API behavior; unsampled frontend modules are represented by their tree paths, without asserting undocumented client-to-endpoint calls.
Main entry points: bins.js Bin and analytics API · server.js HTTP application · logs.js Emptying logs · admin.html Admin panel
Components 24
Field logging
- Bin logging page
public/bin.html - Emptying logs
server/routes/logs.js - QR label API
server/routes/qrLabels.js - QR label manager
public/qr_labels.html
Usage insights
- Dashboard
public/dashboard.html - Dashboard views
public/js/dashboard.js - Heatmap view
public/heatmap.html - Bin map
public/js/map.js - Reports
public/report.html - Report analysis
public/js/report.js - Bin timing view
public/js/bin_times.js - Bin ranking
public/ranking.html
Administration
- Admin panel
public/admin.html - Bin editor
public/bin_editor.html - User management
server/routes/users.js - Bin and analytics API
server/routes/bins.js - Admin authentication
server/routes/auth.js - Admin access guard
server/middleware/adminAuth.js
Server and data
- HTTP application
server/server.js - SQLite records
database/trash.db - Redis sessions
- Server logger
server/logger.js
Other components
- Worker
- Administrator
Connections 31
- Worker → Bin logging page: scans QR
README.md - Bin logging page → Emptying logs: submits emptying
README.md - Emptying logs → SQLite records: validates and records
server/routes/logs.js - QR label manager → QR label API: requests labels
README.md - QR label API → Bin logging page: encodes bin URL
server/routes/qrLabels.js - Administrator → Admin panel: manages system
README.md - Admin panel → Admin authentication: signs in
README.md - Admin authentication → Redis sessions: stores session
- Admin panel → User management: manages users
README.md - User management → SQLite records: reads and writes users
server/routes/users.js - Admin panel → Bin editor: edits positions
README.md - Bin editor → Bin and analytics API: updates bins
README.md - Bin and analytics API → SQLite records: reads and updates
server/routes/bins.js - Admin panel → Emptying logs: reviews and resets logs
README.md - Emptying logs → Admin access guard: protects reset
server/routes/logs.js - Bin and analytics API → Admin access guard: protects position changes
server/routes/bins.js - Dashboard → Dashboard views: renders views
README.md - Dashboard views → Bin and analytics API: loads status and heatmap
README.md - Heatmap view → Bin and analytics API: loads usage counts
README.md - Bin map → Bin and analytics API: loads bin locations
README.md - Reports → Report analysis: renders reports
README.md - Report analysis → Emptying logs: loads activity data
README.md - Bin timing view → Bin and analytics API: loads bin status
README.md - Bin ranking → Emptying logs: loads usage ranking
README.md - HTTP application → Admin authentication: mounts routes
server/server.js - HTTP application → Bin and analytics API: mounts routes
server/server.js - HTTP application → Emptying logs: mounts routes
server/server.js - HTTP application → User management: mounts routes
server/server.js - HTTP application → QR label API: mounts routes
server/server.js - HTTP application → Admin access guard: guards admin pages
server/server.js - HTTP application → Server logger: writes request errors
server/server.js