Overview
The trip models handle trip lifecycle, driver assignments, fare calculations, and location tracking for rides in the Rodando platform.Core Trip Models
TripDto
Complete trip object with all details including status, location, and fare information. Source:src/app/features/trip/interfaces/trip.interface.ts:16
Unique identifier for the trip (UUID).
Current status of the trip in its lifecycle.Possible values:
pending- Trip created, awaiting assignmentassigning- System is finding a driveraccepted- Driver accepted the assignmentarriving- Driver is en route to pickup locationin_progress- Trip is in progresscompleted- Trip finished successfullycancelled- Trip was cancelledno_drivers_found- No available drivers found
Human-readable pickup address (e.g., “123 Main St, New York, NY”).
Geographic coordinates of the pickup location.
Array of intermediate stops and final destination.
Snapshot of fare calculation at trip creation time.
The type of vehicle requested for this trip.
The service level requested for this trip.
Estimated total fare for the trip.
Currency for the final fare (e.g., “USD”).
Distance used for fare calculation in kilometers.
Duration used for fare calculation in minutes.
TripStopDto
Represents a stop (intermediate or final destination) in a trip. Source:src/app/features/trip/interfaces/trip.interface.ts:1
Sequence number for the stop (0-based). Determines the order in which stops are visited.
Geographic coordinates of the stop location.
Human-readable address for the stop.
FareSnapshotDto
Snapshot of fare calculation parameters at the time of trip creation. Source:src/app/features/trip/interfaces/trip.interface.ts:7
ISO 4217 currency code (e.g., “USD”, “EUR”, “GBP”).
Surge pricing multiplier applied to base fare. A value of 1.5 means 1.5x the base price.
Detailed breakdown of fare components. Structure varies based on implementation.
Estimated trip distance in kilometers.
Estimated trip duration in minutes.
Total estimated fare amount in the specified currency.
Driver Action Models
DriverActionPayload
Payload for driver-initiated trip actions (arriving, starting trip). Source:src/app/features/trip/interfaces/trip.interface.ts:31
Unique identifier of the driver performing the action (UUID).
CompleteTripPayload
Payload for completing a trip with final details and charges. Source:src/app/features/trip/interfaces/trip.interface.ts:35
Unique identifier of the driver completing the trip (UUID).
Actual distance traveled in kilometers (from odometer or GPS tracking).
Actual trip duration in minutes.
Additional fees charged (e.g., tolls, parking, special handling).
Time driver waited for passenger in minutes.
Reason for waiting time (e.g., “Passenger delayed”, “Loading luggage”).
Assignment Models
TripAssignedVm
View model for trip assignment notifications displayed to drivers. Source:src/app/features/trip/interfaces/trip-assigned-modal.interface.ts:1
Unique identifier of the assigned trip (UUID).
Short label or address for the pickup location.
Short label or address for the destination.
Estimated distance to complete the trip in kilometers.
Estimated duration to complete the trip in minutes.
Estimated total fare for the trip.
Currency code for the fare (e.g., “USD”).
Related Models
See also:- User Models - User profiles and driver information (includes driver availability)
- Auth Models - Authentication and session data