-
Notifications
You must be signed in to change notification settings - Fork 41
Map based
home > Planning phase > Map based
If a TO wants to facilitate MPs in placing assets on a map, the MP can access the /operator/available-assets endpoint, but the TO has to supply the process identifier ASSET_BASED in combination with the EXACT_ID process identifier.
The TO has to fill the 'assets' field in the Available assets, but has to use rotating IDs to make it hard to track assets (GDPR compliancy). The MP can plan a specific asset on the map, by using the assetId in the POST plannings (see also Asset based) in the 'useAssets' field.
The rest of the process is again the same as Planning based.
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