One probe vehicle, one clean monitoring surface.
Start here when you need a fast project check. The page surfaces runtime health, the latest map signal, and the shortest paths into the live demo flows without making you hunt across separate pages first.
Live Status
Runtime snapshot
Health and latest map feed are fetched together so the page shows one consistent snapshot.
Waiting for first snapshot.
System Status
Service Health
Live readout from the running FastAPI application.
Map Feed
Latest Link Feed
A quick view of how many links are currently available in the map layer.
If the database is empty, the map switches to a local demo layer backed by the Seoul centerline GeoJSON.
Move from snapshot to the right surface.
Open the main demo pages from here once the runtime snapshot above looks healthy.
Live Surface
Map
Review link-level density snapshots and inspect prediction details.
Collection
Mobile Probe
Stream GPS and motion data from a phone into the inference pipeline.
Diagnostics
Health
Open the detailed backend health page when the snapshot shows a problem.
Reference
API Docs
Open Swagger docs for `/predict`, `/ingest`, `/map/*`, and related routes.
Demo Flow
How the pieces connect
Expand for the four-step path from phone collection to map review.
Demo Flow
How the pieces connect
Expand for the four-step path from phone collection to map review.
The phone page sends GPS, speed, heading, and acceleration to
/ingest at 1 Hz.
Incoming points are matched against the local Seoul road centerline layer.
Link-based accumulation (1km target) triggers prediction with multi-probe ensemble and stores link-level results.
The map page colors links and exposes history and detail panels for presentation.
Failure Modes
What this page tells you when something breaks
Expand for the recovery behavior behind health failures, empty map data, and slow refreshes.
Failure Modes
What this page tells you when something breaks
Expand for the recovery behavior behind health failures, empty map data, and slow refreshes.
The health panel keeps the last successful values, marks the section as unavailable, and prompts a retry.
The page distinguishes “no rows yet” from request failure so you can demo an empty DB without confusion.
The snapshot button disables while requests are in flight to prevent overlapping fetches.
Health and map feed fail independently, so one broken endpoint does not blank the whole console.