-
Notifications
You must be signed in to change notification settings - Fork 41
Place
home > Planning phase > Place
field | required | description |
---|---|---|
name | Human readable name of the place, could match Content-Language | |
stopReference | Reference to the (PT) stop, mandatory in case of MANDATORY_FROM_STOP_REFERENCE or MANDATORY_TO_STOP_REFERENCE. See processIdentifiers | |
stationId | reference to /operator/stations, mandatory in case of MANDATORY_FROM_STATION_ID or MANDATORY_TO_STATION_ID. See processIdentifiers | |
coordinates | * | object containing lon/lat information about the exact location |
physicalAddress | Address object, mandatory in case of MANDATORY_FROM_ADDRESS or MANDATORY_TO_ADDRESS. See processIdentifiers | |
extraInfo | Extra object, not standardized. Only to use in a peer-2-peer solution. If you use this field, please create also an issue in github, might be interesting to standardize |
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