-
Notifications
You must be signed in to change notification settings - Fork 41
Stations
home > Operator information > Stations
In case a TO uses stations (or Hubs), this endpoint must be implemented. A request to this endpoint can contain the filter (query parameter) regionId.
field | required | description |
---|---|---|
stationId | * | Unique identifier of a station, self generated by TO or descriptive |
name | * | Public name of the station, matches Content-Language (see Information) |
coordinates | * | Coordinates of the station, lon/lat, WGS84 |
physicalAddress | Address of the station, containing street, city and postal code | |
crossStreet | Cross street of where the station is located. This field is intended to be a descriptive field for human consumption. In cities, this would be a cross street, but could also be a description of a location in a park, etc, matches Content-Language | |
regionId | ID of the region where the station operates (see Regions) | |
rentalMethods | Allowed payment methods. Less important for TOMP API: KEY, CREDITCARD, PAYPASS, APPLEPAY, ANDROIDPAY, TRANSITCARD, ACCOUNTNUMBER, PHONE, OTHER | |
rentalUrl | Optional URL for station |
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