The example below shows a single-row record file.
$VISION
* VisumInst
* 24.07.08
*
*
* Table: Version block
$VERSION:VERSNR;FILETYPE;LANGUAGE;UNIT
4.00;SingleRowSurveyData;ENG;KM
* Table: Single-row survey data
$SingleRowSurveyData:No;Type;SurveyLineName;SurveyLineDirCode;SurveyLineRouteName;SurveyTimeProfileName;PreTSysCode;PreLineName;PreLineDirCode;PreLineRouteName;PreTimeProfileName;SucTSysCode;SucLineName;SucLineDirCode;SucLineRouteName;SucTimeProfileName;InputStopNo;InputStopDepDay;InputStopDepTime;OrigZoneNo;OrigStopNo;PreStopNo;BoardStopNo;AlightStopNo;SucStopNo;DestStopNo;DestZoneNo;NumPass; ExtProjFac
1;0;Train;H;1;;B;BUS1;H;1;1;;;;;;;;5;1;6:26:00;;30;10;20;40;;40;;17;
2;0;Train;R;1;1;;;;;;;;;;;;;5;1;6:25:00;100;;10;20;40;;40;;29;
3;99;Train;H;1;1;B;;;;;;;;;;5;1;6:25:00;;;;10;10;20;40;;40;;33;
4;0;BUS1;H;1;1;B;BUS1;H;1;1;;;;;;5;1;6:15:00;;;;10;20;30;40;;40;;18;
5;0;BUS1;H;1;1;;;;;;Z;Train;R;1;1;5;1;6:05:00;1;6:10:00;;10;;10;20;;40;;15;3
The following combinations of input attributes can serve as keys in the file. Then they are mandatory attributes:
- BoardStopNo, AlightStopNo, BoardStopNo, InputStopDepTime and InputStopDepDay / InputStopDepDate
- SurveyVehJourneyNo, BoardStopNo, AlightStopNo, InputStopNo and InputStopDepDay / InputStopDepDate
When employing this combination, Visum checks whether a vehicle journey item of the specified vehicle journey exists, which departs at the specified stop in the specified combination of time and day. This vehicle journey item is used as survey path leg from the BoardStopNo to the AlightStopNo if the vehicle journey serves this stop.
- SurveyVehJourneyNo, BoardVehJourneyItemIndex, AlightVehJourneyItemIndex and InputStopDepDay / InputStopDepDate
The survey path leg is identified. A vehicle journey is required which departs at the BoardVehJourneyItemIndex on the same day. If no suitable departure exists, the survey path leg is not plausible.
- SurveyVehJourneyNo, BoardVehJourneyItemIndex and InputStopDepDay / InputStopDepDate
Similar to the key described above. The item following the BoardVehJourneyItemIndex is considered the end of the path leg.
The following table describes the input attributes of a single-row survey data record file.
|
Attribute |
Description |
|
|
No. |
Number of the data record |
|
|
Type |
Data record type, serves for filtering during plausibilization (Default: 0) |
|
|
SurveyVehJourneyNo |
Number of the vehicle journey of the survey line |
|
|
SurveyLineName |
Key of the survey line, consisting of 4 compounds. These attributes need to match. |
Name of the survey line |
|
SurveyLineDirCode |
Direction code of survey line |
|
|
SurveyLineRouteName |
Name of the surveyed line route |
|
|
SurveyTimeProfileName |
Name of the surveyed time profile |
|
|
PreTSysCode |
Code of the preceding line’s TSys |
|
|
PreLineName |
Four-part key of the prec. leg These attributes need to match. |
Name of the preceding line |
|
PreLineDirCode |
Direction code of the preceding line |
|
|
PreLineRouteName |
Name of the preceding line route |
|
|
PreTimeProfileName |
Name of the preceding time profile |
|
|
SucTSysCode |
Code of the succeeding line’s TSys |
|
|
SucLineName |
Four-part key of the succ. leg These attributes need to be consistent with each other. |
Name of the succeeding line |
|
SucLineDirCode |
Direction code of succeeding line |
|
|
SucLineRouteName |
Name of the succeeding line route |
|
|
SucTimeProfileName |
Name of the succeeding time profile |
|
|
InputStopDepTime |
Time of departure time of the survey line from the stop specified as InputStopNo. |
|
|
InputStopDepDay |
Day of departure of the survey line from the stop specified as InputStopNo. |
|
|
InputStopDepDate |
Day of departure of the survey line from the stop specified under InputStopNo. If this attribute is available, it is converted into a calendar day index value according to the calendar used and entered into the attribute InputStopDepDay. |
|
|
InputStopNo |
Number of the stop in the survey line, to which the values InputStopDepTime and InputStopDepDay refer. |
|
|
OrigZoneNo |
Number of the passenger’s origin zone. If the OrigStopNo is also defined, both numbers have to match: At least one stop area of the stop needs to be allocated to a node which is connected to the zone. |
|
|
OrigStopNo |
Number of the start stop of the passenger trip. If the OrigStopNo is missing, PreStopNo = OrigStopNo is assumed. |
|
|
PreStopNo |
Number of a preceding stop (transfer stop) of the passenger trip. |
|
|
BoardVehJourneyItemIndex |
Index of the vehicle journey boarding item of the survey line |
|
|
AlightVehJourneyItemIndex |
Index of the vehicle journey alighting item of the survey line |
|
|
BoardStopNo |
Number of the stop where the passenger boarded the survey line. |
|
|
AlightStopNo |
Number of the stop where the passenger will alight the survey line. |
|
|
SucStopNo |
Number of a succeeding stop (transfer stop) of the passenger trip. |
|
|
DestStopNo |
Number of the passenger’s destination stop. If the DestStopNo is missing, SucStopNo = DestStopNo is assumed. |
|
|
DestZoneNo |
Number of the passenger’s destination zone. If the DestStopNo is also defined, both numbers have to match: At least one stop area of the stop needs to be allocated to a node which is connected to the zone. |
|
|
NumPassengers |
Number of boarding persons per ticket (= one data record, default value: 1) |
|
|
ExtProjFactor |
Via the external projection factor, external passenger weights can be taken into account. |
|
