Entrainment Definitions
There are different rules for entraining own mobility options within public transport. E.g., it is allowed to take a bike on board of a city rail (S-Bahn) and metro (U-Bahn) as well as of a tram in Berlin, but not allowed to take it into a bus. The entrainment table contains entrainment possibilities. Each allowed entrainment is defined by the following attributes:
- carrier: the major UrMoAC mode, yet usually “pt” for public transport;
- carrier_subtype: a numeric ID of the pt carrier type as defined by the “route_type” attribute stored in “routes.txt”; Please note that it may differ from the GTFS standard;
- carried: the UrMoAC mode that may be entrained.
The following options are used in combination with this data type:
- --entrainment <ENTRAINMENT_SOURCE>.
Please note that we do not have much experience in using the entrainment table, yet.
Database Format
The definition of an entrainment possibility consists of the following data in a database:
| Column Name | Type | Purpose |
|---|---|---|
| carrier | string | The major mode name |
| carrier_subtype | string | The subtype as defined in GTFS |
| carried | string | The name of the entrained mode, e.g. “bike” |
Use --entrainment jdbc:postgresql:<DB_HOST>,<SCHEMA>.<TABLE>,<USER>,<PASSWORD> to load entrainment definitions from a database. See Origins and Destinations for an explanation.
File (.csv) Format
You may load entrainment definitions from .csv-files. Each entrainment definition is stored in a single line individually. The following example defines that a bike may be taken on board of a pt subcarrier 400 (i.e. city rail in Berlin's GTFS definition):
pt;400;bike
Use --entrainment <MYFILE>.csv; to load the entrainment definitions from a .csv-file.