-
Notifications
You must be signed in to change notification settings - Fork 41
Operator information
The Operator information module provides more or less static data about the operator, its regions, stations, opening hours, pricing and 'terms and conditions' (since version 1.1). The most important endpoints are described here.
Meta information contains per version the implemented endpoints, the supported scenarios, the process identifiers, and process steps. This endpoint is introduced for discovery reasons.
This endpoint contains generic information about the TO.
Regions contains named polygons. These regions can be used to filter other items in the operator module.
The public stations the TO publishes.
Published pricing plans.
The only 'realtime' endpoint in this module. Provides information about classes of assets (like 'Men's bike' or 'e-bike')
Describes the default opening hours per day of the week. Is GBFS compliant, an extension for 'specific days' is on the roadmap.
For compliancy reasons with GBFS. Public notifications/alerts can be done using this endpoint, but peer-to-peer notifications (f.x. communication about support or ETAs) should be done using the /bookings/{id}/notification endpoint.
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