-
Notifications
You must be signed in to change notification settings - Fork 41
InTraffic TURNN
InTraffic has a two propositions. The first one is multimodal trip planner that is offered via an API to MaaS providers. With parameters such as starting location and destination, along with preferences, a multimodal trip is provided. Modalities consist out of the ones that are connected to our trip planner. The second proposition is the trip follower, also offered via an API to MaaS providers. When an end user books a complete and multimodal journey, that journey is saved in our trip follower that will monitor the trip. When there is, for instance, a disturbance, the trip follower communicates back to the user what that is and might include an alternative journey.
TURNN is the MaaS provider app of the ICT Group (of which InTraffic is also apart). TURNN uses the multimodal trip planner from InTraffic. End users can book transport on demand, receive tickets for their journey, travel with public transport, etcetera.
Introduction
- Roadmap
- Semantic versioning
- Use cases
- Changes per version
- Contribution
- Participants
Workflow
- Operator information
- Planning phase
- Booking phase
- Trip execution phase - start
- Trip execution phase - on route
- Trip execution phase - end
- Support
- Payment
Points of attention
- Modalities
- Specifying locations
- GDPR
Eco system
- Relations
Introduction
Scope of the TOMP-API
Versioning and releases
Process Flows
- Authentication
- Operator Information
- Privacy and Registration
- Planning Module
- Booking Module
- Trip Execution Module
- Payment Module
- Support Module
Meta-Information
Reference implementations
To-dos and risks
Technical Specifications
A1 List of terms and definitions
A2 Passenger characteristics dictionary
A3 APIs available on the transportation ecosystem
A4 Overview of the User stories
A5 Authors, Architects, collaborators and stakeholders involved
A6 Adoption and Implementation of the TOMP-API