-
Notifications
You must be signed in to change notification settings - Fork 41
Specify pick up or drop off locations
Q: How do I specify a pick up or drop off location? A simple lon/lat is not enough (taxi scenario)
A: During the planning phase you have to use the lon/lat for the starting and end location. As TO you should add the condition REQUIRE-BOOKING-DATA to your planning conditions:
{ "name": "physical_locations", "conditionType": "conditionRequireBookingData", "requiredFields": ["FROM-ADDRESS", "TO-ADDRESS"] }
And you have to add this to every result:
{ .... conditions: ["physical_locations"] }
This means you request the from and to address when booking. The MP should provide these fields when booking, otherwise you (TO) can reject it directly.
/bookings/
{ "id": "the id you provided as TO", "customer": { "id": "A0-123456", "firstName": "John", "lastName": "Doe", "phone": "string", "email": "string" }, "fromAddress": { "streetAddress": "example street 18, 2nd floor, 18B-33", "areaReference": "Smallcity, Pinetree county", "postalCode": "string", "country": "NL" }, "toAddress": { "streetAddress": "example street 18, 2nd floor, 18B-33", "areaReference": "Smallcity, Pinetree county", "postalCode": "string", "country": "NL" } }
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