State transitions
Keep approach, arrival and departure behavior deterministic and explainable.
Current work · DDC
GPS-based route processing.
My current engineering focus inside the Driver Desk Console: turning live position data into reliable route, station and timing context for an embedded railway system.
High-level flow
From a GPS fix to useful operational information.
The implementation remains private. The public engineering story is the transformation pipeline and the reliability considerations around it.
01
Position input
Read and validate GPS/NMEA location data.
02
Route context
Relate current position to configured route and station coordinates.
03
Station state
Track operational transitions such as approach, arrival and departure.
04
Derived information
Calculate next-station distance, train speed and ETA.
05
Availability
Coordinate GPS sources across redundant DDC units at a high level.
Engineering concerns
The difficult part is not drawing a point on a map.
Real route processing has to cope with noisy data, partial state, startup in the middle of a route and abnormal movement—without exposing implementation-specific thresholds publicly.
Mid-route startup
Recover meaningful route context when the application starts away from the first station.
Direction sanity
Use movement trends to identify conditions that do not match the expected route progression.
Graceful GPS loss
Use high-level source coordination to preserve route awareness when local data is unavailable.