Ride Insights
Demand-only data requirements
This page describes the data requirements for providing demand only with no supply, i.e. only passenger inquiries (route searches) without drivers data.
Ideally the provided data 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 passengerId field, which represents the ID of a passenger, can be anonymized to the extent that it does 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 passengers, so all inquiries performed by the same passenger should have the same passengerId in the data. The reason is to allow for any future correlations when referring to an individual passenger, you will be able to track back from the provided external identification (provided to Mileus) to your internal identification without losing the level of view.
Data fields
| Field | Optional? | Description |
|---|---|---|
| passengerId | mandatory | ID of the passenger |
| inquiryAt | mandatory | Timestamp of when the inquiry occurred |
| originLat | mandatory | Latitude of the requested start location |
| originLon | mandatory | Longitude of the requested start location |
| destinationLat | mandatory | Latitude of the requested end location |
| destinationLon | mandatory | Longitude of the requested end location |
| requestedDepartureAt | optional | Timestamp of when the passenger intended to departure from origin |
| requestedArrivalAt | optional | Timestamp of when the passenger intended to arrive to destination |
If neither requestedDepartureAt nor requestedArrivalAt is provided for the inquiry, it is assumed that the passenger intended to departure at inquiryAt.
If both requestedDepartureAt and requestedArrivalAt are provided, it is assumed that the passenger intended to departure at requestedDepartureAt.