-
Notifications
You must be signed in to change notification settings - Fork 41
Asset class
home > Planning phase > Asset class
These classes are taken from the NeTeX standard, but ALL and UNKNOWN are removed. On the other hand OTHER and PARKING are added.
In the future 'HOTEL' and 'MEETING' can be added.
| Allowed values | Note |
|---|---|
| AIR | |
| BUS | |
| TROLLEYBUS | |
| TRAM | |
| COACH | |
| RAIL | |
| INTERCITYRAIL | |
| URBANRAIL | |
| METRO | |
| WATER | Mainly for ferry |
| CABLEWAY | |
| FUNICULAR | |
| TAXI | |
| SELFDRIVE | |
| FOOT | |
| BICYCLE | |
| MOTORCYCLE | |
| CAR | |
| SHUTTLE | |
| OTHER | |
| PARKING | No difference between on-street and off-street |
| MOPED | |
| STEP |
If you want to specify the modality more accurate, use the field assetSubClass in the assetType.
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