Comparison of VDV 452 and Visum data model

The network file which is generated during the import contains table and attribute names in English. The file contains all data required for the import. It is opened in Visum during data import. Visum then automatically adds tables and attributes to it. After data import, you can save the network as a Version file in the language of your choice.

During data export, the corresponding VDV 452 files are generated directly from the Visum data model. The allocation of tables and attributes of the data models corresponds to the import and export of the following data:

Notes: The tables and attributes are listed in the same order in which they appear in the network file. The names of the tables and attributes of Visum correspond to the names that are used in the network file by default.

The names of the VDV 452 data correspond to those in the German version of VDV PuT data model 5.0.

Visum table: $VERSION

Visum attribute

Attribute value

VERSNR

8,200. The network files are compatible with version 11.5 and higher.

FILETYPE

NET

LANGUAGE

ENG

UNIT

KM

Visum table: $USERATTDEF

Some table columns of the VDV 452 format are not adopted into the standard attributes of the Visum data model, but are saved to automatically generated user-defined attributes. Furthermore, the VDV files may contain additional table columns that are not defined in the VDV 452 format, but have been generated by the writing application. This data is also automatically saved to user-defined attributes. The table USERATTDEF is created dynamically, when the attributes of the Visum tables are generated. In the following, the entries are listed that are generated by default. Depending on any additional columns, there may be additional entries. The allocation to the columns of the VDV 452 data is listed in the descriptions of the Visum tables.

Visum network object type

User-defined attribute

TSYS

ORG_OP_DEP_NO

NODE

ORG_STOP_LONG_NO

NODE ORG_STOP_NO

LINEROUTE

LINEROUTEITEM

VEHJOURNEY

ORG_LINE_NO

LINEROUTE

LINEROUTEITEM

VEHJOURNEY

ORG_ROUTE_ABBR

LINEROUTE

ORG_ROUTE_NO

LINEROUTE

ORG_LINE_DESC

LINEROUTEITEM

ORG_SEQUENCE_NO

LINEROUTEITEM

DEST_BRIEF_TEXT

LINEROUTEITEM

DEST_SIDE_TEXT

LINEROUTEITEM

DEST_FRONT_TEXT

LINEROUTEITEM

DEST_FRONT_CODE

LINEROUTEITEM

ANN_DESC

LINEROUTEITEM

ANN_NO

TIMEPROFILE

ORG_TIMING_GROUP_NO

VEHJOURNEY

ORG_RUN

VEHJOURNEY

ORG_JOURNEY_TYPE_NO

VEHJOURNEY

ORG_JOURNEY_NO

VEHJOURNEY

ORG_BLOCK_NO

VEHJOURNEYSECTION ORG_JOURNEY_NO
STOP ORG_STOP_NO
STOPAREA ORG_STOP_NO
STOPAREA ORG_STOP_NO
STOPPOINT ORG_STOP_NO
VALIDDAYS DAY_TYPE_NO

SYSTEMROUTE

ORG_TIMING_GROUP_NO

SYSTEMROUTE ORG_LINE_NO
SYSTEMROUTE ORG_LINE_DESC

SYSTEMROUTE

ORG_ROUTE_NO

SYSTEMROUTE ORG_ROUTE_ABBR

VEHUNIT

VH_TYPE_SPEC_SEAT

VEHUNIT

VH_TYPE_LENGTH

Visum table: $TSYS

In the VDV 452 data format, the modes of transport of the timetable are not explicitly identified. In the VDV 452 table OPERATING_DEPARTMENT, however, operating departments can be defined and assigned to the supply. These are depicted in the Visum network as transport systems and modes.

If the VDV 452 table OPERATING_DEPARTMENT contains additional attributes, these are saved as user-defined attributes in the Visum table $TSYS.

If the VDV 452 table OPERATING_DEPARTMENT does not contain any data records for the version selected, data import is canceled. Data without a transport system cannot be meaningfully used in Visum.

Visum attribute

Source table

Source attribute/value/type

CODE

OPERATING_DEPARTMENT

OP_DEP_ABBR

NAME

OPERATING_DEPARTMENT

OP_DEP_DESC

PCU

-

1.0

TYPE

-

PuT

ORG_OP_DEP_NO

OPERATING_DEPARTMENT

OP_DEP_NO

Visum table $MODE

Visum attribute

Source table

Source attribute/value/type

CODE

-

PuT

NAME

-

PuT

TSYSSET

OPERATING_DEPARTMENT

All entries of column OP_DEP_ABBR, Individual entries are separated by a comma

TYPE

-

0

Visum table $INFO

In the text field of the first data record, the text VDV 452 Import<Import date>, <Name BASE_VERSION> and <Validity BASE_VERSION> are entered.

Visum attribute

Source table

Source attribute/value/type

INDEX

-

Starting at 1

TEXT

BASE_VERSION

BASE_VERSION/BASE_VERSION_DESC/BASE_VERSION_VALID

Visum table: $DIRECTION

Visum attribute

Source table

Source attribute/value/type

NO

-

Forward = 1

Reverse = 2

CODE

-

Forward = >

Reverse = <

NAME

-

Direction = up

Direction = down

Vehicle units and vehicle combinations

Depending on whether blocks have been taken into account during the import, vehicle units and vehicle combinations are handled differently.

Visum table $VEHUNIT

If blocks are not taken into account during the import, all vehicle journeys are saved with standard vehicles. For each entry in OPERATING_DEPARTMENT, a standard vehicle combination will be created according to the allocation rules of the below table. It will then be used in the respective vehicle journeys.

Visum attribute

Source table

Source attribute/value/type

TSYSSET

OPERATING_DEPARTMENT

OP_DEP_ABBR

NO

OPERATING_DEPARTMENT

OP_DEP_NO

CODE

OPERATING_DEPARTMENT

OP_DEP_ABBR

NAME

OPERATING_DEPARTMENT

OP_DEP_DESC

If blocks are taken into account during the import, the vehicle types defined in VEHICLE_TYPE are mapped directly to vehicle units and vehicle combinations according to the table below and used in the vehicle journeys.

Visum attribute

Source table

Source attribute/value/type

TSYSSET

OPERATING_DEPARTMENT

OP_DEP_ABBR

NO

VEHICLE_TYPE

VH_TYPE_NO

CODE

VEHICLE_TYPE

VH_TYPE_ABBR

NAME

VEHICLE_TYPE

VH_TYPE_DESC

SEATCAP VEHICLE_TYPE VH_TYPE_SEAT
TOTALCAP VEHICLE_TYPE VH_TYPE_SEAT + VH_TYPE_STAND
ORG_VH_TYPE_SPEC_SEAT VEHICLE_TYPE VH_TYPE_SPEC_SEAT
Visum table $VEHCOMB

Depending on whether blocks are taken into account or not, vehicle units and combinations are handled differently.

If blocks are not taken into account, the vehicle combinations are generated in accordance with the vehicle units from OPERATING_DEPARTMENT according to the table below:

Visum attribute

Source table

Source attribute/value/type

NO

OPERATING_DEPARTMENT

OP_DEP_NO

CODE

OPERATING_DEPARTMENT

OP_DEP_ABBR

NAME

OPERATING_DEPARTMENT

OP_DEP_DESC

Similarly to the vehicle units, the vehicle combinations are generated based on the following allocation if blocks are taken into account:

Visum attribute

Source table

Source attribute/value/type

NO

VEHICLE_TYPE

VH_TYPE_NO

CODE

VEHICLE_TYPE

VH_TYPE_ABBR

NAME

VEHICLE_TYPE

VH_TYPE_DESC

Visum table $VEHUNITTOVEHCOMB

Vehicle combinations are always generated from a single vehicle unit each.

If blocks are not taken into account, the vehicle units are allocated to vehicle combinations according to the table below based on OPERATING_DEPARTMENT:

Visum attribute

Source table

Source attribute/value/type

VEHCOMBNO

OPERATING_DEPARTMENT

OP_DEP_NO

VEHUNITNO

OPERATING_DEPARTMENT

OP_DEP_NO

NUMVEHUNITS

-

1

If blocks are taken into account, vehicle combinations are generated based on the following allocation:

Visum attribute

Source table

Source attribute/value/type

VEHCOMBNO

VEHICLE_TYPE

VH_TYPE_NO

VEHUNITNO

VEHICLE_TYPE

VH_TYPE_NO

NUMVEHUNITS

-

1

Visum table: $NODE

In the STOP table, the POINT_NO field is only unambiguous together with POINT_TYPE. This allows the program to generate unambiguous node numbers. According to VDV 452, the coordinates must be specified in WGS84, in the format dddmmssnnn (number of degrees, minutes, seconds with 3 decimal places/milliseconds. A positive (+) longitude value refers to eastern or northern hemisphere, a negative (-) longitude value refers to the western or southern hemisphere.

If the VDV 452 STOP table contains attributes that are not directly adopted into Visum attributes, these are also saved as user-defined attributes in the Visum NODE table.

Visum attribute

Source table

Source attribute/value/type

NO

-

Starting at 1

CODE

STOP

POINT_NO

TYPE

STOP

POINT_TYPE

NAME

STOP

POINT_DESC

XCOORD

-

0 (optional from STOP.POINT_LONGITUDE)

YCOORD

-

0 (optional from STOP.POINT_LATITUDE)

ORG_STOP_LONG_NO

STOP

STOP_LONG NO

ORG_STOP_NO

STOP

POINT_NO

Visum table: $STOP

For stops, only data records of STOP are relevant, for which the STOP_TYPE value is 1 or 2.

Since the VDV number STOP_NO of the stops and depots is not unambiguous, the STOP_NO values of the VDV 452 table STOP cannot be used directly as stop numbers. The imported stops/depots each get a newly generated number. The original STOP_NO number is saved to the user-defined attribute ORG_STOP_NO.

Coordinates are adopted analogous to the NODE.

The stop points depicted are grouped into stops. Stop points and stop areas are 1:1 representations, n stop areas are assigned to a stop. The superordinate stop is formed of Number of STOP_NO + name of STOP_DESC.

Visum attribute

Source table

Source attribute/value/type

NO

-

Starting at 1

CODE

STOP

STOP_ABBR

NAME

STOP

STOP_DESC

XCOORD

-

0 (optional from STOP.POINT_LONGITUDE)

YCOORD

-

0 (optional from STOP.POINT_LATITUDE)

ORG_STOP_NO

STOP

STOP_NO

Visum table: $STOPAREA

For stop areas, only the data records listed in the STOP table are relevant for which the POINT_TYPE value is 1 or 2.

Since the VDV number STOP_NO of the stops and depots is not unambiguous, the STOP_NO values of the VDV 452 table STOP cannot be used directly as stop area numbers. The imported stops/depots each get a newly generated number. The original STOP_NO number is saved to the user-defined attribute ORG_STOP_NO.

Coordinates are adopted analogous to the NODE.

The stop points depicted are grouped into stops. Stop points and stop areas are 1:1 representations, stop areas are assigned to a stop. The superordinate stop is formed of Number of STOP_NO + name of STOP_DESC.

Visum attribute

Source table

Source attribute/value/type

NO

-

Starting at 1

CODE

STOP

STOP_ABBR

NAME

STOP

POINT_DESC

TYPENO

STOP

POINT_TYPE

XCOORD

STOP

0 (optional from STOP.POINT_LONGITUDE)

YCOORD

STOP

0 (optional from STOP.POINT_LATITUDE)

STOPNO

STOP

STOP_NO

ORG_STOP_NO

STOP

STOP_NO

ORG_STOP_NO

STOP

POINT_NO

Visum table: $STOPPOINT

For stop points, only the data records listed in the STOP table are relevant for which the POINT_TYPE value is 1 or 2. Since the VDV number STOP_NO of the stops and depots is not unambiguous, the STOP_NO values of the VDV 452 tables STOP cannot be used directly as stop point numbers. The imported stops/depots each get a newly generated number. The original STOP_NO number is saved to the user-defined attribute ORG_STOP_NO.

Coordinates are adopted analogous to the NODE.

The stop points depicted are grouped into stops. Stop points and stop areas are 1:1 representations, stop areas are assigned to a stop.

As DIRECTED is automatically set to 1 when you read in the network file generated by Visum, the field is left empty.

In the VDV 452 data model, stop points always implicitly form nodes of the link network, while in the Visum data model, stop points may also lie on links. If there are stop points on links, a representation is generated during data export, in which these stop points are also nodes of the link network (Visum table: $LINK).

Visum attribute

Source table

Source attribute/value/type

NO

-

starting at 1

NODENO

STOP

Automatically generated node number (Visum table: $NODE)

CODE

STOP

STOP_ABBR

NAME

STOP

POINT_DESC

TSYSSET

OPERATING_DEPARTMENT

OP_DEP_ABBR (comma-separated concatenation of all values)

STOPAREANO

STOP

POINT_NO

FROMNODENO

-

empty

DIRECTED

-

empty

LINK NO

-

empty

DEPOTVEHCOMBSTANDARD

STOP

FALSE

RELPOS

-

empty

ISDEPOT

STOP

If POINT_TYPE = 2 then TRUE, otherwise FALSE

ORG_STOP_NO

STOP

STOP_NO

ORG_STOP_NO

STOP

POINT_NO

Visum table $FAREZONE

Fare zones in VDV 452 format are not provided as a separate data type. They are defined via fare zone numbers of stop points listed in column ZONE_CELL_NO of table STOP. During VDV 452 data import to Visum, for the fare zone numbers imported, fare zones are automatically created assigned to the stops. For fare zones, only the data records listed in the STOP table are relevant for which the POINT_TYPE value is 1.

Visum attribute

Source table

Source attribute/value/type

NO

STOP

ZONE_CELL_NO

CODE

STOP

ZONE_CELL_NO

NAME

STOP

ZONE_CELL_NO

Visum table $STOPTOFAREZONE

Visum attribute

Source table

Source attribute/value/type

FARZONENO

STOP

ZONE_CELL_NO

STOPNO

STOP

STOP_NO

Visum table $LINKTYPE

Visum attribute

Source table

Source attribute/value/type

NO

-

0

TSYSSET

OPERATING_DEPARTMENT

OP_DEP_ABBR (comma-separated concatenation of all values)

CAPPRT

-

99999

VMINPRT

-

0

RANK

-

1

Visum table: $LINK
Import:

When you generate links in the Visum data model, the VDV 452 tables LINK, POINT_ON_LINK, and STOP are taken into account. Links are created as straight lines (without intermediate points) between two points. The intermediate points specified in POINT_ON_LINK are not implemented as simple polygon points, but as full-fledged nodes. This way, the entries in STOP that are not implemented because of their type are adopted as nodes or route points of time profiles. Subsequent to data import, any two-leg nodes created can be deleted if required (Deleting several marked nodes). A node pair <FromNode, ToNode> is assigned the same link number as <ToNode, FromNode>.

If the LINK table contains coordinates, these are adopted for the nodes, but here no length is entered for the links. When the network file is imported into Visum, the link lengths are calculated automatically. However, the attribute LINK_DISTANCE is adopted as a user-defined attribute for the link.

If the LINK or POINT_ON_LINK table contain attributes that are not directly adopted into Visum attributes, these are saved as user-defined attributes to the Visum table LINK.

Export:

Note: The LINK table is not generated based on Visum links. It is based on line routes. There are no polygon points for instance.

To generate the tables LINK and POINT_ON_LINK during data export, not the actual links of the Visum network model are used, but an abstract link network that consists of line routes and stop points. The route points defined within the line routes are represented in the LINK entries. In addition, line route items that are not route points are exported as intermediate points into POINT_ON_LINK. Polygon points of the underlying link network are not exported. Details of the LINK_DISTANCE column that are used during data export are adopted from route points in the POSTLENGTH attribute. For other line route items, they are adopted from the LENGTH attribute.

Visum attribute

Source table

Source attribute/value/type

NO

-

Start value 1, incremented by 1

FROMNODENO

LINKPOINT_ON_LINK

Automatically generated node number (Visum table: $NODE)

TONODENO

LINKPOINT_ON_LINK

Automatically generated node number (Visum table: $NODE)

TYPENO

-

0

TSYSSET

OPERATING_DEPARTMENT

OP_DEP_ABBR (comma-separated concatenation of all values)

LENGTH

LINK

  • if nodes do not contain coordinates: LINK_DISTANCE (in m -> / 1000).
  • if nodes do contain coordinates: Visum calculates
Visum table $CALENDARPERIOD

If the PERIOD table contains attributes that are not directly imported into Visum attributes, these cannot be imported into Visum, as user-defined attributes cannot be managed for target attributes.

Visum attribute

Source table

Source attribute/value/type

NO

-

1

VALIDFROM

PERIOD

Day of service (first day of time period in table)

VALIDUNTIL

PERIOD

Day of service (last day of time period in table)

TYPE

-

Annual calendar (type 0 = 3)

CODE

BASE_VERSION

BASE_VERSION + BASE_VERSION_DESC

NAME

-

empty

Visum table $VALIDDAYS

For each type of day listed in the DAY_TYPE table, a row is generated in the VALIDDAYS table.

The DAYVECTOR is generated for the entire time period listed in the CALENDERPERIOD table. For all days between the first and last service day, it is initially set to 0.

In the following step, all values of the current day type in the PERIOD  table are compared. Then for all service days listed with the same day type, the DAYVECTOR is set to 1.

In Visum, by default, the number 1 assigned to valid days means daily. If the VDV 452 import data includes a valid day with the DAY_TYPE_NO = 1, the program checks whether this refers to daily. This is the case if all calendar days listed in the PERIOD table are assigned to it. Then the data with the valid day 1 is adopted. Otherwise a new valid day with the next number available is generated. In this case, the numbers of the following valid days imported might change, as each time the next available unique number is assigned.

If the DAY_TYPE table contains attributes that are not directly adopted into Visum attributes, these are saved as user-defined attributes to the Visum table VALIDDAYS.

Visum attribute

Source table

Source attribute/value/type

NO

DAY_TYPE

DAY_TYPE_NO*(see above for description)

CODE

DAY_TYPE

DAY_TYPE_NO

NAME

DAY_TYPE

DAY_TYPE_DESC

DAYVECTOR

 

Bit vector, entry is based on validity of a service day in the PERIOD table:

  • 0 = does not take place
  • 1 = takes place

FROMSYSTEM

 

0

ORG_DAY_TYPE_NO DAY_TYPE DAY_TYPE_NO
Visum table: $LINE

Only regular service trips are considered (i.e. LINE data records with ROUTE_TYPE = 1). If blocks are taken into account, arrival, departure, and approach trips (i.e. LINE data records with ROUTE_TYPE = 2,3 or 4) are saved as empty trips, otherwise they are ignored.

Visum attribute

Source table

Source attribute/value/type

NAME

LINE

LINE_ABBR

VEHCOMB

LINE

OP_DEP_NO

TSYSCODE

OPERATING_DEPARTMENT

OP_DEP_ABBR via LINE.OP_DEP_NO = OPERATING_DEPARTMENT.OP_DEP_NO
Visum table: $LINEROUTE

If the LINE table contains attributes that are not directly adopted into Visum attributes, these are saved as user-defined attributes to the Visum LINEROUTE table.

Visum attribute

Source table

Source attribute/value/type

NAME

-

Start value 1, incremented by 1

LINENAME

LINE

LINE_ABBR

DIRECTIONCODE

LINE

DIRECTION (value1 is replaced by > = up, value 2 is replaced by < = down. See Visum table DIRECTION)

ISCIRCLELINE

-

0 if start stop point is not end stop point, otherwise 1

ORG_LINE_NO

LINE

LINE_NO

ORG_ROUTE_ABBR

LINE

ROUTE_ABBR

ORG_ROUTEN_NR

LINE

ROUTE_NO

ORG_LINE_DESC

LINE

LINE_DESC

Visum table: $LINEROUTEITEM

Please note: At the last line route item of a line route, the stop point is equal to the following stop point, for which the POSTLENGTH value is then = 0.

If the ROUTE_SEQUENCE.DESTINATION table contains attributes that are not directly adopted into Visum attributes, these are saved as user-defined attributes to the Visum LINEROUTEITEM table.

Visum attribute

Source table

Source attribute/value/type

INDEX

 

Consecutive index

ISROUTEPOINT

-

1

POSTLENGTH

LINK

LINK_DISTANCE/1000 (via LINK.OP_DEP_NO and LINK.POINT_NO and LINK.TO_POINT_NO) is required as there are no coordinates.

LINENAME

LINE

LINE_ABBR

DIRECTIONCODE

LINE

DIRECTION (value1 is replaced by > = up, value 2 is replaced by < = down. See Visum table DIRECTION )

LINEROUTENAME

LINE

NAME generated in LINEROUTE

STOPPOINTNO

ROUTE_SEQUENCE

POINT_NO

NODENO

ROUTE_SEQUENCE

If provided: POINT_ON_LINK

Automatically generated node number (Visum table: $NODE)

DEST_BRIEF_TEXT

DESTINATION

DEST_BRIEF_TEXT

DEST_SIDE_TEXT

DESTINATION

DEST_SIDE_TEXT

DEST_FRONT_TEXT

DESTINATION

DEST_FRONT_TEXT

ORG_SEQUENCE_NO

ROUTE_SEQUENCE

SEQUENCE_NO

Visum table $TIMEPROFILE

If the TIMING_GROUP table contains attributes that are not directly adopted into Visum attributes, these are saved as user-defined attributes to the Visum TIMEPROFILE table.

Visum attribute

Source table

Source attribute/value/type

NAME

JOURNEY

TIMING_GROUP

LINE_NO + „|“ + ROUTE_ABBR + „|“ + TIMING_GROUP.TIMING_GROUP_NO + „|“ + TIMING_GROUP.TIMING_GROUP.TEXT (via TIMING_GROUP_NO)

LINENAME

LINE

LINE_ABBR via JOURNEY.LINE_NO = LINE.LINE_NO and JOURNEY.ROUTE_ABBR = LINE.ROUTE_ABBR

DIRECTIONCODE

LINE

DIRECTION via JOURNEY.LINE_NO = LINE.LINE_NO and JOURNEY.ROUTE_ABBR = LINE.ROUTE_ABBR; if DIRECTION = 1 then > if DIRECTION = 2 then <

LINEROUTENAME

LINE

NAME generated in LINEROUTE

VEHCOMBNO

LINE

OP_DEP_NO

ORG_TIMING_GROUP_NO

JOURNEY

TIMING_GROUP_NO

Visum table $TIMEPROFILEITEM

Visum attribute

Source table

Source attribute/value/type

INDEX

-

Start value 1, incremented by 1

LRITEMINDEX

ROUTE_SEQUENCE

ROUTE_SEQUENCE.SEQUENCE_NO via JOURNEY.LINE_NO = ROUTE_SEQUENCE.LINE_NO and JOURNEY.ROUTE_ABBR = ROUTE_SEQUENCE.ROUTE_ABBR

The latter is used to create the index of the corresponding line route items.

LINENAME

LINE

LINE.LINE_ABBR via JOURNEY.LINE_NO = LINE.LINE_NO and JOURNEY.ROUTE_ABBR = LINE.ROUTE_ABBR

DIRECTIONCODE

LINE

DIRECTION via JOURNEY.LINE_NO = LINE.LINE_NO and JOURNEY.ROUTE_ABBR = LINE.ROUTE_ABBR

DIRECTION (value 1 is replaced by > = up, value 2 is replaced by < = down. See Visum table DIRECTION )

LINEROUTENAME

JOURNEY

NAME generated in LINEROUTE

TIMEPROFILENAME

JOURNEY TIMING_GROUP

LINE_NO + „|“ + ROUTE_ABBR + „|“ + TIMING_GROUP.TIMING_GROUP_NO + „|“ + TIMING_GROUP.TIMING_GROUP.TEXT (via TIMING_GROUP_NO)

BOARD

-

For the last data record of a time profile the value is 0, otherwise it is 1.

ALIGHT

-

For the first data record of a time profile the value is 0, otherwise it is 1.

ARR

TRAVEL_TIME

TRAVEL_TIME (added, modulo 24h)

DEP

TRAVEL_TIME+ WAIT_TIME

TRAVEL_TIME.TRAVEL_TIME (added) + WAIT_TIME.WAIT_TIME (modulo 24h)

STOPTIME JOURNEY_WAIT_TIME JOURNEY_WAIT_TIME
Visum table $VEHICLEJOURNEY

If the JOURNEY table contains attributes that are not directly adopted into Visum attributes, these are saved as user-defined attributes to the Visum VEHICLEJOURNEY table.

Visum attribute

Source table

Source attribute/value/type

NO

-

Start value 1, incremented by 1

DEP

JOURNEY

DEPARTURE_TIME (modulo 24h)

LINENAME

LINE

LINE_ABBR/char(6) via JOURNEY.LINE_NO = LINE.LINE_NO and JOURNEY.ROUTE_ABBR = LINE.ROUTE_ABBR

DIRECTIONCODE

LINE

DIRECTION (value 1 is replaced by > = up, value 2 is replaced by < = down. See Visum table DIRECTION )

LINEROUTENAME

JOURNEY

NAME generated in LINEROUTE

TIMEPROFILENAME

JOURNEY TIMING_GROUP

TIMEPROFILE.NAME (= LINE_NO + „|“ + ROUTE_ABBR + „|“ + TIMING_GROUP.TIMING_GROUP_NO + „|“ + TIMING_GROUP.TIMING_GROUP_Text via TIMING_GROUP_NO)

FROMTPROFILITEMINDEX

- 1

TOTPROFILITEMINDEX

ROUTE_SEQUENCE

Value = Number of data records found for which the following is true:

JOURNEY.LINE_NO =

ROUTE_SEQUENCE.LINE_NO and JOURNEY.ROUTE_ABBR = ROUTE_SEQUENCE.ROUTE_ABBR

ORG_JOURNEY_NO

JOURNEY

JOURNEY_NO

ORG_JOURNEY_TYPE_NO

JOURNEY

JOURNEY_TYPE_NO

ORG_RUN

JOURNEY

RUN

THROUGH_START

JOURNEY

The field content is 1 if passengers are allowed in the vehicle at the beginning of the trip.

THROUGH_START

THROUGH_END

JOURNEY

The field content is 1 if passengers are allowed in the vehicle at the end of the trip.

THROUGH_END

Visum table $VEHICLEJOURNEYSECTION

For each entry in VEHICLEJOURNEYS an entry in VEHICLEJOURNEYSECTION is generated, as there is exactly one section listing all time profile items. Accordingly, the number is always 1.

Visum attribute

Source table

Source attribute/value/type

NO

 

Always 1

VALIDDAYSNO

JOURNEY

DAY_TYPE_NO according to VALIDDAYS table (Visum table $CALENDARPERIOD)

VEHCOMBNO

LINE

OP_DEP_NO

FROMTPROFILITEMINDEX

-

1

TOTPROFILITEMINDEX

ROUTE_SEQUENCE

1 to N (number of data records found in ROUTE_SEQUENCE, incremented by 1, for which the following applies: ROUTE_SEQUENCE.LINE_NO = JOURNEY.LINE_NO and ROUTE_SEQUENCE.ROUTE_ABBR = JOURNEY.ROUTE_ABBR

VEHJOURNEYNO

JOURNEY

NO generated in VEHJOURNEY

VEHCOMBSET

JOURNEY TIMING_GROUP

Empty

ORG_JOURNEY_NO

JOURNEY

JOURNEY_NO

Visum table $SYSTEMROUTE

If blocks are taken into account, arrival, departure, and approach trips (i.e. LINE data records with ROUTE_TYPE = 2,3 or 4) are saved as empty trips, otherwise they are ignored. For the course of these empty trips, system routes are generated.

Visum attribute

Source table

Source attribute/value/type

NAME

LINE

LINE_ABBR

TSYSCODE

OPERATING_DEPARTMENT

OP_DEP_ABBR via LINE.OP_DEP_NO = OPERATING_DEPARTMENT.OP_DEP_NO
TNONSTOP TRAVEL_TIME, WAIT_TIME ΣTRAVEL_TIME.TRAVEL + WAIT_TIME.WAIT_TIME
TSTARTSTOP - 0
TENDSTOP - 0
LENGTH LINK LINK_DISTANCE / 1000
Visum table $SYSTEMROUTEITEM

Visum attribute

Source table

Source attribute/value/type

INDEX

-

Consecutive number

NODENO

STOP

Generated number of the allocated node from STOP

STOPPOINTNO

STOP

Generated number of the allocated stop point from STOP

SYSROUTENAME

LINE

NAME generated in SYSROUTE

Visum table $BLOCKVERSION

For each day type defined in the DAY_TYPE table, a separate block version is created and the blocks are allocated according to the service days of their vehicle journeys.

Visum attribute

Source table

Source attribute/value/type

ID

-

Starting at 1

CODE

DAY_TYPE

DAY_TYPE_NO

NAME

DAY_TYPE

DAY_TYPE_DESC

STARTDAYINDEX

PERIOD

Index of the first day with vehicle journeys of the day type

ENDDAYINDEX

PERIOD

Index of the last day with vehicle journeys of the day type

SYSTEMROUTEUSAGE

-

3

Visum table $BLOCK

The blocks of a day type are converted into blocks of a calendar day in the Visum block model. The first day allocated to a day type is used as calendar day. In this case, a valid day contains all blocks of the day type.

Visum attribute

Source table

Source attribute/value/type

ID

-

Starting at 1

BLOCKVERSIONID

-

Block version ID matching the day type_no

CODE

BLOCK

BLOCK_NO

NAME

BLOCK

BLOCK_NO

VEHCOMBNO

BLOCK

VH_TYPE_NO

NUMBLOCKINGDAYS

-

1

SELFCONTAINED

-

0

EMPTYTRIPTSYSCODE

JOURNEY

TSys code of the line route of the first vehicle journey of the block.

Visum table $BLOCKITEM

In this case, a valid day contains all blocks of the day type.

Visum attribute

Source table

Source attribute/value/type

BLOCKID

 

Block ID

INDEX

 

Index

BLOCKINGDAY

 

1

BLOCKITEMTYPENO

JOURNEY

1 or 2, depending on JOURNEY.JOURNEY_TYPE

VEHJOURNEYNO

JOURNEY

If JOURNEY.JOURNEY_TYPE = 1: number of the vehicle journey in VehicleJourney, otherwise 0

VEHJOURNEYSECTIONNO

-

If JOURNEY.JOURNEY_TYPE = 1: 1, otherwise 0

STARTDAYINDEX

JOURNEY

(JOURNEY.JOURNEY_TYPE / 3600 * 24) +1

STARTTIME

JOURNEY

DEPARTURE_TIME (for empty trips DEPARTURE_TIME modulo 24h!)

FROMSTOPPOINTNO

ROUTE_SEQUENCE

First stop point of the line route/system route of the vehicle journey

TOSTOPPOINTNO

ROUTE_SEQUENCE

Last stop point of the line route/system route of the vehicle journey

DURATION

-

0

USEDSYSROUTENAME

-

Generated name of the used system route