-
Notifications
You must be signed in to change notification settings - Fork 41
Return area
Another condition in the legs of the option (booking object) is the conditionReturnArea. Per leg (actually per asset) the return station or area can be described.
field | description |
---|---|
stationId | station to which the asset should be returned, see GET /Operator/stations) |
coordinates | coordinates of the station |
returnHours | opening hours |
returnArea | geojson polygon, first and last node must be the same (https://geojson.org/geojson-spec.html#polygon) |
If the asset needs to be returned at a specific station, fill in the stationId, coordinates and return hours. If the TO uses a free floating set up, respond with the returnArea.
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