Khani, AlirezaBaek, Kwangho2024-06-272024-06-272024-06-27https://hdl.handle.net/11299/264009The project team requested transit agencies to conduct a manual data collection to retrieve each ride's origin, destination, and reservation-related information. The transit agencies were given two different standardized worksheets for two groups of transit service types (1: demand-responsive transit (DRT), route deviations, and some ADA paratransit; 2: fixed route buses). Agencies were asked to collect as many features as possible, considering their operational constraints, and not to compromise the safety and quality of their services. Data collection activity for each feature varied on the existing systems of each agency. In some cases, reservation call receptionists or vehicle drivers manually collected certain features, while in others, data administrators pulled data from their agency’s automated storage systems. For the fixed route bus data collection (conducted only for the pre-deployment phase), bus drivers surveyed the alighting locations of every boarding passenger at each stop. The timestamps of boarding and alighting activities of the fixed routes are attached later using the vehicle trip identifier and predefined timetables. The pre-deployment phase was 2023-01-23 to 2023-02-12, and the post-deployment phase was 2023-10-16 to 2023-10-21.The ODR data provides detailed observations of six Southern Minnesota Transit Agencies' trip reservations and actual trips over two one-week periods, spanning both pre- and post-MaaS deployment phases. The collected features for the reservation-based services — demand-responsive transits, some ADA paratransits, and route deviations — included the following: date and time of phone call (ride requests) received or reservation reception time (RRT or call-in time), the request’s intended trip date, preferred departure time (PDT), scheduled departure time (SDT), actual pick-up time (APT), actual drop-off time (ADT), origin & destination (OD), fare type (cash, token, etc.), service type (paratransit, student, etc.), and some information on trip cancellations. On the other hand, the collected features for the fixed route buses include the number of boarding and alighting activities for each bus stop and the inferred timestamps. Some measures were taken to mask sensitive information.Attribution 4.0 Internationalhttp://creativecommons.org/licenses/by/4.0/Mobility as a ServiceRural transitDatasethttps://doi.org/10.13020/yhg3-qh31