Ride Insights
Full (demand and supply) data requirements
This page describes the data requirements for providing both demand and supply, i.e. both passengers and drivers data.
Ideally the data provided for Ride Insights should cover at least one month and full weeks, so the ideal minimal timespan is 6 weeks worth of data, i.e. from Oct 21, 2019 to Dec 01, 2019.
In the data fields description below, the xExternalId fields represent identity attributes from the ride-hailing platform perspective. Though they can be anonymized to the extent that they do not reveal the platform's internal identification structure, nor any personal identification if applicable.
The anonymization, however, should keep the ability to group / aggregate through individual entities (drivers, passengers). The reason is to allow for any future correlations when referring to an individual entity (order, passenger, driver), you will be able to track back from the provided external identification to your internal identification without losing the level of view.
Data fields
| Field | Optional? | Description |
|---|---|---|
| orderExternalId | mandatory | ID of the order |
| orderCreatedAt | mandatory | Time when passenger submitted the order request |
| passengerExternalId | mandatory | ID of the passenger |
| requestedPickupAt | optional | Passenger ordering for specific time, i.e. 15-min order or pre-order |
| requestedPickupLocationLat | mandatory | Latitude of the requested pickup location |
| requestedPickupLocationLon | mandatory | Longitude of the requested pickup location |
| requestedDestinationLocationLat | optional | Latitude of the requested destination location |
| requestedDestinationLocationLon | optional | Longitude of the requested destination location |
| driverInquiriesCount | optional | Number of drivers that have been sent the inquiry |
| offersCount | optional | Number of offers received from inquired drivers in case the platform is a bidding based system |
| driverExternalId | mandatory | ID of the driver (for finished rides) |
| estimatedDriverPickupArrivalAt | optional | Platform estimated pickup arrival time, not the driver's offered pickup ETA neither the real pickup ETA |
| estimatedRidePrice | optional | Platform estimated ride price |
| priceCurrency | mandatory | Currency of the price |
| estimatedRideDistanceMeters | optional | Platform estimated ride distance (meters) |
| estimatedRideDurationSeconds | optional | Platform estimated ride duration (seconds) |
| rideConfirmedAt | optional | Time when passenger confirmed the ride, in case the workflow includes passenger's confirmation, otherwise time when the ride transaction has been established |
| driverLocationAtRideConfirmationLat | optional | Latitude of driver's location when the passenger confirmed the ride |
| driverLocationAtRideConfirmationLon | optional | Longitude of driver's location when the passenger confirmed the ride |
| driverArrivalAt | mandatory | Time of driver's pickup location arrival (for finished rides) |
| pickupLocationLat | mandatory | Latitude of the realized ride's pickup location (for finished rides) |
| pickupLocationLon | mandatory | Longitude of the realized ride's pickup location (for finished rides) |
| passengerOnBoardAt | mandatory | Realized ride's passenger's onboarding time (for finished rides) |
| destinationLocationLat | mandatory | Latitude of the realized ride's destination location (for finished rides) |
| destinationLocationLon | mandatory | Longitude of the realized ride's destination location (for finished rides) |
| rideDistanceMeters | optional | Realized ride's distance driven (meters) |
| ridePrice | optional | Realized ride price charged to passenger |
| rideFinishedAt | mandatory | Time at end of ride (for finished rides) |