AI-generated Key Takeaways
-
This document describes the
TripLogresource in Fleet Engine, which logs trip details such as status, vehicle information, pickup/dropoff locations, and intermediate destinations. -
TripLogprovides fields for tracking actual pickup, dropoff, and intermediate destination locations and arrival times, offering insights into trip progress. -
StopLocationLogis a sub-resource withinTripLogused to record the precise location and timestamp of pickup/dropoff events for detailed analysis. -
Several fields within
TripLogutilize timestamps and durations to record crucial timing information, allowing for comprehensive trip monitoring and analysis.
The log of a Trip resource in Fleet Engine.
| JSON representation |
|---|
{ "name": string, "status": enum ( |
| Fields | |
|---|---|
name |
The trip resource name in the format of |
status |
The trip status. |
tripType |
The type of the trip. |
vehicleId |
The ID of the vehicle that the trip is assigned to. |
lastLocation |
The last reported location of the vehicle along the route. |
currentRouteSegmentEndPoint |
The waypoint where the |
pickupPoint |
Location where customer indicates they will be picked up. |
actualPickupPoint |
The actual location where customer was picked up. |
actualPickupArrivalPoint |
The actual time and location of the driver arrival at the pickup point. This field lets a provider give feedback on actual arrival information at the pickup point. |
pickupTime |
The customer's drop-off time. May be future or past. Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
intermediateDestinations[] |
Intermediate stops in requested order (in addition to pickup and dropoff). |
intermediateDestinationIndex |
When |
intermediateDestinationsVersion |
The version of the intermediate destinations given Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
actualIntermediateDestinations[] |
The actual time and location when and where the customer was picked up from an intermediate destination. This field lets a provider give feedback on actual pickup information at intermediate destinations. |
actualIntermediateDestinationArrivalPoints[] |
The actual time and location of the driver's arrival at an intermediate destination. This field lets a provider give feedback on actual arrival information at intermediate destinations. |
dropoffPoint |
Location where customer indicates they will be dropped off. |
actualDropoffPoint |
The actual location where customer was dropped off. |
dropoffTime |
Time when customer will be or was dropped off. Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
remainingDistanceMeters |
The remaining driving distance in the current route segment. |
etaToFirstWaypoint |
The ETA to the next waypoint (the first entry in Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
remainingTimeToFirstWaypoint |
The remaining time to the next waypoint (the first entry in A duration in seconds with up to nine fractional digits, ending with ' |
numberOfPassengers |
Indicates the number of passengers on this trip and does not include the driver. A vehicle must have available capacity to be returned in SearchVehicles. |
currentRouteSegmentTraffic |
When available, the traffic conditions along the currentRouteSegment. |
attributes[] |
A list of custom Trip attributes. |
StopLocationLog
The actual location where a stop (pickup/dropoff) happens.
| JSON representation |
|---|
{
"timestamp": string,
"point": {
object ( |
| Fields | |
|---|---|
timestamp |
The timestamp when the location is recorded. Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
point |
Denotes the actual location of the stop. |
TripAttributeLog
An attribute expressed as key-value pair that is associated with a Trip.
| JSON representation |
|---|
{ "key": string, // Union field |
| Fields | |
|---|---|
key |
The attribute's key. |
Union field trip_attribute_value. The attribute's value, can be in string, bool, or double type. trip_attribute_value can be only one of the following: |
|
stringValue |
String typed attribute value. |
boolValue |
Boolean typed attribute value. |
numberValue |
Double typed attribute value. |