You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the comment in PR #27 and a short exchange with @romain-fayoux-ecov, here are several points of attention noted to fully support the "instant carpooling line operator" use case.
There is no search per se, the passenger sends an open request at the station and a driver picks him up. During the pick up, the app may suggest to the passenger a list of drivers currently at the station. How can the deeplink be supported in this conditions ? My first idea is to implement a fake search that returns, once both driver and passenger are at the station, the journeys with this same list of drivers to choose from, with the associated webUrl. This may even be implemented in all cases to allow linking driver and passenger directly in the MaaS app.
Another use case, which is quite marginal, is that the driver is unknown (a driver just stops like for a hitch-hiker). The resulting trip is not reported to the "Registre de preuve de covoiturage". I wonder if just creating an "Anonymous driver" profile would enable this use case, it feels however a little bit hacky (but again, quite marginal use case).
The text was updated successfully, but these errors were encountered:
Following today's conversation, there is another point that was brought to my attention: the price of the trip is provided to the MaaS platform by the search results. Without a search, how would the MaaS know about the price?
Hi @pierrecamilleri , currently the MaaS knows about the price by reading the GTFS describing the carpooling network - not sure how it fits in this standard however
After the comment in PR #27 and a short exchange with @romain-fayoux-ecov, here are several points of attention noted to fully support the "instant carpooling line operator" use case.
search
per se, the passenger sends an open request at the station and a driver picks him up. During the pick up, the app may suggest to the passenger a list of drivers currently at the station. How can the deeplink be supported in this conditions ? My first idea is to implement a fake search that returns, once both driver and passenger are at the station, the journeys with this same list of drivers to choose from, with the associatedwebUrl
. This may even be implemented in all cases to allow linking driver and passenger directly in the MaaS app.The text was updated successfully, but these errors were encountered: