-
Notifications
You must be signed in to change notification settings - Fork 41
Regions
home > Operator information > Regions
The region endpoint returns a list of regions. Each region is described by an id (self generated or descriptive), a name and a polygon. The polygon MUST be closed. This means the last and the first point in the polygon must be the same.
field | required | description |
---|---|---|
regionId | * | Unique identifier for this region. |
name | * | Public name for this region, matches Content-Language (see Information) |
serviceArea | * | geojsonPolygon: geojson representation of a polygon. The first and the last point must be equal. See also https://geojson.org/geojson-spec.html#polygon and example https://geojson.org/geojson-spec.html#id4 |
type | Since 1.3.0. See #384. the type of area. Default this is 'OPERATING', but other areas can be published here as well. Before 1.3.0, it was only allowed to communicate OPERATING areas. Therefore, when it is omitted, it should be assumed it is 'OPERATING' |
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