How digbatt/cits3200 works
nUWAy Fleet Dashboard combines a Flask service and browser dashboard for viewing shuttle positions, history, fleet utilisation and operational status; it also supports rider pickup requests and authenticated operator actions. The documented live-data workflow polls REV vehicle endpoints and appends snapshots for later viewing. The source excerpts establish app registration and several backend dependencies; frontend-to-API wiring and logger internals were not sampled, so those links are omitted or marked unverified.
Main entry points: app.py Flask app · main.js Dashboard shell · pickup_requests.py Pickup API · base.py Repository interface
Components 32
Service runtime
- Flask app
backend/app.py - App configuration
backend/config.py - Admin sign-in
backend/auth.py - Position API
backend/api/positions.py - Vehicle API
backend/api/vehicles.py - Metrics API
backend/api/metrics.py - Earth view API
backend/api/earth.py - Query parsing
backend/api/params.py
Fleet telemetry
- Utilisation model
backend/metrics/tum.py - Fleet data models
backend/models.py - Repository interface
backend/repository/base.py - CSV position store
backend/repository/csv_repo.py - Live-data logger
backend/logger.py
Rider and operator
- Downtime API
backend/api/downtime.py - Pickup API
backend/api/pickup_requests.py - Pickup requests
backend/pickup_requests.py - Stops and routes
backend/stops.py - Downtime records
backend/downtime.py
Browser dashboard
- Dashboard shell
frontend/js/main.js - Bus visual model
frontend/js/bus-model.js - 3D map views
frontend/js/view3d.js - Campus 3D view
frontend/js/campus3d.js - Earth 3D view
frontend/js/earth3d.js - Fleet timeline
frontend/js/timeline.js - Utilisation view
frontend/js/utilisation.js - Operator view
frontend/js/operator.js - Admin dashboard
frontend/js/admin.js - Rider interface
frontend/js/rider.js
Other components
- Fleet user
- Operator
- Rider
- REV tracking
Connections 33
- Fleet user → Dashboard shell: views fleet
README.md - Operator → Operator view: manages service
README.md - Rider → Rider interface: requests pickup
README.md - Flask app → App configuration: loads settings
backend/app.py - Flask app → Admin sign-in: registers sign-in
backend/app.py - Flask app → Position API: registers routes
backend/app.py - Flask app → Vehicle API: registers routes
backend/app.py - Flask app → Metrics API: registers routes
backend/app.py - Flask app → Earth view API: registers routes
backend/app.py - Flask app → Downtime API: registers routes
backend/app.py - Flask app → Pickup API: registers routes
backend/app.py - Flask app → Repository interface: configures repository
backend/app.py - Position API → Query parsing: parses filters
backend/api/positions.py - Metrics API → Query parsing: parses filters
backend/api/metrics.py - Metrics API → Utilisation model: calculates metrics
backend/api/metrics.py - Pickup API → Pickup requests: manages requests
backend/api/pickup_requests.py - Pickup API → Stops and routes: validates routes
backend/api/pickup_requests.py - Downtime API → Downtime records: manages records
backend/api/downtime.py - Downtime records → Repository interface: uses error type
backend/downtime.py - Repository interface → Fleet data models: stores positions
backend/repository/base.py - CSV position store → Repository interface: implements interface
backend/repository/csv_repo.py - Utilisation model → Fleet data models: classifies samples
backend/metrics/tum.py - App configuration → Stops and routes: loads network
backend/config.py - Live-data logger → REV tracking: polls snapshots
README.md - Live-data logger → CSV position store: appends snapshots
README.md - 3D map views → Bus visual model: uses model
frontend/js/view3d.js - Campus 3D view → Bus visual model: uses model
frontend/js/campus3d.js - Earth 3D view → Bus visual model: uses model
frontend/js/earth3d.js - Dashboard shell → Fleet timeline: dashboard feature
- Dashboard shell → Utilisation view: dashboard feature
- Dashboard shell → 3D map views: dashboard feature
- Operator view → Downtime API: uses operations API
- Rider interface → Pickup API: uses pickup API