Visum 75 Manual

9,680 86(5 0$18$/
$QDO\VLV DQG 3ODQQLQJ RI 7UDQVSRUW 1HWZRUNV
9,680
Stumpfstr. 1 D-76131 Karlsruhe Fon: ++49 721 - 9651-313 Fax: ++49 721 - 9651-299 e-mail: hotline.visum@ptv.de
DISCLOSURE
',6&/2685(
Copyright 1991-2001
PTV Planung Transport Verkehr AG All rights reserved
PTV AG Stumpfstr. 1 D-76131 Karslruhe Germany
VISUM User Manual (April 2001) Version 7.50
DISCLOSURE
TABLE OF CONTENTS
7$%/( 2) &217(176
1.1 1.1.1 1.1.2 1.2 1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 1.3 1.3.1 1.3.2 1.3.3 1.4 1.5
,1752'8&7,21 Manual Structure of the manual Format conventions VISUM Capabilities VISUM database Impact models Transport supply analysis Fields of application for planning tasks in Public Transport Fields of application for planning tasks in Private Transport Technical information Available VISUM versions (Size and Add-Ons) Hardware and software requirements Dongle Installation of VISUM Problems during program operation 1-4 1-4 1-5 1-6 1-6 1-7 1-7 1-8 1-8 1-9 1-9 1-11 1-11 1-12 1-16
TABLE OF CONTENTS
2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.1.7 2.2 2.3 2.3.1 2.3.2 2.3.3 2.4 2.4.1 2.4.2 2.4.3 2.4.4 2.4.5 2.4.6 2.4.7 2.5 2.5.1 2.5.2 2.5.2.1 2.5.2.2 2.5.2.3 2.5.2.4 2.5.2.5 2.5.3 2.5.3.1 2.5.3.2 2.5.3.3 2.5.3.4 2.5.3.5 2.5.3.6 2.5.3.7
02'(/ '(6&5,37,21 Network Model Transport systems Nodes, intersections and stops Links Turning relations PuT-lines Zones Connectors Travel Demand Impact Models User Model Operator Model Environmental Impact Model User Model (PrT) Example Network Impedance Function Incremental Assignment Equilibrium Assignment Learning Method Simultaneous Assignment TRIBUT Procedure User Model (PuT) Example network Impedance Function, Indicators of a Connection Connection Indicators Perceived Journey Time Fares Temporal Utility Impedance Distribution models Kirchhoff Model Logit Model Box-Cox Model Lohse Model Comparison of the Distribution Models I Independence of Connections in Timetable-based Assignment Distribution Models with Independence 2-3 2-4 2-6 2-7 2-11 2-14 2-20 2-20 2-23 2-25 2-25 2-27 2-27 2-28 2-30 2-32 2-38 2-42 2-47 2-54 2-62 2-76 2-77 2-79 2-79 2-84 2-84 2-85 2-86 2-87 2-88 2-88 2-89 2-90 2-91 2-93 2-94
ii
TABLE OF CONTENTS
2.5.3.8 2.5.4 2.5.5 2.5.6 2.5.7 2.5.8 2.6 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.6.6 2.6.7 2.7
Comparison of the Distribution Models II Transport system-based Assignment Line-based Assignment Timetable-based assignment 3 Timetable-based assignment 2 Timetable-based assignment 1 Operator model Projection General indicators Transport supply indicators Vehicle requirement indicators Transport demand indicators Cost indicators Revenue indicators Literature
2-95 2-97 2-100 2-108 2-115 2-122 2-126 2-126 2-128 2-129 2-129 2-130 2-131 2-135 2-138
iii
TABLE OF CONTENTS
3.1 3.2 3.3 3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.4.7 3.4.8 3.5 3.6 3.7 3.8 3.8.1 3.8.2 3.9 3.9.1 3.9.2 3.10
)81'$0(17$/6 2) 352*5$0 23(5$7,21 The start-up screen The VISUM interface The VISUM toolbar The VISUM menus FILE menu EDIT menu SELECT menu LISTINGS menu CALCULATE menu GRAPHICS menu EXTRAS menu ? menu VISUM files Version files and graphic parameter files VISUM protocol files VISUM file management Default directories in file management Modifying directories of the file management system VISUM program configuration Default configuration Modifying program configuration VISUM Online Help (VISUM User Manual) 3-2 3-3 3-4 3-7 3-7 3-8 3-10 3-11 3-12 3-13 3-14 3-15 3-16 3-19 3-20 3-22 3-22 3-23 3-25 3-25 3-27 3-29
iv
TABLE OF CONTENTS
4.1
7+( 1(7:25. (',725 Network processing modes INSERT mode SINGLE SELECT mode MULTI SELECT mode 4-4 4-4 4-5 4-7
4.1.1 4.1.2 4.1.3
4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6 4.2.7 4.2.8
Transport systems, Modes and Demand segments Attributes of transport system, mode, demand segment Insert transport system Modify transport system Insert mode Modify mode Insert demand segment Modify demand segment Delete transport system, mode or demand segment
4-9 4-11 4-16 4-18 4-19 4-21 4-22 4-23 4-24
4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.3.5.1 4.3.5.2 4.3.6 4.3.6.1 4.3.6.2 4.3.6.3 4.3.6.4
Nodes Node attributes Insert node Select node Delete node Edit node Modify node position, merge nodes Modify node attributes Edit multiple nodes Modify attribute for multiple nodes Automatic major flow generation AddValue_Nodes data generation Delete active nodes
4-25 4-26 4-31 4-32 4-33 4-34 4-34 4-35 4-40 4-41 4-45 4-46 4-47
4.4 4.4.1 4.4.1.1 4.4.1.2 4.4.2 4.4.3 4.4.4 4.4.5 4.4.5.1
Links Link attributes Link type-specific link attributes Basic link attributes Insert a link Select a link Delete a link Edit a link Modify link attributes
4-48 4-49 4-49 4-51 4-57 4-59 4-59 4-60 4-60

v
TABLE OF CONTENTS
4.4.5.2 4.4.5.3 4.4.5.4 4.4.6 4.4.6.1 4.4.6.2 4.4.6.3 4.4.6.4 4.4.6.5 4.4.6.6
Modify a link course Split a link Edit link label display Edit multiple links Modify attribute for multiple links Generate AddValue_Links from AddValue_TurnRelations Link label display ON/OFF or initialize position Use link attribute values predefined by link type Generate running times of links from line data Delete active links
4-65 4-66 4-68 4-69 4-70 4-72 4-74 4-75 4-76 4-77
4.5 4.5.1 4.5.1.1 4.5.1.2 4.5.2 4.5.3 4.5.4 4.5.5 4.5.5.1 4.5.5.2
Turning relations Turning relation attributes Turning standard Turning relation attributes Insert turning relation Select turning relation Delete turning relation Edit multiple turning relations Modify attribute for multiple turning relations Assigning default values to turning relation attributes
4-78 4-80 4-80 4-81 4-83 4-86 4-86 4-87 4-88 4-90
4.6 4.6.1 4.6.2 4.6.3 4.6.4 4.6.5 4.6.5.1 4.6.5.2 4.6.5.3 4.6.5.4 4.6.6 4.6.6.1 4.6.6.2 4.6.6.3 4.6.6.4
Zones Zone attributes Insert zone Select zone Delete zone Edit zone Modify label position Specify zonal boundary Modify zone attributes Split zone Edit multiple zones Modify attribute for multiple zones Initialize boundaries of multiple zones Aggregate active zones to form one zone Delete active zones
4-91 4-92 4-99 4-101 4-101 4-102 4-102 4-103 4-104 4-106 4-108 4-109 4-111 4-112 4-114
4.7 4.7.1
vi
Connectors Connector attributes

4-115 4-117
TABLE OF CONTENTS
4.7.2 4.7.3 4.7.4 4.7.5 4.7.5.1 4.7.5.2 4.7.6 4.7.6.1 4.7.6.2 4.7.6.3
Insert connector Select connector Delete connector Edit connector Modify connector attributes Proportional distribution of the PrT demand Edit multiple connectors Modify attribute for multiple connectors Delete active connectors Generate connectors
4-119 4-121 4-121 4-122 4-122 4-122 4-123 4-124 4-126 4-126
4.8 4.8.1 4.8.2 4.8.3 4.8.4 4.8.5 4.8.5.1 4.8.5.2 4.8.5.3 4.8.5.4 4.8.6 4.8.6.1 4.8.6.2
Global zones Global zone attributes Insert global zone Select global zone Delete global zone Edit global zone Modify label position Specify boundary of global zone Modify global zone attributes Modify subzones of a global zone Edit multiple global zones Modify attributes for multiple global zones Delete active global zones
4-128 4-129 4-131 4-133 4-133 4-134 4-134 4-134 4-135 4-137 4-138 4-139 4-139
4.9 4.9.1 4.9.1.1 4.9.1.2 4.9.2 4.9.2.1 4.9.2.2 4.9.2.3 4.9.3 4.9.4 4.9.5 4.9.6 4.9.6.1 4.9.6.2 4.9.6.3 4.9.6.4
Lines Vehicle types and operators PuT vehicle types PuT operators Line attributes Attributes of sublines, lines and PuT systems Attributes of the line route Attributes of vehicle trips Insert a subline Select a subline Delete a subline Edit a subline Modify line route Modify line attributes Modify the sequence of served stops Modify line timetables
4-140 4-141 4-141 4-144 4-146 4-146 4-155 4-158 4-159 4-175 4-175 4-176 4-176 4-186 4-187 4-189
vii
TABLE OF CONTENTS
4.9.7 4.9.7.1 4.9.7.2 4.9.7.3 4.9.7.4 4.9.7.5 4.9.8
Edit multiple lines Modify attribute of multiple sublines Assign vehicle type to line services Assign Standard timetable to sublines Delete multiple sublines Aggregate multiple sublines Main lines
4-190 4-191 4-194 4-194 4-195 4-196 4-200
4.10
Areas Area attributes Insert area Select area Delete area Edit area Modify area attributes Modify label position Specify area boundary Edit multiple areas Delete active areas Selection of network objects by area Areas: PuT example
4-201 4-203 4-207 4-207 4-207 4-208 4-208 4-208 4-208 4-209 4-211 4-212 4-213
4.10.1 4.10.2 4.10.3 4.10.4 4.10.5 4.10.5.1 4.10.5.2 4.10.5.3 4.10.6 4.10.7 4.10.8 4.10.9
4.11
Census Points Census point attributes Insert census point Select census point Delete census point Edit census point Modify census point position Modify census point label position Modify census point attributes Edit multiple census points Modify attribute for multiple census points Delete active census points
4-215 4-216 4-218 4-219 4-219 4-220 4-220 4-220 4-221 4-222 4-223 4-224
4.11.1 4.11.2 4.11.3 4.11.4 4.11.5 4.11.5.1 4.11.5.2 4.11.5.3 4.11.6 4.11.6.1 4.11.6.2
4.12
Options for Insert network object
4-225
viii
TABLE OF CONTENTS
5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.2 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.3.7 5.4 5.5
2' 0$75,&(6 O-D matrices Matrix formats Open O-D matrix file Edit matrix Save matrix Patterns of temporal PuT demand distribution Updating O-D matrix using VStromFuzzy Basic principles Preparing data for matrix correction 96WURP)X]]\ operation Modifying parameters and settings Performing matrix correction Opening and saving TStromFuzzy settings Calculation example Projecting PrT route volumes Calibrating a PrT O-D matrix 5-2 5-2 5-3 5-5 5-11 5-13 5-17 5-18 5-25 5-26 5-27 5-31 5-31 5-32 5-34 5-37
ix
TABLE OF CONTENTS
6.1 6.1.1 6.1.2 6.1.3 6.1.3.1 6.1.3.2 6.1.3.3 6.1.3.4 6.1.3.5 6.1.3.6 6.1.3.7 6.1.3.8 6.1.3.9 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6 6.3 6.4
),/7(56 $1' 08/7,6(/(&7 63(&,),&$7,216 Filter Set filters Deactivate or initialize filters Filter types Node filter Link filter Zone and Global zone filter Connector filter Turning relation filter Subline filter Census Point filter Relation filter Time filter Multiselect Selection of network objects by polygon definition Selection of network objects by areas Selection of network objects by individual selection Inverting active/passive network objects Symmetrie beider Streckenrichtungen prfen Initialisieren der Mehrfachauswahl Partial network generator File management 6-3 6-4 6-8 6-9 6-9 6-10 6-12 6-13 6-14 6-15 6-17 6-17 6-19 6-20 6-20 6-21 6-24 6-25 6-26 6-27 6-38 6-32
TABLE OF CONTENTS
7.1 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.2.7 7.2.8 7.3 7.3.1 7.3.2 7.3.3 7.3.4 7.3.5 7.3.6 7.4
$66,*10(176 $1' ,1',&$725 0$75,&(6 Dialog for assignments PrT Assignment procedures Impedance functions Incremental procedure Equilibrium procedure Learning procedure Multi-procedures TRIBUT procedure Indicator matrices PrT PrT assignment analysis PuT Assignment procedures Transport system-based procedure Line-based procedure Timetable-based procedure 3 Timetable-based procedure 2 Timetable-based procedure 1 Indicator matrices PuT Assignment report 7-2 7-6 7-7 7-14 7-16 7-19 7-22 7-23 7-28 7-31 7-33 7-34 7-38 7-48 7-59 7-68 7-70 7-80
8.1 8.2 8.3 8.4 8.5
(19,5210(17$/ ,03$&7 &$/&8/$7,21 General procedure Noise Air pollutants Mobilev- interface IMMIS-Luft- interface 8-2 8-4 8-13 8-21 8-30
xi
TABLE OF CONTENTS
9.1 9.1.1 9.1.2 9.1.2.1 9.1.2.2 9.1.2.3 9.1.2.4 9.1.3 9.1.4 9.1.5 9.1.6 9.1.7 9.1.7.1 9.1.7.2 9.1.7.3 9.1.7.4 9.1.7.5 9.1.8 9.1.8.1 9.1.8.2 9.1.8.3 9.1.8.4 9.1.8.5 9.1.9 9.2 9.2.1 9.2.2 9.2.3 9.2.4 9.2.5
38%/,& 75$163257 $1$/<6(6 /,1( &267,1* Operational indicators Example Tariff model Tariff subzones Tariff zones PuT Ticket types Fare calculation Projection Line Blocking Calculation of performance indicators Calculation of demand indicators Calculation of cost Vehicle type cost Infrastructure cost: stop costs Infrastructure cost: link costs Infrastructure cost: operator costs Total costs Revenue calculation and revenue gearing General procedure Revenue calculation using tariff model Revenue calculation by specifying a fix revenue per pass-trip Revenue calculation by specifying a fix revenue per pass-km Revenue calculation by specifying a total revenue Calculation of cost coverage Analysis of transfer quality Basic approach Setting calculation parameters Defining evaluation classes for Class types File management Application example 9-2 9-4 9-8 9-9 9-12 9-14 9-19 9-27 9-29 9-38 9-39 9-42 9-43 9-45 9-51 9-56 9-60 9-61 9-62 9-64 9-68 9-70 9-71 9-74 9-75 9-76 9-77 9-79 9-81 9-82
xii
TABLE OF CONTENTS
9.3 9.3.1 9.3.2 9.3.3 9.3.4 9.3.5 9.3.6 9.3.7 9.3.8 9.3.9
Passenger survey Add-on Basic data of a passenger trip General approach Loading survey data Plauzibilization of survey data records Generating zones Direct assigment of survey data records Calculating indicators Starting passenger add-on module procedures Saving version and passenger parameters
9-87 9-88 9-91 9-92 9-93 9-107 9-109 9-110 9-111 9-111
10.1 10.1.1 10.1.2 10.1.3 10.1.4 10.1.5 10.1.6 10.2 10.2.1 10.2.2 10.2.3 10.2.3.1 10.2.3.2 10.2.3.3 10.2.3.4 10.2.3.5 10.2.4 10.2.5 10.2.6
/,67,1*6 $1' 67$7,67,&6 List handling Select columns Defining list layouts Saving list layout Printing lists Reading and saving attribute files Attributes in Clipboard List types Zones Gloabl zones Nodes Nodes Basic display Nodes Display of sublines Nodes Timetable at stop Nodes Timetable Arrival/Departure Nodes List of transfers Links Turning relations Connectors 10-2 10-4 10-6 10-9 10-10 10-11 10-16 10-17 10-18 10-19 10-20 10-21 10-22 10-23 10-24 10-25 10-26 10-28 10-29
xiii
TABLE OF CONTENTS
10.2.7 10.2.7.1 10.2.7.2 10.2.7.3 10.2.7.4 10.2.7.5 10.2.8 10.2.9 10.2.10 10.2.11 10.2.12 10.2.13 10.2.14 10.2.15 10.2.16 10.2.17 10.2.18 10.2.19 10.2.19.1 10.2.19.2 10.2.19.3 10.2.19.4 10.2.20
Sublines Sublines Basic display Sublines Line route Sublines Timetable at stop Sublines Timetable booklet Sublines List of transfers Lines Main Lines PuT Transport systems PuT Operators Link types Areas Link sequences Census points PuT Relations Routes Route search Statistics Statistics Network information Statistics Link types Statistics Assignment statistics PuT Statistics Line Blocks Passenger survey list
10-32 10-33 10-34 10-35 10-36 10-37 10-38 10-40 10-40 10-43 10-44 10-44 10-46 10-46 10-47 10-53 10-55 10-59 10-60 10-61 10-62 10-64 10-65
*5$3+,&$/ $1$/<6(6 11.1 11.2 11.3 11.4 11.5 11.6 11.7 Difference network and difference display Flow bundles Isochrones Search for routes Node flows O-D flow PuT Vehicle animation 11-2 11-10 11-19 11-27 11-33 11-38 11-42
xiv
TABLE OF CONTENTS
*5$3+,&6 3$5$0(7(56 12.1 12.2 12.3 12.3.1 12.3.2 12.3.3 12.3.4 12.4 12.5 12.5.1 12.5.2 12.6 12.7 12.7.1 12.7.2 12.7.3 12.7.4 12.7.5 12.8 12.9 12.10 12.11 12.12 12.13 Basics Layers Nodes and stops Parameters for nodes and stops Chart parameters for nodes and stops Node flow parameters for PrT nodes Catchment area parameters for PuT stops Turning relations Zones, global zones, areas Parameters for zones, global zones and areas Chart parameters for zones and global zones Connectors Links Basic link network Link bars Difference display Layers Labels PuT Lines Census points Flow bundles, isochrones, route search, O-D flows Printing page Fonts Reading/saving graphic parameters 12-2 12-4 12-6 12-7 12-9 12-12 12-14 12-16 12-17 12-18 12-19 12-20 12-22 12-23 12-24 12-33 12-34 12-36 12-38 12-41 12-44 12-45 12-46 12-48
xv
TABLE OF CONTENTS
13.1
1(7:25.,1'(3(1'(17 *5$3+,& 2%-(&76 Clips Insert a clip Select a clip Delete a clip Edit a clip Clip co-ordinates Adapt clip section as current window on screen 13-2 13-2 13-4 13-4 13-4 13-4 13-5 13-6 13-7 13-8 13-8 13-8 13-9 13-9 13-10 13-11 13-12 13-12 13-14 13-14 13-15 13-16 13-17 13-17 13-19 13-20 13-20 13-21 13-21 13-21 13-22 13-22 13-23 13-30 13-30 13-32 13-32 13-32
13.1.1 13.1.2 13.1.3 13.1.4 13.1.4.1 13.1.4.2 13.2
Texts Insert a text Select a text Delete a text Edit a text Processing all texts Delete all texts Enlarge or reduce size of all texts Read and save texts
13.2.1 13.2.2 13.2.3 13.2.4 13.2.5 13.2.5.1 13.2.5.2 13.2.6 13.3 13.3.1 13.3.2 13.3.3 13.3.4 13.3.5 13.4 13.4.1 13.4.2 13.4.3 13.4.4 13.4.5 13.4.6 13.4.7 13.4.8 13.4.9 13.4.10 13.5 13.5.1 13.5.2 13.5.3 13.5.4
xvi
Backgrounds Insert a background Select a background Delete a background Edit a background Saving background files Objects Graphic import interface Insert object from file Insert object from clipboard Select an object Delete an object Copy an object Modify object (position/size) Modify color assignment of an object Delete all objects Symbol library Polygons Create a polygon Select a polygon Delete a polygon Copy a polygon
TABLE OF CONTENTS
13.5.5 13.6 13.6.1 13.6.2 13.6.3
Delete all polygons Legend Insert the legend Delete the legend Edit the legend
13-33 13-34 13-34 13-36 13-36
*5$3+,&6 35,17,1* ,17(5)$&(6 14.1 14.2 14.2.1 14.2.2 14.3 14.4 14.5 14.6 Define print area Printer settings Windows printer drivers VISUM printer drivers Print page parameters Preview before Printing Start print output Graphics interfaces PostScript-PDF export PostScript graphic file PDF graphic file HPGL graphic file DXF interface Exporting graphics Importing graphics HGRD background files Output to background file Editing background text files Error messages during background conversion General graphics import interface 14-2 14-6 14-6 14-8 14-12 14-15 14-17 14-19 14-20 14-21 14-24 14-24 14-26 14-26 14-28 14-32 14-32 14-34 14-39 14-41
14.6.1 14.6.1.1 14.6.1.2 14.6.2 14.6.3 14.6.3.1 14.6.3.2 14.6.4 14.6.4.1 14.6.4.2 14.6.4.3 14.6.5
xvii
TABLE OF CONTENTS
15.1
'$7$ )250$76 '$7$ ,03257 $1' (;3257 Network file Structure of a network file General network parameters Transport systems Modes Demand segment Nodes Zones Global Zones Link types Links Turning relations Turning standards Connectors Sublines Main lines PuT vehicle types and operators Tariff zones Ticket types Areas Census Points Example of a VISUM network file Verifying network consistency 15-2 15-2 15-6 15-9 15-11 15-12 15-13 15-14 15-16 15-18 15-20 15-23 15-24 15-26 15-28 15-32 15-32 15-35 15-38 15-42 15-44 15-46 15-52 15-57 15-57 15-57 15-58 15-60 15-61 15-63 15-65 15-65 15-68 15-70 15-70 15-72 15-72 15-73 15-74
15.1.1 15.1.2 15.1.3 15.1.4 15.1.5 15.1.6 15.1.7 15.1.8 15.1.9 15.1.10 15.1.11 15.1.12 15.1.13 15.1.14 15.1.15 15.1.16 15.1.17 15.1.18 15.1.19 15.1.20 15.1.21 15.1.22 15.2
Opening and saving network file Reading network file Opening entire network file Read network file additionally Reading a network with incomplete line routes Timetable update Saving network file
15.2.1 15.2.1.1 15.2.1.2 15.2.1.3 15.2.1.4 15.2.2 15.3
Network file interfaces Interface to previous versions of VISUM PrT Interface previous versions of VISUM PuT VISSIM Export interface Access database interface for network files Interface for attribute files Data transfer via attribute file Data transfer via clipboard Interface to timetable and staff scheduling systems
15.3.1 15.3.2 15.3.3 15.3.4 15.3.5 15.3.5.1 15.3.5.2 15.3.6
xviii
TABLE OF CONTENTS
15.4
Matrix files Matrix file formats O-D matrix Patterns of temporal PuT demand distribution Indicator matrices PuT-indicator matrices PrT-indicator matrices
15-77 15-77 15-81 15-82 15-83 15-83 15-85 15-86 15-86 15-87 15-87 15-88 15-88 15-89 15-92 15-95 15-96
15.4.1 15.4.2 15.4.3 15.4.4 15.4.4.1 15.4.4.2 15.5 15.5.1 15.5.2 15.5.3 15.5.4 15.5.5 15.5.6 15.5.7 15.6 15.7
AddValue files Nodes Links Turning relations Zones/Global zones Sublines Saving AddValue data to file Reading AddValue data from file Text files Background files
16.1 16.2 16.3
0$&52 &200$1'6 List of macro commands Creating a macro file Execution of macros 16-2 16-7 16-9
xix
TABLE OF CONTENTS
xx
INTRODUCTION
,1752'8&7,21
VISUM is a program for computer-aided transport planning which serves to analyse and plan a transportation system. A transportation system includes private and public transport supply (PrT and PuT) and travel demand. VISUM supports planners to develop measures and determines the impact of these measures. This manual is intended to support VISUM users in their work with the program. However, it is not considered to be a substitute for a training course. 7KH SODQQLQJ SURFHVV Planning is a process which starts with an analysis of the state of the art which investigates current transportation system. In this way, possible defficiencies of the transportation systems current state can be identified. The analysis of the current state is followed by a design process, which consists of four steps: Development of a solution, Determination of impacts, Evaluation of impacts, Analysis of deficiencies.
This process continues until a satisfying solution is developed which meets the demand of the planning objectives.
1-1
INTRODUCTION
Manual
$QDO\VLV RI FXUUHQW VWDWH

Supply quality of the current PrT road network PuT line network
'HVLJQ SURFHVV
Development of a solution for private transport public transport
Determining the impact of the current state Indicators of service quality Operational indicators Environmental indicators
Determining the impacts of the solution Service indicators Operational indicators Environmental indicators
Evaluating the impacts of the current state
Evaluating the impact of a solution
Deduction of deficiencies
Analysis of deficiencies
&RPSXWHUDLGHG WUDQVSRUW SODQQLQJ In the process of carrying out computer-aided transport planning with VISUM, status analysis and design process work is shared between the user and the computer. While the planner successively improves his design (suggested solution) based on the current state, the computer determines the impact of the current solution. In computer-aided transport planning, the transportation system is represented in a transport model which, like all models, is an abstraction of the real world. The aim of the modelling process is model-based preparation for decisions taken in the real world. To determine impacts, VISUM supplies indicator values for transport supply indicators which then serve to evaluate a solution. Indicators can be divided into User indicators which describe connection quality between traffic zones, Operator indicators which quantify operational and financial requirements of implementing a given public transport supply, Environmental indicators which quantify the impact of motorised private transport on the environment.
1-2
Manual
INTRODUCTION
$LPV RI 9,680 GHYHORSPHQW Like the transport planning process, the development of the VISUM program is oriented towards objectives. The development goals for VISUM arise from current developments in transport planning (e.g. telematics, PuT regionalisation, line revenue calculations, integrated transport planning), from the requirements of users and from conditions determined by current computer generations and operating systems. Limiting constraints during development are the available development capacities which PTV AG has at its disposal. This conflict between aims and requirements on the one hand, and available development capacities on the other, make requirement prioritisation necessary. The current problems of users are always given priority. Through direct contact to developers, we always try to correct possible errors and to provide support for clients with service contracts should they experience difficulties using the program or with modelling. Requirements for further features are stored in a database at PTV AG and are regularly prioritised. Any specific requirements which you as a user may have with regard to development can be addressed at annual seminars or sent to us in writing.
1-3
INTRODUCTION
Manual
0DQXDO
6WUXFWXUH RI WKH PDQXDO

In addition to this introductory chapter, the manual is structured into two basic parts: The first part which corresponds to chapter 2 explains the basic theory of transport modelling. This chapter describes the structure of the network model and introduces the procedures used to determine the impacts of a given transport supply. To make the procedures more easy to understand, their mode of operation is demonstrated with a small and easily comprehensible example of transport supply. The network data used for this example are supplied together with the VISUM program, so that the calculations and results introduced in chapter 2 can be directly verified with VISUM. The second part describes the functionality of the program, which is introduced in chapters 3 to 16 (according to topics): 2YHUYLHZ: Chapter 3 provides a general overview of VISUMs functionality. ,QSXW GDWD: Chapters 4 and 5 describe the input parameters of transport supply and travel demand which are used for the determination of impacts. Chapter 4 introduces the network objects which constitute a network model. Chapter 5 is concerned with O-D matrices which contain detailed lists covering travel demand. Chapter 6 explains functions for filtering network objects which are helpful for creating a network model and useful for the impact analysis. ,PSDFW PRGHOV Chapter 7 introduces functions which are used to assign travel demand to transport supply and for determining available transport quality indicators. Chapter 8 explains special impact models for PrT which are used to estimate the impacts of motorised private transport on the environment. The functions for determining operational impacts of PuT are introduced in chapter 9. These functions can be used to calculate the necessary operational indicators for line revenue calculations. 5HVXOWV: Chapters 10 - 14 introduce possibilities as to how the results of impact models can be displayed and analysed in lists or in graphic representations. 'DWD IRUPDWV Chapters 15 and 16 describe the formats of VISUM files and macros.
1-4
Manual
INTRODUCTION
)RUPDW FRQYHQWLRQV

The manual uses the following format conventions to describe buttons, menus, functions, key assignments and file specifications: )RUPDW H[DPSOH 'HVLJQDWRUV DQG UHIHUHQFHV In the WRRO EDU pictograms are used to designate buttons for the most important functions of network editing (including filters for network elements) and graphic screen display. EDIT-INSERT 0HQXV are written in SMALL CAPITALS; the command to be activated in the pull-down menu follows a hyphen. Generally, menus can be activated with left mouse click on the respective menu name or via shortcut (see below). In the manual, buttons which can be activated in a diaog box are written in LWDOLFV .H\V are marked by pointed brackets e.g. "Cancel" with <Esc>. The menu bar is activated by pressing <Alt>. Underlined letters in menus are used as VKRUWFXWV, i.e. pressing shortcuts activates the respective menu or function, e.g.: ..exe\file.ext <Alt-E>,<S> (EDIT menu - 6LQJOH 6HOHFW), <Alt>+<X>+<F>+<Z> (EXTRAS-FILTERS-=RQHV).
([HFXWH <Esc> <Alt-E>, <S> or <Alt>+<E>+<S>
)LOH DQG SDWKQDPH with ..\Directory\Name.Ext.
1-5
INTRODUCTION
VISUM Capabilities
9,680 &DSDELOLWLHV
VISUM determines the impacts of existing or planned transport supply which can encompass both the PrT-transport network and the PuT-line network (including timetables). The transport planner is supported in developing a supply design, in analysing the supply, and in evaluating network variants.
9,680 GDWDEDVH

A transport model in VISUM consists of transport supply data and travel demand data. Transport supply data are represented in a network model. The integrated network model distinguishes between "PrT" and "PuT" mode. By combining different means of transportation and modes, the planner can define different transport systems. PrT-transport systems depend on permissible speed and link capacity. PuT-transport systems are bound to a timetable. Basically the network model includes the following network objects which can be modified interactively: Nodes: PrT intersections or PuT-stops. Zones: origin and destination of travel demand. Links: speeds and capacities for PrT, travel times for PuT. Turning relations: turning penalties for PrT, points and turning places for PuT. Lines: line name, line variant, line route and timetable. operational information on PuT-vehicles and operators to be managed in the network model, census points on links for evaluation of traffic counts (by direction), and user-defined areas (representing e.g. a district or a county), for which PrT and PuT indicators can be determined precisely based on the polygon that describes the areas boundaries.
Furthermore the network may contain,
1-6
VISUM Capabilities
INTRODUCTION
,PSDFW PRGHOV

VISUM includes different models which are used to determine the impacts of given transport supply: Different assignment procedures make it possible to assign current or anticipated travel demand to existing or planned transport supply. The connection quality of private or public transport in the network is described by indicators which can be displayed in the form of indicator matrices (impedance matrices). The environmental model makes it possible to determine noise and/or pollution emissions of motorized private transport for traffic volumes in the existing or planned transport network. An operator model determines the operational and financial requirements of PuT supply. The number of required vehicles is computed by a line-blocking calculation procedure. To estimate fare revenue in the context of a line costing calculation, a revenue model is available which estimates revenue from travel demand and ticket prices, and then distributes the revenue across the lines used by the passenger.
7UDQVSRUW VXSSO\ DQDO\VLV

Transport supplies can be evaluated and displayed according to different criteria, e.g. as Volume differences of two network variants Flow bundles which filter routes that use network objects selected by the user (nodes, links, zones), Evaluation of network volumes according to traffic types (outbound, inbound, external or internal traffic), Node flow diagrams which display PrT turning flows at intersections, Isochrones for classifying the reachability of network objects and for comparing PuT journey times and PrT travel times. Graphical route search which visualises PrT-routes and PuT-connections between network nodes.
1-7
INTRODUCTION
VISUM Capabilities

)LHOGV RI DSSOLFDWLRQ IRU SODQQLQJ WDVNV LQ 3XEOLF 7UDQVSRUW
Planning and analysis of line networks. Design and analysis of timetables. Estimation of driver and vehicle requirements. Cost-benefit analyses. Display (graphic/tabular) of PuT-specific characteristics (sold tickets, number of passengers boarding/alighting, number of students per zone or stop). Evaluation and display of passenger numbers and other indicators per transport system, link, stop, line, and operator. Creation of presentation graphics to illustrate different planning variants or differences between planning variants and the current state. Calculation and prognosis of area and operator-specific expenditure and revenue values. Operational indicators for line costing calculation. Generation of partial networks with corresponding partial O-D matrices.

)LHOGV RI DSSOLFDWLRQ IRU SODQQLQJ WDVNV LQ 3ULYDWH 7UDQVSRUW
Simulation of transport planning measures or construction measures to forecast resulting traffic volumes and their impacts. Prognosis of the impacts of road tolls. Separate analysis of different PrT-transport systems (car, HGV, bicycle). Comparison of O-D matrices with current counted data. Determination of noise and/or pollution emissions. Basic data for calculating immissions with IMMIS-Luft and Mobilev. Generation of partial networks with corresponding partial O-D matrices.
1-8
Technical information
INTRODUCTION
7HFKQLFDO LQIRUPDWLRQ
$YDLODEOH 9,680 YHUVLRQV 6L]H DQG $GG2QV

9HUVLRQ VL]HV VISUM is delivered in different version sizes which are determined by the number of network objects in the network: 6L]H B D E F G H I =RQHV 200 400 600 1000 3000 5000 10000 1RGHV 1000 2000 4000 8000 25000 50000 100000 /LQNV 2500 5000 12000 20000 50000 100000 200000 6XEOLQHV 500 1000 2500 5000 10000 20000 50000 2SHUDWRUV 10 20 30 200 200 300 300 9HK W\SHV 20 50 80 200 200 300 300
1-9
INTRODUCTION
0RGXOHV VISUM is available with the following modules 3U7: Module for PrT-assignments and indicator calculations. 3X7: Module for PuT-assignments and indicator calculations. 75,%87: French procedure (private transport assignment) for modeling tolls and road pricing schemes. 3X7 SDVVHQJHU VXUYH\V: Module for analysis of passenger interviews and counts. 3X7 /LQH UHYHQXH FDOFXODWLRQ / 5RVWHU FDOFXODWLRQ: module for line costing calculation and for computing vehicle requirements for PuT. &DOL: Module for calibrating PrT-O-D matrices using counted volumes. 96WURP)X]]\: Module for o/d matrix update and correction based on counted data (private and public transport). (:6: German analysis procedure regarding efficiency of road construction (based on EWS-97, Empfehlungen fr Wirtschaftlichkeitsuntersuchungen von Straenbauvorhaben, 1997). 3DUWLDO QHWZRUN JHQHUDWRU: Module for generating a partial network with corresponding partial matrices from the total network. &HQVXV SRLQWV: Module for input and management of counted data and census points on links. %DFNJURXQG: Module for graphical network display with network-independent graphic objects (DXF, BMP, TIF, SGI, JPG etc.). (QYLURQPHQW: Module for noise and pollution emission calculations of motorised private transport. 0RELOHY-LQWHUIDFH: interface to Mobilev, program for calculating pollution emissions of motor vehicles (Supplier: FiGE GmbH, Herzogenrath; Right of use: Federal Office for the Environment, Berlin); part of the (QYLURQPHQW module. ,00,6/8)7LQWHUIDFH: interface to IMMIS-LUFT, program for calculating pollution immissions of motor vehicles (Supplier: IVU, Berlin/Freiburg); separate module.
1-10
INTRODUCTION
+DUGZDUH DQG VRIWZDUH UHTXLUHPHQWV

2SHUDWLQJ V\VWHPV VISUM runs under Windows 95, Windows 98, Windows NT and Windows 2000.
1HWZRUNV Compatible networks are: Novell Netware 3.11,3.12, 4.x. Microsoft networks (Windows NT Client and Server from 3.51).
+DUGZDUH DQG RSHUDWLQJ V\VWHP UHFRPPHQGDWLRQV Pentium III . Minimum working memory of 64 MB, for optimal performance use 128 MB; for very large networks use > 128 MB. For smooth operation and optimal multitasking enough RAM reserves should be available. For extraordinary RAM peaks the virtual memory (swap file) can be extended. 17" or 21" monitor with a resolution of 1280 x 1024.
'RQJOH
To operate VISUM, you must install a dongle. Two types of dongle can be distinguished: 6WDQGDORQH GRQJOH for local installation on a stand-alone PC, 1HWZRUN GRQJOH for installation on a server. 6LQJOH GRQJOH only for use of VISUM or &ROOHFWLYH GRQJOH for use of several PTV software products (VISUM, VISEM).
In addition to this, both dongle types are distinguished by
1-11
INTRODUCTION
Installation of VISUM
,QVWDOODWLRQ RI 9,680
VISUM is usually supplied on CD-ROM along with demo and example files, and online documentation.
G
8
Close all open applications under Windows to avoid possible loss of data. ,QVWDOODWLRQ SURFHGXUH Insert CD into respective CD-ROM drive: under Windows 3.1x, Windows NT to 3.51: use file manager to execute setup.exe on CD. under Windows 95, Windows NT from 4.0 and Windows 2000: installation is started automatically.
Follow installation program instructions. Fastest installation possibility: confirm all suggested entries with mouse click on <Next>. You can return to all previous screens by clicking <Back>. During subsequent installations (complete installation or individual components) take care that the existing path is used.
6HOHFWLQJ WKH WDUJHW GLUHFWRU\ Instead of the suggested target directory you can specify your own directory: select existing directory or enter new directory name; the new directory is then created automatically.
1-12
INTRODUCTION
9,680 6HWXS
6HOHFW 6HWXS W\SH 7\SLFDO: installs all components (Standard). &RPSDFW: installs only the Program Files component (Minimum). &XVWRP: installs only the component(s) checked by the user.
3URJUDP FRPSRQHQWV WR EH VHOHFWHG E\ WKH XVHU
1-13
INTRODUCTION
3URJUDP )LOHV: VISUM program files. ([DPSOH )LOHV: Example data files. +HOS )LOHV: Online Help files. 'HPR )LOHV: Demo macro files and Demo data files. ';)B%DFNJURXQG: Data files for the Background/DXF Add-on.
6HOHFW )ROGHU Accept the suggested Program Group ()ROGHU) or select an existing folder or define a new folder.
Installation process is executed. Start dongle instructions. installation and follow installation program
Several VISUM installations can be saved to one PC or network. Therefore different paths need to be specified. Deinstall VISUM unter 6HWWLQJV &RQWURO 3DQHO $GG5HPRYH 3URJUDPV.
1-14
INTRODUCTION
After successful installation, several buttons will appear in the specified folder which can be used to start the following applications. Start the Demo Macro session to get an overview of the complex VISUM functionality. 9,680 'HPR *HQHUDO The Macro includes Example data for PrT and PuT. Start the Public Transport Demo Macro. 9,680 'HPR 3X7 Start the Private Transport Demo Macro. 9,680 'HPR 3U7 Starts VISUM with an example network for training purposes in order to develop a basic understanding of how to use VISUM.
9,680 ([DPSOH $SSOLFDWLRQ
Start VISUM program session. 9,680 The following sub-directories are generated in the ..\VISUM750 directory: VISUM750\EXE VISUM750\DEMO VISUM750\Example VISUM750\DXF VISUM750\Hgrd Program files, Default parameter files, Path files. All files required for running the Demo Macro (demo.mac). Example network file and related parameter files. DXF interface. Background data files.
1-15
INTRODUCTION
Problems during program operation
3UREOHPV GXULQJ SURJUDP RSHUDWLRQ
The interrelationships in the transport system are complex. For this reason, a program which models such complex interrelationships demands a great deal from users and developers. During the construction and the use of a transport model, different sources of error might arise: 1. Errors resulting from wrong program operation (e.g. active filter is not noticed by user, a matrix file is assigned to the wrong transport system during loading), 2. Errors resulting from inadequate modelling of transport supply (e.g. missing links or connectors, 60-second rhythm for PuT-line instead of 60-min rhythm), 3. Errors resulting from choosing an inapplicable procedure or inapplicable procedure parameters (e.g. assignment procedure and parameters), 4. Program errors resulting in program crashes or incorrect calculation results. Errors 1 to 3 can be reduced by careful processing of data and through gaining sufficient knowledge about procedures. The manual and special VISUM training courses fulfil this purpose. In addition to this, clients with a service contract can directly turn to PTV AG to have their questions answered. Please also inform PTV AG about errors that result in a program crash or in incorrect calculation results: Fax ++49 721 - 9651-299, Fon ++49 721 - 9651-313 Mailto KRWOLQHYLVXP#SWYGH
If errors can be reproduced, we will try to fix the problem immediately. The following details are required for quick and efficient service: VISUM version number (e.g. 6.50) Operating system (e.g. Windows 95) Exact description of error (e.g. read version, delete link 999, start incremental assignment....) Person to contact for further questions.
We might ask you to grant us access to the network or version file which caused the problem.
1-16
MODEL DESCRIPTION
02'(/ '(6&5,37,21
VISUM is a macroscopic transportation model which integrates private transport (PrT) and public transport (PuT) in one model. Together with VISEM, a program for demand calculation, VISUM consists of a demand model, a network model and impact models (,OOXVWUDWLRQ : The GHPDQG PRGHO contains the travel demand data. The program VISEM estimates and forecasts mode-specific origin-destination matrices for behaviorally homogeneous person groups. The QHWZRUN PRGHO describes the relevant supply data of a transport system. It consists of traffic zones, nodes and public transport stops, links and public transport lines with their timetable. VISUM provides advanced, user-friendly methods to enter and to modify network data. The LPSDFW PRGHO takes its input data from the demand model and the network model. VISUM provides different impact models to analyse and evaluate the comprehensive transport system. A user model simulates the travel behaviour of public transport passengers and car drivers. It calculates traffic volumes and service indicators, e.g. journey time, number of transfers or service frequency. An operator model determines operational indicators of a public transport service, like vehicle kilometres, number of vehicles or operating costs. In combination with the demand data it allows to estimate line revenues. An environmental impact model offers several methods to assess the impacts of motorised transport on the environment. VISUM displays the calculated results in graphic and tabular form and allows graphical analysis of results. In this way, for example, flow bundles, isochrones, and node flows can be displayed and analysed. Indicators such as journey time, number of transfers, service frequency, etc. are computed as indicator matrices.
2-1
MODEL DESCRIPTION
Network Model
7UDQVSRUWDWLRQ 0RGHO
'HPDQG0RGHO 1HWZRUN0RGHO
Contains demand GDWD: Origin, destination, number of trips temporal distribution of travel demand.
Contains supply GDWD: Transport systems Traffic zones Nodes/stops Links PuT-lines.
,PSDFWPRGHO
contains PHWKRGV to determine impacts: assignment, calculation of service indicators User model: number of vehicles, line costing, revenues Operator model: Environmental model: pollution and noise emissions.
5HVXOWV
Listings and statistics (calculated attributes of network objects and routes) Indicator matrices (journey time, service frequency, ...) Graphical analysis (flow bundles, isochrones, ...) Plots
,OOXVWUDWLRQ
VISUM network model and impact model
A transportation model, like all models, represents an abstraction of the real world. The objective of the modelling process is model-based preparation of decisions taken in the real world.
2-2
Network Model
MODEL DESCRIPTION
1HWZRUN 0RGHO
A QHWZRUN PRGHO representing the transport system must describe the spatial and temporal structure of the transport supply. For this reason, the network model consists of several network objects which contain relevant data about the link network, the PuT lines and traffic zones: =RQHV are objects which describe areas with a particular land use and their location within the network (e.g. residential areas, commercial areas, shopping centres, schools). They are origin and destination of trips within the transport network. Zones and the transport network are connected through connectors. 1RGHV are objects which define the position of stops and intersections in the network. Links start and end at nodes. /LQNV connect nodes and thus describe the rail and road infrastructure. A link has a particular direction, so that the opposite direction of a link represents a separate network object. 7XUQLQJ UHODWLRQV indicate, which turning movements are permitted at a node. &RQQHFWRUV connect zones to the link network. 3X7OLQHV which are listed with a name in a timetable usually go into both directions. A line can consist of several line variants, so-called sublines, which, for example, have a different line route or running times between stops. Every subline is described by a line route and a timetable. $UHDV are user-defined polygons which may describe e.g. a district or a county. They serve for precise calculation of private and publich transport indicators with regard to the specified boundaries.
The integrated network model distinguishes between the private transport and the public transport type. The combination of type and means of transport (i.e. vehicles) allows the planner to define several transport systems. The actual speed of vehicles of a private transport system is influenced by the capacity of links whereas public transport vehicles operate according to their timetable.
2-3
MODEL DESCRIPTION
Network Model
Every network object is described by its attributes. One must distinguish between: Input attributes, e.g. stop numbers and calculated attributes, e.g. the number of people embarking at a stop.
7UDQVSRUW V\VWHPV

The transport supply consists of several transport systems. A transport system is defined by a type of transport: Private (PrT) or Public (PuT) transport or PuTWalk and a means of transport, e.g. car, tram, bike.
Basic characteristics of transport types are: 3ULYDWH WUDQVSRUW Travel times of a private transport system depend on the max. speed of the means of transport, e.g. 100 km/h for trucks, the speed permitted on the link used, e.g. 80 km/h, the capacity of the link used.
3XEOLF WUDQVSRUW Running times of vehicles of a public transport system and the dwell times at stops are determined by the timetable. 3X7:DON This type serves to model walking transfer links between stops; This type may be specified for one transport system only in a network model.
,QSXW DWWULEXWHV A transport system is described by the following input attributes: Code of transport system (1 character, A..Z or 0..9) Name of transport system, e.g. car, HGV or bus Type of the transport system (PrT, PuT or PuTWalk) max. permitted speed, e.g. 100 km/h for bus Car units to describe the impact of one PrT-vehicle on the capacity.
The transport supply, which is modelled by transport systems of the types listed aboove, is linked with the transport demand by modes and demand segments (see figure below).
2-4
Network Model
MODEL DESCRIPTION
Priv.TSys1 (e.g. HGV)
Priv.TSys2 (e.g. Car)
Publ. TSys1 (e.g. Bus)
Publ. TSys2 (e.g. Tram)
7UDQVSRUW V\VWHPV
HGV
Car
Park&Ride (Car, Bus, Tram)
Publ. Transport (Bus+Tram)
0RGHV
HGV
Carprivate
Carbusiness
P&R
Publ. Transp. Students
Publ. Transp. Adults
'HPDQG VHJPHQWV 'HPDQG PDWULFHV
Matrix
Matrix
Matrix
Matrix
Matrix
Matrix
,OOXVWUDWLRQ
Relationship between transport systems, modes, demand segments, and demand matrices.
0RGHV A mode connects one or several transport systems. A mode can include either one private transport system or several public transport systems. In future also the intermodal combination of private and public transport systems to form an intermodal mode will be possible. This way it is possible to model that e.g. long-distance passengers (Mode PuT-Long) may use all public transport systems (Intercity, Regional train,Bus, etc.) whereas e.g. commuters (Mode PuT-Local) may use only particular transport systems (Regional train, Bus). 'HPDQG VHJPHQWV A demand segment belongs to exactly one mode. This way a demand segment is the link between transport supply and transport demand. As several demand segments can be defined for each mode, different types of demand can be combined in the transport model. Demand segments can be used for differentiation among: Population groups: Employed-PrT (car drivers), Commuters, Students-PuT, etc. Ticket types: Single trip ticket, Monthly Pass, etc. Vehicle types: Car-Diesel, Car-Petrol, etc. Trip purposes: to work, shopping, home etc. For each demand segment a demand matrix has to be specified. Usually PrT demand matrices contain the demand in car units, whereas passenger units are used for public transport demand matrices. For calculation of O-D trips (PrT) from car units the occupancy rate can be specified for each demand segment.
2-5
MODEL DESCRIPTION
Network Model
1RGHV LQWHUVHFWLRQV DQG VWRSV

Nodes determine the locations of PuT-stops and intersections. They are starting and terminating elements of links. A special stop identifier determines if PuT lines can stop at a particular node and if passengers may embark (=board) and disembark (=alight). In addition to this, a major flow can be specified for every node specifying the direction of the flow with the right of way. The major flow which has the right of way can be determined automatically by VISUM from the ranks of the intersecting links. ,QSXW DWWULEXWHV A node object is defined by the following input attributes: Unique node number Node code (8 characters) Node name (20 characters) Node type (00-99) which can be used to categorise nodes (e.g. nodes with traffic lights, nodes with OHIW JRHV EHIRUH ULJKW rules) X-co-ordinate and Y-co-ordinate Stop identifier which specifies if the node is a PuT-stop max. 3 cost parameters for PuT stops (depreciation, maintenance, usage) Major flow link numbers.
2-6
Network Model
MODEL DESCRIPTION
/LQNV
Links describe roads or rail tracks of the transport network. They connect nodes, that is, intersections of private transport or PuT-stops. A link is represented as a directed element and is described by the FromNode-number and ToNode-number. Both directions of a link are independent network objects but sharing the same link number. For every link, the permissible transport systems of PrT and PuT mode must be specified which are allowed to use the link. ,QSXW DWWULEXWHV A link object is defined by the following input attributes: Unique number of link FromNode-number of link ToNode-number of link Link type Link length List of permissible transport systems PrT capacity Permissible PrT-speed v0-PrT (free flow speed) Running times for every PuT-transport system Road tolls for every PrT-transport system Up to three cost values for calculating PuT-link costs (Investments, maintenance, usage fees).
/LQN W\SHV The 00 to 99 link types serve as network classifiers and make it possible to assign type-specific standard values for Permissible transport systems PrT-capacity free flow PrT-speed v0-PrT Permissible maximum speed, vMax-TSys, of every PrT-transport system PuT-running times t-PuT, which result from link lengths and transport systemspecific speed.
2-7
MODEL DESCRIPTION
Network Model
3HUPLVVLEOH WUDQVSRUW V\VWHPV The permissible transport systems describe the layout of a link. A link, for example, can be: A simple road which can be used by PrT-vehicles and street-bound PuT A rail track which can only be used by trains (trains, subways) A road with tramlines A one-way road which can only be traversed in one direction A transfer walking link between PuT-stops.
The number of lanes of a link is not specifically specified as an attribute, but rather is described by the capacity. A link always exists for both directions. In order to define a one-way road, the transport systems of the opposite direction are blocked. Links which are permissible to 3U7WUDQVSRUW V\VWHPV, are taken into account during SULYDWH WUDQVSRUW assignment. Links which are permissible to 3X7WUDQVSRUW V\VWHPV are taken into account during the FRQVWUXFWLRQ RI 3X7OLQH URXWHV. PuT-assignments (line-based, timetable-based) are not based on link data, but on PuT-line timetables. To model passenger transfers between certain public transport stops a transfer link may be introduced to connect these stops. This link is part of a special public transport system "PuTWalk".
x Car x HGV x Bus x Tram PuT-Walk x Car x HGV x Bus x Tram PuT-Walk
Road with tram lines ,OOXVWUDWLRQ
x Car x HGV x Bus Tram PuT-Walk Car HGV Bus Tram PuT-Walk
One-way road without tram lines
Car HGV Bus Tram x PuT-Walk Car HGV Bus Tram x PuT-Walk
Transfer walking link
Examples for defining transport systems of a link.
2-8
Network Model
MODEL DESCRIPTION
3U7FDSDFLW\ 3U7VSHHG DQG 3U7WUDYHO WLPH When there is free traffic flow in an unloaded network, the travel time, t0 of a link can be determined from the link length and the free flow speed v0: Input: Input: Result: length L [m], free flow speed, v0 [km/h] free flow travel time for t0 [s] = L 3,6 / v0
The free flow speed v0-TSys of vehicles of a particular transport system can be lower than speed the free flow speed v0, of a link, because special speed limits might apply to these vehicles or because the vehicles cannot drive faster. The maximum speed of a PrT transport system, vMax-TSys, is an attribute of the link type. For speed v0-TSys or travel time t0-TSys therefore applies: v0-TSys t0-TSys = MIN (v0, vMax-TSys) = L 3.6 / v0-TSys
In a loaded network travel time of a link is determined through a so-called capacity restraint function (CR-function) which describes the correlation between the current traffic volume q and the capacity qMax. The result of the CR-function is the travel time tCur in the loaded network: Input Input Input Input Result: Result Free flow travel time t0[s] Traffic volume q [car units/time interval] Capacity qMax [car units/time interval] CR-function, e.g. BPR-function from the U.S. Bureau of Public Roads current travel time in loaded network
E T WFXU = W 0 1D T F max
current travel time of a transport system = MAX (tCur, t0-TSys)
2-9
MODEL DESCRIPTION
Network Model

Car

HGV
Link v0
Link type: "Motorway" = 130 km/h vMAX (car) vMAX (HGV) = 150 km/h = 100 km/h
Free traffic flow: ,OOXVWUDWLRQ vcur (car) vcur (HGV) = 130 km/h = 100 km/h
Dense traffic flow: vcur (car) vcur (HGV) = 110 km/h = 100 km/h
Saturated traffic flow: vcur (car) vcur (HGV) = 80 km/h = 80 km/h
Example for the different speeds of two PrT-transport systems in dependence of volume.
3X7UXQQLQJ WLPH With every link, a PuT-running time [s] is stored for each PuT-transport system. When a link is inserted this running time is calculated automatically from the link length and the link-specific speed of the transport system. During the construction of a PuT-line, a suggested running time between stops is then calculated from the PuTrunning time of the link.
2-10
Network Model
MODEL DESCRIPTION
7XUQLQJ UHODWLRQV

Turning relations indicate if it is permissible to turn at a node and specify a time penalty for PrT-transport systems: For private transport systems time penalty and capacity can be specified, which describe the impact of the intersection on the network performance. Turning relations are considered for PrT-transport systems during assignment. For public transport systems turning prohibitions are considered during the construction of a line route and during transport system-based PuT-assignment.
When a link is inserted, VISUM generates all possible turning relations at both nodes of the link. A four-way intersection, for example, altogether has 16 turning relations (four right turns, four straight ones, four left turns and four U-turns). Every turning relation is described by a list of permissible/blocked transport systems PrT-capacity and PrT-time penalty.
For every turning relation, transport systems have to be specified which are permitted to use the turning relation. A turning relation distinguishes between permitted and blocked transport systems: Permitted PuT-transport systems: the turning relation may be used during the construction of line routes. Permitted PrT-transport systems: the turning relation may be used during assignment considering PrT-capacity and PrT-time penalties. Blocked transport systems: turning prohibition.
,QSXW DWWULEXWHV A turning relation is described by the following input attributes: FromNode-Number ViaNode-Number ToNode-Number List of permitted transport systems Turning type 0 to 9 Turning time penalty t0-PrT PrT-capacity.
2-11
MODEL DESCRIPTION
Network Model
7XUQLQJ W\SHV VISUM distinguishes 10 turning types (0 to 9), of which types 0 to 4 are predefined: 0 1 2 3 4 5..9 no specification right turn straight on left turn U-turn free for user-defined cases
The turning type can be calculated automatically from the geometry of the turning relation. 7XUQLQJ VWDQGDUGV Turning standards are used for automatic assignment of turning time penalty and capacity attributes. Standard values for these attributes are defined in the TURNINGSTANDARD table in the network file. The following can be distinguished: Node type which the turning relation traverses Right of way rules which apply to the turning relation ++ from major flow into major flow +- from major flow into minor flow -+ from minor flow into major flow -- from minor flow into minor flow
turning type (right, straight, left).
* Attention: times always in seconds $TURNINGSTANDARD:NodeType;TurnRel;TurnType;t0-PrT;Cap-PrT 10;--;1;10;32000 10;-+;1;10;32000 // Right turn from Minor flow into major flow 10;+-;1;10;32000 // Right turn from major flow into minor flow 10;++;1; 0;32000 // Road with right of way which bends to the right 10;--;2;15;32000 // Crossing from minor flow into minor flow 10;-+;2;10;32000 10;+-;2;10;32000 10;++;2; 0;32000 // Crossing straight from major into major flow 10;--;3;20;32000 10;-+;3;20;32000 // Left turn from minor flow into major flow 10;+-;3;15;32000 // Left turn from major flow into minor flow 10;++;3; 0;32000
,OOXVWUDWLRQ
Example of a TURNINGSTANDARD table in the network file which is used to specify standard values for turning penalties and turning capacity.
2-12
Network Model
MODEL DESCRIPTION
3U7FDSDFLW\ DQG 3U7WXUQLQJ WLPH Turning relations show basically the same correlation between capacity and travel time as links. The only difference results from the fact that a turning relation does not have a length and that the travel time t0 therefore comes from the turning time penalty. The turning time tcur in the loaded network then results from the selected CRfunction and the relationship between the current traffic volume q and the capacity, qmax: Input: Input: Input: Input: Result: Free flow turning time t0 (turning time penalty) [s] Traffic volume q of the turning relation [car units/time interval] Capacity qMAX of the turning relation [car units/time interval] CR-function, e.g. BPR-function from U.S. Bureau of Public Roads current turning time in loaded network
b q t cur = t0 1+a q c max
To model turning times which do not depend on capacity, a constant CR-function must be chosen.
2-13
MODEL DESCRIPTION
Network Model
3X7OLQHV
A PuT-line consists of one or several line variants (sublines) which can have different line routes or running times between stops. A subline is defined by the line name the line variant the direction the line route (sequence of stops) with the running time between stops the timetable (list of departure times) operational data: operator name and vehicle type.
Sublines with the same name are aggregated to one line. Using different variants it is possible to model a line consisting of several sublines, which show different line routes or running times between stops (,OOXVWUDWLRQ ). The sublines of a line have to be part of the same transport system can have different operators and different vehicle types
2-14
Network Model
MODEL DESCRIPTION
Bus999-1O Bus999-1R Stop 1 Stop 2 Stop 3 Stop 4 Stop 5 Stop 6
Bus999-2O Bus999-2R
Bus999-3O Bus999-3R
%XVWLPHWDEOH6WRS6WRS
Stop 1 Stop 2 Stop 3 Stop 4 Stop 5 Stop 6
6:00 6:10 | 6:20 6:30 6:40
6:40 6:50 7:00 7:05 | |
7:00 7:10 | 7:20 7:30 7:40
| 8:40 8:50 8:55 9:05 |
%XVWLPHWDEOH6WRS6WRS
Stop 6 Stop 5 Stop 4 Stop 3 Stop 2 Stop 1
6:10 6:20 6:30 | 6:40 6:50
| | 7:15 7:20 7:30 7:40
| 8:05 8:15 8:20 8:30 |
8:10 8:20 8:30 | 8:40 8:50
,OOXVWUDWLRQ
Example of bus line 999 which consists of six sublines. (O = direction outward, R = direction return)
2-15
MODEL DESCRIPTION
Network Model
,QSXW DWWULEXWHV RI D VXEOLQH A PuT-subline is described by the following basic data: Line name (e.g. %XV) Line variant (e.g.) Direction (1 character, e.g. . < for one direction or > for opposite direction) Transport system Number of vehicle type Number of operator and Minimum layover time which is necessary for turning the vehicle, driver breaks, and buffer times.
Line identifiers (LinID) are determined by concatenating the line name, the line variant and the direction. A line identifier refers to one particular subline and can only be assigned once in a network model. The line identifier may consist of a maximum of 12 characters. The maxium number of characters for name or variant must have been specified previously in the network file before a network model is created. Definition of a line identifier made up of 9 characters (VISUM-DOS compatible): Name: up to 6 characters Variant: up to 2 characters Direction: 1 character Line identifier Bus999 -1 O Bus999-1O Bus999 -2 O Bus999-1O Bus999 -1 R Bus999-1R Bus999 -2 R Bus999-1R
* Structure of a line identifier $LINID:LinNameLength;LinVarLength;Dir1Code;Dir2Code 6;2;O;R
Definition of a line identifier consisting of 12 characters: Name: up to 4 characters Variant: up to 7 characters Direction: 1 character Line identifier RE-1 101 O RE-1101O RE-1 103 O RE-1103O RE-1 102 R RE-1102R RE-1 104 R RE-1104R
* Structure of a line identifier $LINID:LinNameLength;LinVarLength;Dir1Code;Dir2Code 4;7;O;R
,OOXVWUDWLRQ
Two examples for specifying a line identifier in the LINID table of the network file.
2-16
Network Model
MODEL DESCRIPTION
,QSXW DWWULEXWHV RI WKH OLQH URXWH The line route is specified by the node sequence: Line name (e.g. %XV), Line variant (e.g.), Direction (1 character, e.g. . < for one direction or > for opposite direction) Node sequence (stops and other nodes) with the following information for every stop node: Boarding permitted Alighting permitted Dwell time at stop Running time between current stop and previous stop Length between current stop and previous stop
,QSXW DWWULEXWHV RI WKH WLPHWDEOH The timetable is defined by the departure times at the first line stop from which the departure times of the following line stops can be concluded. The departure times can be specified as individual departure times or as departure times with a fixed rhythm headway. The following input data are necessary: Line name (e.g. %XV) Line variant (e.g.) Direction (1 character, e.g. < for one direction or > for opposite direction) For individual departure times: departure time at origin stop For departure times with a fixed rhythm: first departure time, headway, last departure time.
2-17
MODEL DESCRIPTION
Network Model
OLQN QHWZRUN
/LQH URXWH %XV!

board / run alight time dwell time arr. dep.
/LQH URXWH %XV!

board / alight run time dwell time arr. dep.
Node 1 Link 1 2 min/800m Node 2 Link 2 2 min/1000m Node 3 Link 3 1 min/600m Node 4 Link 4 1 min/800m Node 5
x x
0 min 0:00 0:00 2 min
x x
0 min 0:00 0:00
1 min 0:02 0:03 2 min
3 min
x
2 min
0 min 0:05 0:05
0 min 0:03 0:03
2 min
0 min 0:07 0:07
0 min 0:05 0:05
Representation in the network file

* Line route with running time profile $LINEROUTE:Name;Variant;Direction;NodeNr;Board;Alight;Arr;Dep;Length BUS1;1;>;1;1;1;00:00:00;00:00:00;0 BUS1;1;>;2;1;1;00:02:00;00:03:00;800 BUS1;1;>;3;1;1;00:05:00;00:05:00;1000 BUS1;1;>;4;0;0;00:00:00;00:00:00;600 BUS1;1;>;5;1;1;00:07:00;00:07:00;800 BUS1;2;>;1;1;1;00:00:00;00:00:00;0 BUS1;2;>;2;0;0;00:00:00;00:00:00;800 BUS1;2;>;3;1;1;00:03:00;00:03:00;1000 BUS1;2;>;4;0;0;00:00:00;00:00:00;600 BUS1;2;>;5;1;1;00:05:00;00:05:00;800
,OOXVWUDWLRQ
Example for two line routes with their input data.
2-18
Network Model
MODEL DESCRIPTION
,QSXW DWWULEXWHV RI YHKLFOH W\SH Vehicle types which have been assigned to the individual vehicle trips contain the data which are required to calculate Kilometer-dependent costs Time-dependent costs Fixed costs per vehicle Vehicle saturation.
For these calculations the following input attributes are specified for every vehicle type: Number of the vehicle type Name of the vehicle type Transport system Seating capacity Total capacity Cost per kilometer Cost per operating hour Cost per vehicle/day (or year).
,QSXW DWWULEXWHV RI WKH RSHUDWRU To assign indicators of individual lines to operators and to distribute the general costs of the operator over the lines, operators can be defined with the following input attributes: Number of operator Name of operator Up to three cost values for specifying costs for management, operating site, etc.
2-19
MODEL DESCRIPTION
Network Model
=RQHV
Traffic zones are the origins and destinations of trips, that is, of traffic. A traffic zone is an object with an area whose size may vary depending on its degree of detail. In the network model, traffic zones are reduced to a zone centroid. Here the trips of a O-D matrix are fed into the network. Every traffic zone can be assigned a zone boundary which represents the spatial extension of the zone. Several zones can be aggregated to one global zone. Every zone must be connected by a connector to at least one PrT-node or to at least one serviced PuT-stop. In contrast to a zone, a stop does not have to be connected. In this case, however, it can at only be a transfer stop. ,QSXW DWWULEXWHV A zone is described by the following input attributes: Unique zone number Name of zone Zone type (0 to 9) X-co-ordinate and Y-co-ordinate of zone centroid Identifier which specifies if PrT-origin and destination traffic is to be distributed proportionally over PrT-connectors.
&RQQHFWRUV
Every zone must be connected to at least one PuT-stop and one PrT-node via a connector so that travellers can leave/reach this zone. A connector corresponds to access and egress routes for which a walking time and length is given. A connector has two directions which can be used by PrT and/or PuT as access or egress routes: Origin connector from zone to node. Destination connector from node to zone.
Zones are origins and destinations of trips so that an origin connector is always the first part, and a destination connector is always the last part of a trip.
2-20
Network Model
MODEL DESCRIPTION
,QSXW DWWULEXWHV A connector is described by the following input attributes: Number of zone which is reached by connector Number of node which connects the zone to the link network Connector type Direction of connector (O = Origin traffic, D = Destination traffic, OD = Origin and Destination traffic) Connector length Connector permitted for PrT: (yes/no) Connector permitted for PuT: (yes/no) Access and egress times for PrT type Access and egress times for PuT type For proportional distribution: proportion of travel demand using the connector
3URSRUWLRQDO GLVWULEXWLRQ RI 3U7WUDIILF GHPDQG The distribution of PrT-origin and destination traffic onto PrT-connectors can be done freely or proportionally: )UHH GLVWULEXWLRQ: during route search, only the connector time is considered and traffic demand is distributed without further constraints onto the routes with the lowest impedance. 3URSRUWLRQDO GLVWULEXWLRQ: before the route search is carried out, the share of origin and destination traffic for every zone whose demand is to be distributed proportionally is calculated. From this origin and destination traffic a virtual connector capacity (= proportion x origin/destination traffic) for every connector can be deduced which modifies the impedance of the connectors during assignment in such a way that proportional distribution is achieved. The correspondence between the distribution of the assignment and the predefined values depends on the selected assignment procedure and the selected CRfunction for connectors. A "steep" CR-function should be used. In addition to this, the connector times must not be too low so that the connector impedance has an effect on the route search.
2-21
MODEL DESCRIPTION
Network Model
60 %
=RQH
=RQH
40 %
=RQH
1
Zone 1: Zone 2: Zone 3: proportional distribution proportional or absolute distribution proportional or absolute distribution 1000 trips 400 trips 1400 trips 40 % proportion 60 % proportion 40 % 1400 = 560 trips 60 % 1400 = 840 trips
Travel demand from zone 1 to zone 2: Travel demand from zone 1 to zone 3: Origin demand from zone 1: Connector zone 1 node 1: Connector zone 1 node 2: Capacity of connector zone 1 node 1: Capacity of connector zone 1 node 2:
"Steep CR-function for connector, e.g. BPR-function with a = 1, b 4, c 1 ,OOXVWUDWLRQ Example for the determination of connector capacity for proportional distribution of demand.
2-22
Travel Demand
MODEL DESCRIPTION
7UDYHO 'HPDQG
Travel demand develops when a sequence of activities (living - working - shopping living) cannot be carried out at the same location and thus requires a journey. Travel demand is described by an O-D matrix: A matrix element has the unit 1XPEHU RI MRXUQH\V or 1XPEHU RI WULSV . It contains the number of trips from one origin zone to a destination zone. A travel demand matrix refers to a time interval (analysis time interval) and thus only contains trips which depart within the time interval. Trips of a travel demand matrix can refer to the total transport system, to partial transport systems (e.g. pedestrian, bicycle, PuT, car), to person groups (e.g. employed, students, retired persons) or to purposes (e.g. commuting, shopping, leisure).
Travel demand can be divided into VXUYH\HG and FDOFXODWHG demand as well as into WRGD\
V and IXWXUH demand: 6XUYH\HG travel demand describes the number of trips and the trip distribution within a fixed time interval for an existing transport supply system. It represents a snapshot of the current traffic situation and cannot be reproduced again practically. An exact survey of WRGD\
V FXUUHQW WUDYHO GHPDQG in an area of interest is not possible in practice because all travellers would have to be interviewed at the same time. For this reason, only a representative, random sample of travellers is interviewed to determine travel demand for the purposes of transportation planning. From this survey a matrix of todays travel demand is then deducted. It represents the travel demand for the existing supply system. &DOFXODWHG WUDYHO GHPDQG contains assumptions about the number of trips and trip distribution. To calculate travel demand, demand models are used which, for example, differentiate between the three steps of trip generation, trip distribution and mode choice.
2-23
MODEL DESCRIPTION
Travel Demand
The calculated travel demand can be designated differently depending on the used input data: Calculated travel demand is called WRGD\
V WUDYHO GHPDQG if the input of the demand calculation is todays landuse structure, todays population and economic structure, and todays transport supply system. )RUHFDVWHG WUDYHO GHPDQG is based on data about future landuse, future population and economic structure and the future transport supply system.
An overview of the procedures for determining travel demand can be found in LEUTZBACH et. al. (1988). For detailed modelling of travel demand matrices (O-D matrices) PTV AG provides the programs VISEM and MUULI: The program VISEM estimates and forecasts mode-specific origin-destination matrices for behaviorally homogeneous person groups MUULI supports matrix processing and provides a gravity model.
7HPSRUDO GLVWULEXWLRQ RI WUDYHO GHPDQG IRU SXEOLF WUDQVSRUW Trips between two zones usually take place at distinct times. The temporal distribution of trips within each time interval of an observed time period is described by a distribution curve which is considered by PuT-assignments. The temporal distribution (,OOXVWUDWLRQ ) specifies the proportion of trips which want to leave a zone during each time interval of an observed time period. An equal distribution of travel demand during the observed time period is assumed as default.

,OOXVWUDWLRQ

Example for the temporal distribution of travel demand by four intervals of 30 minutes.
2-24
Impact Models
MODEL DESCRIPTION
,PSDFW 0RGHOV
A transport supply system has diverse impacts which may vary because of measures. Impacts on the user of the transport system. Impacts on the operators who have to produce a transport service. Impacts on the general public who benefits from the transport infrastructure but also has to pay for it. Impacts on the environment which is harmed by pollution.
7UDQVSRUW XVHUV Users of infrastructure for private transport are mostly car drivers and their passengers, but also non-motorised travellers such as cyclists and pedestrians. Users of public transport are public transport passengers. 7UDQVSRUW RSHUDWRUV The road network is usually operated by the state, federal states or communities and increasingly by private investors. These "operators" of the road network have to decide on investments for the construction and maintenance of road infrastructure. The PuT-operators are transport companies and transport associations. To offer a public transport service, PuT-operators develop line networks and timetables from which the user can then choose connections. To organise drivers and vehicles PuT operators develop vehicle employment plans and rosters.
8VHU 0RGHO

Objective of the user model is to determine the impacts of a transport supply system on travellers. Important indicators for evaluating the transport supply are the indicators journey time and travelling expenses between two zones. To evaluate a public transport supply, additional indicators such as number of transfers, transfer wait time and service frequency must be considered.
2-25
MODEL DESCRIPTION
Impact Models
To determine these service indicators, the journeys of travellers are modelled. A private transport user chooses a route for his journey which appears convenient to him. In addition to choosing a route, a public transport user also selects a departure time from the timetable, that is, he searches for a connection. While a route only describes the spatial course of a trip within a network, a connection additionally encompasses temporal contraints such as departure and arrival times at the origin stop, transfer stops, and at the destination stop. Methods to model the travel behaviour are based upon search algorithms which determine routes or connections between an origin and a destination. So-called shortest-path algorithms are used as search algorithms which determine the "best", that is, the shortest route with the lowest impedance. Impedance can consist of times, distances, and costs. Depending on the search algorithm used, this shortest path represents a route or a connection. The trips of an origin/destination relation are then distributed over the found routes or connections. This combination of search and trip distribution is called assignment. Private transport assignment assigns car trips, public transport assignment assigns passenger trips. For every route/connection between two zones indicators can be calculated which describe the service quality of the route/connection. In addition to this, assignment produces traffic volumes for links, turning relations, and PuT-lines. In contrast to a service indicator such as, for example, journey time, the volume indicator is only an indirect indicator which by itself is not suited for evaluating the transport supply system. Volume rather serves to deduce volume-dependent wait times which affect journey times saturation of PuT-linies which affects the comfort of passengers and the revenues of operators noise and pollution emissions which are indicators for environmental impact
The assignment procedures which are used to calculate service indicators and traffic volumes are a central component of VISUM. The different assignment procedures are explained in chapter 2.4 "User model (PrT)" for private transport and chapter 2.5 "User model (PuT)" for public transport.
2-26
Impact Models
MODEL DESCRIPTION
2SHUDWRU 0RGHO

To estimate the impacts on PuT-operators, the so-called operator model is used to determine indicators which express the operational and financial requirements for offering a public transport service. The operator model which is described in chapter 9 includes methods for determining the number of required vehicles determining operational costs estimating revenue line costing which distributes the operational costs and revenues over PuT lines.
(QYLURQPHQWDO ,PSDFW 0RGHO

VISUM provides four models which calculate environmental impact, that is, noise and pollution emissions, caused by motorised private transport. These are described in chapter 8. The results can be displayed in tabular or graphic form: 1RLVH,PPLV: noise calculation in accordance with immission parameters specified by 5/6 (Guideline of the German Federal Ministry for Transport). 1RLVH-(PLV: calculation of noise emission levels in accordance with 5/6 without considering immission parameters. 3ROOXWLRQ-(PLV: calculation of air pollution emissions in accordance with emission factors of the Swiss Federal Office for the Environment (BUS). 0/X6 calculation of air pollution emissions in accordance with 0/XV (Guideline by the German Society for Road and Traffic).
VISUM environmental impact analysis also contains two interfaces for external pollution calculation programs: ,00,6/XIW: pollution distribution program for immission calculation for road traffic (Supplier: IVU, Berlin/Freiburg). 0RELOHY: "Measure-oriented calculation instrument for local pollution emissions of motorised traffic" commissioned by the Federal Office for the Environment (Supplier: FiGE GmbH, Herzogenrath; right of use: Federal Office of the Environment, Berlin).
2-27
MODEL DESCRIPTION
User Model (PrT)
8VHU 0RGHO 3U7
VISUM provides four assignment procedures for private transport: ,QFUHPHQWDO DVVLJQPHQW divides the O-D matrix into several partial matrices. These partial matrices are then successively assigned to the network. The route search considers the impedance which results from the traffic volume of the previous step. (TXLOLEULXP DVVLJQPHQW distributes demand according to Wardrops first principle: "Every individual road-user chooses his route in such a way so that his journey takes the same time on all alternative routes and that switching routes would only increase personal journey time." The state of equilibrium is reached by multisuccessive iteration based on an incremental assignment as a starting solution. In the inner iteration step two routes of a relation are brought into a state of equilibrium by shifting vehicles. The outer iteration step checks if new routes with lower impedance can be found as a result of the current network state. /HDUQLQJ PHWKRG DVVLJQPHQW models the learning process of road-users in the network. Starting with "all or nothing assignment", drivers consecutively include information gained during their last journey for the next route choice. 7ULEXW is a bicriterion traffic assignment method which equally considers travel time and cost. The trip choice between different paths is modeled by defining the value of time as a random variable with a distribution of the log-normal type, thus considering that each trip has a specific willingness to pay toll for travel time reduction. This approach offers a significantly better price elasticity than monocriterion methods.
Each of the mentioned assignment procedures has two variants: Simple assignment: RQH demand matrix of RQH PrT-transport system, e.g. a car O-D matrix is assigned. Multi-class assignment (simultaneous assignment): PXOWLSOH demand matrices which contain demand for one or PXOWLSOH PrT-transport systems, e.g. a car O-D matrix and a HGV O-D-matrix are assigned simultaneously.
2-28
User Model (PrT)
MODEL DESCRIPTION
This chapter explains the algorithms for the PrT-assignment procedures. The algorithms for simple assignment are introduced first. The procedure for simultaneous assignment is then introduced for all three procedures in a separate section. The abbreviations used in this chapter are listed in ,OOXVWUDWLRQ . v0 t0 vcur tcur Imp q free flow speed [km/h] free flow travel time [s] speed in loaded network [km/h] travel time in loaded network [s] impedance = f (tcur) volume of a network object [car units/time interval] = sum of volumes of all PrT-transport systems including basic volume (preloaded volume):
q=
qmax Sat Fij F ,OOXVWUDWLRQ
Num TSys i =1
(qi car unitsi ) + qbasic
volume
capacity [car units/time interval] saturation number of trips [vehicles/time interval] for relation from zone i to zone j. O-D-matrix which contains the trips for all relations. Abbreviations used in "User model (PrT)" chapter.
2-29
MODEL DESCRIPTION
User Model (PrT)
([DPSOH 1HWZRUN

The way the PrT-assignment procedure works is described below using the example given in ,OOXVWUDWLRQ . The example anayses the relation between traffic zone "AVillage" and traffic zone "X-City" under the following assumptions: The access and egress times are not considered, that is, they are set to 0 minutes. Turning relation penalties are not considered. Capacity and demand refer to one hour. Traffic demand between A-Village and X-City consists of 2000 car trips (car.fma matrix) during the peak hour. To explain simultaneous assignment in chapter 2.4.6, 200 additional HGV trips (hgv.fma matrix) are considered. One HGV corresponds to 2 car units. On federal roads (link type 20) there is a speed limit of 80 km/h for HGVs.
The example network contains three routes which connect A-Village and X-City: Route 1: 10 11 41 40 Route 2: 10 11 20 21 30 31 40 Route 3: 10 12 21 30 31 40
Route 1 mostly uses country roads and is 26 km long. It is the shortest route. Route 2 is 30 km long. It is the fastest route because the federal road can be traversed at a speed of 100 km/h if there is free traffic flow. Route 3 which is also 30 km/h long is an alternative route which only makes sense if the federal road is congested.
2-30
User Model (PrT)
MODEL DESCRIPTION
$9LOODJH
10
11
41

20
40
;&LW\
12

21

Type
30

Length [m] 5000 5000 5000 10000 5000 5000 5000 16000 5000 10000 5000
31
LinkNr FromNode 1 2 3 4 5 6 7 8 9 10 11 10 11 20 20 21 30 31 11 40 10 12
ToNode 11 20 21 40 30 31 40 41 41 12 21
Capacity [car units/h] 2400 2400 2400 0 2400 2400 2400 1600 1600 1000 1000
v0-PrT [km/h] 100 100 100 0 100 100 100 80 80 60 60
20 Federal road 20 Federal road 20 Federal road 90 Rail track 20 Federal road 20 Federal road 20 Federal road 30 Country road 30 Country road 40 Other roads 40 Other roads
,OOXVWUDWLRQ
Example network
The example network is stored in the VISUM/example directory. Version file: Assignment parameters file: Example.ver Auto.par
2-31
MODEL DESCRIPTION
User Model (PrT)
,PSHGDQFH )XQFWLRQ

The route choices of travellers depend on objective and subjective factors. Indicators which influence route choice are, particularly, the anticipated journey time for the route the length of the route possible road tolls.
In addition to this, a multitude of other factors can influence route choice. One can imagine, for example, that road users who know their way around will choose other routes than people who do not know the area and who mainly orient themselves according to the sign-posted traffic network. 7UDYHO WLPHV Travel times for motorised transport are determined by the saturation of links and intersections which result from the traffic volume and the capacity of these network objects. Due to this, PrT-journey times in contrast to PuT-journey times vary, and can only be anticipated to a certain degree before a journey. PrT-journey time of a route between two zones consist of access and egress times, travel times of links, turning times at intersections.
For free traffic flow, the travel time, t0, of a link can be determined from the link length and the free-flow speed, v0. For turning relations at an intersection, the turning time, t0, is specified directly. In loaded networks the link travel time and the turning time is determined by a so-called capacity restraint function (CR function). This capacity restraint function describes the correlation between the current traffic volume q, and the capacity qmax. The result of the CR function is the travel time tCur in the loaded network. VISUM provides three types of CR function: the BPR function from the American Bureau of Public Roads (,OOXVWUDWLRQ ), a modified BPR function with different parameter b for the saturated / unsaturated state (,OOXVWUDWLRQ ), a modified BPR function with an additional penalty parameter d regarded for each vehicle in the saturated state (,OOXVWUDWLRQ ), the INRETS-function developed by the French Institute National de Recherche sur les Transports et Leur Scurit (,OOXVWUDWLRQ ), a constant function where the capacity does not influence travel time (tCur = t0).
2-32
User Model (PrT)
MODEL DESCRIPTION
b q tcur = t 0 1+a q max c
tcur t0 q
current travel time in loaded network [s] free flow travel time [s] volume of a network object [car units/time interval] = sum of volumes of all PrT-transport systems including basic volume (preloaded volume):
q=
qmax a, b ,c
Num TSys i =1
(qi car unitsi ) + qbasic
volume
capacity [car units/time interval] User-defined parameters a [0.00;), b {0.00...10.00}, c [0.00;) CR-curve for a=1 and c=1, tcur = t0 f(q/qmax)
10 9 8 7 6 5 4 3 2 1 0 0,1 0,3 0,5 0,7 0,9 1,1 1,3 1,5
b=5 b=4 b=3 b=2
f(q/qmax)
q / qmax
,OOXVWUDWLRQ
CR function according to BPR (Traffic Assignment Manual)
2-33
MODEL DESCRIPTION
User Model (PrT)
t cur = t 0 1+a Sat b1 t cur = t 0

a, b1,b2 ,c
( ) (1+a Sat )
b2
if saturation < 1 if saturation 1
user-defined parameter a {0.00;}, b1,2 {0.00;10.00}, c {0.00;} CR Function Type BPR2: modified BPR type
,OOXVWUDWLRQ
t cur = t 0 1+a Sat b t cur = t 0

a, b, c, d
( ) (1+a Sat ) + ((q q ) d )

b max
if saturation < 1 if saturation 1
user-defined parameter a {0.00;}, b {0.00;10.00}, c {0;}, d {0.00;100.00} CR Function Type BPR3: modified BPR type
,OOXVWUDWLRQ
2-34
User Model (PrT)
MODEL DESCRIPTION
1.1 - a Sat t cur = t 0 1.1 - Sat

1.1 - a Sat 2 t cur = t 0 0.1
Sat tcur t0 q Saturation; Sat =
for Sat < 1
for Sat 1
q qmax c
current travel time in loaded network [s] free flow travel time [s] volume of a network object [car units/time interval] = sum of volumes of all PrT-transport systems including basic volume (preloaded volume):
q=
qmax a c
Num TSys i=1
(qi car units i ) + qbasic
volume
capacity [car units/time interval] user-defined parameters a (0.00;1.10] user-defined capacity parameters c [0;) CR curve for c=1, tcur = t0 f(Sat)
10 9 8 7
W D 6 I
a=0,0 a=0,2 a=0,4 a=0,6 a=0,8
6 5 4 3 2 1 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 1,1 1,2 1,3 1,4 1,5
6DW
,OOXVWUDWLRQ
CR function according to INRETS

VISUM User Manual (April 2001) Version 7.50 2-35
MODEL DESCRIPTION
User Model (PrT)
,PSHGDQFH The impedance of a route between two zones relevant to route search consists of the impedance of the connectors the impedance of the links the impedance of the turning relations.
The impedance of a OLQN is a user-defined function which is defined for every transport system and which can depend on the following variables: transport system-specific travel time, tcur [s], in loaded network link length [m] transport system-specific road tolls [money units] user-defined AddValues link type factor [-].
Because the variables have different units (seconds, metres, money units), impedance cannot be written in a universally applicable unit. For a combination of the variables, travel time and road toll, it might be convenient to express impedance in terms of money units, that is, travel times are converted to money units using a "value of time" factor. ,OOXVWUDWLRQ shows an example in which link impedance consists of current travel time and road toll. For HGV transport systems which have a higher "value of time" the influence of road tolls on link impedance is less than for car transport systems. The impedance of WXUQLQJ UHODWLRQV and FRQQHFWRUV in contrast to links only depends on the variables tcur and possibly on the AddValue. Since the impedance of a connector is not capacity-dependent, access and egress impedance corresponds to tcur = t0. The proportional distributions of traffic demand onto different connectors is, however, reached through a virtual capacity, so that tcur > t0 can also apply to connectors: for each assignment the particular virtual capacity (100%) is recalculated from the current volume total and the demand to be assigned in the next assignment, e.g. Vol(car-business) + Vol(car-private) + Demand(HGV) = 100% Capacity(connector). %DVLF YROXPH When impedances are determined, basic volumes, i.e. a preloaded volume, can also be considered. Basic volumes can either be user-defined additional values or volume values which resulted from the assignment of a different o-d matrix.
2-36
User Model (PrT)
MODEL DESCRIPTION
([DPSOH
PRWRUZD\ OLQN 10000 m 130 km/h 100 km/h 1 Euro 5 Euro 3000 car units/h 1000 cars/h= 1000 car units/h
Link length: Permitted maximum speed v0-car: Permitted maximum speed v0-HGV: Road toll for cars: Road tolls for HGVs: Capacity: Car volume:
HGV volume: 100 HGV/h = 200 car units/h Value of time VOTcar = 18 Euro/h = 0,005 Euro/s Value of time VOTHGV = 36 Euro/h = 0,010 Euro/s
CR-function according to BPR with a=1, b=2, c=1 &DU WUDYHO WLPHV DQG VSHHGV Car travel time in unloaded network Car travel time in loaded network Car speed in loaded network +*9 WUDYHO WLPHV DQG VSHHGV HGV travel time in unloaded network HGV travel time in loaded network HGV speed in loaded network t0-HGV = 10000 3.6 / 100 = 360s tcur-HGV = MAX (321s; 360s) = 360s v0-HGV = 100 km/h t0-car = 10000 3.6 / 130 = 277s tcur-car = 277 (1+(1200/3000)2)= 321s v0-car = 10000 3.6 / 321 = 112 km/h
HGV speed only declines if the volume is more than 1644 car units/h, i.e. tcur = 277 (1+(1644/3000)2) = 360s ,PSHGDQFHV Car impedance in loaded network HGV impedance in loaded network ,OOXVWUDWLRQ Impcar = 1 + 0.005 321 = 2.61 Euro ImpHGV = 5 + 0.010 360 = 8.60 Euro
Example of the calculation of link impedance.
2-37
MODEL DESCRIPTION
User Model (PrT)
,QFUHPHQWDO $VVLJQPHQW

The incremental assignment procedure models how a network continuously "fills up". In the beginning, road-users can use a free network for which exactly one shortest route exists for every origin/destination relation. The traffic network is then successively loaded. Every step congests the road network with additional vehicles and, in this way, increases impedance on the congested links, turning relations, and connectors. Because of the changed impedance, alternative shortest routes may be found in every step.
2-38
User Model (PrT)
MODEL DESCRIPTION
'HVFULSWLRQ RI WKH 3URFHGXUH
,QSXW
Demand matrix F Number of iteration steps N Demand proportion Pn for every iteration step n = 1,N
n=0 Volume q0 = 0 or basic volume
,PSHGDQFH GHWHUPLQDWLRQ
Determination of impedances,Impn, for all network objects with the corresponding impedance function.
5RXWH VHDUFK
Determination of the best route for all relations based on impedance Impn.
9ROXPH
Assignment of travel demand which results from Pn onto network objects which are part of the best route. qn+1 = qn + Pn+1 F
n=n+1
4XHU\
n=N? Yes
No
(QG
Determination of impedances, Impn, of all network objects with the corresponding impedance function.
,OOXVWUDWLRQ
Incremental assignment procedure
2-39
MODEL DESCRIPTION
User Model (PrT)
([DPSOH
LinkNr 1 2 3 5 6 7 8 9 10 11 Route 1 2 3 LinkNr 1 2 3 5 6 7 8 9 10 11 Route 1 2 3 ,OOXVWUDWLRQ Type 20 20 20 20 20 20 30 30 40 40 Links of route 1+8+9 1+2+3+5+6+7 10+11+5+6+7 tcur Volume 1. step (50%) 1000 1000 1000 1000 1000 1000 0 0 0 0 05:05 05:05 05:05 05:05 05:05 05:05 12:00 03:45 10:00 05:00 Length [m] 5000 5000 5000 5000 5000 5000 16000 5000 10000 5000 Length [m] 26000 30000 30000 tcur Volume 2. step (25%) 1500 1000 1000 1000 1000 1000 500 500 0 0 07:41 05:05 05:05 05:05 05:05 05:05 16:41 05:13 10:00 05:00 v0 [km/h] 100 100 100 100 100 100 80 80 60 60 Capacity 1200 1200 1200 1200 1200 1200 800 800 500 500 t0 [min] 03:00 03:00 03:00 03:00 03:00 03:00 12:00 03:45 10:00 05:00 t0 [min] 18:45 18:00 24:00 tcur Volume 3. step (25%) 2000 1000 1000 1000 1000 1000 1000 1000 0 0 11:20 05:05 05:05 05:05 05:05 05:05 30:45 09:37 10:00 05:00
tcur Volume 1. step (50%) 0 1000 0 20:50 30:30 30:15
tcur Volume 2. step (25%) 500 1000 0 29:35 33:06 30:15
tcur Volume 3. step (25%) 1000 1000 0 51:42 36:45 30:15
Example incremental assignment (BPR function a=1, b=2, Imp=tcur)
2-40
User Model (PrT)
MODEL DESCRIPTION
,OOXVWUDWLRQ shows how the incremental assignment procedure works on the example network. The 2000 car trips are assigned in three iteration steps (50 %, 25 %, 25 %). Iteration step 1: the shortest route in the unloaded network is route 2 with an impedance of 18:00 min. It is loaded with 50 % of car trips, that is, with 1000 car trips. Iteration step 2: the shortest route after the first iteration step is route 1 with an impedance of 20:50 min. It is loaded with 25% of car trips, that is, with 500 car trips. Iteration step 3: after the second iteration step route 1 remains the shortest route with an impedance of 29:50 min. It is again loaded with 25% of car trips, that is, with 500 car trips, and now has 1000 car trips. After the third iteration step, route 3 turns out to have the lowest impedance. This route, however, is no longer found because all trips have been assigned.
In the example above, the impedance of a route results from the sum of the link impedances of a route. Additional impedances for connectors and turning are not considered. In addition to this, it is assumed that impedance results from current travel time, tcur, and that current travel time in turn results from the BPR function with a=1, b=2 and c=1.
(YDOXDWLRQ RI WKH 3URFHGXUH

LOHSE (1997) lists the following decisive disadvantages of the successive procedure: The number and the size of layers (partial matrices) mainly decides on the quality of the results. However, there is no procedure to specify optimal layers. The calculation is ended after the specified number of steps has been executed without checking correspondence between the resulting traffic volume and link impedances.
2-41
MODEL DESCRIPTION
User Model (PrT)
(TXLOLEULXP $VVLJQPHQW

7KH HTXLOLEULXP SURFHGXUH distributes demand according to Wardrops first principle: "Every individual road user chooses his route in such a way that his trip takes the same time on all alternative routes and that switching routes would only increase personal journey time." The state of equilibrium is reached by multi-successive iteration based on an incremental assignment as a starting solution. In the inner iteration step, two routes of a relation are brought into a state of equilibrium by shifting vehicles. The outer iteration step checks if new routes with lower impedance can be found as a result of the current network state. The equilibrium procedure determines a user optimum which is different from a system optimum as is shown by ,OOXVWUDWLRQ . A user optimum means that the same impedance results for all routes of a traffic relation i-j. A system optimum means that the product of route impedance and route volume is minimised for all traffic relations.
User optimum Route 1 2 3 Sum Links 1+8+9 1+2+3+5+6+7 10+11+5+6+7 Volume 736 995 269 2000 System optimum Route 1 2 3 Sum ,OOXVWUDWLRQ Links 1+8+9 1+2+3+5+6+7 10+11+5+6+7 Volume 734 919 347 2000 tcur [min] 37:43 37:13 41:13 Volume tcur 461:46:27 569:58:45 238:11:24 1269:56:36 tcur [min] 38:19 38:21 38:20 Volume tcur 470:05:53 636:01:21 171:50:02 1277:57:17
User optimum and system optimum for the example network
The computing time for the equilibrium procedure depends on the saturation of the traffic network, because new routes are found for every iteration step if the network is strongly congested.
2-42
User Model (PrT)
MODEL DESCRIPTION

Loaded network (starting solution) with routes R Maximum number of iteration steps N Maximum absolute deviation of impedance Ea Maximum relative deviation of impedance Er
,QSXW
n=0
1HWZRUN EDODQFLQJ
Balance the volumes of all routes for all O-D pairs i-j so that the impedance, Imp r,i-j, of the routes is: | min. Imp ij max. Imp ij | max. Imp ij / min. Imp ij < Ea or < 1 + Er
n = n +1
5RXWH VHDUFK
Determination of the best route for all relations i-j based on impedance Imp(n).
4XHU\
New routes found and n < N ? No End
Yes
,OOXVWUDWLRQ
Equilibrium assignment procedure
2-43
MODEL DESCRIPTION
User Model (PrT)
,QSXW
Number of routes R of an O-D pair i-j Volume Volr of every route r, r = 1, R Impedance Impr of every route r, r = 1, R Maximum absolute deviation of impedance Ea Maximum relative deviation of impedance Er
5RXWH VHOHFWLRQ
Select two routes Route R1: Route with minimal impedance Imp1 Route R2: Route with maximum impedance Imp2
Balance the volume of the routes R1 and R2 so that the 3DLU EDODQFLQJ impedance of the routes is: | Imp1 Imp2 | 1 - Er < Imp1 / Imp2 < Ea or < 1 + Er
If the volume of route R1 or R2 is 0 after balancing, delete route.
8SGDWH LPSHGDQFH
Update impedance of all network objects whose volume has changed.
4XHU\
Is the following condition fulfilled for the route with the minimum impedance, Imp1, and the route with No the maximum impedance Imp2? | Imp1 Imp2 | Imp2 / Imp1 < Ea or < 1 + Er Yes
(QG ,OOXVWUDWLRQ
Network balancing completed
Network balancing for an o-d pair using equilibrium procedure
2-44
User Model (PrT)
MODEL DESCRIPTION
([DPSOH
Route Starting solution Route 1 + 2 are known Network balancing 0 Route 1 + 2 1 2 3 1 2 3 1. iteration step: route search finds route 3 Network balancing 1 Route 1 + 3 1 2 3 Network balancing 2 Route 2 + 3 1 2 3 Network balancing 3 Route 1 + 2 1 2 3 Network balancing 4 Route 1 + 3 1 2 3 Network balancing 5 Route 2 + 3 1 2 3 Network balancing 6 Route 1 + 2 ,OOXVWUDWLRQ 1 2 3 649 1224 127 649 1067 284 734 982 284 741 982 277 741 990 269 736 995 269 36:25 42:58 36:23 35:15 40:17 40:15 38:09 38:10 38:51 38:27 38:07 38:31 38:30 38:14 38:15 38:19 38:21 38:20 Volume 1000 1000 0 776 1224 0 tcur [min] 51:42 36:45 30:15 41:54 41:56 33:22
Max. Imp route = 2, Min. Imp route = 3
Example equilibrium procedure (BPR function a=1, b=2)
2-45
MODEL DESCRIPTION
User Model (PrT)
,OOXVWUDWLRQ shows how the equilibrium procedure works for the example network. The volume determined in chapter 2.4.3.2 with the incremental procedure is here used as the starting solution. This starting solution encompasses two routes which are each congested with 1000 car trips. The specified absolute deviation is a value of five impedance units, and the relative deviation is specified as being 0.1 %. Based on the starting solution, the following steps are then carried out: Network balancing for starting solution: the volumes of route 1 and 2 are changed in such way that the deviation of the two route impedances is below the specified deviation. This is guaranteed with a volume of 776 and 1224 vehicles for route 1 and 2. Route search for iteration step 1: after network balancing of routes 1 and 2, the shortest-path search of the first iteration step determines route 3. Network balancing for iteration step 1: the three routes are balanced in pairs until the impedance of all routes accords with the specified deviation. This is the case in the example if the absolute deviation between maximum and minimum impedance is smaller than 5 seconds or the relative deviation between the maximum and minimum impedance is less than 0.1 %
Pair network balancing always changes the volumes of the route with the minimum impedance and the route with the maximum impedance. Route search for iteration step 2: no new route is found, the equilibrium procedure terminates.
In the above example, the impedance of a route results from the sum of the link impedances of the route. It is assumed that impedance is equal to the current travel time, tcur, and that the current travel time is calculated using the capacity restraint function BPR with a=1, b=2 and c=1.

Because the procedure only terminates when all routes of any O-D relation are in the equilibrium state, the procedure provides more realistic results than the incremental procedure. For lower traffic volumes a similar result is achieved as with best-route assignment, because the route search does not find new routes. In this case it is recommended to use an incremental assignment with suitable parameters as initial solution or the learning procedure.
2-46
User Model (PrT)
MODEL DESCRIPTION
/HDUQLQJ 0HWKRG

The OHDUQLQJ SURFHGXUH was developed by Lohse and is described in SCHNABEL and LOHSE (1997). This procedure models the "learning process" of road users using the network. Based on an "all or nothing" assignment, drivers make use of information gained during their previous trip for the new route search. Several shortest routes are searched in an iterative process whereby for the route search the impedance is deduced from the impedance of the current volume and the previously estimated impedance.
2-47
MODEL DESCRIPTION
User Model (PrT)

,QSXW Upper and lower threshold of delta: Upper and Lower Parameters of the f(TT) function: V1, V2, V3 Termination conditions: max. number of iterations N; E1, E2, E3 for determining the max. deviation E of impedance
* n = 0, Imp n =0 = impedance in unloaded network
n=n+1 Determination of the shortest route Rn for all O-D pairs based on * impedance Imp n1. If route Rn is new route r: If route Rn already exists as route r: 5RXWH YROXPHV Countr = 1 Countr = Countr + 1
5RXWH VHDUFK
Determine volumes for all routes of any relation i-j: Route volume Volr = Fij / n x Countr
,PSHGDQFH Impn = impedance at current volume n * * GHWHUPLQDWLRQ TTn = Im p n Im p n 1 Im p n1
f ( TTn ) = V1 (1 + eV 2 V 3TTn )
n = Lower + Upper Lower
(1 + TTn )f (TT )
* * * Imp n = Imp n 1 + n Imp n Imp n 1
)
No
4XHU\
n = N or for every link the following applies:

* Im p n Im p n 1
<E=
E 2 / E3 E1 Im p n1
Yes End ,OOXVWUDWLRQ Assignment with learning method
2-48
User Model (PrT)
MODEL DESCRIPTION
([DPSOH
LinkNr 1 2 3 5 6 7 8 9 10 11 Route 1 2 3 Type 20 20 20 20 20 20 30 30 40 40 Links 1+8+9 1+2+3+5+6+7 10+11+5+6+7 Length [m] 5000 5000 5000 5000 5000 5000 16000 5000 10000 5000 Length 26000 30000 30000 v0 [km/h] 100 100 100 100 100 100 80 80 60 60 Capacity [car units] 1200 1200 1200 1200 1200 1200 800 800 500 500 Imp0* [min] 03:00 03:00 03:00 03:00 03:00 03:00 12:00 03:45 10:00 05:00 Imp0* 0:18:45 0:18:00 0:24:00
,QSXW SDUDPHWHUV BPR function with a = 1, b = 2, c = 1 Lower Upper V1 = 2.5 V2 = 4 V3 = 0.002 Impedance in unloaded network, input parameters of learning method. = 0.15 = 0.5
f (TT ) = 2.5 (1 + e 40.002TT )
,OOXVWUDWLRQ
2-49
MODEL DESCRIPTION
User Model (PrT)
LinkNr 1 2 3 5 6 7 8 9 10 11 Route 1 2 3
Volume1 [car units] 2000 2000 2000 2000 2000 2000 0 0 0 0 Volume1 0 2000 0
Imp1 [min] 11:20 11:20 11:20 11:20 11:20 11:20 12:00 03:45 10:00 05:00 Imp1 0:27:05 1:08:00 0:49:00
TT1 2,78 2,78 2,78 2,78 2,78 2,78 0,00 0,00 0,00 0,00
f(TT1) 0,0452 0,0452 0,0452 0,0452 0,0452 0,0452 0,0450 0,0450 0,0450 0,0450
Delta 1 0,4796 0,4796 0,4796 0,4796 0,4796 0,4796 0,5000 0,5000 0,5000 0,5000
Imp1* [min] 07:00 07:00 07:00 07:00 07:00 07:00 12:00 03:45 10:00 05:00 Imp1* 0:22:45 0:41:59 0:35:59
,OOXVWUDWLRQ LinkNr 1 2 3 5 6 7 8 9 10 11 Route 1 2 3
Example of learning method: 1. Iteration step Imp2 [min] 11:20 05:05 05:05 05:05 05:05 05:05 30:45 09:37 10:00 05:00 Imp2 0:51:42 0:36:45 0:30:15 TT2 0,62 0,27 0,27 0,27 0,27 0,27 1,56 1,56 0,00 0,00 f(TT2) 0,0450 0,0450 0,0450 0,0450 0,0450 0,0450 0,0451 0,0451 0,0450 0,0450 Delta 2 0,4925 0,4962 0,4962 0,4962 0,4962 0,4962 0,4855 0,4855 0,5000 0,5000 Imp2* [min] 09:08 06:03 06:03 06:03 06:03 06:03 21:06 06:36 10:00 05:00 Imp2* 0:36:50 0:39:22 0:33:08
,OOXVWUDWLRQ
Example of learning method: 2. Iteration step
2-50
User Model (PrT)
MODEL DESCRIPTION
LinkNr 1 2 3 5 6 7 8 9 10 11 Route 1 2 3
Imp3 [min] 06:42 03:56 03:56 06:42 06:42 06:42 20:20 06:21 27:47 13:53 Imp3 0:33:23 0:34:40 1:01:47
TT3 0,27 0,35 0,35 0,11 0,11 0,11 0,04 0,04 1,78 1,78
f(TT3) 0,0450 0,0450 0,0450 0,0450 0,0450 0,0450 0,0450 0,0450 0,0451 0,0451
Delta 3 0,4963 0,4953 0,4953 0,4984 0,4984 0,4984 0,4994 0,4994 0,4842 0,4842
Imp3* [min] 07:56 05:00 05:00 06:22 06:22 06:22 20:43 06:28 18:37 09:18 Imp3* 0:35:07 0:37:03 0:47:02
,OOXVWUDWLRQ
Example of learning method: 3. Iteration step
2-51
MODEL DESCRIPTION
User Model (PrT)
,OOXVWUDWLRQ to ,OOXVWUDWLRQ illustrate the first three iteration steps of the learning procedure for the example network: ,WHUDWLRQ VWHS Q
Volume 1: the volume of the 1. Iteration step results from an "all or nothing" assignment onto the lowest impedance route of the unloaded network. For Imp0* this is route 2, which is loaded with 2000 car trips. Current impedance Imp1: the current impedance Imp1 of every link results from the HCM capacity function (a =1, b = 2, c= 1). For link 1, for example, the following can be calculated: Imp1 (link 1) = 3min (1+(2000/1200)2) = 11min 20s Estimated impedance Imp1*: the estimated impedance Imp1* of every link consists of the current impedance Imp1 and the estimated impedance Imp0* of the last iteration step. It results from the learning factor . To determine Imp1* for link 1, the following calculations are necessary:
* Imp0 = 3 min
= 180s
Imp 1 = 11min 20s = 680s

* * TT1 = Imp 1 Imp 0 Imp 0 = 680s 180s 180s = 2.78
f (TT1 ) = V1 (1 + e V 2 V 3TT1 ) = 2.5 1 + e 4 0.0022.78 = 0.0452

1 = Lower +
* Imp 1
(1 + 2.78 )0.0452 * * ) = 180s + 0.4796 (680s 180s) = 420s = Imp 0 + 1 (Imp 1 Imp 0
f ( TT1 )
Upper Lower
(1 + TT1 )
= 0.15 +
0.5 0.15
= 0.4796
,WHUDWLRQ VWHS Q
Volume 2: the lowest impedance route for Imp1* is route 1. Now two routes exist, route 1 and 2. Every route is loaded with 1/n, that is, with demand, so that every route is used by 1000 cars. Current impedance Imp2: the current impedance Imp2 of every link increases on newly loaded links 8 and 9, and it decreases on links 2, 3, 5, 6 and 7. Estimated impedance Imp2*: The estimated impedance Imp2* of every link consists of the current impedance Imp2 and the estimated impedance Imp1* of the last iteration step.
2-52
User Model (PrT)
MODEL DESCRIPTION
,WHUDWLRQ VWHS Q
Volume 3: the lowest impedance route for Imp1* is now route 3. 1/3 of the 2000 car trips are now distributed over routes 1, 2 and 3. Current impedance Imp3: the current impedance Imp3 again results from the current volume 3 via the CR-function. Estimated impedance Imp*: the estimated impedance Imp3* of every link consists of the current impedance Imp3 and the estimated impedance Imp2* of the last iteration step.
,WHUDWLRQ VWHS Q
The concluding route search based on Imp3* determines route 1 as the shortest route. Thus, the following route volumes result: Volume route 1 Volume route 2 Volume route 3 = 2/4 2000 = = 1/4 2000 = = 1/4 2000 = 1000 trips 500 trips 500 trips

Under the condition that a sufficient number of iteration steps (N > 40) are carried out and that the procedure is not terminated due to the condition n = N, the learning method produces realistic, stable results. Even in networks with low saturation, the distribution of volumes onto alternative routes is good. The greater number of iteration steps necessary for a good solution usually requires more route searches than the equilibrium procedure. This results in longer computing times.
2-53
MODEL DESCRIPTION
User Model (PrT)
6LPXOWDQHRXV $VVLJQPHQW

Simultaneous assignment procedures (multi-class assignment) differ from simple assignment procedures by being able to assign several demand matrices simultaneously. $VVLJQLQJ VHYHUDO GHPDQG PDWULFHV WR RQH WUDQVSRUW V\VWHP Simultaneous assignment of several demand matrices to one PrT-transport system is suitable if evaluations need to differentiate trip purposes or person groups. To achieve this, different demand types (e.g. matrix1 = trip purpose commuting, matrix2 = trip purpose shopping) can be defined for one PrT transport system. Because the demand types of a PrT-transport system use the same link network and the same impedance function, the assignment results do not differ from an assignment where an entire matrix (= matrix1 + matrix2) is assigned. The only advantage is that the volume values for every demand type can be displayed, and that matrix-specific flow bundle evaluations are possible. $VVLJQLQJ VHYHUDO GHPDQG PDWULFHV WR VHYHUDO WUDQVSRUW V\VWHPV Usually, private transport encompasses several PrT-transport systems (e.g. car and HGV) which can differ in terms of the structure of demand, the type of road network, and in travel behaviour: There are roads which may not be used by all PrT-transport systems, e.g. some roads might be closed to HGVs because they run through towns or lanes may only be used by cars with more than 2 people. It is possible that there are different speed limits for different PrT-transport systems. HGVs, for example, have a speed limit of 100 km/h on motorways, while cars may drive faster than 100 km/h. Road tolls vary according to vehicle types, this means, for example, that HGVs must pay higher road tolls than cars. The effects of road tolls are evaluated differently by PrT-drivers. For an HGV driver or a car driver who is on a business trip, road tolls do not have the same impact as for drivers who drive a private vehicle.
2-54
User Model (PrT)
MODEL DESCRIPTION
These transport system-specific differences in the road network or in travel behaviour can influence the route choice: Transport system-specific differences in the road network are represented in the network model by transport system-specific attributes of links: list of permissible transport systems and road tolls of link types: maximum speed vMax
Differences in travel behaviour are represented by different impedance functions which are defined for every transport system.
Simultaneous assignment considers these different characteristics of PrT transport systems and for this purpose carries out a separate route search for every transport system.

Simultaneous procedures exist for the incremental assignment, equilibrium assignment, and the learning method. They differ from simple assignment procedures only by the fact that for every transport system a separate search is carried out during the route search which considers the transport system-specific impedance. The following illustrations show the course of simultaneous assignment (multi-assignment) for different assignment procedures.
0XOWL,QFUHPHQWDO 3URFHGXUH For all PrT-DSeg to be assigned Initialise existing assignment For all iteration steps Update impedance of network objects For all PrT-DSeg to be assigned For all origin zones Search for shortest routes and load these routes Update impedance of network objects ,OOXVWUDWLRQ Multi-incremental assignment
2-55
MODEL DESCRIPTION
User Model (PrT)
0XOWL(TXLOLEULXP 3URFHGXUH If not all selected PrT-DSeg have been assigned or If the "Use existing assignment as initial solution" button is not active Carry out multi-incremental assignment If equilibrium condition is not met %DODQFH QHWZRUN Repeat For all PrT-TSys to be assigned For all origin zones Search for shortest routes If new routes were found %DODQFH QHWZRUN Until no new routes are found %DODQFH QHWZRUN procedure Repeat For all o-d pairs i-j which have not been balanced For all PrT-DSeg to be assigned Paired network balancing Until equilibrium condition is achieved ,OOXVWUDWLRQ Multi-equilibrium procedure
2-56
User Model (PrT)
MODEL DESCRIPTION
0XOWL/HDUQLQJ 0HWKRG For all PrT-DSeg to be assigned Initialise existing assignment For all PrT-TSys to be assigned Calculate estimated impedance Imp* Repeat For all PrT-TSys to be assigned For all origin zones Search for shortest route based on Imp* If route r already exists from previous iteration step NSeg-Countr = NSeg-Countr + 1 Otherwise Save route, NSeg-Countr = 1 For all PrT-NSeg to be assigned NSeg-volume route r = NSeg-demand Fij / n NSeg-Countr Update impedance of network objects For all PrT-TSys to be assigned Calculate estimated impedance Imp* Until no link impedance for every transport system differs more than epsilon E from the link impedance of the previous iteration step or until the maximum number of iterations has been reached. ,OOXVWUDWLRQ Simultaneous multi-learning procedure
([DPSOH
The procedure of simultaneous assignment is explained with the example of a multiincremental assignment for the example network. In addition to the 2000 car trips, 200 HGV trips are also assigned in this process. ,OOXVWUDWLRQ shows the input parameters for the procedure and lists the relevant link attributes in the unloaded network. Because there is a speed limit of 80 km/h for HGVs on federal roads (type 20), the speed, v0, and the travel time, t0, in the unloaded network must be displayed separately. The speed v0 of a transport system (v0-TSys) results from the minimum v0 of the link and the speed vMax-TSys which is defined for every transport system by the link type.
2-57
MODEL DESCRIPTION
User Model (PrT)
LinkNr 1 2 3 5 6 7 8 9 10 11 Route 1 2 3
Type 20 20 20 20 20 20 30 30 40 40 Links 1+8+9 1+2+3+5+6+7 10+11+5+6+7
Length [m] 5000 5000 5000 5000 5000 5000 16000 5000 10000 5000 Length [m] 26000 30000 30000
V0 [km/h] Car 100 100 100 100 100 100 80 80 60 60
Capacity HGV [car units] 80 80 80 80 80 80 80 80 60 60 1200 1200 1200 1200 1200 1200 800 800 500 500
Imp0 = t0 [min] Car 03:00 03:00 03:00 03:00 03:00 03:00 12:00 03:45 10:00 HGV 03:45 03:45 03:45 03:45 03:45 03:45 12:00 03:45 10:00
05:00 05:00 t0 [min] Car 18:45 18:00 24:00 HGV 19:30 22:30 26:15
,QSXW SDUDPHWHUV BPR function with a = 1, b = 2, c = 1 1. Iteration step 50 % of demand = 1000 cars and 100 HGVs 2. Iteration step 25 % of demand = 500 cars and 50 HGVs 3. Iteration step 25 % of demand = 500 cars and 50 HGVs Example for a simultaneous incremental assignment: impedance in unloaded network and input parameters.
,OOXVWUDWLRQ
Because of their different speeds, the shortest routes for cars and HGVs are different. For cars, route 2 (18:00 min) is the fastest in an unloaded network while HGVs reach their destination fastest if they use route 1 (19:30 min). As shown in ,OOXVWUDWLRQ , route 2 is, therefore, loaded with 50 % of car trips. Analogously, route 1 is assigned 50 % of HGV trips. From this transport system-specific route volume the link volumes and level of saturation relevant to determining impedance are calculated. The saturation of a link results from the comparison of the total volume [car units] and the capacity [car units].
2-58
User Model (PrT)
MODEL DESCRIPTION
For link 1, for example, the following saturation is calculated (1000 cars 1.0 car units + 100 HGV 2.0 car units) / 1200 car units = 1 or 100 %. With this saturation the travel time tCur is doubled compared to travel time t0 in the unloaded network. Since the current speed vCur is now lower than the permitted HGV speed, v0-HGV, cars and HGVs drive at the same speed and thus have the same link and route impedance for the impedance function (Imp = tcur) chosen in the example.
LinkNr 1 2 3 5 6 7 8 9 10 11 Route 1 2 3
TSys-volume 1 [veh] Car HGV 1000 1000 1000 1000 1000 1000 0 0 0 0 TSys-volume 1 [veh] Car HGV 0 1000 0 100 0 0 100 0 0 0 0 0 100 100 0 0
Total volume 1 [car units] 1200 1000 1000 1000 1000 1000 200 200 0 0 Total volume 1 [car units] 200 1000 0
Imp1 = tcur 1 [min] Car 06:00 05:05 05:05 05:05 05:05 05:05 12:45 03:59 10:00 05:00 Car 22:44 31:25 30:15 HGV 06:00 05:05 05:05 05:05 05:05 05:05 12:45 03:59 10:00 05:00 HGV 22:44 31:25 30:15
Imp1 = tcur1 [min]
,OOXVWUDWLRQ
Example for simultaneous assignment with incremental procedure: 1. Iteration step.
2-59
MODEL DESCRIPTION
User Model (PrT)
During the second iteration step (,OOXVWUDWLRQ ), route 1 is loaded with 25 % of demand, that is, 500 car trips and 50 HGV trips, because this route has the lowest impedance for both transport systems after the 1. Iteration step. LinkNr 1 2 3 5 6 7 8 9 10 11 Route 1 2 3 ,OOXVWUDWLRQ TSys-volume 2 [veh] Car HGV 1500 1000 1000 1000 1000 1000 500 500 0 0 TSys-volume 2 [veh] Car HGV 500 1000 0 150 0 0 150 0 0 0 0 0 150 150 0 0 Total volume 2 [car units] 800 1000 0 assignment Total volume 2 [car units] 1800 1000 1000 1000 1000 1000 800 800 0 0 Imp2 = tcur 2 [min] Car 09:45 05:05 05:05 05:05 05:05 05:05 24:00 07:30 10:00 05:00 Car 41:15 35:10 30:15 with HGV 09:45 05:05 05:05 05:05 05:05 05:05 24:00 07:30 10:00 05:00 HGV 41:15 35:10 30:15 incremental
Imp2 = tcur 2 [min]
Example for simultaneous procedure: 2. Iteration step.
2-60
User Model (PrT)
MODEL DESCRIPTION
The route search in the 3. and last iteration step (,,OOXVWUDWLRQ ) determines route 3 as being the route with the lowest impedance. It is loaded with the remaining 25 % of demand. LinkNo 1 2 3 5 6 7 8 9 10 11 Route 1 2 3 ,OOXVWUDWLRQ TSys-volume 3 [veh] Car HGV 1500 1000 1000 1500 1500 1500 500 500 500 500 150 0 0 50 50 50 150 150 50 50 Total volume 3 [car units] 1800 1000 1000 1600 1600 1600 800 800 600 600 Total volume 3 [car units] 800 1000 600 0 50 Imp3 = tcur 3 [min] Car 09:45 05:05 05:05 08:20 08:20 08:20 24:00 07:30 24:24 12:12 Car 00:41:15 00:44:55 01:01:36 HGV 09:45 05:05 05:05 08:20 08:20 08:20 24:00 07:30 24:24 12:12 HGV 00:41:15 00:44:55 01:01:36
TSys-volume 3 [veh] Car HGV 500 1000 500 150
Imp3 = tcur 3 [min]
Example for simultaneous assignment with incremental procedure: 3. Iteration step.
2-61
MODEL DESCRIPTION
User Model (PrT)
75,%87 3URFHGXUH

TRIBUT is a bicriterion traffic assignment method which equally considers travel time and cost. The trip choice between different paths is modeled by defining the value of time as a random variable with a distribution of the log-normal type, thus considering that each trip has a specific willingness to pay toll for travel time reduction. Numerous applications of TRIBUT in Europe, Asia and North America have shown that this approach offers a significantly better price elasticity than monocriterion methods. Its most prominent features are randomly distributed values of time, the principles of path search and path choice. Furthermore it presents different aspects of the application in practice, in particular the definition of different demand classes, the modeling of linear or non-linear pricing schemes and the value of time estimation.
$VVLJQPHQW FRQVLGHULQJ 5RDG 7ROO

For toll assignments, the criteria for choosing path p consist of time tp and cost cp. The objective function or the generalized path choice criterion Critp can be formulated as follows:
Crit p = t p + c p / VT =
with: tL
c / VT t + L L Lp Lp
travel time on a network object L as a function of traffic volume tL = t(volL), L may represent a link, a node or a turning movement, toll value for using link L, assumed to be invariant of link volume, value of time in [e.g. $/h] .
volL volume of link L, cL VT
It is assumed, that each individual trip tries to minimize this criterion Critp in its path choice within a road network. The way Critp is formulated above, it represents a generalized time. Critp may as well be defined as generalised cost by using the value of time VT for converting time into cost, which will lead to identical deductions.
2-62
User Model (PrT)
MODEL DESCRIPTION
So far the conventional monocriterion toll assignment and TRIBUT can be described by the same objective function. However, they differ in modeling the value of time VT: In the PRQRFULWHULRQ approach the value of time VT is assumed to be constant for all trips, or at least for all trips within one trip class, i.e. o-d matrix. Therefore the expression cp/VT in the objective function Critp represents a constant supplement to time tp for each path p. As a consequence the value of Critp is identical for all trips. In the ELFULWHULRQ approach of TRIBUT the value of time VT is randomly distributed. That way each trip within a matrix can apply a specific value of time and it is taken into account that each trip has its own perception about spending time and money for travel.
This assumption of individual values of time has various consequences on the model structure: During assignment both criteria tR and cR need to be accessible for each path at all times, so the values for time and cost must be stored in the data structures. A unique best path does not exist, as each trip has its specific best path. This has two effects: (1) the assignment will produce more alternative paths, (2) a multi-path-search algorithm is required.
2-63
MODEL DESCRIPTION
User Model (PrT)
7KH 7LPH&RVW 'LDJUDP The time-cost diagram displayed in the figure below may illustrate some aspects of the bicriterion path choice. In this diagram alternative paths for one o-d pair are represented by a set of points, each characterized by time and cost, e.g. path A = (tA,cA). A specific value of time VT can be represented by any straight line with the slope -VT. If the same straight VT line encounters two paths, they are considered indifferent, i.e. equally good for a user who has this particular VT. This VT, which is determined by two alternative points, is also described as critical value of time for the two alternatives in question. In ,OOXVWUDWLRQ the straight line representing the critical VT for A and B is drawn as a dotted line.
FRVW F
cA cB
$ %
; VT = |cB - cA| / |tB - tA|
< tA
,OOXVWUDWLRQ
tB
WLPH W
Time-cost diagram with alternative paths and critical value of time
The point where the VT-line fits the cost-axis represents the total cost equivalent of both paths A and B, for the specific value of time, i.e. the critical value of time. The corresponding point on the time-axis represents the general criterion (i.e. the time equivalent). It is obvious that trips will prefer A to X for any value of time, i.e. A dominates X. More generally for any given VT, each path located to the right side of the VT-line is dominated by A and B (so is Y), because it is assumed that all trips prefer paths that minimize the general criterion as well as the cost equivalent.
2-64 VISUM User Manual (April 2001) Version 7.50
User Model (PrT)
MODEL DESCRIPTION
9DOXH RI 7LPH DV D ORJ1GLVWULEXWHG 5DQGRP 9DULDEOH

As mentioned before, it is assumed that each vehicle applies its individual value of time VT. This assumption is reflected in the model by defining the value of time VT as a random variable with a distribution of the log-normal type:
VT = log N vt,
)
( )
with the following distribution parameters:
vt
the median of
VT = log N vt,
the standard deviation of the associated random variable Y=loge(VT), where Y is normally distributed. The logN-distribution is widely used in income statistics. One important property of the logN-distribution for income or toll modeling is, that the probability equals zero for negative values, which is a trivial assumption for values of time. The use of the median vt as positioning parameter may appear strange, but this corresponds to a convention in income statistics to publish quantils rather that mean values. Nevertheless the logN-distribution could as well be defined by the mean =loge( vt ) and standard deviation both of the associated normal distribution Y=loge(VT).
vt
Density JYW and distribution function G ( vt ) =
g(vt)
2-65
MODEL DESCRIPTION
User Model (PrT)
0,060
Density function g1(vot)

0,050
Density function g2(vot)
0,040
0,030
0,020
0,010
0,000 0 10 20 30 40 50 60 70 80 90
YDOXHRIWLPH
,OOXVWUDWLRQ
Density function
,OOXVWUDWLRQ
Distribution function
2-66
User Model (PrT)
MODEL DESCRIPTION
Using TRIBUT in a planning project, the definition of the VT distribution, i.e. of the two parameters, is one of the most crucial steps. Therefore empirical methods to determine the distribution parameters are discussed.
3DWK 6HDUFK (IILFLHQW )URQWLHU DV ([FOXVLYH &ULWHULRQ

In monocriterion methods one unique best path (shortest path) can be determined for each o-d pair. In the case of TRIBUT, however, due to the random distribution of VT, numerous best paths must be determined and stored in memory not only during path search but during the entire assignment procedure. That is the reason for the high complexity of multicriterion methods. Nevertheless, it is possible to reduce this complexity by identifying the HIILFLHQW paths for each o-d pair. ,OOXVWUDWLRQ shows a path search with six paths, where paths A, B, C and D represent the set of efficient paths. It can easily be demonstrated either graphically or analytically that there is no VT for which paths X or Y would be preferred over A, B, C or D. Generally speaking, the convex curve formed by the three critical VTstraight-lines A-B, B-C and C-D limits the range of relevant cost-time combinations to the right side. This convex curve is therefore called efficient frontier. Therefore X and Y can be deleted in the example.
vtcrit,C-D
C
vtcrit,B-C vtcrit,A-B
B Y A
W
,OOXVWUDWLRQ Critical values of time building up the efficient frontier
2-67
MODEL DESCRIPTION
User Model (PrT)
The introduction of the efficient frontier has important consequences: Only the efficient paths need to be stored during path search for the subsequent path choice. As a consequence the majority of the various possible paths for one o-d pair can be discarded thus limiting computing time and memory. Nevertheless TRIBUT needs to perform a simultaneous multi-path search that is more complex than the best-path-search procedures in the monocriterion case. The set of efficient paths of any o-d pair is unique for one state of the network, meaning that it does not depend on the kind of VT-distribution which has been defined. Hence in the case of a multi-class assignment, only one search step has to be performed in each equilibrium iteration, although the subsequent demand allocation will be determined specifically for each demand class.
The TRIBUT multi-path-search algorithm consists of two steps: First, it uses a classic shortest-path search to determine the paths with minimum travel time from one origin o to DOO QHWZRUN HOHPHQWV. Note, that a classic shortest path search would only build up paths from one origin to DOO GHVWLQDWLRQV. This first step is not sufficient to determine the entire efficient frontier, but it will find the fastest paths, which will definitely be the most expensive paths on the efficient frontier. Next, the procedure extends the path-tree with less expensive paths. This expansion is achieved not by considering the travel time, but by considering the critical value of time between the last inserted path to a network object and the other candidates.
2-68
User Model (PrT)
MODEL DESCRIPTION
3DWK &KRLFH IRU D *LYHQ 6HW RI $OWHUQDWLYHV

Path choice aims to distribute the travel demand of an o-d pair onto the set of available paths. In the bicriterion case, the demand is allocated to the efficient paths. The way the total o-d demand is distributed onto the different paths, depends on the critical values of time between two adjacent paths along the efficient frontier. In our example, there are three critical VTs defined by the path pairs A-B, B-C and C-D. The demand share of each efficient path is deduced from the given probability distribution function. In the figure below the distribution function is evaluated for the three values VT=vtcrit,A-B, VT=vtcrit,B-C and VT=vtcrit,C-D. The share P(A) of alternative A on the lowest cost level is: P(A) = G (VT = vtcrit,A-B) The shares of B, C and D are: P(B) = G (VT = vtcrit,B-C) - P(A) P(C) = G (VT = vtcrit,C-D) - G(VT=vtcrit,B-C) P(D) = 1 - G (VT = vtcrit,C-D) This allocation states, that trips, performed by travelers who are not willing to spend money on travel (VT0), up to trips with a VT <= vtcrit,A-B will definitely choose the cheapest path A. Traveler on the more wealthy side of the trip demand with VT >= vtcrit,C-D will choose the fastest and most expensive path D.
G(vt)
P(D) p(C)
100%
P(B)
50%
P(A)
0%
VTcrit A/B
VTcrit B/C
VTcrit C/D
vt
,OOXVWUDWLRQ
Path choice for initial loading

MODEL DESCRIPTION
User Model (PrT)
Within the TRIBUT assignment this kind of path choice is applied only once to provide an initial loading. This step which considers each o-d pair independently, is similar to an all or nothing assignment and provides an initial solution. But as travel time on network objects, i.e. links and nodes, is capacity restraint-dependent, the path choice for one specific o-d pair depends on the path choice of all other o-d pairs. This leads to an iterative procedure attempting to find a solution, where all o-d pairs are in equilibrium state.
$GMXVWPHQW RI 3DWK &KRLFH 'XULQJ WKH (TXLOLEULXP ,WHUDWLRQ

An o-d pair is in an equilibrium state, if the following conditions are accomplished: Path search does not find another efficient path for the o-d pair. The flow-dependent travel time is identical for all efficient paths on the same cost level. The shares of demand on the different cost levels correspond to the VTdistribution.
TRIBUT performs a path search at the beginning of each new assignment iteration. If new paths are found which are located on the efficient frontier or to the left of it, they are added to the set of existing efficient paths. VISUM stores all path-information (itinerary, used network objects, allocated demand), so that complete path information is available during the whole assignment process as well as after assignment for post-assignment analysis. If new paths are found and stored for a specific o-d pair, the o-d demand must be reallocated within the resulting new efficient frontier to obtain a new equilibrium state. This is achieved in two steps: INTRA-Level-Balancing: reallocation of demand among the paths of the same cost level of the o-d pair and recalculation of flow-dependent time on the associated paths and their links, INTER-Level-Balancing: reallocation of demand between the paths of two adjacent cost levels and recalculation of flow-dependent time.
It is important to note, that during the balancing process of shifting demand from one efficient path to another, path travel time changes, as it depends on the traffic volumes. So during balancing, the shape of the efficient frontier is modified and the critical values of time change. The figure below illustrates an efficient frontier with three paths A, B, C. If a new path N is found which shows the same cost level as the efficient path B, demand is shifted from B to N. As a consequence travel time tB and tN change. That way both paths will move to a point in the middle of their initial positions.
User Model (PrT)
MODEL DESCRIPTION
As a result the critical values of time for the adjacent cost levels will change. So the demand must be reallocated among all efficient paths and between the different cost levels. Note, that this simple case of adjustment only occurs if the paths A and C do not share links with the B or N, so that tA and tC are not affected.
&
% 1 $
,OOXVWUDWLRQ
Adjustment of the efficient front during INTRA-Level-Balancing
The figure on the next page presents a simplified flow chart of the TRIBUT assignment.
2-71
MODEL DESCRIPTION
User Model (PrT)
)ORZ FKDUW RI WKH HTXLOLEULXP LWHUDWLRQ

** INITIAL LOADING: ** FOR origins o := 1 ... N DO Perform MULTI-PATH-SEARCH to all destinations d := 1 ... N FOR all destinations d := 1 ... N DO Allocate o-d-trip demand on the efficient paths of o-d Store the efficient paths of o-d Compute flow dependent link times for all network objects of the efficient path set ** EQUILIBRIUM ITERATION: ** WHILE NOT all-od-in-equilibrium DO all-od-in-equilibrium := TRUE FOR origins o := 1 ... N DO Perform MULTI-PATH-SEARCH to all destinations d := 1 ... N IF new efficient path are found THEN o-in-equilibrium := FALSE Store paths WHILE NOT o-in-equilibrium DO o-in-equilibrium := TRUE FOR all destinations d := 1 ... N DO WHILE NOT od-in-equilibrium DO od-in-equilibrium := TRUE FOR all cost-levels of o-d DO INTRA-Level-Balance Compute link times for all network objects FOR all neighbor-cost-levels of o-d DO INTER-Level-Balance Compute link times for all network objects IF flow has been changed on any network object THEN od-in-equilibrium := FALSE o-in-equilibrium := FALSE all-od-in-equilibrium := FALSE
2-72
User Model (PrT)
MODEL DESCRIPTION
The flow-dependent travel time on a link is calculated at three points in this procedure: In the initial loading, after each origin computation. In the INTRA-Level Balance, when vehicles are shifted from one path to another within the same cost level. For each modified link volume, the actual link time has to be computed again. In the INTER-Level Balance, when vehicles are pushed from one cost level to another and shifted between the paths of those levels.
7ROO 6FKHPHV

VISUM allows to define linear and non-linear road pricing schemes. Linear toll is modeled as a toll value per road segment (link). To model classical toll schemes, where toll is typically linear to trip length and where toll is paid for the next road section at stations which are located at entry or exit points, a linear toll model is sufficient. In modern toll projects, more sophisticated systems of pricing are applied. Especially telematic techniques allow to design price schemes, where the price to drive from A to C via B may not be equal to the sum of A-B and B-C. These nonlinear toll schemes can be modeled within VISUM as a price matrix between motorway entries and exits.
6LPXOWDQHRXV 0XOWL&ODVV $VVLJQPHQW

VISUM provides multi-class assignment, where several demand classes with specific o-d matrices can be assigned simultaneously. The introduction of demand classes to the model is helpful in the case of group specific pricing for different vehicle types or travelers with different types of tickets (single riders, commuter pass holders). Additionally specific VT-distributions can be defined for each demand class thus leading to a more realistic composition of the entire demand and of its elasticity to pricing policies. An example of user classes for home-work-commuters, other private demand and professional demand is shown in ,OOXVWUDWLRQ .
2-73
MODEL DESCRIPTION
User Model (PrT)
1,00
0,75
0,50
home-work other private
0,25 &RVW 0 ,OOXVWUDWLRQ 10 20 30 40
professional
0,00
50
60
Multi-class VT-distributions
)LQGLQJ WKH SDUDPHWHUV vt DQG
Applying TRIBUT in a planning project, the definition of the VT-distribution, i.e. of the two distribution parameters vt and of the value of time distribution for different trip classes or unique ones for a global travel demand is one of the most crucial steps. In practice there are three ways to find the parameters: revealed preference surveys, stated preference surveys or macroeconomic calculus. The weakest but cheapest method is the macroeconomic calculus which for instance divides total work income of a society by the total work time in order to obtain a mean value of time for trips to work. Such an approach does not reflect real behaviour, e.g. the significant differences in the behavior of commuters in urban areas compared to long distance travelers. Secondly, this approach determines a PHDQ value of time, which is less appropriate than quantiles (medians). When toll is introduced into a society without revealed toll experience, usually stated preference methods are applied. In the stated preference interview different hypothetical situations with variation of time and cost are simulated to find the critical cost-time combination (transfer price), where the traveler changes his behaviour. Maximum likelihood estimation will determine the two logN-parameters from a stated or revealed preference sample. It has been found that persons can hardly imagine a toll situation as it is proposed in a stated preference interview if they are not used to toll in real life. Consequently, the standard deviation is mostly overestimated by the stated preference method.
2-74
User Model (PrT)
MODEL DESCRIPTION
The best method is to estimate the value of time on the basis of revealed preferences. This requires a toll road and pricing system, which operates at least three or four years prior to the survey, to ensure that the system has come to an equilibrium. Recently a revealed preference study has been carried out in the area of Marseille/France [6]. The method consisted of an o-d survey, measuring the shares of cars using the toll road or the alternative non-priced infrastructure and real travel time for each o-d at different day periods. The most important results are: Time saving was found to be the most explicative variable of the use of toll roads, no statistical effect was found for travel time deviations or road comfort. It was found that the median of the value of time is a very significant and stable value, even if different types of distributions are estimated. The logN parameters for the global demand were estimated by 10 Euro/h and = 0.66.
vt
= 57 FF/H
The different trip purposes show a less significant influence on the value of time parameters than the fact whether a traveler must pay the toll out of his own pocket or whether he gets the toll refunded for instance by his company.
6RPH $VSHFWV RI 7UDYHO 7LPH 0RGHOLQJ

As cost is not flow-dependent, it is a given model input. On the other hand, time is modeled by the help of flow-dependent functions and therefore represent a less certain input of the assignment model. But the quality of the forecasted volumes in toll projects depends largely on path time and related cost. Therefore the modeling of the flow-dependent time on links and nodes requires more attention than in ordinary planning projects without toll. The modeler has to consider especially the following aspects: For trips which originate or terminate outside the scope of the model, only a part of their path is covered by the model. Therefore it is not possible to evaluate the total travel time and thus it is not recommended to apply the same value of time distribution as for internal trips. Link and node flows that exceed capacity should be avoided. In this case capacity restraint functions do not produce realistic travel times. Especially if peak hours are modeled, the capacities of highly charged links need to be defined very carefully.
2-75
MODEL DESCRIPTION
User Model (PuT)
8VHU 0RGHO 3X7
To model PuT trips, VISUM provides three types of PuT-assignment procedures which differ in required input data, accuracy of results, and computing time: The WUDQVSRUW V\VWHPEDVHG SURFHGXUH uses a PuT-specific "all or nothing" assignment in which passengers select the fastest route without being constrained by line routes and timetables. The result provides an overview of the structure of travel demand for planning purposes ("ideal line network"). This procedure does not require any line network or timetables as input. The OLQHEDVHG SURFHGXUH is ideal for urban networks with short headways, where the co-ordination of the timetable need not be taken into account. The line-based procedure determines the transfer wait time at transfer stops from the mean headway of the following line. This assumption ensures short computing times even for large networks. The WLPHWDEOHEDVHG SURFHGXUH considers the exact timetable and is therefore the appropriate method for rural areas or train networks, where headways are long and the co-ordination of the timetable is important for the service quality. There are three variants of the timetable-based procedure. Procedure 1 and 2 are based on the same connection search algorithm, but differ in how they distribute travel demand onto connections during the connection split. The new procedure 3 uses a different approach, providing a larger amount of alternatives. The exact calculation of connections based on the timetable requires more computing time than the line-based procedure.
The PuT-assignment procedures are used to determine volumes: line volumes, link volumes, and the number of passengers who board, transfer or alight at stops, to calculate user-specific PuT-indicators: e.g. journey time, number of transfers, service frequency, as a timetable information system which provides information about the departure and arrival times of individual connections.
2-76
User Model (PuT)
MODEL DESCRIPTION

([DPSOH QHWZRUN
The different procedures are described below using an example (,OOXVWUDWLRQ ). Given the examples PuT-supply, the connections between "A-Village" and "X-City" are to be determined. The following assumptions apply: Access and egress times are not considered, that is, they are set to 0 minutes. The analysed time interval starts at 5:30 a.m. and ends at 7:30 a.m.. Travel demand between "A-Village" and "X-City" amounts to 90 trips (matrix file pub.fma). 33 % of travel demand, that is, 30 trips occur between 5:30 a.m. and 6:30 a.m., the remaining 67 % or 60 trips are distributed across the period between 6:30 a.m. and 7:30 a.m. (file pub.fga). O-D matrix: pub.fma
$OR * From To 5.30 7.30 * factor 1.00 * * Means of transport Nr 3 * 3 Public transport * 4 Private transport 100 200 90
Amount of trips: pub.fga

$ * TFrom TTo 5.30 7.30 $ 1 5.30 6.30 1 0 33 $ 100 1 200 1 $
7.30 67
-1 -1
,OOXVWUDWLRQ
O-D matrix and amount of trips for example
The example network is stored in the VISUM/example directory: example.ver pub.gpa pub.fma pub.fga pub.par version file graphic parameters file O-D matrix temporal distribution of travel demand assignment parameters
2-77
MODEL DESCRIPTION
User Model (PuT)
7LPHWDEOH
6.00
%XV
6.30
%XV
7UDLQ
7.00
7UDLQ %XV
7.30
7UDLQ
8.00
$9LOODJH 2ULJLQ
6WDWLRQ
%9LOODJH
;&LW\ 'HVWLQDWLRQ
/LQHV
$9LOODJH2ULJLQ
6WDWLRQ
;&LW\GHVWLQDWLRQ
7UDLQ
%XV
%9LOODJH
7LPHWDEOH RI EXV A-Village 6.10 Station 6.22 B-Village 6.42 X-City 6.55
6.55 7.07 6.27 7.40
7.25 7.37 7.57 8.10
7LPHWDEOH RI WUDLQ Station 6.25 X-City 6.41
7.05 7.21
7.45 8.01
&RQQHFWLRQV Departure 6.10 a.m., Arrival 6.55 a.m., ride time 45 min., 0 transfer Departure 6.10 a.m., Arrival 6.41 a.m., ride time 31 min., 1 transfer Departure 6.55 a.m., Arrival 7.40 a.m., ride time 45 min., 0 transfer Departure 7.25 a.m., Arrival 8.10 a.m., ride time 45 min., 0 transfer Departure 7.25 a.m., Arrival 8.01 a.m., ride time 36 min., 1 transfer ,OOXVWUDWLRQ PuT-supply of the example with connections from A-Village to XCity
2-78
User Model (PuT)
MODEL DESCRIPTION

,PSHGDQFH )XQFWLRQ ,QGLFDWRUV RI D &RQQHFWLRQ
Like PrT-assignment procedures the PuT-assignment procedures use an impedance function to determine the impedance of a connection from several indicators of this connection. In contrast to PrT, however, this impedance is used by some PuTprocedures not only for the connection search, but also to evaluate the connections prior to the connection split. Impedance can consist of time indicators and travel costs.

&RQQHFWLRQ ,QGLFDWRUV
The indicators of a connection can be divided into five categories: 1. Time indicators 2. Length indicators 3. Frequency indicators 4. Monetary indicators 5. Derived indicators Because there are usually numerous connections for one o-d pair, connection indicators are aggregated to relation indicators. Apart from the service frequency indicator which results from the number of connections, the following indicators are used on the level of connections as well as on the level of relations.
2-79
MODEL DESCRIPTION
User Model (PuT)
7LPH LQGLFDWRUV Inside VISUM, time indicators are administered in seconds. Dialogs for assignment parameters and indicator matrices files, however, show minutes as a unit. Indicator Access time (AT) Egress time (ET) Origin wait time (OWT) Transfer wait time (TWT) In-vehicle time (IVT) Definition Walk time from start address to origin stop Walk time from destination stop to destination address Wait time at origin stop Wait time between arrival and departure at transfer stops Time inside public transport vehicles including dwell time at stops
In-vehicle time by TSys In-vehicle time for a specific transport system, e.g. bus (TS) Walk time (WT) Journey time (JT) Walk time for transfer links Time from departure from start address (origin zone) until arrival at destination address (destination zone): JT = AT + OWT + IVT + TWT + WT + ET Ride time (RT) Time from departure from origin stop until arrival at destination stop: TAT = IVT + TWT + WT User-defined perceived journey time (PJT) ,OOXVWUDWLRQ Perceived journey time: PJT = f(AT, ET, OWT, TWT, RT, WT)
Time indicators [min]
2-80
User Model (PuT)
MODEL DESCRIPTION
/HQJWK LQGLFDWRUV Indicator Access distance (AD) Egress distance (ED) In-vehicle distance (IVD) In-vehicle distance TSys (DS) Walking distance (WD) Journey distance (JD) Definition Walking distance origin address origin stop Walking distance destination stop dest. address Travel distance inside public transport vehicles
by Travel distance inside vehicles of a specific public transport system Length of a transfer link between two transfer stops Journey distance between origin and destination zone: JD = AD + IVD + WD + ED
Ride distance (RD)
Distance between origin and destination stop: RD = IVD + WD
Direct distance (DD) ,OOXVWUDWLRQ
Direct distance between origin and destination zone
Length indicators [m]
)UHTXHQF\ LQGLFDWRUV Indicator Number of transfers (NT) Service frequency (SF) ,OOXVWUDWLRQ Definition Number of transfers [-] Number of connections [departures/time interval] between two zones
Frequency indicators
0RQHWDU\ LQGLFDWRUV Indicator Fare (FA) ,OOXVWUDWLRQ Definition Travel cost for one trip between origin and destination zone Monetary indicators [money units]
MODEL DESCRIPTION
User Model (PuT)
'HULYHG LQGLFDWRUV Derived indicators result from combinations of indicators listed above. Indicator Impedance (IMP) Journey speed (JV) Definition Impedance of connection = f (perceived journey time, fare) Speed calculated from journey distance and journey time between origin and destination zones [km/h] JV [km/h] = (JD [m] 1/1000) / (JT [min] / 60) Direct distance speed Proportion of direct distance and journey time between (DV) origin and destination zones [km/h] DDS [km/h] = (DD [m] 1/1000) / (JT [min] / 60) Proportional travel distance by TSys (PS) Equivalent journey time ,OOXVWUDWLRQ Transport system proportion of travel distance of connection. Indicator calculated according to formula specified by the user (see Chapter 7).
Derived indicators
2-82
User Model (PuT)
MODEL DESCRIPTION
$9LOODJH
%XV
6WDWLRQ ;&LW\ 7UDLQ
%XV
Connection 1 Used sequence of lines / route Access distance [m] Access time [min] In-Vehicle time [min] Transfer wait time [min] Egress distance [m] Egress time [min] Ride time [min] Journey time [min] Journey distance [m] Direct distance [m] Journey speed [km/h] Direct distance speed [km/h] Number of transfers [-] ,OOXVWUDWLRQ Bus1 300 3 45 0 500 5 45 53 27500 18385 31.1 20.8 0
Connection 2 Bus1, Train 300 3 28 8 500 5 36 44 20000 18385 27.3 25.1 1
Example of the connection indicators of a relation
2-83
MODEL DESCRIPTION
User Model (PuT)

3HUFHLYHG -RXUQH\ 7LPH
Perceived journey time, PJT, consists of weighted components of journey time: Perceived journey time PJT [min] = in-vehicle time + access time + egress time + walk time + origin wait time + transfer wait time + number of transfers )DF
,97
)DF )DF )DF )DF )DF )DF
$7
(7
:7
2:7
7:7
17
The perceived journey time is used for the line-based procedure and timetablebased procedure 2 and 3, to evaluate individual connections during the connection split. Weighting transfer frequency strongly, for example, results in passengers preferring minimum transfer connections.

)DUHV
VISUM can be used to calculate fares. The trip cost results from the ticket type and the distance travelled (distance-dependent tariff) or from the number of traversed tariff zones. In addition, supplements for the use of particular transport systems (e.g. InterCity supplement) may apply. These travel costs are calculated for every connection and can later be: used during connection split, listed in indicator files, used for calculating the line revenue.
2-84
User Model (PuT)
MODEL DESCRIPTION

7HPSRUDO 8WLOLW\
For the timetable-based assignment methods 2 and 3, the temporal utility of a connection is included as a further indicator in the definition of impedance. The temporal utility of a connection depends on: the desired departure time of passengers, which is indicated by the temporal distribution of passengers, the time difference departure,
T between provided time of departure and desired time
of
the tolerance with respect to deviations between the provided and the desired time of departure, which is indicated by the sensitivity to earlier or later departures.
This can be modelled so that the WHPSRUDO SRVLWLRQ of a connection also has an effect on its attractiveness. The temporal utility of a connection is highest for that interval in which the connection is placed, because then T = 0 applies. The higher T, the lower the temporal utility. In the timetable-based methods 2 and 3, the temporal utility is included in the impedance definition in different ways either by using a function N = f(T) or by using T directly. In both cases, the sensitivity towards early or late departure can be set by means of parameters. For both variants, the following holds: the shorter the period between the actual and the desired departure time, the higher the temporal utility and the lower its impedance. Example of determining T
6:00 7:00 8:00 Dep. 7:20 9:00
Distribution curve with hourly intervals T (6-7) = 7.20 7.00 = 20 min T (7-8) = 0 min T (8-9) = 8.00 7.20 = 40 min
2-85
MODEL DESCRIPTION
User Model (PuT)

,PSHGDQFH
In VISUM, connection impedances are considered when comparing different connections in a connection split (and partly also in the search). Impedance is described as a user-defined combination of various indicators. Various connection properties can thus be impeded or favoured. The general rule is: the lower the impedance of a connection, the higher its share of the traffic demand. Since the impedance used in the connection split of the timetable-based methods 2 and 3 depends on the temporal utility, it varies over time. The actual definition of impedance differs in the various assignment methods. In timetable-based method 3, two different approaches are used even within the calculation. An overview is given in the following table. All factors are freely adjustable and can also be set to zero. Method Timetable-based 3 search Timetable-based 3 split Timetable-based 2 search Timetable-based 2 split Definition of impedance IMP = JT )DF + NT )DF + TSysIMP )DF

IMP = PJT )DF + Tlate )DF

+ Fare )DF
+ Tearly )DF
IMP = JT + NT )DF IMP = PJT / U )DF + Fare )DF

where U = f(T) is the temporal utility Timetable-based 1 search Line-based search IMP = JT + NT )DF IMP = IVT + TWT )DF + NT )DF where TWT is 50% of the average headway of the lines, onto which the passenger transfers

Line-based split
IMP = PJT )DF + Fare )DF

2-86
User Model (PuT)
MODEL DESCRIPTION

'LVWULEXWLRQ PRGHOV
When determining the share of the travel demand that is assigned to a connection, the impedance is decisive. As described above, the impedance is generally defined as a function of time and fare indicators. This function can differ depending on the assignment method used. Denote by Pi the percentage of connection i in terms of the travel demand in the a time interval a. It is determined by including the impedance IMPi in a distribution a function and then calculating the XWLOLW\ Ui of the connection. In versions prior to version 7.5 VISUM always used the so-called Kirchhoffs law of distribution. Now there are various models available. The following approach applies to all models: 1. Impedance IMPi is converted to the XWLOLW\ Ui a a interval a: Ui = f(IMPi )
a a a a
of the connection i in the time

a
2. From this utility Ui the percentage of demand Pi is calculated as
Pia
:=
U ia
n j =1
Ua j
where n is the total number of connections. The models reveal differences in the functional relation f of impedance and utility. When the independence attribute (see 2.5.3.6) is used, this is also included in the a formula for calculating Pi .
2-87
MODEL DESCRIPTION
User Model (PuT)

.LUFKKRII 0RGHO
a a
In this case Ui = IMPi , so that
Pia
:=
IMP
a i
IMP
a j
where the sum is taken over all connections j, and serves as a parameter to describe the impedance sensitivity. In this distribution method, the UDWLRV of the various impedances are decisive. It does not matter, therefore, whether two connections have impedances of 5 and 10 minutes, for example, or 50 and 100 minutes the distribution is the same.

/RJLW 0RGHO
In this model, the GLIIHUHQFH rather than the ratio, between the impedances is used a -IMPia to calculate distribution. In this case Ui = e , so that
e Pi :=
a
IMP ia IMP ja
e
j
Parameter describes the sensitivity of passenger towards increased impedances. As in this case the differences rather than the ratios of the impedances are considered, it does not matter whether two connections have impedances of 5 and 10 minutes, for example, or 95 and 100 minutes.
2-88
User Model (PuT)
MODEL DESCRIPTION

%R[&R[ 0RGHO
This distribution model is based on the Box-Cox transformation. For 0, it is explained as follows:
x 1 if b ( x ) := log( x ) if
()
( ) a ( ) -b (IMPia) a i a
0 = 0.
a
When calculating the utility, b (IMP ) is included in the Logit model instead of IMPi , . The percentage Pi of the connection i in terms of the demand for i.e. Ui = e time interval a is then calculated as follows
Pi
:=
b ( ) ( IMP i a )
b ( ) ( IMP
a j
.
)
The importance of the Box-Cox model is illustrated by the two special cases below: UHVXOWV LQ WKH .LUFKKRII GLVWULEXWLRQ
(0) a
With parameter b (IMPi ) = log(IMPi ), so that the split becomes
Pi a =
log( IMP ia )
log( IMP ja )
IMP
j
a i
IMP
a j
which is precisely the Kirchhoff model. UHVXOWV LQ WKH /RJLW GLVWULEXWLRQ

(1) a a
With parameter b (IMPi ) = IMPi 1, so that the split becomes
Pi =
a
e
j
( IMP ia 1) ( IMP ja 1)
= e
IMP ia IMP ja
e
j
This is identical to the Logit distribution.
2-89
MODEL DESCRIPTION
User Model (PuT)

/RKVH 0RGHO
a 2 IMP i 1 a IMP a 2 IMP j 1 a IMP
In this model, the impedances are related to each other in an entirely different way:
e a Pi :=
e
j
a a j
Here IMP* := minj IMP is the smallest occurring impedance, and is again a parameter to control the impedance sensitivity. When calibrating, do not forget that is squared. In this case, the impedance of a connection is related to the minimum impedance, i.e. the relative difference from the optimum is measured. Due to this different approach, the Lohse model can be used as an alternative to Kirchhoff and Logit. It should be noted, that the Lohse distribution formula cannot be regarded as a special form of Box-Cox transformation.
2-90
User Model (PuT)
MODEL DESCRIPTION

&RPSDULVRQ RI WKH 'LVWULEXWLRQ 0RGHOV ,
In order to illustrate the effects of the four distribution models (Kirchhoff, Logit, BoxCox and Lohse), Figure shows three simple cases of a split between two alternatives, which can represent routes or connections: Example 1: Alternative 1 has an impedance of 5, alternative 2 an impedance of 10. Thus alternative 2 has a 5-unit higher impedance or a double impedance compared to alternative 1. Example 2: The impedance of example 1 is increased by 100 units, so that alternative 1 now has an impedance of 105 and alternative 2 an impedance of 110. This means that Alternative 2 thus has a 5-unit higher impedance, as in example 1; however, the impedance ratio is now 0.95 rather than 0.5. Example 3: The impedance of example 1 is multiplied by 10, so that alternative 1 now has an impedance of 50 and alternative 2 an impedance of 100. This now means that alternative 2 has a 50-unit higher impedance; the impedance ratio is 0.5 as in example 1.
The distribution results demonstrate that in the Logit model the GLIIHUHQFH of impedances is decisive, so that examples 1 and 2 result in the same distribution values. The Kirchhoff model, on the other hand, evaluates the UDWLR of the impedances and thus generates the same distribution values for examples 1 and 3. The Box-Cox model allows a FRPELQDWLRQ of Logit and Kirchhoff, which is also illustrated by the distribution values. It would seem that the Logit model cannot be recommended for practical use, because the basis for a passengers choice is different for short and long connections. In practice, it will certainly make a difference whether a passenger has to travel 5 or 10 minutes, for example, or 105 or 110 minutes. In the case of long journeys, the additional 5 minutes are not as important as in case of short trips. The weaknesses of the Kirchhoff model in example 3, where one can expect all passengers to chose alternative 1, are not relevant for the assignment, because connections that differ to such an extent would not be found in the search at all and would therefore not be real alternatives for the passenger.
2-91
MODEL DESCRIPTION
User Model (PuT)
1. Distribution for two alternatives with impedance 5 and 10 No. 1 2 IMP 5 10 Kirchhoff 94 % 6% Logit 78 % 22 % Box-Cox 86 % 14 % Lohse 100 % 0%
2. Distribution for two alternatives with impedance 105 and 110 No. 1 2 IMP 105 110 Kirchhoff 55 % 45 % Logit 78 % 22 % Box-Cox 62 % 38 % Lohse 51 % 49 %
3. Distribution for two alternatives with impedance 50 and 100 No. 1 2 IMP 50 100 Kirchhoff 94 % 6% Logit 100 % 0% Box-Cox 100 % 0% Lohse 100 % 0%
Model parameters Kirchhoff: Logit: Box-Cox: Lohse: )LJXUH =4 = 0.25 = 1, = 0.5 =4 Distribution values of the four distribution models (Kirchhoff, Logit, Box-Cox and Lohse) in the case of a split between two alternatives.
2-92
User Model (PuT)
MODEL DESCRIPTION

,QGHSHQGHQFH RI &RQQHFWLRQV LQ 7LPHWDEOHEDVHG $VVLJQPHQW
All distribution models presented above cannot, in their basic form, take into account interactions between different connections in a timetable-based assignment (2 and 3). However, ignoring this aspect can be a drawback. In order to model interactions, one defines functions wi, which describe the impact of other connections on a connection i. The range of values for wi is the interval [0,1]. If j has no impact on i, then wi(j)=0, if i and j are absolutely equal, then wi(j)=1, i.e. it is always wi(i)=1. The following quantities are used to calculate wi(j): the temporal proximity of the connections with regard to departure and arrival:
x i ( j) =
Depj Depi + Arr j Arri 2 y i ( j) := PJT PJT
the advantage of i over j in terms of the perceived journey time:

j i
the advantage of i over j in terms of the fare:
z i ( j) := F j F
Thus, wi is defined as follows:
x i ( j) w i ( j) := 1 s x
where
+ s y s y := s y
s | y i ( j) | +s y | z i ( j) | 1 c min 1, z , s s y z s + z = : s z
if if
if if
y i ( j) 0
y i ( j) < 0
and
sz
z i ( j) 0
z i ( j) < 0 .
s..>0 are internal parameters for controlling the influence areas of the three values. c is a constant that controls the absolute effect of the second factor and is userdefined within [0,1]. The first factor describes the temporal proximity of i and j. If the times are the same, then xi(j)=0, so that this factor equals one. If the time difference is wi(j)Vx, the expression vanishes zero and wi(j)=0. Thus, sx is the maximum temporal distance in which j can effect i.
2-93
MODEL DESCRIPTION
User Model (PuT)
The second factor lies between 1 (in case of absolute equality in the context of yi(j)=0 and zi(j)=0) and 1-c (when there is a significant difference between i and j). As with sx, sy+ or sy - is the maximum temporal advantage or disadvantage of i in which j can possibly have an impact. The same applies to sz with regard to the fare. The default setting is sy- = 2sy+ and sz- = 2sz+. As a result of this asymmetry, in the case of two connections with temporal proximity, the better is favoured, because its influence on the worse alternative is greater than the other way around. The following parameter settings apply: sx = 50 % of the average waiting time of a random passenger between the first and the last departure sy+ = sz+ = 30% of the average PJT in the total assignment period 30% of the average fare in the total assignment period
If no fares are available (i.e. Fi = 0 for all i), then sz=1 is set. The independence of a connection is now defined as follows.
Ind
:=
n j =1
1 1+
w i ( j)
n j =1, j i
w i ( j)
where n is the total number of connections.

'LVWULEXWLRQ 0RGHOV ZLWK ,QGHSHQGHQFH
If independence is used for a connection split, then this attribute must be integrated a in the distribution model. In the version described above, the utility Ui of a connection i was calculated per time interval a, and used to determine its percentage a in terms of the demand for the time interval. If independence is applied, Ui INDi a replaces Ui , i.e.
Pia =
U ia IND
n j =1
i j
IND Ua j
This linear dependence on the independence attribute ensures that k simultaneous, identical alternatives are treated as a single connection: According to the definition of IND, the independence of each of such k alternatives is precisely 1 / k (if no other connections with temporal proximity have an effect). $V D UHVXOW WKH WRWDO RI LWV ZHLJKWV LQ WKH GLVWULEXWLRQ LV HTXDO WR WKH ZHLJKW RI D VLQJOH QRQPXOWLSOLHG FRQQHFWLRQ RI WKH VDPH NLQG
User Model (PuT)
MODEL DESCRIPTION

&RPSDULVRQ RI WKH 'LVWULEXWLRQ 0RGHOV ,,
The parameters for the methods are chosen as follows: Indicator Kirchhoff Logit Box-Cox Lohse PJT formula IMP formula IND parameter Definition =4 = 0.25 = 1 and = 0.5 =4 PJT = RT + 2 TWT + 2 NT IMP = PJT + 4 fare c=1
Connection data that differ from the previous example are set in EROG W\SH. All assignment percentages are given. Example 1: Initial situation Connection data No. Dep Arr
1 2 3 10 30 50 30 50 70 PJT 20 20 20
Distribution without IND

Fare Kirch. Logit 3.00 33.3 3.00 33.3 3.00 33.3 33.3 33.3 33.3 BCox 33.3 33.3 33.3 Lohse 33.3 33.3 33.3
Distribution with IND

Kirch. Logit 33.3 33.3 33.3 33.3 33.3 33.3 BCox 33.3 33.3 33.3 Lohse 33.3 33.3 33.3
Example 2: Identical pair of connections with temporal proximity Connection data No. Dep Arr
1 2


Fare Kirch. Logit 3.00 25 3.00 25


Kirch. Logit 33.3 16.7

PJT 20 20

BCox 25 25

Lohse 25 25

BCox 33.3 16.7

Lohse 33.3 16.7

10 30

30 50

25 25

33.3 16.7

50
70
20
3.00 25
25
25
25
33.3
33.3
33.3
33.3
2-95
MODEL DESCRIPTION
User Model (PuT)
Example 3: Identical pair of connections with high temporal proximity Connection data
No. Dep Arr 1 2 3 4 10 30


Fare Kirch. Logit 3.00 25 3.00 25 3.00 25 3.00 25 25 25 25 25 BCox 25 25 25 25 Lohse 25 25 25 25

Kirch. Logit 32.7 17.3 17.3 32.7 32.7 17.3 17.3 32.7 BCox 32.7 17.3 17.3 32.7 Lohse 32.7 17.3 17.3 32.7
PJT 20 20 20 20
30 50

50
70
Example 4: Identical pair of connections with high temporal proximity (conn. 3 now includes transfer) and higher fare Connection data
No. Dep Arr 1 2 3 4 10 30 32 50 30 50 47 70 PJT 20 20 20 20

Fare Kirch. Logit 3.00 25.9 3.00 25.9


BCox 26.2 26.2 21.3 26.2
Lohse 25,1 25,1 24.6 25,1
26.7 26.7 19.8 26.7
22.3
3.00 25.9
Example 5: Differing connections with moderate temporal proximity Connection data No. Dep Arr
1 2 3 4 10 30 32 50 30 50


Fare Kirch. Logit 3.00 23.5 3.00 23.5 3.30 29.6 3.00 23.5 21.9 21.9 34.3 21.9 BCox 22.8 22.8 31.5 22.8 Lohse 24.6 24.6 26.1 24.6

PJT 20 20 17 20
70
The fact that, without IND being applied the connections 1, 2 and 4 have WKH VDPH QXPEHU RI SDVVHQJHUV LQ DOO FDVHV shows, that the interaction between different alternatives ought to be taken into account. In becomes apparent that better results are then achieved with all distribution models.
2-96
User Model (PuT)
MODEL DESCRIPTION

7UDQVSRUW V\VWHPEDVHG $VVLJQPHQW
The transport system-based procedure does not differentiate between individual PuT lines. The procedure only considers links of a basic network with their respective travel times. The basic network can consist of all roads and rail links of the network or only those links which are served by lines.
From the links of this basic network a graph is constructed which forms the basis for a best-route search. Because individual lines are not distinguished, transfer stops with their respective transfer times cannot not be included in the search. It is possible, however, to include transfer times between different transport systems (transfer penalties for transport system transfers, e.g. between bus and train).

5RXWH VHDUFK Search for the route with lowest impedance for each O-D pair. The impedance of a route consists of the travel times of traversed links, the transfer penalty for every transport system transfer and node-specific transfer penalties for stops.
For links which may be used by several PuT-transport systems with different travel times, the shortest travel time is used. 5RXWH YROXPHV The total demand of an O-D relation is assigned to the route with the lowest impedance. The transport system-based procedure carries out exactly one best-route search for every O-D pair.
2-97
MODEL DESCRIPTION
User Model (PuT)

([DPSOH
For the PuT-service in the example (,OOXVWUDWLRQ ), the procedure determines the following shortest route given a transfer penalty of 10 minutes for the transfer from bus to train: from A-Village to station with "Bus" transport system - 12 minutes, from station to X-City with "Train" transport system - 16 minutes.
With a 10-minute transfer penalty, this results in a ride time of 38 minutes. All 90 trips from A-Village to X-City are assigned onto this route. This results in the volumes shown in ,OOXVWUDWLRQ .
A-Village

Station

X-City

,OOXVWUDWLRQ
B-Village
Network volume for transport system-based assignment (10minute transfer penalty, parameters file V\VSDU).
From a transfer time of 18 minutes onward the bus is used instead of the train for the section between the station and X-City (,OOXVWUDWLRQ
2-98
User Model (PuT)
MODEL DESCRIPTION
A-Village

Train
X-City

,OOXVWUDWLRQ
B-Village

Network volume for transport system-based assignment (transfer penalty 18 minutes, parameters file V\VSDU).

(YDOXDWLRQ RI WKH 3URFHGXUH $UHDV RI $SSOLFDWLRQ
The transport system-based procedure is characterised by the following features: The timetable (service frequency, transfer wait times) is not considered. Unrealistic route choice caused by frequent transfers within a transport system. Lines of one transport system which run in parallel but have different travel times (e.g. bus 1 and bus 2) can only be represented by a mean travel time. The journey time or ride time can be estimated if PuT-lines have short headways. Number of transfers, transfer wait time, and service frequency cannot be calculated.
The assignment procedure based on transport systems is recommended for a first draft of a new line network. The procedure calculates the shortest routes (minimum time required) which are then charged with the travel demand. The resulting link volumes represent the passengers "desired line network". The volumes resulting from the assignment procedure based on timetable or on lines will differ significantly from the results calculated by the assignment procedure based on transport systems. Under no circumstances should a timetable-based or linebased calculation be replaced by a transport system-based procedure.
2-99
MODEL DESCRIPTION
User Model (PuT)

/LQHEDVHG $VVLJQPHQW
The line-based procedure models each line through a sequence of stops (line route), through the running times between the stops, and through the headway of the line. Lines with no fixed-rhythm headway are described by their mean headway. This procedure does not explicitly calculate a transfer time but assumes that the transfer time depends on the headway. This means, the co-ordination of the timetable is not considered. Usually one assumes that the wait times at the boarding stop or at transfer stops is equal to half of the lines headway. The line-based assignment procedure encompasses three steps: route search, route choice, and route split. The first step searches for possible paths between two traffic zones. These paths do not represent connections, but routes, because the search procedure does not consider the exact timetable. The second step compares the individual routes and deletes routes which have relatively long journey times. The third step evaluates the remaining routes and assigns the trips of the O-D-matrix to those routes.

5RXWH VHDUFK
Applying a shortest-path algorithm, the shortest route between two traffic zones is calculated. The impedance for each route considers access and egress times as well as the running times between stops. Every transfer increases the impedance with a fixed transfer penalty [min] and with a weighted mean transfer time which depends on the mean headway (mHead) of the following PuT line and on a weighting factor Fac mean transfer time = Fac mHead mHead = time interval/service frequency within time interval.
For different transfer penalties and different weighting factors, different routes may be calculated. According to user-defined preferences, the shortest-path algorithm may be run several times with different penalties and weighting factors in order to calculate not just one but several routes. Each route between two traffic zones consists of a sequence of n route sections. Each route section describes a part of a route which is either a walking link or does not require any transfers. The first and last route section of a route is always a connector.
2-100
User Model (PuT)
MODEL DESCRIPTION
Route section Origin node 1 2 ... n-1 n Zone i Boarding stop Transfer stop Transfer stop Alighting stop
Destination node Boarding stop Transfer stop Transfer stop Alighting stop Zone j
Line Connector Line A Line B Line C Connector
To consider alternative lines, for example parallel lines, the procedure examines for each route section, whether there are alternative lines which serve this route section without transfer. For each alternative line a new route section is generated. Through the combination of all route sections of a route, new routes can be created which have the same transfer stops but use different lines (,OOXVWUDWLRQ ). All routes generated by the route search are considered during subsequent route choice.
Line A Line C
Stop1
Stop2
Line B Line D
Stop3
Route 1: Route 2: Route 3: Route 4: ,OOXVWUDWLRQ
Line A Line A Line B Line B
Line C Line D Line C Line D
Combination of route sections for route Stop1
Stop3

5RXWH FKRLFH
All routes which were calculated in the route search are evaluated before route split in order to delete extremely unattractive routes. A route between two traffic zones will be deleted if or transfer frequency of route > minimum transfer frequency + constant impedance of the route > impedance of the shortest route factor + constant
The impedance is calculated with the route split parameters.
2-101
MODEL DESCRIPTION
User Model (PuT)
5RXWH VSOLW

The route split evaluates all remaining routes by means of an impedance function. The impedance function contains the perceived journey time, PJT, and the fare. Imp = PJT )DF
3-7
+ Fare )DF
)DUH
The perceived journey time, PJT, has the unit "Minutes" and consists of the following times: Perceived journey time, PJT [min] = in-vehicle time )DF ^ $GG9Q` + access time )DF + egress time )DF + walk time )DF + origin wait time )DF + transfer wait time )DF + number of transfers )DF + node-specific transfer penalty )DF
,97 $7 (7 :7 2:7 7:7 17 12'(
The mean wait time at the origin stop and the mean transfer wait time depend on the mean headway (mHead) of the PuT-line the passenger boards at the origin or at the transfer stop: mean wait time at origin stop = A (mHead) ,
E E
mean wait time at transfer stop = A (mHead) . with A = 0.5 and E = 1, the wait time is assumed to be half of the headway with A = 1.5 and E = 0.5 we get a root function which assumes for the wait time at origin stops that passengers have a better knowledge of the timetable when headways are long. For the wait times at transfer stops these values assume a co-ordinated timetable for lines with long headways.
Journey time can be multiplied by AddVal_Subline data in order to model saturation (availability of seats) or further details (e.g. the level of comfort). The distribution of the travel demand to the different routes depends on the impedance of the routes and is calculated using one of the distribution models (Kirchhoff, Logit, Box-Cox, Lohse) The factor describes the impedance sensitivity of passengers. A high value for this factor means that routes with lower impedance are more likely to be used.
2-102
User Model (PuT)
MODEL DESCRIPTION

([DPSOH
For the PuT-service of the example (,OOXVWUDWLRQ ), the line-based procedure determines the following origin wait times (OWT) and transfer wait times (TWT) for the analysed interval from 5:30 a.m. to 7:30 a.m. (120 minutes): Previous line Walking Bus 1 Bus 1 Stop A-Village Station Station Next line Bus 1 Bus 1 Train Mean headway 120/3 = 40 min 120/2 = 60 min 120/2 = 60 min Wait time 40 = 20 0 60 = 30
3 departures in analysed interval (6.10, 6.55, 7.25) from A-Village 2 departures in analysed interval (6.22, 7.07) from station 2 departures in analysed interval (6.25, 7.05) from station
5RXWH VHDUFK To determine the following routes between A-Village and X-City Route 1 (bus 1, no transfer) and Route 2 (bus 1 and train, 1 transfer)
with the route search, two best-route searches with different transfer penalties and weighting factors for the transfer wait time must be carried out. A weighting factor of 1.0 significantly increases impedance of the second route because of the transfer wait time of 30 minutes, so that route 1 is the shorter route. A weighting factor of 0.2, on the other hand, decreases the influence of the transfer wait time to such an extent that route 2 now has lower impedance. OWT 7UDQVIHU SHQDOW\ Route 1 20 min Route 2 20 min 7UDQVIHU SHQDOW\ Route 1 20 min Route 2 20 min IVT TWT Impedance
PLQ ZHLJKWLQJ IDFWRU IRU WUDQVIHU ZDLW WLPH 45 min 0 min 20 + 45 + 1.00 12+16 min 30 min
+ 02 =
20 + 28 + 1.030 + 12 = 80 20 + 45 + 0.20 + 02 = 65
PLQ ZHLJKWLQJ IDFWRU IRU WUDQVIHU ZDLW WLPH 45 min 0 min 12+16 min 30 min
20 + 28 + 0.230 + 12 =
2-103
MODEL DESCRIPTION
User Model (PuT)
5RXWH VSOLW To evaluate both routes via the impedance, the following assumptions may apply: Imp = PJT 1.0 + Fare 0.0 mean origin wait time = mHead mean transfer wait time = mHead perceived journey time PJT = in-vehicle time + access and egress time + walk time + origin wait time + transfer wait time + transfer frequency 1.0 1.0 1.0 1.0 1.0 2.0
In this way, the following impedances, Imp, are calculated for routes 1 and 2: Route 1 Origin wait time Access and egress time, walk time In-vehicle time Transfer wait time Transfer penalty Imp = PJT 20 min 0 min 45 min 0 min 0 2 = 0 min 65 min Route 2 20 min 0 min 12 + 16 = 28 min 30 min 1 2 = 2 min 80 min
From the impedances Imp1 and Imp2, the following percentages P1 and P2 result according to Kirchhoff's Law. They describe the distribution of travel demand onto both routes (quantity M1 and M2). The distribution is influenced by the potential factor, , which determines impedance sensitivity (,OOXVWUDWLRQ ). For practical purposes, the potential factor usually lies between 3 and 4. 1 2 3 4 Imp1 Imp2 65 65 65 65 80 80 80 80 (Imp1)- 1.5410-2 2.3710-4 3.6410-6 5.6010-8 (Imp2)- 1.2510-2 1.5610-4 1.9510-6 2.4410-8 (Imp-) 2.7910-2 3.9310-4 5.5910-6 8.0410-8 P1 0.55 0.60 0.65 0.70 P2 0.45 0.40 0.35 0.30 M1 M2 50 54 59 63 40 36 31 27
,OOXVWUDWLRQ
Distribution of travel demand (90 trips) onto both routes for different potential factors using Kirchhoffs Law
2-104
User Model (PuT)
MODEL DESCRIPTION
,OOXVWUDWLRQ shows the volume plot for potential factor =1.
A-Village

Station

X-City

,OOXVWUDWLRQ
B-Village

Volume for line-based assignment (potential factor = 1, example parameter file OLQHSDU).
The indicators for the relation A-Village to X-City are shown by ,OOXVWUDWLRQ . These indicators are mean indicators of both routes which consider the number of passengers of each route. Since access and egress time are equal to 0 min, travel time and journey time have the same value. Route Passengers Passengers in-vehicle (=1) time 50 40 90 50 45 min 40 28 min 3370 min 3370/90 = 37.4 min Passengers transfer wait time 50 0 min 40 30 min 1200 min 1200/90 = 13.3 min Passengers ride time 50 45 min 40 58 min 4570 min 4570/90 = 50.7 min Passengers number of transfers 50 0 40 1 40 40/90 = 0.4
1 2 Total mean indicator ,OOXVWUDWLRQ
Mean indicators for line-based assignment ( = 1)
2-105
MODEL DESCRIPTION
User Model (PuT)

6HUYLFH IUHTXHQF\ LQGLFDWRU
Using the assignment procedure based on lines, the indicators service frequency (SF) and transfer wait time (TWT) can only be estimated, since the service frequency is an input parameter for the assignment procedure which defines the mean headway (mHead) and thus the transfer wait time. TWT = factor mHead = factor time interval / SF per interval For service frequency estimation, the service frequency is modeled as a flow problem. Service frequency results from the service frequency of those lines limiting the maximum flow. If necessary, service frequency has to be reduced to selected lines, which may occur if not all combinations of lines form realistic connections in terms of travel time, thus not meeting the route choice prerequisites. Case 1: Considers all combinations of lines
max. Flow = 11
/LQH$
/LQH&
SF = 10 RT = 30
SF = 1 RT = 10
top 1
/LQH%
Stop 2
SF = 6 RT = 18 LLQH' SF = 10 RT = 22
Stop 3
Case 2: Considers only those combinations of lines with ride time < min. ride time 1.5 (Route choice settings)
max. Flow = 7
/LQH$
/LQH&
SF = 1 RT = 30
SF = 1 RT = 10
top 1
/LQH%
Stop2
SF = 6 RT = 18 LLQH' SF = 6 RT = 22
Stop3
Connection Line A + Line C: Line A + Line D: Line B + Line C: Line B + Line D:
Ride time 40 min 52 min 28 min 40 min
SF 1 10 1 6
Consider connection, if ride time < min. ride time 1.5
reduced SF for A and D
,OOXVWUDWLRQ
2-106
Service frequency indicator for line-based assignment

User Model (PuT)
MODEL DESCRIPTION

(YDOXDWLRQ RI WKH SURFHGXUH DUHDV RI DSSOLFDWLRQ
The line-based procedure is characterised by the following features: The procedure determines several low-impedance routes where the transfer wait time is taken into account via service frequency, that is determined from mean headway by a rough estimation. Co-ordination of the timetable is not taken into account. Transfer frequency, journey time or ride time can be estimated with sufficient accuracy if all lines have short mean headways. Transfer wait time and service frequency are input values and thus can only be roughly estimated. For most PuT-networks there is a considerable reduction of computing time for the line-based procedure compared with the timetable-based procedure, this is especially the case of networks with regular headways (fixed-time rhythm). In networks in which many lines consist of only one trip, however, time savings are low. Since the mean origin wait time and the mean transfer wait time are calculated from the mean headway of a subline, the procedure only produces meaningful results if the sublines have a timetable which does not only contain one single vehicle trip, but many vehicle trips, preferably with rhythms. Because the line-based procedure does not take the co-ordination of the timetable into account, the procedure is suited for public transport planning in urban areas, particularly if the current state (exact timetable is available) is to be compared with scenarios for which no exact timetables yet exist. This procedure is not suited to planning supply in rural areas or for long distance transport, because in these cases long mean headways occur, and it is an elementary planning task to provide connections.
2-107
MODEL DESCRIPTION
User Model (PuT)

7LPHWDEOHEDVHG DVVLJQPHQW
A search method is called WLPHWDEOHEDVHG if all trips on PuT lines are taken into account with their precise departure and arrival times. Timetable-based methods are applicable to assignments and the calculation of indicators, when a line network plan and a detailed timetable are available for the PuT supply analysed. They take the coordination of the timetable into account and thus ensure very precise results of the indicator calculation. The timetable-based method 3 calculates connections by means of a so-called Branch & Bound algorithm. In order to do this, a search tree of suitable partial connections is generated for each origin zone. In that tree, all sufficiently suitable connections from this origin zone are stored. This means that, not only the best connection is found for a relation, but a large number of good connections. In this way, a very selective distribution of traffic demand is possible. It is assumed in the search that the passengers have timetable information available and choose their access time according to the departure on the first PuT line. During the search, the user can influence the kind of connections found in different ways by means of a search impedance. When choosing a connection, the connections yielded by the search algorithm are re-analysed by means of general criteria as to whether some of them are of a significantly lower quality and can thus be deleted. In the connection split, the demand is distributed to the remaining alternatives based on one of the models described above. The independence of connections can be taken into account if required.

&RQQHFWLRQ VHDUFK
For every o-d relation, not only is the best connection found for a given time but several suitable connections. A search impedance is used in order to evaluate the quality of connections. For all (partial) connections found in the search, the search impedance is calculated using the following equation: SearchIMP = JT )DF
-7
+ NT )DF
17
+ ImpTSys )DF
,PS76\V
In addition to the travel time and the number of transfers, the equation includes fares classified on the basis of the transport system in ImpTSys, i.e. the influence of fares can even be taken into account during the search.
2-108
User Model (PuT)
MODEL DESCRIPTION
For the evaluation of a newly found (partial) connection to a target or an interim node, the following rules apply: The new partial connection is deleted if search impedance of the connection > minimum search impedance factor + constant, or journey time of the connection > minimum journey time factor + constant, or transfer frequency for the connection > constant. minimum transfer frequency +
These rules ensure that inconvenient partial connections can be eliminated while the search is progressing. It is possible to specify an upper limit for the number of transfers in a connection.

&RQQHFWLRQ FKRLFH
The connection choice procedure evaluates and compares all connections in order to identify and delete less attractive ones. Only convenient connections are presented to the passenger in a connection split. In order to exclude inconvenient connections, the following exclusion rules are applied in turn: search impedance of the connection > minimum search imp. factor + constant (no limitations) journey time of the connection > minimum journey time factor + constant (unless the connection is optimal with respect to the number of transfers) transfer frequency for the connection > minimum transfer frequency + constant (unless the connection is optimal with respect to the travel time)
The factors and constants are user-defined.
2-109
MODEL DESCRIPTION
User Model (PuT)

&RQQHFWLRQ VSOLW
The connection split distributes the trips of a relation onto the found connections. In order to do this, the connection impedances are calculated; they include the perceived journey time PJT, the fare and the temporal utility of the connection. These impedances serve as an input to the distribution models for calculating the shares of the connections in the travel demand. Optionally, the independence can be included in the distribution rule. 3HUFHLYHG MRXUQH\ WLPH 3-7 RI D FRQQHFWLRQ PJT [min] + in-vehicle time + access time + egress time + transfer walk time + origin wait time + transfer wait time + number of transfers )DF )DF )DF )DF )DF )DF )DF
,97 $7 (7 :7 2:7 7:7 17
^ 6/LQ$9 6/LQ$9 6/LQ$9`
The origin wait time, OWT, can be determined from the service frequency of all connections with the following equation: OWT = A (assignment time interval/service frequency) . With A = 0.5 and E = 1, the origin wait time corresponds to half the average headway. With A = 1.5 and E = 0.5, a root function is created which assumes that passengers have better knowledge of timetables in the case of low service frequency.
E
The origin wait time is the same for all connections of an O-D pair. Including them in the PJT is therefore just like a constant supplement. The output of OWT in an indicator matrix can be important for the network analysis. Furthermore it is possible to model known utilisation effects (e.g. no seat guarantee) or other aspects (e.g. comfort) of a line by multiplying the travel time with a subline AddValue SLinAV.
2-110
User Model (PuT)
MODEL DESCRIPTION
7HPSRUDO XWLOLW\ RI D FRQQHFWLRQ In the timetable-based method 3, the temporal utility of a connection is modelled as follows: a early = the amount of time that connection i departs earlier than desired for Ti departure; equals zero, if i departs ZLWKLQ a or DIWHU interval a. Ti = the amount of time that connection i departs later than desired for departure ; equals zero, if i departs ZLWKLQ a or EHIRUH interval a. FacTearly + Ti FacTlate = temporal distance between connection i Ti and interval a; the first factor controls the early sensitivity, the second the late sensitivity of passengers. This temporal distance is included as a further summand in the definition of impedance, in order to impede lower utilities.
a early a late a late
&RQQHFWLRQ LPSHGDQFH DQG GLVWULEXWLRQ RI WULSV The impedance of a connection i used in the connection split in a time interval a is calculated as follows
Imp
a i
= PJT
T
i
i a early
Fac Fac
PJT T early
+ Fare + Ti
a late
Fac Fac
Fare T late
By including these impedances in a distribution model (Kirchhoff, Logit, Box-Cox, Lohse), VISUM then determines the utility of a connection in a given time interval and ultimately its percentage of the demand for this interval. The independence can also be included in the distribution rule, if required.

([DPSOH
The effect of the connection split for timetable-based method 3 is shown with the results of the connection search including a 10-minute transfer penalty. This search gives the five connections shown in Figure . The table displays the corresponding indicators journey time (JT), transfer wait time (TWT) and number of transfers. The perceived journey time results from the weighted sum of these indicators:
2-111
MODEL DESCRIPTION
User Model (PuT)
Conn i Dep. 1 2 3 4 5 )DF

7:7
JTi
TWTi NTi PJTi = JTi + TWTi )DF 1 0 0 1 0
7:7
+ NTi )DF
17
6:10 6:10 6:55 7:25 7:25
28 min 3 min 45 min 0 min 45 min 0 min 28 min 8 min 45 min 0 min
17
28 + 3 2 + 1 2 = 36 45 + 0 2 + 0 2 = 45 45 + 0 2 + 0 2 = 45 28 + 8 2 + 1 2 = 46 45 + 0 2 + 0 2 = 45
= 2, )DF
=2
)LJXUH
Result of connection search (transfer penalty 10 min, parameter file timetable3-1.par)
)LJXUH shows the connection impedances. As T depends on the desired departure time of the passengers, each period of travel demand results in a different impedance. Thus, the impedances of the first two connections are lower in the first interval, whereas those of the last three connections are lower in the second interval. The impedance definition is set to IMPi = PJTi 1.0 + Ti Conn. i 1 2 3 4 5 )LJXUH 6:10 6:10 6:55 7:25 7:25 Dep. Ti
1 a a early
1.0 + Ti Ti
2
a late
1.0
1
IMPi
IMP i
5:30-6:30
6:30-7:30
5:30-6:30
6:30-7:30
0 min 0 min 25 min 55 min 55 min
20 min 36 + 0 = 36 36 + 20 = 56 20 min 45 + 0 = 45 45 + 20 = 65 0 min 45 + 25 = 70 45 + 0 = 45 0 min 46 + 55 = 101 46 + 0 = 46 0 min 45 + 55 = 100 45 + 0 = 45
Temporal distances T and impedances IMP of the connections for the two intervals of travel demand
2-112
User Model (PuT)
MODEL DESCRIPTION
A distribution rule (here: Kirchhoff with = 3) is then used to calculate the shares Pi of the individual connections. The independence is ignored in this formula. As shown in Figure , all five connections are assigned non-zero percentages of the travel demand of the two intervals. Conn Dep. i 1 2 3 4 5 )LJXUH 6:10 6:10 6:55 7:25 7:25 Pi
1
Pi
Trips Mi
Trips Mi
Trips
5:30-7:30
5:30-6:30
6:30-7:30
5:30-6:30
6:30-7:30
57% 30% 7% 3% 3% 100%
13% 8% 27% 25% 27% 100%
30 0.57 = 17 30 0.30 = 9 30 0.07 = 2 30 0.03 = 1 30 0.03 = 1 30
60 0.13 = 8 60 0.08 = 5 60 0.27 = 16 60 0.25 = 15 60 0.27 = 16 60
25 14 18 16 17 90
Distribution of trips for the connections (Kirchhoff, = 3)
This results in the volume diagram shown in Figure :

A_village T
90
Station
X_city
41
B_village
49 )LJXUH Network volume for timetable-based assignment 3 (parameter file timetable3-1.par)
2-113
MODEL DESCRIPTION
User Model (PuT)

(YDOXDWLRQ RI WKH 3URFHGXUH DUHDV RI DSSOLFDWLRQ
The timetable-based method 3 is characterised by the following features: The procedure calculates all suitable connections throughout the entire search period. The search can be influenced by means of a search impedance. The actual transfer wait time, and thus the coordination of the timetable, is taken into account. All indicators in the search period can be calculated. It is possible to search for both at the same time, either for shortest connections or for connections with the least number of transfers. The decision model for the connection split describes the actual decision behaviour of the passengers realistically, because a passenger usually has some information on the PuT supply (connection search) and then makes his choice from the connections offered (connection split). The procedure is suitable for the analysis of a period (whole day or several hours). When performing a search at a specific WLPH (e.g. in the case of a graphical route search), the shortest-path algorithm of timetable-based method 2 is recommended.
2-114
User Model (PuT)
MODEL DESCRIPTION

VISUM provides two other timetable-based assignment procedures. Different from procedure 3, these procedures use the "best" route search strategy on the basis of the particular time of departure and the time of arrival. A shortest-path algorithm based on these data calculates the best connection between two traffic zones for a particular departure time. For different times of departure, different best connections may be calculated which may differ by the used PuT lines and/or transfer stops. To determine all "best" connections within the analysed time interval the shortest-path algorithm is performed several times for all possible departure times within the assignment time interval. Since in some cases several connections are possible for a given time, the timetable-based search procedure requires a definition of "best connection". For this purpose VISUM provides an impedance function which increases the impedance of a connection for each transfer through transfer penalty. A low penalty has the result that connections which take the least time are favoured, while a high transfer penalty gives priority to connections with a lower number of transfer. The timetable-based assignment procedures 1 and 2 are based on this connection search procedure, but differ in the connection split. Timetable-based procedure 1 assumes that passengers are not familiar with timetables and make their way to the origin stop more or less randomly. Having reached the origin stop they use the next connection (e.g. leaves 7:00 a.m., arrives 7:45 a.m.) which is offered. A faster connection which, for example, leaves an hour later, is not considered since the passenger has already made his way to the stop and, therefore, will reach his destination sooner than with the later, but faster connection. Timetable-based procedure 2 assumes that passengers have the knowledge about PuT-supply in time, e.g., from a passenger information system. The passengers select a connection from a set of possible connections. Their choice is influenced by the service indicators of each connection and by the utility of the departure time. Thus e.g. a slow connection may be attractive for a student, who has to be at school at 8.00 am (e.g. departure at 7.00 am., arrival at 7.45 am.), though faster connections (8.00 - 8.30) are provided later in the morning.
2-115
MODEL DESCRIPTION
User Model (PuT)

&RQQHFWLRQ VHDUFK
Determination of all possible times of departure for trips which originate in traffic zone i. The departure times result from the departure times of PuT-lines at stops which can be reached from zone i via a connector. In the example, the start times correspond with the departure times of bus line 1 from A-Village (6.10, 6.55, 7.25), because A-Village is only serviced by one bus line and an access time of 0 minutes is assumed.
For every start time, a shortest-path search is carried out which searches for the "best" route from traffic zone i to traffic zone j. The search procedure identifies the route with the lowest impedance as the best route. The impedance of the route is measured in "minute" units and consists of the following times: Access time [min] In-vehicle time [min] Transfer walk time between two transfer stops [min] Transfer wait time [min] Egress time [min] Number of transfers [-] transfer penalty [min]
This lowest impedance route represents a connection, because the used sequence of lines and the exact departure and arrival times at boarding stop, transfer stops, and alighting stop are known.

&RQQHFWLRQ FKRLFH
Similar to procedure 3, the two following rules are used to delete connections with excessive journey time or a relatively high number of transfers: or Number of transfers of connection > minimum number of transfers + constant. Journey time of connection > minimum journey time factor + constant
2-116
User Model (PuT)
MODEL DESCRIPTION

&RQQHFWLRQ VSOLW
&RQQHFWLRQ VSOLW distributes the trip demand of a relation onto selected connections. For this purpose impedance is calculated, which reflects the perceived journey time, PJT, the fare F, and the temporal utility of the connection. These impedances are regarded by the distribution model, when demand shares are calculated and distributed to the connections. Furthermore also the independence of a connection can be included. 3HUFHLYHG MRXUQH\ WLPH 3-7 RI D FRQQHFWLRQ PJT [min] + in-vehicle time + access time + egress time + transfer walk time + origin wait time + transfer wait time + number of transfers )DF )DF )DF )DF )DF )DF )DN
,97 $7 (7 :7 2:7 7:7 17
^ 6/LQ$9 6/LQ$9 6/LQ$9`
The origin wait time, OWT, can be determined from the service frequency of all connections with the following formula: OWT = A (assignment time interval/service frequency)
E
with A = 0.5 and E = 1 the origin wait time corresponds to half the mean service frequency. with A = 1.5 and E = 0.5 a root function is created which assumes that passengers have better knowledge of timetables in case of low service frequency.
The origin wait time is the same for all connections of an O-D pair. Output of OWT as an indicator matrix can be useful for network analysis. The in-vehicle time can be multiplied by AddValue_subline data in order to model saturation of seats or other details, e.g. the level of comfort of a subline.
2-117
MODEL DESCRIPTION
User Model (PuT)
8WLOLW\ 8 RI D FRQQHFWLRQ The timetable-based procedure 2 models the temporal utility of a connection as follows: Ti = time difference between departure time interval a ( pattern) and the actual departure time of connection i SD = Sensitiveness to early or late departure (0.0 = none / 0.1 = low / 0.2 = medium / 0.3 = high)
a
Uia = e ( Ti SD )
a
/2
= temporal utility of connection i within time interval a
In the impedance definition the perceived journey time is devided by the temporal utility to impede lower utilities.
&RQQHFWLRQ LPSHGDQFH DQG GLVWULEXWLRQ RI WULSV The impedance of a connection i used in the connection split in a time interval a is calculated as follows
IMPia =
PJTi Uia
Fac PJT + Fare i Fac Fare
By including these impedances in a distribution model (Kirchhoff, Logit, Box-Cox, Lohse), VISUM then determines the utility of a connection in a given time interval and ultimately its percentage of the demand for this interval. The independence can also be included in the distribution rule, if required.
2-118
User Model (PuT)
MODEL DESCRIPTION

([DPSOH
Connection search and connection choice are identical for both timetable-based procedures. The different effect of the connection split for timetable-based procedure 2 is shown with the results of the connection search with a 10-minute transfer penalty. This search produced three connections which are shown in ,OOXVWUDWLRQ along with the corresponding in-vehicle time (IVT), transfer wait time (TWT), and number of transfers (NT). The perceived journey time (PJT) results from weighting these indicators. Conn 1 2 3 Dep 6:10 6:55 7:10 IVT TWT NT PJT = IVT + TWT FacTWT + NT FacNT 28 + 3 2 + 1 2 = 36 45 + 0 2 + 0 2 = 45 45 + 0 2 + 0 2 = 45
28 min 3 min 1 45 min 0 min 0 45 min 0 min 0
FacTWT = 2, FacNT= 2 ,OOXVWUDWLRQ Results of connection search (transfer penalty 10 min; see WLPHWDEOHSDU)
,OOXVWUDWLRQ shows the temporal utilities U1 and U2 resulting from comparing the desired and offered departure times. Connection 1 has a utility of 1 for the 30 passengers who want to depart between 5:30 a.m. and 6:30 a.m., because its departure lies within this time interval. For the 60 passengers who want to depart between 6:30 a.m. and 7:30, connection 1 has a lower utility of 0.61, as the connection departs at 6:10 a.m., 20 minutes before the desired departure time. The decrease of utility in dependence on T is controlled by the sensitivity SD towards early or late departure. Since the utility, U, of a connection depends on the desired departure times of passengers, different impedances, IMP, are generated for every time interval. Conn dep. No. 1 2 3 6:10 6:55 7:10 T1 T2 U1 U2 IMP1=PJT/U1 IMP2=PJT/U2
6:30-7:30
5:30-6:30 6:30-7:30 5:30-6:30 6:30-7:30 5:30-6:30
0 min 25 min 40 min
20 min 0 min 0 min
1.00 0.46 0.14
0.61 36/1.00 = 36 1.00 45/0.46 = 98
36/0.61 = 59 45/1.00 = 45
1.00 45/0.14 = 333 45/1.00 = 45
U=e
-( T S D ) 2 / 2
, SD = 0.05 Temporal utility, U, and impedance, IMP, of connections for the two analysed time intervals of travel demand distribution.
,OOXVWUDWLRQ
MODEL DESCRIPTION
User Model (PuT)
The percentages, Pi of each connection i can then be calculated from the impedances using Kirchhoffs law. As can be seen from ,OOXVWUDWLRQ , 18 % of the 60 passengers who want to depart between 6:30 a.m. and 7:30 a.m. choose connection 1 which is faster, but leaves 20 minutes before the desired time interval. The remaining 82 % are equally distributed over connections 2 and 3. Conn i 1 2 3 ,OOXVWUDWLRQ 6:10 6:55 7:10 Dep Pi
1
Pi
Trips Mi
Trips Mi
Trips
5:30-7:30
5:30-6:30
6:30-7:30
5:30-6:30
6:30-7:30
95% 5% 0% 100%
18% 41% 41% 100%
30 0.95 = 29 30 0.05 = 1 30 0.00 = 0 30
60 0.18 = 10 60 0.41 = 25 60 0.41 = 25 60
39 26 25 90
Distribution of connections over connections (Kirchhoff, = 3)
For resulting volumes see ,OOXVWUDWLRQ

A_village
90
Station
X_city
39
51
,OOXVWUDWLRQ
B_village
51
Volumes resulting from timetable-based assignment procedure 2 (see parameter file timetable2-1.par)
2-120
User Model (PuT)
MODEL DESCRIPTION

(YDOXDWLRQ RI WKH 3URFHGXUH DUHDV RI DSSOLFDWLRQ
The timetable-based procedure 2 is characterised by the following features: The procedure determines the "best" connections for all possible departure times in the analysed time interval. Actual transfer wait times and thus co-ordination of the timetable are taken into account. All indicators are calculable in the analysed time interval. Connections with minimum time and connections with minimum transfers cannot be determined at the same time. The decision model for the connection split of timetable-based procedure 2 models actual decision behaviour of passengers more realistically than timetable-based procedure 1. Usually, a passenger will inform himself about PuT-supply (connection search) before departure, and will then choose from the offered connections (connection split). The assumption made by timetable-based procedure 1, that all passengers arrive randomly at the boarding stop without any knowledge of the timetable, is comparably unlikely.
2-121
MODEL DESCRIPTION
User Model (PuT)

&RQQHFWLRQ VHDUFK
see timetable-based assignment 2

&RQQHFWLRQ FKRLFH
see timetable-based assignment 2

&RQQHFWLRQ VSOLW
Every current connection is charged with the passengers who arrive at the stop between the departure of the previous connection and the departure of the current connection. The number of passengers and their arrival times at the boarding stop is specified by the transport demand matrix and the temporal distribution of passengers.

([DPSOH
As to be seen from the line network and the timetable in ,OOXVWUDWLRQ , different connections with shortest times are calculated for the departure times, 6:10 a.m. and 6:55 a.m.. The departure time, therefore, can influence the selected connection and thus the indicators of journeys. The search impedance definition also influences indicators. If the impedance of a connection is calculated solely from in-vehicle time and transfer wait time without weighting, then the following connections are the result: 1. departure 6:10 a.m., arrival 6:41 a.m., ride time 31 min, 1 transfer 2. departure 6:55 a.m., arrival 7:40 a.m., ride time 45 min, 0 transfer 3. departure 7:25 a.m., arrival 8:01 a.m., ride time 36 min, 1 transfer
2-122
User Model (PuT)
MODEL DESCRIPTION
The assignment of transport demand onto these three connections results in the volume plot shown in ,OOXVWUDWLRQ . Passengers who wish to depart between 5:30 a.m. and 6:10 a.m. are assigned to the first connection. These are 20 passengers (30 passengers 40 min / 60 min). The second connection is used by 10 passengers who arrive at the boarding stop between 6:10 a.m. and 6:30 a.m.. This connection is also chosen by 25 passengers who reach the boarding stop between 6:30 a.m. and 6:55 a.m. (60 passengers 25 min / 60 min). 30 passengers are assigned to the third connection who wish to depart between 6:55 a.m. and 7:25 a.m. (60 passengers 30 min / 60 min). The remaining 5 trips arriving at the boarding stop after 7:25 a.m. are assigned to the third connection, because no further service exists after 7:25 a.m..
A-Village

Station

X-City

,OOXVWUDWLRQ
B-Village

Network volume for timetable-based assignment 1 (transfer penalty 0 min., connections requiring minimum time; see assignment parameter file WLPHWDEOHSDU)
2-123
MODEL DESCRIPTION
User Model (PuT)
The indicators for the relation from A-Village to X-City are shown in ,OOXVWUDWLRQ . They represent mean indicators for the relation calculated from the specific indicators of each connection weighted with the number of passengers. As access and egress time have been assumed = 0 min ride time is equal to journey time. Connection No. 1 2 3 Sum mean indicator ,OOXVWUDWLRQ Pass. 20 35 35 90 Passengers journey time 20 31 min 35 45 min 35 36 min 3455 min 3455/90 = 38.4 min Passengers no. of transfers 20 1 35 0 35 1 55 55/90 = 0.6 Passengers transfer wait time 20 3 min 35 0 min 35 8 min 340 min 315/90 = 3.8 min
Mean indicators for timetable-based assignment (transfer penalty 0 min., connections which require minimum time).
A penalty of 10 minutes per transfer leads to a different result during the connection search and thus to a different network volume (,OOXVWUDWLRQ ): 1. Departure 6:10 a.m., arrival 6:41 a.m., ride time 31 min., 1 transfer (perceived journey time 41 min., 20 passengers) 2. Departure 6:55 a.m., arrival 7:40 a.m., ride time 45 min., 0 transfer (perceived journey time 45 min., 35 passengers) 3. Departure 7:25 a.m., arrival 8:10 a.m., ride time 45 min., 0 transfer (perceived journey time 45 min., 35 passengers)
A-Village
90
Station
X-City
20
70
B-Village
70
,OOXVWUDWLRQ
Network volume for timetable-based assignment 1 (transfer penalty 10 min; see assignment parameter file WLPHWDEOHSDU)
2-124
User Model (PuT)
MODEL DESCRIPTION
For the example the search procedure calculates connections with minimum transfers if every transfer is given a penalty of at least 14 minutes. In this case, the shortes route (departure 6:10 a.m., arrival 6:41 a.m., 31 min. ride time, 1 transfer) also has a perceived journey time of 45 minutes which corresponds to the journey time of the direct connection (departure 6:10 a.m., arrival 6:55 a.m., 45 minutes ride time, without transfers). The volume plot (,OOXVWUDWLRQ ), therefore, does not indicate any volume for the train.
A-Village

Station
X-City

,OOXVWUDWLRQ
B-Village

Volume for timetable-based assignment 1 (transfer penalty 14 min., connections with minimum transfers; see WLPHWDEOHSDU).
2-125
MODEL DESCRIPTION
Operator model
2SHUDWRU PRGHO
Operational indicators can be divided into the following categories: General indicators Performance indicators Vehicle requirement indicators Transport demand indicators Cost indicators Revenue indicators.
Most operational indicators are calculated for one vehicle trip (e.g. vehicle kilometers) or one subline (e.g. person kilometers), and are then aggregated to indicators of a line or transport system. Vehicle number indicators and vehicle cost indicators, however, can only be calculated for one line or one transport system. To list these indicators for a subline, they are distributed over vehicle kilometers.
3URMHFWLRQ
The network model encompasses PuT-supply for one day. To determine annual indicators from daily indicators, projection factors are necessary. This kind of projection is possible with the Line-costing module. Projection can be carried out with a constant projection factor or with indicator-specific projection factors. Indicator-specific projection uses specific factors to project: demand indicators (demand, revenue) supply indicators (performance, costs) hourly costs
In this way, the fact that on weekends transport demand, for example, may decline more than transport supply is taken into account. At the same time, higher personnel costs, that is, higher hourly costs, can arise on Sundays.
2-126
Operator model
MODEL DESCRIPTION
,OOXVWUDWLRQ shows the input data which are used for projection, and the formulas for determining the projection factors for transport demand, FacTD, transport supply, FacTS, and hourly costs, FacHour. Type of day 1corresponds to the demand and supply of the transport model. Input data for projection Type of day 1 2 3 4 Days/Year NumDay1 NumDay2 NumDay3 NumDay4 Transport demand FacTD1 FacTD2 FacTD3 FacTD4 Transport supply FacTS1 FacTS2 FacTS3 FacTS4 Projection example PassengerKm/year = PassengerKm FacTD VehicleKm/year = VehicleKm FacTS HourlyCosts/year = hourly costs FacHour Hourly costs FacHour1 FacHour2 FacHour3 FacHour4
Projection factor determination
FacTD = NumDay(i) FacTD(i)

i =1 4
FacTS = NumDay(i) FacTS(i)

i =1
FacHour = NumDay(i) FacTS(i) FaHour (i)

i =1
,OOXVWUDWLRQ Type of day
Input data for projection and projection formulas
Days/year 190 60 52 63 365
Transport demand 1.0 0.8 0.5 0.3 282.9
Transport supply 1.0 0.8 0.7 0.4 299.6
Hourly costs 1.0 1.0 1.0 1.5 312.2
1. Mo Fr (school days) 2. Mo Fr (vacation) 3. Saturdays 4. Sundays, public holidays
FacTD = 190 1.0 + 60 0.8 + 52 0.5 + 63 0.3 = 282.9 FacTS = 190 1.0 + 60 0.8 + 52 0.7 + 63 0.4 = 299.6
FacH = 190 1.0 1.0 + 60 0.8 1.0 + 52 0.7 1.0 + 63 0.4 1.5 = 312 .2
,OOXVWUDWLRQ Example projection
MODEL DESCRIPTION
Operator model
*HQHUDO LQGLFDWRUV

General operational indicators combine line data from the line route and the timetable. The calculation is carried out automatically after every modification to line data, and does not require demand data. 7 / 6 $WWULEXWH 'HVFULSWLRQ
Number of sublines Number of sublines which belong to one line or one transport system. Number of lines Total number stops Number of lines which belong to a transport system. of Number of traversed stops (serviced and not serviced). Stops traversed several times are counted several times. Number of serviced stops, stops which were serviced several times are only counted once. Number of stops; stops served several times are counted several times. Length from origin to destination stop. Mean length of all vehicle trips. Length of link network which is permitted for one transport system.
Served stops Number of stops Length Mean vehicle trip length Network length
Line network length Length of link network which is traversed by lines of a transport system. Running time Time from origin to destination stop including wait times. Average running time of all vehicle trips. Departure time of first vehicle trip. Arrival time of last vehicle trip. Average speed between origin and destination stop for all vehicle trips.
Avg. running time
First departure Last arrival Avg. speed ,OOXVWUDWLRQ
General operational indicators (T = TSys, L = Line, S = Subline).
2-128
Operator model
MODEL DESCRIPTION
7UDQVSRUW VXSSO\ LQGLFDWRUV

Supply indicators are performance indicators which express operational requirements in kilometers or in time units. They are calculated automatically after every modification to line data, and do not require demand data. These indicators can be calculated from: all vehicle trips which are represented in the network model (usually one day) or from all vehicle trips which depart within a given time interval. 7 / 6 $WWULEXWH Vehicle trips Vehicle kilometers Service time In-action time Seat kilometers ,OOXVWUDWLRQ 'HVFULSWLRQ Number of vehicle trips according to timetable. Veh.-km = Veh. trip length Number of vehicle trips Time for passengers transport = Line running time Number of vehicle trips. = Out of depot time = Service time + Layover time Seat kilometers = VehKm Seats of vehicle.
For projection for 1 year the projection factor of transport supply, FacTS is used.
Performance indicators
9HKLFOH UHTXLUHPHQW LQGLFDWRUV

VISUMs Line-costing module provides an algorithm with which planners can estimate the number of required vehicles for specified PuT-supply. The main goal of this calculation is to assign the total number of vehicle trips of an operational day to vehicles in such way that a minimum number of vehicles is required. The basis for this calculation is the WLPHWDEOH. It consists of individual vehicle trips which are described by subline, direction, and departure time from the first stop of the line. 9HKLFOH URVWHUV results from the concatenation of individual trips into EORFNV which can each be serviced by one vehicle. In the simplest case a vehicle trip is concatenated at its last stop with a subsequent vehicle trip which starts at the same stop. If such a concatenation is not possible or not meaningful, the vehicle can be redeployed to a different stop. This results in a FRQQHFWLQJ URXWH or LQWHUOLQLQJ. 7 / 6 $WWULEXWH 'HVFULSWLRQ
Number of vehicles Number of required vehicles = Number of blocks. Vehicle requirement indicators
,OOXVWUDWLRQ
2-129
MODEL DESCRIPTION
Operator model
7UDQVSRUW GHPDQG LQGLFDWRUV

Demand indicators result from the use of lines by passengers. They are calculated automatically during assignment and thus are based on PuT-demand data. Projection for a year is carried out with the projection factor of travel demand FacTD. 7 / 6 $WWULEXWH Person kilometers Person hours Total Linetrips Linetrips with 0 transfers Linetrips with 1 transfer Linetrips with 2 transfers Linetrips > 2 transfers Mean number of transfers ,OOXVWUDWLRQ 'HVFULSWLRQ Passengers kilometers = Transported passengers on line Trip length from origin to destination stop. Passengers hours which passengers spend in PuT vehicle of one line or transport system. Passengers on line = Number of boarding passengers. Passengers on line with no transfer (passengers only use current line). Passengers on line with 1 transfer. Passengers on line with 2 transfers. Passengers on line with more than 2 transfers. Mean number of transfers of passengers of a subline or of all sublines of line.
Transport demand indicators
2-130
Operator model
MODEL DESCRIPTION
&RVW LQGLFDWRUV

The costs of a line consist of the following cost segments: hourly costs: kilometer costs: vehicle costs: link costs: operator costs: time-dependent costs for personnel kilometer-dependent costs for fuel, repair, etc. fixed costs for vehicles costs for the use of links share of costs for general operational costs
The projection of cost indicators is carried out with the projection factor for transport supply FacTS. Annual hourly costs are calculated using a special projection factor, FacHour, which takes possible higher personnel costs on Sundays and public holidays into account. 7 / 6 ,QGLFDWRU Costs Hourly costs Kilometer costs Vehicle costs Link costs Operator costs ,OOXVWUDWLRQ 'HVFULSWLRQ Costs = Hourly costs + Kilometer costs + Vehicle costs + Link costs + Operator costs. Hourly costs = In-action time Hourly costs of vehicle type. Kilometer costs = Vehicle kilometers Kilometer costs of vehicle type. Vehicle costs = Number of vehicles Vehicle costs/day of vehicle type. Link costs from depreciation costs, running costs or utilisation costs. Operator costs from depreciation costs or running costs.
Cost indicators
/LQN FRVWV To model link costs, up to three cost values can be specified per link and transport system. For each of these three cost values, the following cost types can be selected: depreciation costs, e.g. investment costs running costs, e.g. maintenance costs utilisation costs, e.g. track charges.
MODEL DESCRIPTION
Operator model
&RVW W\SH GHSUHFLDWLRQ FRVWV CostValue = e.g. investment costs for a link
CostValue qDT (q 1) L,T 1 CostLink Day,L,T = DT FacTS q 1

CostLink VehTrip,L,T = CostLink Day,L,T
with q = 1 + p / 100
VehTripL,T
&RVW W\SH UXQQLQJ FRVWV CostValue = e.g. annual maintenance costs for a link
CostLink VehTrip,L,T =
VehTripL,T FacTS
CostValueL,T
&RVW W\SH XWLOLVDWLRQ FRVWV CostValue = e.g. track charges for the use of a link CostLink VehTrip,L,T = CostValueL,T
CostValue L,T CostLink Day,L,T
CostLink VehTrip,L,T
Cost value which is specified as an attribute of link L and transport system T. Daily link cost of link L for transport system T. Cost of one vehicle trip of transport system T, which uses link L. Number of vehicle trips of transport system T, which use link L. Projection factor for transport supply Day Year Projection factor for transport supply Year Day Depreciation time [Years] Interest rate [%] Formulas to calculate link costs for one vehicle trip
VehTripL,T
FacTS 1/FacTS DT p ,OOXVWUDWLRQ
2-132
Operator model
MODEL DESCRIPTION
2SHUDWRU FRVWV For every operator, up to three cost values can be specified. For each of these three cost values of the following cost types can be selected: tax-deductible costs, e.g. investment costs regular costs, e.g. maintenance costs.
To distribute these operator costs onto vehicle trips or sublines which are operated by the operator, a distribution key can be specified which consists of the following weighted indicators: Vehicle kilometers (W-VehKm) Seat kilometers (W-SeatKm) Service time (W-ServiceT) Number of vehicle trips (W-VehTrip) LineTrips (W-LineTrips) Passenger kilometers (W-PassKm).
2-133
MODEL DESCRIPTION
Operator model
'LVWULEXWLRQ RI RSHUDWRU FRVWV RQWR YHKLFOH WULS
ShareVehTrip =
VehKmVehTrip
VehKmi
i=1
x W VehKm +
SeatKmVehTrip
SeatKmi
i=1
x W SeatKm
ServiceTVehTrip
ServiceTi
i=1
x W ServiceT +
1 x W VehTrip V
&RVW W\SH GHSUHFLDWLRQ FRVWV CostValue = e.g. investment costs for company CostValueO qDT (q 1) 1 CostOpDay,O = DT FacTAS q 1
CostOp VehTrip,O = CostOpDay,O Share VehTrip,O
with q = 1 + p / 100
&RVW W\SH UXQQLQJ FRVWV CostValue = e.g. annual maintenance costs for company CostOp VehTrip,O = CostValue O
CostOp Day,O CostOp VehTrip,O Share VehTrip
CostValueO Share VehTrip,O FacTS Cost value which is specified as operator attribute. Daily operator costs of operator O. Operator costs for one vehicle trip by operator O. Share of one vehicle trip of operator costs. Number of vehicle trips of an operator. Projection factor for traffic supply Day Year Projection factor for traffic supply Year Day Depreciation time [Years] Interest rate [%]
V FacTS 1/FacTS DT p ,OOXVWUDWLRQ
Formulas for calculating operator costs for one vehicle trip.
2-134
Operator model
MODEL DESCRIPTION
5HYHQXH LQGLFDWRUV

To estimate revenue from ticket fares, a revenue value per transported passenger can be specified in the Line-costing module. This revenue value is then distributed over the lines used by the passenger for one passenger trip. Revenue can be distributed onto route sections (RS) using the length of each route section or the number of route sections. Cost coverage is calculated by comparing revenue and costs. 7 / 6 ,QGLFDWRU Total revenue Revenue per line trip Cost coverage total Cost coverage % Cost coverage per line trip Revenue indicators 'HVFULSWLRQ Total revenue from ticket charges from one line or transport system. Revenue per line trip. Cost coverage total = Revenue - Costs. Cost coverage % = Revenue / Costs 100. Cost coverage per line trip.
,OOXVWUDWLRQ
2-135
MODEL DESCRIPTION
Operator model
Share-Km ShareRouteSection Share-Line Rev-RS
= Length-RS / Length-Tot = 1 / Num-RS = Share -Km W-Km + Share-RS W-RS = Rev-Fix + (Rev-PassTrip Rev-Fix Num-RS) Share-Line
Num-RS Length-RS Length-Tot W-Km W-RS
Number of route sections for one passenger trip Length of route sections Total length of passenger trip Weighting of length W-Km + W-RS = 1.0 Weighting of route sections
Rev-PassTrip Revenue per passenger trip Rev-Fix Rev-RS ,OOXVWUDWLRQ Fixed revenue value assigned to every route section Revenue per route sections, i.e. share of revenue for used line for this route section Formulas for calculating the revenue of a route section
2-136
Operator model
MODEL DESCRIPTION
Bus 1
S1 S2
Train
S3
Bus 2
S4
2 km
Number of passenger trips: Number of line trips: Total length Share-Km (Bus1) Share-Km (Train) Share-Km (Bus2) Share-RS Rev-PassTrip Distribution 1: Line Bus 1 Train Bus 2 W-Km = 1.0
6 km
1 3 12 km = 2 / 12 = 0.167 = 6 / 12 = 0.500 = 4 / 12 = 0.333 = 1 / 3 = 0.333 3.00 W-RS = 0.0
4 km
Rev-Fix = 0.00
Line share 1.0 0.167 + 0.0 0.333 = 0.167 1.0 0.500 + 0.0 0.333 = 0.500 1.0 0.333 + 0.0 0.333 = 0.333 W-Km = 0.5
Revenue 0.167 3.00 = 0.50 0.500 3.00 = 1.50 0.333 3.00 = 1.00 Rev-Fix = 0.00
Distribution 2: Line Bus 1 Train Bus 2
W-RS = 0.5
Line share 0.5 0.167 + 0.5 0.333 = 0.250 0.5 0.500 + 0.5 0.333 = 0.417 0.5 0.333 + 0.5 0.333 = 0.333 W-Km = 0.5
Revenue 0.250 3.00 = 0.75 0.417 3.00 = 1.25 0.333 3.00 = 1.00 Rev-Fix = 0.20
Distribution 3: Line Bus 1 Train Bus 2
W-RS = 0.5
Line share 0.5 0.167 + 0.5 0.333 = 0.250 0.5 0.500 + 0.5 0.333 = 0.417 0.5 0.333 + 0.5 0.333 = 0.333
Revenue 0.20 + 0.250 (3.00 3 0.20) = 0.80 0.20 + 0.417 (3.00 3 0.20) = 1.20 0.20 + 0.333 (3.00 3 0.20) = 1.00
,OOXVWUDWLRQ
Example for revenue distribution
2-137
MODEL DESCRIPTION
Literature
/LWHUDWXUH
Forschungsgesellschaft fr Straen- und Verkehrswesen (German Research Society for Roads and Traffic) Leitfaden fr Verkehrsplanungen, ("Guideline for Transportation Planning) Cologne, 1985 Kirchhoff, P.; Leutzbach, W.; Pampel, E.; Holz, S.; Mott, P.; Sahling, B. M.: Verkehrs- und Betriebsplanung (Traffic and Operational Planning") Forschung Stadtverkehr, Reihe Auswertungen, Heft A3, 1987 Leutzbach, W.; Haupt, T.; Mott, P.: Ermittlung der Verkehrsnachfrage (Determination of Travel Demand") Forschung Stadtverkehr, Reihe Auswertungen, Heft A4, 1988 Schnabel, W., Lohse D. Grundlagen der Straenverkehrstechnik und der Verkehrsplanung, Band 2 ("Foundations of Traffic Engineering and Transportation Planning") Verlag fr Bauwesen, Berlin, 1997
U.S. Department of Commerce, Bureau of Public Roads (ed.) Traffic Assignment Manual. Washington, D.C. (1964)
2-138
FUNDAMENTALS OF PROGRAM OPERATION
)81'$0(17$/6 2) 352*5$0 23(5$7,21
This chapter contains a general description of VISUMs features, including short explanations of the screen layout toolbar buttons menus and the file management system.
Detailed descriptions of particular VISUM commands and how to work with VISUM are contained in the following chapters.
To illustrate how VISUM works, a macro can be activated by selecting the 9,680 'HPR button. Activate the 9,680 ([DPSOH button to experiment with example network data and example parameter files.
3-1
The start-up screen
7KH VWDUWXS VFUHHQ
6WDUW 9,680 ZLWK PRXVH FOLFN Information on your program installation: VISUM version number version size (A-H) licensee expiry date, if applicable
0RUH GHWDLOHG LQIRUPDWLRQ RQ WKH FXUUHQW LQVWDOODWLRQ LQ /LFHQFH GLDORJ VHH (;75$6PHQX /,&(1&(

3-2
version size (max. number of zones, links, nodes, PuT lines). language of the VISUM version. Non-German VISUM users may select up to 3 languages. Phrases which have not yet been translated into language 1 (e.g. French) are displayed in language 2 (e.g. English), if available. add-on modules (installed add-ons can be switched off individually) and length units used (miles or meters).
The VISUM interface
7KH 9,680 LQWHUIDFH
VISUM commands can be activated on the screen in two ways: quick access to basic commands to work with VISUM is available via the symbol buttons in the WRROEDU. all basic commands, except the zoom commands, and all other commands can be activated in the pull-down menus of the PHQX EDU. 0HQX EDU
7RROEDU
Display/Zoom
Processing modes
Network objects
Graphic objects
Filters
6FUROO EDUV
3-3
The VISUM toolbar
7KH 9,680 WRROEDU
%XWWRQV VFUHHQ GLVSOD\ %XWWRQ )XQFWLRQ Zoom in Zoom out Full screen display (entire network) Redraw picture Enlarge section by factor Preview (also via the 3UHYLHZ command in the FILE menu) %XWWRQV SURFHVVLQJ PRGHV %XWWRQ )XQFWLRQ ,QVHUW an object 6LQJOH VHOHFW an object for editing/deleting 0XOWL VHOHFW a group of objects for editing/deleting/aggregating
These buttons correspond to the commands in the upper command field of the EDIT menu.
3-4
The VISUM toolbar
%XWWRQV QHWZRUN REMHFWV %XWWRQ )XQFWLRQ Activate /LQNV network object Activate 1RGHV network object Activate &RQQHFWRUV network object Activate =RQHV network object Activate *OREDO =RQHV network object Activate 7XUQLQJ 5HODWLRQV network object Activate 6XEOLQHV network object Activate $UHDV network object Activate &HQVXV SRLQWV network object
G
%XWWRQ
These buttons correspond to the commands in the upper command field of the SELECT menu.
%XWWRQV JUDSKLFV REMHFWV )XQFWLRQ Activate %DFNJURXQGV graphics object Activate 2EMHFWV graphics object Activate 7H[WV graphics object Activate 3RO\JRQV graphics object Activate /HJHQG graphics object Activate &OLSV graphics object

These buttons correspond to the commands in the lower command field of the SELECT menu.
1) Only for users of the %DFNJURXQG add-on module VISUM User Manual (April 2001) Version 7.50 3-5
The VISUM toolbar
%XWWRQV )LOWHUV %XWWRQ )XQFWLRQ Specify link filter. Specify node filter. Specify zone filter. Specify global zone filter. Specify connector filter. Specify turning relations filter. Specify PuT line filter (select TSys, lines, sublines and/or main lines). Specify relation filter for selecting origin-destination relations. Specify census points filter Specify time filter for selecting line services.
These buttons correspond to the commands of the FILTER command in the EXTRAS menu. The colour of the Filter bag of the symbol indicates if a filter is currently active (red = active; white = inactive).
3-6
The VISUM menus
7KH 9,680 PHQXV
),/( PHQX

&RPPDQG 1EW 2PEN 6AVE DATA %ASE 'HVFULSWLRQ Generate new network Open file Save file ,PSRUW([SRUW database <Ctrl-S> 6KRUWFXW
OPEN 'IRECTORIES.. 2SHQ6DYH most frequently used file types. SAVE D,RECTORIES.. OPEN 9ERSION... SAVE V(RSION... OPEN *RAPHIC PARAMETERS... SAVE G5APHIC PARAMETERS... 35,17 SE7 PRINT PAGE... PRINT $REA... PREVIE:... DIRE&TORIES... )ILE-INFO E;,7 Output network to printer, plotter or file. Specify print page format (can also be activated via menu GRAPHICS-PARAMETERS button SULQW SDJH) Specify print area Print preview Modify directories of the file management system Edit information field of a network or version file. Exit VISUM
<Alt-F4>
3-7
The VISUM menus
(',7 PHQX

&RPPDQG VW FRPPDQG ILHOG IMPORT FROM CLIP%OARD (Interface for attribute data import, see Chapter 15) QG FRPPDQG ILHOG ,NSERT 6INGLE SELECT 0ULTI SELECT Insert a new object Select a single object Select multiple objects 'HVFULSWLRQ %XWWRQ
UG FRPPDQG ILHOG 6,1*/(6(/(&7 PRGH SEAR&+ Search for a particular network object <F3>
WK FRPPDQG ILHOG 6,1*/(6(/(&7 PRGH M2DIFY 'ELETE 7EXT ON/OFF SPECIF<COURSE SHIFT TE;T Modify object attributes Delete object Switch label of OLQN on or off S3LIT &OPY Modify course of OLQN ]RQH ERXQGDU\ or OLQH, Shift FHQVXV SRLQW along link. Shift label position of a OLQN. Shift position of the centroid of a ]RQH or JOREDO ]RQH or an DUHD. =RQH: split zone into two new zones. /LQN: insert node, split link into two links. <F9> <F8> <Enter> <Del> <F4> <F5> <F6>
Copy a OLQH or a graphic object of types REMHFW or SRO\JRQ
The edit commands in SINGLE SELECT mode can only be activated if a particular object has been selected. Pressing the right mouse-key in the SINGLE SELECT MODE calls up the lower command block as a context-sensitive menu for each type of objects.
3-8
The VISUM menus
&RPPDQG
'HVFULSWLRQ
WK FRPPDQG ILHOG 08/7,6(/(&7PRGH M2DIFY Modify input attributes for multiple network objects of one type. Modify parameters for graphic objects globally. Switch link labels globally on/off. Initialize boundaries of zones globally. Specify default values for attributes of links, turning relations or major flow. Use standard timetable for sublines. Aggregate active ]RQHV to a single zone. Aggregate active VXEOLQHV. <F7> <Del> <Enter>
$GGREGATE 'ELETE *(1(5$7(
Delete active objects globally: network objects, e.g. QRGHV, or REMHFWV SRO\JRQV and WH[WV. Generate connectors for all active zones automatically.
3-9
The VISUM menus
6(/(&7 PHQX

&RPPDQG VHOHFW DQ REMHFW W\SH /INKS 1ODES =ONES *LOBAL ZONES &ONNECTORS 7URNING RELATIONS 6UBLINES $5($6 CENS8S POINTS %$&.*5281'6 2%-(&76 TE;TS 32/<*216 /(*(1' CL,PS
1) Only for users of the %DFNJURXQGadd-on module.

%XWWRQ
3-10
The VISUM menus
/,67,1*6 PHQX

&RPPDQG 'HVFULSWLRQ Object type-specific listings
Calculation of PuT service indicators List of all PrT/PuT routes (result of assignment). List of found PrT/PuT routes using the 5RXWH VHDUFK command.
Statistics (network objects, link types, PuT assignment, and PuT vehicle runnings). Plausibility status of survey records (Add-on)
Lists contain input data and calculation results. Via the FILE submenu a list can be copied into clip board ($WWULEXWHV LQWR FOLS ERDUG command), saved as attribute file (6DYH $WWULEXWHV), printed (3ULQW command). The layout of a list can be modified via the O37,216submenu and savedvia the FILE submenu.
3-11
The VISUM menus
&$/&8/$T( PHQX

&RPPDQG &HECK NETWORK 2-D MATRIX MATRI; CORRECTION 'HVFULSWLRQ Carry out network check. Edit current O-D matrix or time interval of temporal PuT-demand distribution, Use census data for matrix update by 5RXWH SURMHFWLRQ or 96WURP)X]]\ (add-on). Calculation of assignment and indicators according to current parameter settings. Overview of assignment procedures used by demand segment. Reset current assignment result. Comparison of current PrT assignment result and census data.
3ROCEDURES ASSIGNMEN7 REPORT ,NITIALIZE ASSIGNMENT PRT ASSIGNMENT ANAL<SIS
(NVIRONMENTAL IMPACT PARAMETERS Add-on module (QYLURQPHQW (PrT): CALCULATE E1VIRONMENTAL IMPACT Calculation of noise and pollutant emissions: set parameters and run selected procedures. INITIALIZE EN9IRONMENTAL IMPACT Reset current environmental impact result. 'IFFERENCE NETWORK 3ARTIAL NETWORK GENERATOR Calculate and display the difference in volumes between two versions Generate partial networks and corresponding O-D matrices (add-on)
PASSEN*ER SURVEY PUT TRANSFER 4UALITY
Add-on Modules PuT Passenger survey: plausibilization of survey data records. PuT transfer quality: evaluation of connections (arrival and departure times). For /LQH FRVWLQJ Add-on (Lineblocking, revenue calculation and distribution) see 3URFHGXUHV.
3-12
The VISUM menus
*5$3+,&6 PHQX

&RPPDQG )LOW BUNDLE 1ODE FLOWS ,SOCHRONES R2UTE SEARCH 2-D FLOW 'HVFULSWLRQ Display of PrT and/or PuT flow bundles. Display of PrT node flows at selected nodes. Display of PrT and/or PuT isochrones. Generation and display of routes between zones and/or nodes. Display of demand between zones (select relations)
PUT VEHICLE ANIMATION Vizualization of flow of Put vehicles through the network 3ARAMETERS... Set graphic parameters for network display: EDVLF-graphic parameters display of QRGHV or VWRSV display of ]RQHV and global zones display of OLQNV (basic network), display of OLQHV and PuT line volumes, display and labelling of FHQVXV SRLQWV, display of YROXPHV and other link attributes, ODEHOV along links display of isochrones and IORZ EXQGOHV display of 2' IORZV OD\HU definition and display in clips specification of SULQW SDJH format selection of Windows IRQWV.
3-13
The VISUM menus
(;75$6 PHQX

&RPPDQG 7RANSPORT SYSTEMS /INK TYPES 1ETWORK
PARAMETERS
'HVFULSWLRQ Definition of transport systems (PuT and PrT), demand segments, transport modes, link types, current network parameter (f. e. scaling factor), PuT main lines PuT operators, PuT vehicle types, PuT fares and tariff zones.
PUT MAIN LINES PUT 2PERATORS PUT 9EHICLE PUT )ARES PUT TARIFF ZONES 0ACRO PROGRAM 6TATUS CONVERT %ACKGROUND FILE F,LTERS 0ULTI SELECT
TYPES
Run macro by opening a macro file. Command dialog for particular macro commands.
Statistics on current network status (number of active and passive network objects, filter status, etc.)

Import of DXF-graphics files via background text files *.hgt into the binary VISUM background file format *.hgr. )LOWHUV: selection criteria for network objects, origindestination relations and for line trips within a given time interval. 0XOWL 6HOHFW: Setting of network objects to the active/ passive state by areas or polygon definition and by individual or global selection.
O3TIONS /ICENCE
Specify settings: default parameters for links, connectors, lines, standard timetable; network file format for saving, etc. Information on add-ons, language, version size etc.
1) Only for users of the %DFNJURXQGadd-on module.
3-14
The VISUM menus
" PHQX

&RPPDQG ,NFO 'HVFULSWLRQ Copyright, version size, date of expiry, and PTV hotline
+ELP
Call up 2QOLQH +HOS.
3-15
VISUM files
9,680 ILOHV
)LOH H[WHQVLRQV SUHVHW LQ WKH VWDQGDUG GLUHFWRULHV ILOH VWGSIG )LOH W\SH *.ane Active network elements )LOH PDQDJHPHQW RSHUDWLRQV *.apa PuT transfer quality parameters *.fga *.fil Temporal demand distribution (PuT) Filter parameters OPEN/SAVE in FILE menu. 2SHQ6DYH DFWLYH QHWZRUN REMHFWV via MULTISELECT in EXTRAS menu. Context-sensitive menu by right mouse click in PXOWL VHOHFW mode. OPEN/SAVE in FILE menu. 2SHQ/6DYH via Menu CALCULATE - PUT
TRANSFER QUALITY
*.att
Attribute file
Open: OPEN in FILE menu. Save: LISTINGS menu; 6DYH DWWULEXWHV in FILE submenu of current list.
OPEN/SAVE in FILE menu. OPEN/SAVE in FILE menu. 2SHQVDYH ILOWHU ILOH via FILTERS in EXTRAS menu OPEN/SAVE in FILE menu. 0DWUL[5HDG/6DYH via Menu CALCULATE ASSIGNMENT
*.fma
O-D matrix
*.fzt
PrT indicator matrix
Menu CALCULATE - PROCEDURES; Operation: ,QGLFDWRU0DWUL[; Select '6HJ of PrT Switch 3DUDPHWHUV.
G
3-16
Various types of PuT indicator matrices: Menu CALCULATE PROCEDURES; Operation: ,QGLFDWRU0DWUL[ Select '6HJ RI 3X7; Switch 3DUDPHWHUV Tab ,QGLFDWRU0DWULFHV.
VISUM files
)LOH W\SH *.gpa Graphic parameters
)LOH PDQDJHPHQW RSHUDWLRQV OPEN/SAVE in FILE menu. OPEN/SAVE menu

GRAPHIC PARAMETERS
in FILE
*.hgr
Background file
Save: PRINT in FILE menu output to: ILOH; device: +*5' Open: INSERT in EDIT menu; %DFNJURXQG graphic object type or 2EMHFW.
*.imm *.kno *.lla *.mac
,PPLV link attributes TurnRel-AddValues Listings layout Macro file
OPEN/SAVE in FILE menu. OPEN/SAVE in FILE menu. LISTINGS menu; RSHQVDYH OD\RXW in the FILE submenu of the current list. OPEN in FILE menu. 2SHQ PDFUR ILOH via MACRO in EXTRAS menu.
*.mdb *.mob *.net *.par
Access data base
IMPORT/EXPORT via DATA BASE in FILE menu.
0RELOHY link attributes OPEN/SAVE in FILE menu. Network file Assignment parameters OPEN/SAVE in FILE menu. OPEN/SAVE in FILE menu. 2SHQ6DYH via PROCEDURES in CALCULATE menu OPEN/SAVE in FILE menu. OPEN/SAVE DIRECTORIES in the FILE menu. 2SHQ6DYH YLD DIRECTORIES in the FILE menu.
*.pfd
Directories
*.plt *.pol
Plot file
PLOT in FILE menu output to: ILOH
Boundaries of zones OPEN in FILE menu. and/or global zones SAVE as network file (only boundaries) and read network additionally.
3-17
VISUM files
)LOH W\SH *.spa Survey parameter
)LOH PDQDJHPHQW RSHUDWLRQV OPEN/SAVE in FILE menu. 2SHQ6DYH via PASSENGER SURVEY in CALCULATE menu
*.str *.sur *.txt *.upa
Link-AddValues Survey data Text file Environmental impact calculation parameters Version file
OPEN/SAVE in FILE menu.

SURVEY
Action 5HDG LQWHUYLHZ GDWD via in CALCULATE menu
PASSENGER
OPEN/SAVE in FILE menu. OPEN/SAVE in FILE menu.
*.ver
OPEN/SAVE in FILE menu. 2SHQ6DYH YHUVLRQ in FILE menu
*.zbz *.zkn *.zli *.zob
Zone-AddValues Node-AddValues Subline-AddValues Global ZoneAddValues
OPEN/SAVE in FILE menu. OPEN/SAVE in FILE menu. OPEN/SAVE in FILE menu. OPEN/SAVE in FILE menu.
The listed file type extensions correspond to the default entries in the std.pfd directory file may be edited by the user (via DIRECTORIES in the FILE menu).
3-18
Version files and graphic parameter files
9HUVLRQ ILOHV DQG JUDSKLF SDUDPHWHU ILOHV
The most important and most used file types for saving work in VISUM are: version files (*.ver) which include network data, polygons of zones and global zones graphic parameters and loaded graphics (except *.hgr), e.g. *.bmp, all current AddValues, all current O-D matrices and PuT demand patterns, assignment parameters as well as the assignment result.
graphic parameter files (*.gpa) with all graphic parameter settings: display type, value ranges, labels, layers, co-ordinates, output device, colour assignment, current section, etc. all graphic texts, graphics, e.g. *.bmp, and references to active background objects *.hgr and all output of node flows, flow bundles, and isochrones.
Both files are saved in binary format.
3-19
VISUM protocol files
9,680 SURWRFRO ILOHV
During all current VISUM work sessions all operations and all erroneous program procedures are recorded in a protocol. After completing the VISUM work session these are saved in the files trace.lst and fehler.lst.
PREREQUISITE: Enable OPTIONS in EXTRAS menu: Open trace file. Open error file fehler.lst.
:RUN SURWRFRO ILOH WUDFHOVW The file contains the sequence of all executed operations and internal program procedures with additional information (underlying parameters, statistical analyses, etc.) Consider the following example:
Exedir:>C:\VISION\VISUM750< Read Version C:\Proj\City.ver Version read: Start 17.50.58 138 Nodes 40 Zones 227 Links Read version from file: Finished 17.50.59 Assignment started 01/12/01 17.50.59 Assignment finished 01/12/01 17.50.59 ODMat C:\Proj\car_priv.fma Total 2481 ODMat C:\Proj\car_bsnss.fma Total 740 Assignment started 01/12/01 17.51.50 No.Iter 1 No.DiffEval 0 No. of routes prior to DeleteUnchargedRoutes No. of deleted routes Time prior to RTCalcPack 01/12/01 17.51.50 Time after RTCalcPack 01/12/01 17.51.50 Assignment finished 01/12/01 17.51.50 ... ...
219 0
3-20
VISUM protocol files
(UURU SURWRFRO ILOH HUURUOVW The file can contain the following information: Error messages
Warnings (only if 2XWSXW ZDUQLQJV LQ error.lstis activated under OPTIONS in the EXTRAS menu)
Outputting error messages and warnings into a file is especially useful when running macros since no messages can be displayed on-screen during a macro process and, therefore, no error sources identified.
Network check (turning prohibitions, permitted U-turns, ...) is run automatically via CHECK NETWORK in the CALCULATE menu or OPEN file type 1HWZRUNV in the FILE menu when reading a network file saved with VISUM-IT Version 5.xx, VISUM-IT (DOS) or VISUM-PT 4.5 (DOS).
3-21
VISUM file management
9,680 ILOH PDQDJHPHQW
'HIDXOW GLUHFWRULHV LQ ILOH PDQDJHPHQW

During the installation of VISUM, the following subfolders are created in the ..\visum750 directory: ..\visum750\exe ..\visum750\demo ..\visum750\example contains all program files, default parameter files, and protocol files. contains all files for running a VISUM demo macro. contains files for example applications (small example network).
'LUHFWRU\ ILOHV contain the directory paths for all VISUM file types to determine from which directories the VISUM files are to be opened and where they are to be saved. Directory files also include a file extension for every file type which allows the different file types to be clearly distinguished. VISUM provides the following directory files: the default directory file std.pfd (=example.pfd) is automatically loaded when VISUM is started up. the directory files demo.pfd and example.pfd assign all file types the path name ..\visum750\demo and. ..\visum750\example in order to directly access the example and demo files stored there. the directory file aktdrv.pfd specifies the current drive for all file types.
3-22
0RGLI\LQJ GLUHFWRULHV RI WKH ILOH PDQDJHPHQW V\VWHP

To work with VISUM, the user should create special directories for his different projects. For the files created with VISUM to be saved in the newly defined directories, the path names for the VISUM file types may be modified and saved in a file.
DIRECTORIES... in theFILE menu 0RGLI\ GLUHFWRULHV GLDORJ ER[
6DYH EXWWRQ Save modifications in the current directory file or by specifying a different file name for a new directory file. 2SHQ EXWWRQ Open a directory file. The newly opened directory file determines in which directories the particular file types are to be saved for the current VISUM work session.
To access the modified directories at start up automatically, the std.pfd default file can be overwritten. These modifications, however, are overwritten again in the same directory when an update of VISUM is installed. If a different directory file than std.pfd is to be activated during start up, the relevant modification must be entered in the visum.cfg configuration file (see chapter 3.9.2 "Modifying the program configuration").
3-23
0RGLI\ GLUHFWRU\ GLDORJ 0RGLI\ EXWWRQ
Modifying a single file type selected in the "Modify directories" dialog box: 'LUHFWRU\: modify the directory. ([WHQVLRQ: modify the file extension. Different file types must have different file extensions. Modifications which result in ambiguities are not accepted. %URZVH: Select drive and folder in the 2SHQ dialog box. 0RGLI\LQJ GLUHFWRU\ IRU DOO ILOHV GLDORJ $OO EXWWRQ Specifying a global directory for all file types. Enter drive/directory name, as applicable. %URZVH: Select drive and directory in the 2SHQ dialog box.
The file types file extensions are not modified.
3-24
VISUM program configuration
9,680 SURJUDP FRQILJXUDWLRQ
'HIDXOW FRQILJXUDWLRQ

The default configuration file visum.cfg contains default settings for VISUM: 6HWWLQJV * -C std.zsk 'HVFULSWLRQ Loads a list of devices and interfaces supported by VISUM. Loads settings for graphics cards and output devices (binary format). Loads emission factors of the Swiss Federal Ministry for the Environment for Environmental Impact Analyses. Saves a protocol of erroneous program procedures. Loads graphic default parameters (binary format). Free input option for version file to be loaded (contains comprehensive data of VISUM work in binary format). Loads program settings (via OPTIONS in the EXTRAS menu) as well as current screen settings for VISUM. Free input option for macro file to be loaded (contains commands which are automatically executed in sequence).
ZSKfile * -D
ZGIfile * -E
std.zgi
Emissionsfile * -F error file * -G
emiss.dat
fehler.lst
GParfile * -H Version file * -I Inifile * -M
std.gpa
visum.ini
Macrofile
3-25
6HWWLQJV * -P std.pfd
'HVFULSWLRQ Loads defined extensions for different VISUM file types and their default directories. Loads adjustment factors for different road surface types for noise emission calculations. Saves a protocol of VISUM operations. trace.lst Free input option for assignment parameters to be loaded (file in binary format).
Directory file * -R
RLSfile * -T Tracefile * -U
rls.dat
Assignment Parameter file
The default settings listed here are loaded from the default directory visum750\exe when VISUM is started up. This activates the contained settings. The protocol files fehler.lst and trace.lst are saved in the default directory visum750\exe.
3-26
0RGLI\LQJ SURJUDP FRQILJXUDWLRQ

By modifying the default configuration file visum.cfg, each program installation can be customized to meet ones own personal needs: specify specific program settings by using the file types *.zgi, *.zsk (configuration specified for output on screen ond to plotter/printer) and *.pfd (directories and extensions specified for each file type). specify the files for work with VISUM which are to be loaded at every start-up.
The settings are activated automatically at every start-up.
0RGLI\ VWDQGDUG FRQILJXUDWLRQ +RZ WR HGLW WKH YLVXPFIJ ILOH ([DPSOH When the program is called up, the last saved version of the project worked on 1 LQ FXUUHQW VWDWXV (version file pr1_is.ver) is to be loaded with the appropriate graphic parameters (pr1_is.gpa). All data created in VISUM as well as the protocol files fehler.lst and trace.lst are to be saved in the c:\projects\n1 directory. Modifications in the configuration file: original entry fehler.lst std.gpa std.pfd modified entry c:\projects\n1\error.lst pr1 is.gpa pr1 is.ver pr1 is.pfd The path name "c:\projects\n1\" has been set for all file types via DIRECTORIES in the FILE menu and has been saved with the new directory file name. c:\projects\n1\trace.lst
trace.lst
Save the configuration file under a different name e.g. pr1_is in the project directory c:\projects\n1. This guarantees that userspecific modifications cannot be overwritten during the installation of a VISUM update. Furthermore all project data files are in one project directory.
3-27
+RZ WR PRGLI\ WKH SURSHUWLHV RI WKH 9,680 FRQILJXUDWLRQ ILOH :LQGRZV :LQGRZV 17 [ Click on (right-hand mouse-key) the VISUM icon to open up the context-sensitive menu, actuate 3URSHUWLHV to open up the dialog box displayed below.
Dialog box "VISUM.exe Properties - 6KRUWFXW7DUJHW
Enter the valid drive, directory and file name of your configuration file as the visum.exe target. :LQGRZV 17 XS WR [ Start up the 3URJUDP-0DQDJHU: and mark the VISUM Icon. Menu File-Properties. Dialog box "Program properties: Enter the valid drive, directory and file name of your configuration file as the visum.exe target.
3-28
When VISUM is started up, the entries in the configuration file are considered: pro1_is.cfg in the c:\projects\n1 directory.
VISUM Online Help (VISUM User Manual)
9,680 2QOLQH +HOS 9,680 8VHU 0DQXDO
G
8
The online help tool provides 7DEOH RI FRQWHQWV and ,QGH[ of the Users Manual VISUM Version 7.50. 0HQX " +ELP6KRUWFXW "! DQG $OW +! 6WDUWXS VFUHHQ &KDSWHU 2QOLQH'RFXPHQWDWLRQ
Analysis and Planning of Transport Networks
3-29
Select from &RQWHQWV, e.g. &KDSWHU 7KH 1HWZRUN (GLWRU.
and confirm 2SHQ
or call ,QGH[ and search for the particular item, e.g. /LQNV.
and confirm 'LVSOD\
3-30
Select e.g. (GLW D OLQN from the topics found and confirm 'LVSOD\.
Scroll through screen display.
Use e.g. 3ULQW or %RRNPDUN functionality, if applicable.

3-32
THE NETWORK EDITOR
7+( 1(7:25. (',725
The supply data of a transport network are described in a network model consisting of various network objects. To describe the transport supply, VISUM distinguishes between the following network object types: zones and global zones, nodes, links, turning relations, zone connectors, public transport lines with line routes and timetables.
The network model also contains operational data on the PuT vehicles and on public transport operators, census points on links areas for precise indicator calculation (with regard to user-defined area boundaries).
Network processing modifies the properties of the transport network which may produce different indicator values and assignment results. In the case of modifications to the network structure, a current assignment result is initialised. Inserting or deleting a network object, splitting zones or links, and aggregating zones represent modifications to the network structure. As long as only attribute data of network objects are modified, e.g. length of a link or position of a node, the current assignment result will not be initialised, although another assignment might produce a different result.
4-1
THE NETWORK EDITOR
Network processing modes
'HVFULSWLRQ RI 1HWZRUN REMHFWV =RQHV Zones are objects which describe areas with a particular land use and their location within the network (e.g. residential areas, commercial areas, shopping centres, schools). They are the origin and destination of travel demand within the transport network. Zones are linked to the transport network via connectors. Global zones are objects which incorporate several zones. Each zone may be an element of only one global zone.
*OREDO ]RQHV
1RGHV
Nodes are objects which define the location of stops and intersections in the network. Links start and end at nodes. Links connect up nodes and thus describe the rail and road infrastructure. A link has a particular direction, so that the opposite link represents a separate network object. Turning relations indicate whether turning is permitted at a node. For private transport systems, time penalty and capacities can be specified which describe the impact of the intersection on the network performance. Prohibited turning for public transport systems is taken into account in the construction of a line route. Prohibited turning for private transport systems is taken into account in a route search.
/LQNV
7XUQLQJ UHODWLRQV
&RQQHFWRUV Connectors connect up the zones to the transport network. They describe access and egress between a zones centroid and the public transport stop and/or private transport node. /LQHV 6XEOLQHV A public transport line is indicated in the timetable under a line name and usually travels the route in both directions. It may include one or several line variants, known as sublines, which differ, for example, in terms of the route travelled. Each subline is described by its line route and its timetable An area is a network object which represents e.g. a district or county. Based on the polygon that describes an areas boundaries it is possible to determine PrT and PuT indicators for each area. Census points serve for data management and display of counted link data. CPs are network objects allocated to a particular link at a particular position. Several census points can be defined per link.
$UHD
&HQVXV 3RLQWV
4-2
THE NETWORK EDITOR
Each of these network objects is described by means of attributes. VISUM distinguishes between: input attributes (e.g. stop numbers) and calculated attributes (e.g. passengers boarding at a stop).
Each attribute in VISUM has a name (e.g. Number), a code (e.g. Nr) and an attribute identifier. Depending on the space available in the dialog boxes, the name or the code is displayed. For outputs in ASCII files, the attribute identifiers are used, which are usually identical to the codes, but do not contain particular characters of the language-specific letter set. In this chapter, the attributes of each network object are made up as follows: 7\SH PrT + PuT $WWULEXWH Code Name (source) 'HVFULSWLRQ Description of attribute Default value: for input attributes only Value range: for input attributes only
The source indicates whether an attribute is an input attribute (=Input) or a calculated attribute (calculated, assignment, timetable etc.).
4-3
THE NETWORK EDITOR
1HWZRUN SURFHVVLQJ PRGHV
Three network processing modes are provided by VISUM: INSERT Mode, SINGLE SELECT Mode, MULTI SELECT Mode, which are used in combination with the currently active network object type. Processing mode and network object type can be activated in two ways: via the EDIT and SELECT menus or via the buttons in the Toolbar.
,16(57 PRGH

The INSERT mode allows new network objects to be defined. To insert a network object, do the following: $FWLYDWH ,16(570RGH via INSERT in the EDIT menu, or via the Toolbar button. $FWLYDWH QHWZRUN REMHFW W\SH via the SELECT menu - e.g. NODE, or via the Toolbar button.
)L[ SRVLWLRQ RI QHZ QHWZRUN REMHFW using left mouse button. ,QVHUW GLDORJ ER[ WUDQVIHU LQSXW DWWULEXWHV Network object attributes: accept or modify default values.
G
4-4
Modifying a previously inserted object requires switching to 6,1*/(6(/(&7 0RGH.
THE NETWORK EDITOR
6,1*/( 6(/(&7 PRGH

The SINGLE SELECT Mode allows a network object to be selected and then deleted or modified. To select a network object, do the following: $FWLYDWH 6,1*/(6(/(&70RGH via SINGLESELECT in the EDIT menu, or via the Toolbar button. $FWLYDWH QHWZRUN REMHFW W\SH via the SELECT menu - e.g. NODE, or via the Toolbar button.
6HOHFW WKH QHWZRUN REMHFW 0DUN RU 6HDUFK 0DUN REMHFW /HIW FOLFN directly on object: 6HDUFK IRU REMHFW 5LJKW FOLFN opens search dialog box, Select/Enter Search parameters: Number, name, code Number (direction by FromNode) Number, name or code of the ViaNode Number, name Zone: number, name node: number, name, code Number, name For lines, a dialog box appears immediately for search by name
1RGH /LQN 7XUQLQJ UHODWLRQ =RQH
On node On FromNode, then on ToNode On ViaNode or as link sequence: on FromNode, ViaNode, ToNode On zones centroid or within zonal boundaries
&RQQHFWRU On connected node or on zone *OREDO ]RQH 6XEOLQH $UHD &HQVXV 3RLQW On global zones centroid or within zonal boundaries On stop or stop sequence along line route
On area name or within boundary Search not provided. on census point or text position Double-click calls up 0RGLI\ $WWULEXWHV dialog box for all network object types! Number, Name, Code The relevant code must be available, otherwise search by number only is possible.
G
8
$FWLYDWH WKH DSSURSULDWH SURFHVVLQJ FRPPDQG LQ WKH (',7PHQX
4-5
THE NETWORK EDITOR
In SINGLESELECT mode, the following edit commands are defined for the various network object types: )XQFWLRQ 6HDUFK 0RGLI\ 'HOHWH 7H[W RQRII 6SHFLI\ FRXUVH 6KLIW WH[W $JJUHJDWH 6SOLW &RS\ Node X X X Link X X X X X X X TRel Zone GZon Conn SubL Area X X X X X X X X X X X X X X X X X X X X X X X X X X CP X X X X X
6HDUFK and any processing function in SINGLESELECTMODE can be called via EDIT menu (press left mouse-key) or via context menu (press right mouse-key). %DVLF IXQFWLRQ RI HGLW FRPPDQGV )XQFWLRQ 6HDUFK 0RGLI\ 'HOHWH 7H[W RQRII 6SHFLI\ FRXUVH 6KLIW WH[W *HQHUDO IXQFWLRQDOLW\ <F3> Allows searching for a particular object of the selected network object type.
<Enter> Modifies attributes of the selected object. <Del> Deletes the selected object from network. <F4> <F5> <F6> Switch off (or on) the label for the selected link for easily identifiable plots. Modifies the course of a link, a zonal boundary or a line route or the position of census point. Shifts position of node, of centroid (zone, global zone) or of label (area, zone, global zone, census point, link) for easily identifiable plots. Aggregates subline. Zone: Link: splits one zone into 2 new zones, insert node, splits link into 2 links.
$JJUHJDWH 6SOLW &RS\
<F7> <F8> <F9>
Copies a subline
4-6
THE NETWORK EDITOR
08/7, 6(/(&7 PRGH

The MULTISELECT mode allows an attribute for several network objects to be modified simultaneously. Do the following: $FWLYDWH 08/7,6(/(&7 PRGH via MULTISELECT in the EDIT menu, or via Toolbar button. $FWLYDWH QHWZRUN REMHFW W\SH via SELECT menu - e.g. NODE, or via Toolbar button.
6HOHFW WKH QHWZRUN REMHFWV WR EH PRGLILHG selected objects are active objects, objects not selected are passive objects. Define active objects to determine which network objects are to be edited in MULTISELECT mode; several options are available:
&RQWHQWV Specify filter criteria. /RFDWLRQ Specify spatial filter: Specify the polygon as Activates all objects located com- a rectangle: drag pointer while pletely within the polygon. The holding down left mouse following co-ordinates apply: button centroid for zones, global a polygon: while holding down zones and areas, <Ctrl> key, fix polygon points ViaNode for turning relations, one by one with left mouse FromNode and ToNode for click; release <Ctrl> key prior links. to marking the last point. Select area and apply the 2EMHFWV ZLWKLQ DUHD 6HW DFWLYH function (call via EXTRAS - MULTISELECT or context menu (right-click)). The current state of each object can still be redefined individually. ,QGLYLGXDO Change state of individual object: set active object to passive or passive object to active state. *OREDO For all objects: ,QYHUW: set all active objects to the passive state and all passive objects to the active state simultaneously, ,QLWLDOLVH: reactivate all objects. Mark an individual object of the active object type as described for SINGLESELECT mode. Right mouse click activates and left mouse-click closes the context menu: *.fil *.ane
or
Read filter parameters or active Filter parameters network objects from file: Active network objects
4-7
THE NETWORK EDITOR
In MULTISELECT mode, the following edit commands are defined for the various network object types: )XQFWLRQ 0RGLI\ 'HOHWH $JJUHJDWH *HQHUDWH Node Link X X X X TRel X Zone GZon Conn SLin X X X X X X X X X X X Area X CP X X
%DVLF IXQFWLRQV RI HGLW FRPPDQGV )XQFWLRQ 0RGLI\ *HQHUDO IXQFWLRQDOLW\ <Enter> For all or only the active network objects, the input attributes (except object identifiers such as Nr.) can be modifed. Enter FRQVWDQW attribute value, Enter IDFWRU for multiplication of attribute value, Assign DWWULEXWH values from another attribute, Specify IRUPXOD for calculations. Special functions for OLQNV, the texts (link labels) can also be switched on and off globally, and Link AddValues may be generated from Turning AddValue data. ]RQHV and JOREDO ]RQHV, the display of boundaries may be switched off globally. QRGHV, generate major flow from link types. VXEOLQHV the distances between stops can also be taken from the link lengths, and the lines running time between stops can be replaced by the link times of the transport system. Assign default values preset by type to attributes of WXUQLQJ UHODWLRQV, (time penalty and capacity) OLQNV (e.g. permitted transport systems) and standard timetable to VXEOLQHV. 'HOHWH $JJUHJDWH *HQHUDWH <Del> <F7> Delete active objects of the selected network object type. Aggregates active zones to form a single zone. Generate connectors from/to active zones.
4-8
Transport systems, Modes and Demand segments
THE NETWORK EDITOR
7UDQVSRUW V\VWHPV 0RGHV DQG 'HPDQG VHJPHQWV
7UDQVSRUW V\VWHP The transport supply consists of several transport systems. A transport system is defined by a type of transport: Private (PrT) or Public (PuT) transport or PuTWalk and a means of transport, e.g. car, tram, bike. 7\SH RI WUDQVSRUW V\VWHPV Basic characteristics of transport types are: 3ULYDWH WUDQVSRUW Travel times of a private transport system depend on the max. speed of the means of transport, e.g. 100 km/h for trucks, the speed permitted on the link used, e.g. 80 km/h, the capacity of the link used. 3XEOLF WUDQVSRUW Running times of vehicles of a public transport system and the dwell times at stops are determined by the timetable. 3X7:DON This mode serves to model walking transfer links between stops; This mode may be specified for one transport system only in a network model.
0RGH A mode connects one or several transport systems. A mode can include either one private transport system or several public transport systems. 'HPDQG VHJPHQW A demand segment belongs to exactly one mode. This way a demand segment is the link between transport supply and transport demand. As several demand segments can be defined for each mode, different types of demand can be combined in the transport model. Demand segments can be used for differentiation among: Population groups: Employed-PrT (car drivers), Empl-PuT, Students-PuT, etc. Ticket types: Single trip ticket, Monthly Pass, etc. Vehicle types: Car-Diesel, Car-Petrol, etc. For each demand segment a demand matrix has to be specified. Usually private transport demand matrices contain the demand in car units, whereas passenger units are used for public transport demand matrices.
4-9
THE NETWORK EDITOR
For calculation of O-D trips (PrT) from car units the occupancy rate can be specified for each demand segment. $VVLJQPHQW RI GHPDQG VHJPHQWV For private transport demand segments of different modes can be assigned simultaneously by Multi-Procedures (Multi-Incremental, Multi-Equilibrium, MultiLearnProcedure, Tribut). Each iteration step requires a mode-specific route search, as each mode has a particular impedance function for each transport system. For public transport only the demand segments of one public transport mode can be selected for assignment calculation. For modelling more than one PuT mode (e.g. PuT-Long, PuT-Local), a separate assignment is required for each mode, as route search needs to consider different transport systems. For each demand segment particular split parameters can be defined (see assignment parameters). This serves to model e.g. deviating tolerance levels towards transfers. 5HVXOWV RI DVVLJQPHQW Volumes calculated by assignment can be displayed through the following attributes which may be selected for graphical display of volume bars along links: Vol-PrT[Veh]: Number of PrT vehicles = PrT demand segments Vol-PrT[Pers]: PrT persons = PrT demand segments x occupancy rate Vol-PrT[PCU]: PrT passenger car units = PrT demand segments x PCU Vol-PrT[Sat]: Number of PrT passenger car units including a basic volume Vol-PuT[Pers]: Number of PuT passengers = PuT demand segments Vol-TSys[Veh]: Number of vehicles per transport systems (only PrT) Vol-TSys[Pers]: Number of persons per transport systems Vol-DSeg[Veh]: Number of vehicles per demand segment (only PrT) Vol-DSeg[Pers]: Number of persons per demand segment Vol-DSeg-TSys[Pers]: Persons per demand segment and transport system
4-10
THE NETWORK EDITOR
$WWULEXWHV RI WUDQVSRUW V\VWHP PRGH GHPDQG VHJPHQW

$WWULEXWHV RI 7UDQVSRUW V\VWHPV 7\SH PrT+PuT $WWULEXWH TSysCode Transport system code (Input) TSysName Transport system name (Input) 'HVFULSWLRQ Code of the transport system. Range: one character, A-Z or 0-9 Name of the means of transport, e.g.: P Car, T Truck, B Bus. Range: Text30 Transport system type: PrT: Private transport, PuT: Public transport, PuTWalk: PuT Walking transfer link. Range: PrT or PuT or PuTWalk Passenger car units to describe the impact of one vehicle of a private transport system on the capacity. Default value: 1.0 Range: 0.0 - 9.9 Default speed of a TSys. Default values: PrT: max. spped (200 km/h) PuT: mean speed (50 km(h) PuTWalk: avg. walking speed (4 km/h) Range: Long Int
PrT+PuT
PrT+PuT
TSysMode Transport system mode (Input)
PrT
PCU Pass. Car Units (Input)
PrT+PuT
TSys-v TSys-v (Input)
4-11
THE NETWORK EDITOR
7\SH PuT
$WWULEXWH NumLines Num Lines (subline) NumService Num Services (subline) NumSLines Num sublines (subline) NumVeh Num vehicles (roster planning) Stop-ser Stop-served (subline) SeatKm (subline) ServiceT ServiceTime (subline) VehKm VehicleKm (subline) OpTime OperationTime (subline) Passh Passengerhours (assignment) PassKm PassengerKm (assignment) TWT Transfer waiting time (assignment)
'HVFULSWLRQ Number of lines which belong to the transport system. Number of services (vehicle trips) of all sublines of the transport system. Number of sublines which belong to the transport system. Number of required vehicles (result from roster calculation). Number of served stops by all sublines of transport system. Seat kilometers = VehKm x number of seats. Service time for passenger transport of all lines. Vehicle kilometers of all sublines = Line length x VehTrips. Operating time (out-of-depot time) of all lines. Passenger hours = number of line trips x in vehicle time. Passenger kilometers = number of line trips x trip length. Transfer waiting time of all passengers boarding this Transport system.
PuT
PuT
PuT
PuT
PuT PuT
PuT
PuT
PuT
PuT
PuT
4-12
THE NETWORK EDITOR
7\SH PuT
$WWULEXWH aLinRunT avg. running time of line (calculated) aVehTripLength avg. vehicle trip length (calculated) LinTrips LineTrips total (assignment) RefNet Reference Network (Input)
'HVFULSWLRQ Average running time of vehicle trips.
PuT
Average length of vehicle trips.
PuT
Total number of line trips = number of boarding passengers. Code of reference network for a demand type (before VISUM vers. 7). In VISUM 7 demand segments are generated, the attribute will no longer be saved to *.net file.
PrT
PuT
LinNetLenCS Length of used network = sum of all used LineNetLengthCrossSec links, where both directions are calculated (subline) only once. LinNetLenDir LineNetLengthDir (subline) NetLenCS NetLengthCrossSection (link network) NetLenDir NetLengthDir (link network) Length of used network = sum of all used links, where both directions are calculated separately. Length of permitted network = sum of all permitted links, where both directions are calculated only once. Length of permitted network = sum of all permitted links, where both directions are calculated separately.
PuT
PuT
PuT
4-13
THE NETWORK EDITOR
7\SH PuT PuT
$WWULEXWH Cost (subline) CostHour Cost-Hour (subline) CostKm Cost-Km (subline) CostLink Cost-Link (subline) CostOp Cost-Operator (subline) CostStop Cost-Stop (subline) CostVeh Cost-Vehicle (subline) CostCovTot Cost cover total (calculated) RevTot Revenue total (subline)
'HVFULSWLRQ Cost = CostKm + CostHour + CostVeh + CostLink + CostStop + CostOp. Cost-Hour = OpTime x HourCost.
PuT
Cost-Kilometer = VehKm x KmCost.
PuT
Cost from link cost CostLink2 + CostLink3.
CostLink1
PuT
Cost from operator cost = CostOp1 + CostOp2 + CostOp3. Cost from stop cost = CostStop1 + CostStop2 + CostStop3. Cost-Vehicle = NumVeh x VehCost.
PuT
PuT
PuT
Total cost coverage operational cost. Total revenue of all lines.
Revenue
PuT
4-14
THE NETWORK EDITOR
$WWULEXWHV RI 0RGHV 7\SH PrT+PuT $WWULEXWH Code (Input) PrT+PuT Name (Input) PrT+PuT TSysCode (Input) 'HVFULSWLRQ Code. range: Text1 Name. range: Text30 List of permitted transport systems default: from link type range: defined transport systems
$WWULEXWHV RI 'HPDQG VHJPHQWV 7\SH PrT+PuT $WWULEXWH Code (Input) PrT+PuT Name (Input) PrT+PuT Mode (Input) PrT+PuT OccRate OccupancyRate (Input) 'HVFULSWLRQ Code. range: Text1 Name of demand segment. default: empty string range: Text20 Mode the DSeg was specified for.. range: Text1 Occupancy rate = factor for converting the matrix value into number of travelers. range: Real
4-15
THE NETWORK EDITOR
,QVHUW WUDQVSRUW V\VWHP
(;75$6 PHQX 75$1632576<67(06 7UDQVSRUW V\VWHPV SURSHUW\ VKHHW 7UDQVSRUW V\VWHPV page ,QVHUW button
4-16
THE NETWORK EDITOR
,QVHUW WUDQVSRUW V\VWHP Code: 1 character (A-Z or 0-9), Name: up to 30 characters, Type: PrT, PuT or PuTWalk, PCU: passenger car units to describe impact of one vehicle by PrT-TSys, link types the TSys may use.
Select link types permitted for the TSys (<Ctrl> - left mouse key). vMax-PrT: maximum speed of PrT means of transport v-PuT: average speed of a PuT means of transport
4-17
THE NETWORK EDITOR
0RGLI\ WUDQVSRUW V\VWHP
(;75$6 0HQX 75$1632576<67(06 0RGLI\ button 0RGLI\ WUDQVSRUW V\VWHP GLDORJ 3X76\V TSysName
3U76\V TSysName Car-Units
Y0D[3U7 Y3U7 and Y3X7 may be modified by link type or global link type in the EDIT menu with LINK TYPES. If a modification to FRGH or transport PRGH is necessary: delete the transport system and reinsert with the correct code/mode.
4-18
THE NETWORK EDITOR
,QVHUW PRGH
(;75$6 0HQX 75$1632576<67(06 7UDQVSRUW V\VWHPV SURSHUW\ VKHHW 0RGHV page ,QVHUW button
4-19
THE NETWORK EDITOR
,QVHUW 0RGH GLDORJ Code: 1 character (A .. Z), Name: max. 30 characters, Select type under 76\V the relevant transport system type and the relevant transport system(s): Type PrT: Type PuT: Select one TSys. Select all permitted TSys.
4-20
THE NETWORK EDITOR
0RGLI\ PRGH
(;75$60HQX 75$1632576<67(06 7UDQVSRUW V\VWHPV SURSHUW\ VKHHW 0RGHV SDJH Select mode 0RGLI\ button
0RGLI\ 0RGH" GLDORJ The mode code is kept, only name and transport system settings under 76\V (see ,QVHUW 0RGH) can be changed.
4-21
THE NETWORK EDITOR
,QVHUW GHPDQG VHJPHQW
(;75$6 0HQX 75$1632576<67(06 7UDQVSRUW V\VWHPV SURSHUW\ VKHHW 'HPDQG VHJPHQWV page ,QVHUW button
,QVHUW 'HPDQG VHJPHQW Enter Code: 1 character (A ... Z), Name: max. 30 characters, occupancy rate (only relevant to PrT) and select under 0RGH the relevant Mode:
4-22
THE NETWORK EDITOR
0RGLI\ GHPDQG VHJPHQW
(;75$6 0HQX 75$1632576<67(06 7UDQVSRUW V\VWHPV SURSHUW\ VKHHW 'HPDQG VHJPHQWV page Select Demand segment 0RGLI\ button
0RGLI\ 'HPDQG VHJPHQW GLDORJ The code is kept, only name, occupancy rate and settings under Mode can be edited.
4-23
THE NETWORK EDITOR
'HOHWH WUDQVSRUW V\VWHP PRGH RU GHPDQG VHJPHQW
(;75$6 0HQX 75$1632576<67(06 Select page: Transport systems, Modes or Demand segments.
Select one of the listed entries and click 'HOHWH button 0RGH
76\V
A transport system may not be deleted as long as PuT lines have been specified for it, may be deleted even though it is still permitted for links (modes and demand segments defined for it will also be deleted).
4-24
Nodes
THE NETWORK EDITOR
1RGHV
Nodes represent PrT intersections and PuT stops. They are the start and end points of links. Nodes can be edited using the following commands:
(GLW FRPPDQG 6HDUFK 0RGLI\ 'HOHWH 7H[W RQRII 6SHFLI\ FRXUVH 6KLIW WH[W $JJUHJDWH 6SOLW &RS\
6KRUWFXW <F3> <Enter> <Del> <F4> <F5> <F6> <F7> <F8> <F9> X X X X X X
4-25
THE NETWORK EDITOR
Nodes
1RGH DWWULEXWHV

7\SH PrT+PuT $WWULEXWH Nr Number (Input) Name (Input) PrT+PuT Code (Input) Type (Input) X-Coord X-Coordinate (Input) Y-Coord Y-Coordinate (Input) Con-PrT Connector-PrT (network) Con-PuT Connector-PuT (network) Stop (Input) 'HILQLWLRQ Number of node. default: max. NodeNr+1 range: 1-999999999 Name of node. default: empty string range: Text20 Code of node. default: empty string range: Text8, no number as first character Type of node. default: 0 range: 00 99 X-Coordinate. default: from mouse position range: Real Y-Coordinate. default: from mouse position range: Real Node is connected by a PrT connector (yes/no). Node is connected by a PuT connector (yes/no). 0 node is no public transport stop. 1 node is a public transport stop. default: last node range: yes/no Number of arms. range: Int
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT
PuT
PuT
PrT+PuT
NumArms Num Arms (link network)
4-26
Nodes
THE NETWORK EDITOR
7\SH PrT+PuT
$WWULEXWH TotNumConZone Total number Conn.Zones (connector) NumConZone Num ConnectedZones (connector) NumOConZone Num Orig.Conn.Zones (connector) NumDConZone Num Dest.Conn.Zones (connector) AddVal1 AddValue1 (user-defined)
'HILQLWLRQ Total number of zones which are connected via this node (PrT and Pu, both directions). range: Int Number of zones which are connected (by mode, both directions) via this node. range: Int Number of zones which are connected (orig. conn. only, PrT or PuT) via this node. range: Int Number of zones which are connected (dest. conn. only, PrT or PuT) via this node. range: Int AddValue1. range: Long Int
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
AddVal2 AddValue2 (user-defined) AddVal3 AddValue3 (user-defined) SumTRAddV1 SumTurnRelAddV1 (calculated) SumTRAddV2 SumTurnRelAddV2 (calculated) SumTRAddV3 SumTurnRelAddV3 (calculated) Vol-PrT Volume-PrT (assignment)
AddValue2. range: Long Int AddValue3. range: Long Int Sum of AddValue1 relations by node. Sum of AddValue2 relations by node. Sum of AddValue3 relations by node. data of turning
PrT+PuT
PrT
PrT
data
of
turning
PrT
data
of
turning
PrT
Node volume caused by Private transport vehicles.
4-27
THE NETWORK EDITOR
Nodes
7\SH PuT
$WWULEXWH NumArr Num PuT Arrivals (timetable) NumDep Num PuT Departures (timetable) NumService Num Services (timetable) NumLines Num Lines (line network) NumSLines Num sublines (line network) NumArrSys Num Arrivals Sys (line network) NumDepSys Num Departures Sys (line network) NumServiceSys Num ServiceSys (line network) NumLinesSys Num LinesSys (line network) NumSLinesSys Num SLinesSys (line network)
'HILQLWLRQ Number of vehicle trips arriving at stop.
PuT
Number of vehicle trips departing from stop. Number of services (vehicle trips), which use the node. Number of lines, which serve the node.
PuT
PuT
PuT
Number of sublines, which serve the node.
PuT
Number of vehicle trips per PuT-system arriving at stop. Number of vehicle trips per PuT-system departing from stop. Number of services (vehicle trips) of one transport system, which serve the node. Number of lines per PuT-system, which serve the node. Number of sublines of one transport system, which serve the node.
PuT
PuT
PuT
PuT
4-28
Nodes
THE NETWORK EDITOR
7\SH PuT
$WWULEXWH PassThroughNoStop (assignment) PassThroughStop (assignment) PassAlight (assignment) PassBoard (assignment) PassTransDir PassTransDirect (assignment) PassTransfer (assignment)
'HILQLWLRQ PuT passengers who traverse the stop in a PuT line; the stop is not served by the line. PuT passengers who traverse the stop in a PuT line, which serves the stop, or which use walking links to and from the stop. PuT passengers alighting the vehicle at stop. PuT passengers boarding the vehicle at stop. Number of PuT passengers, who transfer to another PuT line at this stop. Transfer passengers using a PuT Walk link (transfer link) are not counted. PuT passengers, who transfer to another PuT line at that stop. Transfer passengers, who use a PuT Walk link (transfer link), are only counted, when they board another line. PassTransTot = PassTransDir + PassTransAW + PassTransWB. Number of PuT passengers, who alight at this stop, use a transfer link to another stop, where they board another line. Number of PuT passengers, who alighted at a different stop, then used a transfer link to this stop in order to board another line. Transfer waiting time of all passengers, who transfer at stop. PuT
PuT
PuT PuT PuT
PuT
PuT PuT
PassTransTot (assignment) PassTransAW PassTransAlightWalk (assignment) PassTransWB PassTransWalkBoard (assignment) TWT Transfer waiting time (assignment)
PuT
PuT
4-29
THE NETWORK EDITOR
Nodes
7\SH PuT
$WWULEXWH StopCost1, 2, 3 (Input)
'HILQLWLRQ Public transport stop cost for depreciation, maintenance or link usage. default: 0 range: Real Cost for stop usage per vehicletrip. range: Real
PuT
StopCost1VT StopCost1 VehTrip StopCost2VT StopCost2 VehTrip StopCost3VT StopCost3 VehTrip (calculated) PrT-Isoc-Time PrT-Isochrone-Time (Isochrone) PuT-Isoc-Time PuT-Isochrone-Time (Isochrone)
PrT
PrT travel time from Iscochrone starting node to node. PuT travel time from Iscochrone boarding stop to stop.
PuT
PuT
PuT-Isoc-Transfers PuT number of transfers from Iscochrone PuT-Isochrone-Transfers boarding stop to stop. (Isochrone) MFNod1 MajorFlow Node1 (link network) MFNod2 MajorFlow Node2 (link network) MLnk1 MajorLink1 (Input) MLnk2 MajorLink2 (Input) Adjacent node of major link 1.
PrT
PrT
Adjacent node of major link 2.
PrT
Number of major link 1. default: from rank of link range: defined link number Number of major link 2. default: from rank of link range: defined link number
PrT
4-30
Nodes
THE NETWORK EDITOR
,QVHUW QRGH

Activate INSERT mode. Activate NODE network object type.
G
8
Activate graphic representation of isolated nodes on 1RGH page under PARAMETERS in the GRAPHICS menu Fix node position by clicking left mouse button. ,QVHUW QRGH GLDORJ %DVLF WDE
4-31
THE NETWORK EDITOR
Nodes
1XPEHU if n is the highest node number in the network, VISUM suggests n+1. 7\SH the node type is used to categorise the node. 0 or the most recently entered node type is suggested. 1DPH FRGH $GG9DOXHV optional to describe the node. 3RVLWLRQ the coordinates of the mouse position can be corrected. 6WRS mark PuT stop with 6WRS.
Insert more nodes and links. To insert a node on a link, it is possible to split the link using the SPLIT LINK function.
6HOHFW QRGH

Activate SINGLE SELECT mode and NODE network object type.
To select a node: mark node by clicking left mouse button. search for node by clicking right mouse button and <F3>.
Then call up desired edit command. Double-clicking on a node or pressing <Enter> immediately opens the dialog box for the MODIFY NODE command.
4-32
Nodes
THE NETWORK EDITOR
'HOHWH QRGH

Select node. Delete node with DELETE in the EDIT menu, or <Del> shortcut. A node which is still being served by public transport lines cannot be deleted. To delete a stop without deleting the node, set the Stop attribute from active to inactive o. This is only permitted in the case of nodes which are not the origin or destination terminal of a line.
'LDORJ ER[HV IRU '(/(7(12'( if more than 2 links start/end at the node.
if only 2 links start/end at the node
'HOHWH button: All links which start or end at the selected node will also be deleted. &RQQHFW button: A new link number must be entered. For the new link, VISUM takes the lower link type and the transport systems which were permitted on the two previous links.
There is no option to connect the two links if a link already exists between the adjacent nodes of the node which is to be deleted, as 2 nodes can only be linked once.
4-33
THE NETWORK EDITOR
Nodes
(GLW QRGH

0RGLI\ QRGH SRVLWLRQ PHUJH QRGHV
Select node Press <F6> to call the Shift function. Drag the selected node to the desired position while holding down the mouse button. The resulting direct distance of links from/to the shifted node is calculated automatically and can be selected for link length.
If one node is dragged to the position of another node, the two can be merged. The current result of assignment is deleted. Nodes cannot be merged if parallel links would be created as a result, or a subline serves both nodes.
'LDORJ ER[ 0HUJLQJ QRGHV
Select one of the nodes: VISUM accepts the node number selected by the user; all other attribute values of the selected node are accepted as default values and can be modified. Set link length option. No adjustment of length and running time of a FromStop-ToStop relation for existing PuT lines.
4-34
Nodes
THE NETWORK EDITOR

0RGLI\ QRGH DWWULEXWHV

Select node. Call up 0RGLI\ QRGH with MODIFY in the EDIT menu, or <Enter> shortcut, or Double-click on selected node. 0RGLI\ QRGH GLDORJ %DVLF WDE All input attributes, also the node number can be modified.
%DVLF
When the node Nr is modified, the result of assignment is deleted.
4-35
THE NETWORK EDITOR
Nodes
0RGLI\ QRGH GLDORJ 7LPHWDEOHV WDE 7LPHWDEOH Modify timetables of all lines on node.
Tabs only active for PuT stops 7LPHWDEOH, -&RVW, -7DULII ]RQHV. The timetable can also be edited using MODIFY LINE.
4-36
Nodes
THE NETWORK EDITOR
0RGLI\ QRGH GLDORJ &RVW 6WRS&RVW WDE Only for /LQH FRVWLQJ Add-on users:
Enter stop-related attribute values Cost1, Cost2 and/or Cost3 in [monetary units].
Specify stop cost parameters: CALCULATE menu LINE COSTING command 6WRS FRVW button. Stop cost values are saved with the network file (see $NODE).
4-37
THE NETWORK EDITOR
Nodes
0RGLI\ QRGH GLDORJ 7DULII ]RQHV 7DULII ]RQHV WDE
To allocate stops and tariff zones or subzones also the PUT ZONES command can be called in the EXTRAS menu.
TARIFF
4-38
Nodes
THE NETWORK EDITOR
0RGLI\ QRGH GLDORJ 0DMRU IORZ 0DMRU IORZV WDE
The major flow describes the direction of the priority flow. It is indicated by the FromLink, ViaNode and ToLink. The major flow is fixed: DXWRPDWLFDOO\ by the user-defined rank per link type, i.e. the highest-ranked links which are connected to the node, or specified PDQXDOO\ by the user via the < and > buttons.
4-39
THE NETWORK EDITOR
Nodes
(GLW PXOWLSOH QRGHV

Activate MULTI SELECT mode and NODE network object type.
6SHFLI\ DFWLYH QRGHV IRU HGLWLQJ by one of the methods described below or a combination of them. Active nodes are only those which satisfy all current specifications! Filter: specify node filter MultiSelect selection specified in MULTI SELECT mode as rectangle: drag while holding down left mouse button; polygon: while holding down the <Ctrl> key, fix the polygon points one by one by clicking left mouse button. Release <Ctrl> prior to marking the last point. All nodes within the polygon are set to active. AREA through : Call the 2EMHFWV ZLWKLQ $UHD 6HW DFWLYH function
and right-hand mouse-click or MULTISELECT command in the EXTRAS menu and select area. Modify state of single object: set single nodes in MULTI SELECT mode to active/passive by clicking left mouse button. This can also be used for fine editing of MultiSelect polygons. Nodes which are passive because of current filter parameters cannot be set to active! Invert: set all active nodes to passive and all passive nodes to active. Click the right mouse button to call ,QYHUW. File: set nodes to active by reading the following file type(s): filter parameters *.fil, specified active network objects *.ane. If there are no passive nodes in the network, the modifications apply to all nodes. Nodes which are passive due to node filters or $UHD settings can be treated as active nodes when editing in MULTISELECT mode: Disable the 2QO\ DFWLYH option. Display of current status (number of active or passive links) via PROGRAM STATUS in the EXTRAS menu.
4-40
Nodes
THE NETWORK EDITOR

0RGLI\ DWWULEXWH IRU PXOWLSOH QRGHV

Call up 0RGLI\ DWWULEXWH IRU PXOWLSOH QRGHV with MODIFY in the EDIT menu, or double-click left mouse button, or <Enter> shortcut. All input attributes except the node Nr., name and code can be edited. Calculated attributes (e.g. Volume-PrT) cannot be modified. 1RGH DWWULEXWHV GLDORJ )RUPXOD WDE The listed node attributes can be modified.
The selected attribute is not regarded for 6SHFLDO )XQFWLRQV.
4-41
THE NETWORK EDITOR
Nodes
The following sequence must be followed if an attribute is to be modified for multiple nodes: Select option: Edit only active nodes? o Edit all nodes. Select attribute to be edited (e.g. node-AddValue 2), Activate button for editing operation: Enter value, Set $GG option to active/inactive, Confirm editing operation with OK, Close 1RGH DWWULEXWHV dialog box with OK.
G
Constant
Only stops which are not served by PuT lines are considered, when Constant = 0 is specified for attribute 6WRS (node is no stop).
The attribute selected for editing is AddValue 2. The entered constant is added to the existing Node-AddValue 1 for all active nodes. AddValue 2(new) = AddValue 2(old) + 500
Factor
Attribute
AddValue 2(new) = AddValue 2(old) x 2.5
AddValue 2 = AddValue 1 x 2.0 Previous node AddValue 1 will be overwritten.
4-42
Nodes
THE NETWORK EDITOR
Formula
7UDQVIRUPDWLRQ RI ;FRRUGLQDWHV RI QRGHV E\ OHQJWK XQLWV
1. Initial situation: 2. <Enter>: Change ;FRRUGLQDWH of all active nodes 3. 6SHFLI\ )RUPXOD
4. Confirm OK, redraw screen:
5. Resulting link length is not adapted automatically for links from/to shifted nodes; Set Link length = Direct distance, if applicable.
4-43
THE NETWORK EDITOR
Nodes
Round
Enter rounding factor for values of the selected attribute.
4-44
Nodes
THE NETWORK EDITOR

$XWRPDWLF PDMRU IORZ JHQHUDWLRQ

1RGH DWWULEXWHV GLDORJ 6SHFLDO IXQFWLRQV WDE Major flows at selected (active) nodes can be generated automatically. Therefore the ranks of the link types are regarded.
0DMRU IORZV
0DMRU IORZV Set option and click +6SHFLI\ PDMRU IORZV DXWRPDWLFDOO\ button.
4-45
THE NETWORK EDITOR
Nodes

$GG9DOXHB1RGHV GDWD JHQHUDWLRQ

1RGH DWWULEXWHV GLDORJ 6SHFLDO IXQFWLRQV WDE
$GG9DOXH AddValue data for the selected (active) nodes can be generated 1RGHV automatically from the Nr of the zone, the area or the global zone, the node is located in.
*HQHUDWH $GG9DOXHB1RGHV GDWD Set option, select network object type (polygon: Area, Zone, Global zone), select AddValue 1, 2 or 3.
Click 6HW: button. Save data with version file or to AddValues_Nodes file.
4-46
Nodes
THE NETWORK EDITOR

'HOHWH DFWLYH QRGHV

Call 'HOHWH DFWLYH QRGHV through DELETE in the EDIT menu or Shortcut <Del>. A node traversed by PuT lines cannot be deleted. 'HOHWH DFWLYH QRGHV GLDORJ This statistics sums up all active: connector nodes isolated nodes nodes with only one link nodes with 2 links multi-way links.
+ + + +
Options for GHOHWH DFWLYH QRGHV for each listed category: delete active nodes of the category. o do not delete active nodes of the category. If only GHOHWH DFWLYH QRGHV ZLWK OLQNV is activated: connect links at deleted node, or o delete links from/to deleted node. Confirm OK: The current assignment result is deleted.
THE NETWORK EDITOR
Links
/LQNV
Links define roads and rail connections in the transport network. They connect up nodes, i.e. private transport intersections and public transport stops. A link is displayed as a line with a particular direction and is thus described by the FromNode and ToNode numbers. The outward and return directions of a link are considered as two separate objects in the network model to which the same link number has been assigned. For every link, the permitted transport systems of the PrT mode and the PuT mode which are permitted to use this link must be indicated. Links can be edited using the following commands: (GLW FRPPDQG 6HDUFK 0RGLI\ 'HOHWH 7H[W RQRII 6SHFLI\ &RXUVH 6KLIW 7H[W $JJUHJDWH 6SOLW &RS\ 6KRUWFXW <F3> <Enter> <Del> <F4> <F5> <F6> <F7> <F8> <F9> X X X X X X X X X
4-48
Links
THE NETWORK EDITOR
/LQN DWWULEXWHV

/LQN W\SHVSHFLILF OLQN DWWULEXWHV
VISUM provides link types 00..99; Link types are used for network categorization and for defining standard parameters of link attributes. /LQN DWWULEXWH YDOXHV IRU HDFK OLQN W\SH 7\SH $WWULEXWH 'HILQLWLRQ Number of link type. range: 00 - 99 Name of link type. range: Text20 List of permitted transport systems. range: defined transport systems Capacity of private transport. range: Long Int, >0
PrT+PuT Nr Number (Input) PrT+PuT Name (Input) PrT+PuT TSysCode (Input) PrT Cap-PrT Capacity-PrT (Input)
PrT
v0-PrT Free flow speed of private transport. v0-PrT free flow speed (Input) range: Long Int, >0 vMax-PrT (Input) vMin-PrT (Input) v-PuT v-PuT speed (Input) Rank (Input) Maximum speed for each private transport system. range: Long Int, >0 Minimum speed by link type, e.g. congestion speed. range: Long Int, >0 Default speed for a public transport system, which is used to calculate running times of a link. range: Long Int, >0 Rank defines the hierarchy of link types which is used to determine major flows. range: Long Int, >0
PrT
PrT
PuT
PrT
4-49
THE NETWORK EDITOR
Links
0RGLI\LQJ OLQN DWWULEXWH YDOXHV IRU VHOHFWHG OLQN W\SHV
(;75$60HQX /,1.7<3(6 Select JOREDO W\SHV (0* -9*) or W\SHV (00 - 99) and select the link types to which the modifications apply with <Ctrl> and the left mouse button. The following attributes can be defined: name capacity-PrT in [passenger-car units] v0-PrT vMin-PrT rank permit / do not permit o defined transport systems vMax-PrT: maximum speed of PrT means of transport v-PuT: default speed for PuT means of transport.
4-50
Links
THE NETWORK EDITOR

%DVLF OLQN DWWULEXWHV
In addition to the link attributes listed here, VISUM also handles other link attributes, e.g. for the environmental impact analysis. 7\SH PrT+PuT $WWULEXWH Nr Number (Input) Type (Input) 'HILQLWLRQ Number of link. default: max. LinkNr+1 range: 1-999999999 Type of link for network classification; specifies type-specific default values for: permitted TSys TSysCode, PrT-Capacity Cap-PrT, PrT-Speed v0-PrT, PuT-Running time t-PuT. default: last link type range: 00 99 Global type of link (0*-9*)
PrT+PuT
PrT+PuT
GType GlobalType (from Type) SType SubType (from Type) FromNodeNr (Input) FromNodeCode (from FromNode) FromNodeName (from FromNode) ToNode ToNodeNr (Input) ToNodeCode (from ToNode) ToNodeName (from ToNode)
PrT+PuT
Subtype of link (*0-*9)
PrT+PuT
Number of the FromNode of a link. default: selected with mouse range: defined node numbers Code of the FromNode of a link. Name of the FromNode of a link. Number of the ToNode of a link. default: selected with mouse range: defined node numbers Code of the ToNode of a link. Name of the ToNode of a link.
PrT+PuT PrT+PuT PrT+PuT
PrT+PuT PrT+PuT
4-51
THE NETWORK EDITOR
Links
7\SH PrT+PuT
$WWULEXWH FromX From XCoord (from FromNode) FromY From YCoord (from FromNode) ToX To XCoord (from ToNode) ToY To YCoord (from ToNode) Oneway (Input) Length (Input) LengthDir Length-direct distance (calculated) LengthPoly Length-Polygon (calculated) TSysCode (Input) Cap-PrT Capacity-PrT (Input) v0-PrT (Input)
'HILQLWLRQ X-Coordinate of the FromNode.
PrT+PuT
Y-Coordinate of the FromNode.
PrT+PuT
X-Coordinate of the ToNode.
PrT+PuT
Y-Coordinate of the ToNode.
PrT+PuT PrT+PuT
One-way road identifier. range: yes/no Link length default: direct distance range: Long Int, >0 Direct distance between FromNode and ToNode of a link (as the crow flies). Direct distance between FromNode and ToNode regarding intermediate points of the link course. List of permitted transport systems default: from link type range: defined transport systems Private transport capacity of a link within a time interval. default: from link type range: Long Int Link-related maximum speed of private transport (free flow). default: from link type range: Long Int
PrT+PuT
PrT+PuT
PrT+PuT
PrT
PrT
4-52
Links
THE NETWORK EDITOR
7\SH PuT
$WWULEXWH t-PuT (Input) Name (Input) AddVal1 - 3 AddValue1, 2, 3 (user-defined) AddVal-Subline (user-defined) AddVal-TSys (user-defined) NumLines Num Lines (line network) NumSLines Num sublines (line network) NumSLinesSys Num SLinesSys (line network) NumService Num Service (timetable) NumServiceSys Num ServiceSys (timetable) NumService/TI Num Service/TI (timetable) NumServiceSys/TI Num ServiceSys/TI (timetable)
'HILQLWLRQ Running time for each PuT system. default: from link type, length range: time interval Name of street. default: empty string, range: Text20 AddValue1, 2 and 3 of link range: Long Int Sum of AddValues of sublines using the link. default: 0 AddValue for every permitted TSys. default: 0 Number of lines which use the link.
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT PuT
PuT
Number of sublines, which use the link.
PuT
Number of sublines of one transport system, which use the link. Number of services (vehicle trips), which use the link. Number of services (vehicle trips) of one transport system, which use the link. Number of services (vehicle trips), which use the link within a time interval (timefilter). Number of services (vehicle trips) of one transport system, which use the link within a time interval (timefilter).
4-53
PuT
PuT
PuT
PuT
THE NETWORK EDITOR
Links
7\SH PrT
$WWULEXWH t0-PrTSys (calculated) v0-PrTSys (calculated)
'HILQLWLRQ Running time by private transport system in unloaded network, calculated from link length and v0-PrTSys. Free flow speed by private transport system (uncharged network); Minimum of v0-PrT and vMax-PrT. default: from link type range: Long Int Current PrT running time by private transport system in loaded network, which results from the volume- and capacitybased CR function. Current speed of a private transport system. PrT system-specific value of the capacitybased impedance function considering the current traffic volume. Road toll by transport system default: 0 range: Real Number of census points on link.
PrT
PrT
tCur-PrTSys (assignment)
PrT PrT
vCur-PrTSys (assignment) Imp-PrTSys Impedance-PrTSys (assignment) Toll-PrTSys (Input) NumCP NumCensusPoints (calculated)
PrT
PrT
PrT
CP-AddVal1-5 Total calculated from the AddVal-values CP-AddValue1, 2, 3, 4, 5 (1..5) of all Census Points on the link. (calculated) Cap-PuT-Seat (calculated) Cap-PuT-Seat/TI (calculated) Cap-PuT-Total (calculated) Cap-PuT-Total/TI (calculated) Public transport seats capacity of all lines using the link. Public transport seats capacity of all lines using the link within a time interval (timefilter). Total public transport capacity of all lines using the link. Total public transport capacity of all lines using the link within a time interval (time filter).
PuT PuT
PuT PuT
4-54
Links
THE NETWORK EDITOR
7\SH PuT
$WWULEXWH Cost1-PuTSys (Input)
'HILQLWLRQ Public transport link cost for depreciation, maintenance or link usage default: 0 range: Real Public transport link cost for depreciation, maintenance or link usage default: 0 range: Real Public transport link cost for depreciation, maintenance or link usage default: 0 range: Real Cost for linkusage per vehicletrip
PuT
Cost2-PuTSys (Input)
PuT
Cost3-PuTSys (Input)
PuT
Cost1VT-PuTSys Cost1 VehTrip-PuTSys (calculated) Cost2VT-PuTSys Cost2 VehTrip-PuTSys (calculated) Cost3VT-PuTSys Cost3 VehTrip-PuTSys (calculated) FlowBundle (flow bundle) Sat-PrT Saturation-PrT (calculated) Sat-PuT-Seat (calculated) Sat-PuT-Tot (calculated) VehKm-PuT VehicleKm-PuT (calculated)
PuT
Cost for linkusage per vehicletrip
PuT
Cost for linkusage per vehicletrip
PrT+PuT PrT
Flow bundle volume. Private transport saturation = PrT-Volume / PrT-Capacity range: Percent Public transport seats saturation =PuTVolume / Seats range: Percent Total public transport saturation = PuTVolume / Seats and standing capacity range: Percent Vehicle kilometers summed up from all lines which use the link
PuT
PuT
PuT
4-55
THE NETWORK EDITOR
Links
7\SH PrT+PuT
$WWULEXWH VolPers-DSeg Volume-DSeg[Pers] (assignment)
'HILQLWLRQ Link volume: segment. persons per demand
PrT+PuT
VolPers-DSeg-Sys Link volume: persons per Volume-DSeg-Sys[Pers] segment + transport system. (assignment) VolPers-PuT Volume-PuT[Pers] (assignment) VolPers-Sys Volume-Sys[Pers] (assignment) VolPers-PrT Volume-PrT[Pers] (assignment) VolVeh-PrT Volume-PrT[Veh] (assignment) VolVeh-Sys Volume-Sys[Veh] (assignment) VolVeh-DSeg Volume-DSeg[Veh] (assignment) VolPCU-PrT Volume-PrT[PCU] (assignment) VolSat-PrT Volume-PrT-Sat[PCU] (assignment) PlanNr (Input)
demand
PuT
Link volume: persons public transport.
PuT
Link volume: system.
persons
per
transport
PrT
Link volume: persons private transport.
PrT
Link volume: transport.
PrT
vehicles
private
PrT
Link volume: PrT vehicles per transport system. Link volume: PrT vehicles per demand segment. Link volume: PrT vehicles in passenger car units. Link volume: PrT vehicles in passenger car units + basic volume. Number of the planned link. range: long Int
PrT
PrT
PrT
PrT+PuT
4-56
Links
THE NETWORK EDITOR
,QVHUW D OLQN

$FWLYDWH ,NSERT PRGH $FWLYDWH /INK QHWZRUN REMHFW
Mark FromNode and ToNode with left mouse click. ,QVHUW OLQN GLDORJ Compulsory input parameters: LinkNr (identical for both directions) LinkType for each direction. The link attributes predefined by link type (permitted transport systems, PrT speed/capacity, and PuT travel time) can be subject to changes
"Generate opposite direction of link" option If RSSRVLWH GLUHFWLRQ is active , both directions of the link are generated between the selected nodes with identical link numbers. For the opposite direction, a different link type can be selected for which other default values have been preset. If RSSRVLWH GLUHFWLRQ is inactive o, a link with an identical LinkNr will still be generated, but it will be closed to all transport systems. As a result, the inserted FromNode-ToNode link will become a one-way road in the transport network. VISUM analyses one-way roads with reference to permitted TSys: to highlight a one-way road graphically see /LQN- PARAMETERS in the GRAPHICS menu 0DUN RQHZD\ URDGV can be selected for each TSys of the network. VISUM marks each link with an arrow for which the selected TSys is not permitted for the opposite direction. In this way, links which were explicitly inserted as one-way roads (opposite direction not permitted for any TSys) are highlighted graphically.
4-57
THE NETWORK EDITOR
Links
This previously nonexistent direction of the link cannot be included in the differential network calculation following the 3HUPLW 76\V IRU WKH RSSRVLWH GLUHFWLRQ operation, because differences are only determined between two volume values of an existing link. For a subsequent difference network calculation in PrT mode, it is recommended that, instead of a "real" one-way road, capacity = 0 should be entered for the opposite direction. 'HWDLOV: opens all other dialog boxes. 2.: the link and the opposite direction - depending on the option specified - as well as all turning relations at both nodes are generated by adopting the link type-specific default values of the compulsory input parameters.
When a link is inserted, VISUM generates all theoretically possible turning relations at both nodes of the link. A four-way intersection, for example, has 12 turning relations. Each turning relation is described by: a list of permitted/closed transport systems PrT capacity and PrT time penalty. For each turning relation, the transport systems which are permitted to use the turning relation must be defined. A turning relation distinguishes between permitted and closed transport systems: Permitted PuT transport systems: the turning relation may be used in the construction of a line route. Permitted PrT transport systems: the turning relation may be used during assignments where the PrT capacity and the PrT time penalty are taken into account. Closed TSys: prohibited turning
4-58
Links
THE NETWORK EDITOR
6HOHFW D OLQN

Activate SINGLE SELECT mode and LINK network object.
Selecting a link: mark link with left mouse click on FromNode and ToNode, search for link with right mouse click and <F3>. Then call up the desired edit command. Double-clicking on a ToNode (or < Enter >) immediately calls up the MODIFY LINK dialog box.
'HOHWH D OLQN

Select link. Delete link with DELETE in the EDIT menu or shortcut <Del>. both directions of the link are always deleted. if only one direction of a link is to be deleted: close all transport systems for this direction or delete both directions and insert a link with no opposite direction.
4-59
THE NETWORK EDITOR
Links
(GLW D OLQN

0RGLI\ OLQN DWWULEXWHV
With the exception of Number, all input attributes of the selected link can be modified; the dialog boxes for INSERT and MODIFY are identical. Via the following tabs all attributes of the selected link are available for MODIFY LINK: Basic PrT-Sys PuT-Sys Emis Immis Noise MLuS MobiAtt MobiRes EWS Add-on according to German guidelines. Specific link attributes are described with the Add-on. Basic link attributes: Output of calculated results, allows modification of input attributes; Privatre transport systems defined for the network: Output and modification of the currently permitted/closed TSys by link direction. Public transport systems defined for the network: Output and modification of the currently permitted/closed TSys by link direction. Add-on module Environmental impact calculation: Attributes for calculation of pollutant emissions Add-on module IMMIS: IMMIS-Luft - Data interface Add-on module Environmental impact calculation: Attributes for noise emission calculation. Attributes for calculation of emissions according to German MLuS guidelines Add-on module Mobilev: Attributes and results
4-60
Links
THE NETWORK EDITOR
Select link. Call up 0RGLI\ OLQN with MODIFY in the EDIT menu or shortcut <Enter> or double-clicking on the ToNode of the selected link. Similar to permitted/not permitted transport systems all link attributes have to be specified by link direction. Attribute values that differ from those entered for the opposite direction are yellow-shaded. Set basic attributes (link-specific, preset be link type) first, then actuate the 76\V button: permit transport systems by direction, finally call up 3U76\V tab and 3X76\V tab and enter TSysspecific attributes by direction.
Transport systems
Transport systems which may use the link direction are highlighted. Enable/Disable a transport system: Select a single TSys by mouse-click, several TSys by pressing <Ctrl> simultaneously. Opp.Dir. Button 2SS'LU: Switch to opposite link direction. Change link attributes by link direction. Attribute values that differ by direction are highlighted.
4-61
THE NETWORK EDITOR
Links
0RGLI\ OLQN GLDORJ %DVLF WDE %DVLF
Input attributes (Cap-PrT and v0-PrT can be preset by default values according to link type): Length (preset = direct distance) Number of lanes (VISSIM interface: Junction editor), v0-PrT and CapacityPrT (summed up over all lanes), Display of LinkNr., FromNode- and ToNodeNr., direct distance as well as PrT volume and saturation. Optional input attributes: AddValues, PlanNr., Name of the road. Option /DEHO: switch link labels on/off. Prerequisite: Layer /DEHOV under 3DUDPHWHUV in the must be set to 'UDZ active and 7H[W VL]H > 0 mm.
GRAPHICS
menu
4-62
Links
THE NETWORK EDITOR
0RGLI\ OLQN GLDORJ 3U76\V WDE 3U76\V
Display of link attributes regarding permitted private transport systems. Click on Option SHUPLWWHG to block a PrT-Sys, which is curently permitted to use the link or permit a PrT-Sys, which has been blocked. Enter: Permitted PrT-Sys, TSys-specific AddValue and Road toll. Output (calculated by PrT-Sys) of: t0 (from link length and v0) and v0 is the lower value comparing v0-PrT and v0-PrTSys, tCur, vCur, volume, impedance (assignment result).
4-63
THE NETWORK EDITOR
Links
0RGLI\ OLQN GLDORJ 3X76\V WDE 3X76\V
Display of link attributes regarding permitted public transport systems. Click on Option SHUPLWWHG to block a PuT-Sys, which is curently permitted to use the link or permit a PuT-Sys, which has been blocked. Enter: Permitted PuT-VSys, TSys-specific AddV and Cost-AddValues Output (calculated by PuT-Sys) of: t -PuT (from link length and v-TSys) and volumes (assignment result).
4-64
Links
THE NETWORK EDITOR

0RGLI\ D OLQN FRXUVH

Activate SINGLE SELECT mode and LINK network object
Select link. Call up 0RGLI\ OLQN FRXUVH with SPECIFY COURSE in the EDIT menu or shortcut <F5>. Procedure: select link (node5 - node6) and activate SPECIFY COURSE command with <F5>. VISUM connects the FromNode with the ToNode of the selected link via the mouse cursors current position with a rubber band. move the cursor to the position desired for the first intermediate point and confirm with left mouse click. enter further polygon points between FromNode and ToNode in the correct sequence.
finally transfer link course with a double click. Enable option to use new link length: 7DNH /HQJWK3RO\JRQ IRU OLQN OHQJWK? Initialize specified link course via <F2>; Link = Direct distance FromNode-ToNode.
VISUM calculates the direct distance for the link polygon using the coordinates of the intermediate points and the lengths of the resulting sublinks. The resulting direct distance can be used as the link length in SINGLE SELECT mode: enter length (Length = LengthPoly) MULTI SELECT mode: select "Length" attribute, click $WWULEXWH button, generate length from the /HQJWK3RO\ attribute. The link label is displayed at the longest section of a specified course. Reduce text size, if necessary. A specified link course can be redefined: Shift (left mouse) or delete (<Ctrl> simultaneously) or add new intermediate points. See 6SHFLI\ ]RQH SRO\JRQV.
THE NETWORK EDITOR
Links

6SOLW D OLQN
Select link. Splitting a link involves the following operations: deleting the link that is to be split defining the intermediate node: inserting a new node or marking any node which already exists in the network; inserting two new links: between the FromNode, the ToNode, and the intermediate node respectively, as defined by the user. Call up VSOLW OLQN with SPLIT in the EDIT menu or shortcut <F8>. Procedure: Example: Link 2 (FromNode 11 - ToNode 20) select link by clicking both nodes and activating SPLIT command with <F8>. VISUM displays the following message:
the intermediate node need not be on the link to be split. an intermediate node can be any node marked in the network or inserted in the network as an "isolated" node. define the intermediate node with mouse click: enter new NodeNr or confirm selected NodeNr.
i.e.
4-66
Links
THE NETWORK EDITOR
assign new link numbers to the two new links; the proposed numbers can be modified.
enter attributes for all new turning relations at the intermediate node.
The attributes of the new turning relations at the intermediate node can be defined immediately: VISUM opens the dialog box for editing turning relations. Default values: for new turning relations all transport systems are permitted. The attributes of the new network objects (1 intermediate node and 2 resulting links) can subsequently be edited in SINGLE SELECT mode.
4-67
THE NETWORK EDITOR
Links

(GLW OLQN ODEHO GLVSOD\

Select link. By default VISUM displays the link label alongside the link in the middle of the link, and at the longest straight section for a specified link course. Prerequisite for displaying link labels: settings must be specified for all links under PARAMETERs in the GRAPHICS menu: via the /LQNV/DEHOV tab: 'UDZ and Text Size > 0.0 mm. via /LQNV$WWULEXWH tab: select value, for multiple bars activate 'UDZ . via the /D\HUV tab: Activate 'UDZ for layer link labels.
The label of a link can be moved along the link or turned on/off for each link. For display on screen the text scaling factor is considered, use the 3UHYLHZ command to check print/plot output prior to printing. No display of labels which are longer than the link or the link section, reduce text size for display. The current settings are stored along with the graphics parameters.
Shift link labels with 6KLIW WH[W in the EDIT menu or shortcut <F6>. You will be prompted for the opposite direction. Turn link labels on/off with 7H[W RQRII in the EDIT menu or shortcut <F4>.
The link label can also be turned on/off with the graphics button 7H[W in the MODIFY LINK dialog box.
4-68
Links
THE NETWORK EDITOR
(GLW PXOWLSOH OLQNV

Activate MULTI SELECT mode and LINK network object.
6SHFLI\ DFWLYH OLQNV IRU HGLWLQJ by one of the methods described below or a combination of them. Active links are only those which satisfy all current specifications! Filter: specify link filter MultiSelect selection specified in MULTI SELECT mode as rectangle: drag while holding down left mouse button; polygon: while holding down the <Ctrl> key, fix the polygon points one by one by clicking left mouse button. Release <Ctrl> prior to marking the last point. All links with FromNode and ToNode within the polygon are set to active. AREA through : Call the 2EMHFWV ZLWKLQ $UHD 6HW DFWLYH function
and right-hand mouse-click or MULTISELECT command in the EXTRAS menu and select area. Modify state of single object: set single links in MULTI SELECT mode to active/passive by clicking left mouse button. This can also be used for fine editing of MultiSelect polygons. Links which are passive because of current filter parameters cannot be set to active! Invert: set all active links to passive and all passive links to active. Click the right mouse button to call ,QYHUW. File: set links to active by reading the following file type(s): filter parameters *.fil, specified active network objects *.ane. If there are no passive links in the network, the modifications apply to all links. Links which are passive due to /LQN )LOWHU 0XOWLVHOHFW or $UHD settings can be treated as active links when editing in MULTISELECT mode: Disable the 2QO\ DFWLYH option. Display of current status (number of active or passive links) via PROGRAM STATUS in the EXTRAS menu.
4-69
THE NETWORK EDITOR
Links

0RGLI\ DWWULEXWH IRU PXOWLSOH OLQNV

Call up 0RGLI\ DWWULEXWH IRU PXOWLSOH OLQNV with MODIFY in the EDIT menu or shortcut <Enter>. Only attributes which are neither identifiers of network objects (e.g. LinkNr) nor calculation results (e.g. volume) can be edited. 0RGLI\ OLQN DWWULEXWHV GLDORJ )RUPXOD WDE
)RUPXOD
Set option: include RQO\ DFWLYH or all o links Click attribute, and sub-attribute, if applicable, which is to be modified.
G
8
4-70
The marked attribute is irrelevant if mdofications are performed using the 6SHFLDO )XQFWLRQV tab. Follow the sequence to modify an attribute for multiple links: set option and select attribute to be edited
Links
THE NETWORK EDITOR
activate button and enter or select value(s) set $GG option to active/inactive confirm with OK close /LQN DWWULEXWHV dialog box with OK
%XWWRQV &RQVWDQW enter constant attribute value )DFWRU: multiply current attribute value by factor. $WWULEXWH: accept values of another attribute. )RUPXOD: indicate formula for accepting and calculating. 5RXQG: enter rounding factor for values of the selected attribute.
G
6SHFLDO IXQFWLRQV
For the functionality provided with the buttons see Chapter 4.3.6.1 0RGLI\ DWWULEXWH RI PXOWLSOH QRGHV. /LQN DWWULEXWHV GLDORJ 6SHFLDO IXQFWLRQV WDE
4-71
THE NETWORK EDITOR
Links

*HQHUDWH $GG9DOXHB/LQNV IURP $GG9DOXHB7XUQ5HODWLRQV

Activate MULTI SELECT mode and LINK network object. 0RGLI\ OLQN DWWULEXWHV 6SHFLDO IXQFWLRQV tab
TurnRel- If counted data on volumes of turning relations are available as TurnAddValue Rel-AddValues, then Link-AddValues can be generated from them:
Set
Example: Generate AddVal1_Links from AddVal_TurnRelations data.
4-72
Links
THE NETWORK EDITOR
Comparison of TurnRel-AddValues for each node of the link: which value is to be calculated and copied?
Which TurnRel-AddValue data are to be used to calculate the link attribute AddValue 1?
In this case, Link-AddValue 1 is generated using the relative deviation of the TurnRel-AddValue 1 data: Link-AddVal 1 is determined by calculating the relative deviation between the sum of the ingoing volume (all turning relations into the link) from the FromNode and the sum of the outgoing volume (all turning relations from the link) at the ToNode.
4-73
THE NETWORK EDITOR
Links

/LQN ODEHO GLVSOD\ 212)) RU LQLWLDOL]H SRVLWLRQ

Labels
Options: Label/Do not label all active links; After moving the label along a link via 6KLIW 7H[W in WKH EDIT menu move label back to default position, i.e. for link course = direct distance: at the middle of link, specified link course: at the longest section. Prerequisite (PARAMETERS in the GRAPHICS menu): Enable 'UDZ /D\HU /LQN ODEHOV, set 7H[W VL]H > 0 mm.
4-74
Links
THE NETWORK EDITOR

8VH OLQN DWWULEXWH YDOXHV SUHGHILQHG E\ OLQN W\SH

Default values
$WWULEXWHV Select the attributes (left-click and <Ctrl>), which are to assigned the default values preset by link type (see LINK TYPES in EXTRAS menu). Button 8VH GHIDXOW YDOXHV Default values are assigned to all/all active links.
4-75
THE NETWORK EDITOR
Links

*HQHUDWH UXQQLQJ WLPHV RI OLQNV IURP OLQH GDWD

Running times of links
Set options: RQO\ DFWLYH to select all or only active links for modifications. &RQVLGHU RQO\ DFWLYH VXEOLQHV to include either all or only active sublines.
'LVWULEXWLRQ Line route sections between 2 stops may cover several links, thus running times of sublines between neighbouring stops are distributed to the traversed links according to: length of the links, direct distance of links or Length-Poly of links.
4-76
Links
THE NETWORK EDITOR
:HLJKWLQJ A link may be traversed by several sublines. In this case the running time results from the weighted mean of all line services, the weighted mean of all subline services, the minimum running time or the maximum running time of active/all sublines. Click 6HW button to calculate new running times of links.

'HOHWH DFWLYH OLQNV

Activate MULTI SELECT mode and LINK network object.
Call 'HOHWH DFWLYH OLQNV : Click DELETE in the EDIT menu or Shortcut <Del>.
Only links which are not part of a public transport line route network can be deleted. Always both directions of a link are deleted. The current result of assignment will be reset.
4-77
THE NETWORK EDITOR
Turning relations
7XUQLQJ UHODWLRQV
Turning relations indicate whether turning is permitted at a node and what time penalty has to be considered for PrT transport systems. For PrT transport systems, time penalties and capacities can be specified for each turning relation, which describe the impact of the intersection on the network performance. Turning relation attributes are taken into account for PrT transport systems during the assignment. Turning prohibitions for PuT transport systems are taken into account in the construction of the line route.
When inserting a link, VISUM generates all the turning relations that are theoretically possible at both nodes of the link. For example, at a four-way intersection, there are a total of 12 turning relations. Each turning relation is described by: The list of permitted/closed transport systems, PrT capacity and PrT time penalty.
4-78
Turning relations
THE NETWORK EDITOR
For each turning relation, the transport systems which are permitted to use this turning relation must be specified. A turning relation distinguishes between permitted and blocked transport systems: Permitted PuT transport systems: The turning relation may be used when constructing the line route. Permitted PrT transport systems: The turning relation may be used when transferring from link to link, taking into account Capacity-PrT and the TimePenaltyPrT. Closed TSys: prohibited turning relation
Turning relations may be edited using the following commands: (GLW FRPPDQG 6HDUFK 0RGLI\ 'HOHWH 7H[W RQRII 6SHFLI\ FRXUVH 6KLIW WH[W $JJUHJDWH 6SOLW &RS\ 6KRUWFXW <F3> <Enter> <Del> <F4> <F5> <F6> <F7> <F8> <F9> X X X X
4-79
THE NETWORK EDITOR
Turning relations
7XUQLQJ UHODWLRQ DWWULEXWHV

7XUQLQJ VWDQGDUG
The default selection of attribute values for t0-PrT and Cap-PrT is held in the network file. Default values for the attribute types Cap-PrT and t0-PrT can be assigned to active turning relations (MULTI SELECT mode MODIFY command 6SHFLDO IXQFWLRQV tab 'HIDXOW YDOXHV button).
The data in the following table can only be edited in the network file: 7\SH PrT PrT $WWULEXWH NodeType (Input) TurnRel (Input) 'HILQLWLRQ Type of node range: Text2 (00...99) or ++ From major flow to major flow, +- From major flow to minor flow, -+ From minor flow to major flow, -- From minor flow to minor flow range: Text2 ( ++,+-,-+,--, ?? ) Type of turning relation: 0 not specified 1 right (> 0 - 120) 2 straight (121 - 240) 3 left (241 - < 360) 4 U-Turn (360) 5-9 free range: Text1 (0 - 9 or ?) Time penalty for turning movement (free flow). range: time interval Private transport capacity of the turning relation. range: Long Int, < 0
PrT
TurnType (Input)
PrT
t0-PrT t0 time-PrT (Input) Cap-PrT Capacity-PrT (Input)
PrT
4-80
Turning relations
THE NETWORK EDITOR

7\SH
7XUQLQJ UHODWLRQ DWWULEXWHV

$WWULEXWH 'HILQLWLRQ FromNode-number of link, which leads to the node. range: defined node numbers Type of the FromNode, which leads to the node. range: defined node numbers Node-number, where the turning movement takes place. range: defined node numbers Type of the node, where the turning movement takes place. range: defined node numbers
PrT+PuT FromNode FromNodeNr (Input) PrT+PuT FromNodeType (Input) PrT+PuT ViaNode ViaNodeNr (Input) PrT+PuT ViaNodeType (Input) PrT+PuT ToNode ToNodeNr (Input) PrT+PuT ToNodeType (Input) PrT+PuT FromLink (Input) PrT+PuT ToLink (Input) PrT+PuT TSysCode (Input) PrT+PuT Type (Input)
ToNode-number of link, which leaves from the node. range: defined node numbers Type of the ToNode of link, which leaves from the node. range: defined node numbers Number of the link that leads towards the node. range: defined link number Number of the link that leaves from the node. range: defined link number List of permitted transport systems. range: defined transport systems Turning relation type calculated from turning relation geometry: 0 not specified 1 right 2 straight 3 left 4 U-Turn range: 0 - 9 (>0 - 120) (121 - 240) (241 - <360) (360)
4-81
THE NETWORK EDITOR
Turning relations
7\SH PrT PrT
$WWULEXWH t0-PrT (Input) tCur-PrT tCurrent-PrT (assignment) Cap-PrT Capacity-PrT (Input) Imp-PrTSys Impedance-PrTSys (assignment) Vol-PrT Volume-PrT (assignment)
'HILQLWLRQ PrT turning time penalty (free flow). range: time interval Private transport turning time in the charged network. Private transport capacity of turning relation. range: Long Int, >0 PrT system-specific value of the capacity-based impedance function considering the current traffic volume. PrT turning volume.
PrT
PrT
PrT
PrT+PuT Vol-TSys Volume-TSys (assignment) PrT+PuT AddVal1-3 AddValue 1-3 (user-defined) PrT+PuT FromPrio (Input) PrT+PuT ToPrio (Input)
Turning volume by transport system.
AddValue1, AddValue2, AddValue3, range: Long Int Indicating whether the FromLink of the turning relation is a higher-ranking link (0=No, 1=Yes). Indicating whether the ToLink of the turning relation is a higher-ranking link (0=No, 1=Yes).
4-82
Turning relations
THE NETWORK EDITOR
,QVHUW WXUQLQJ UHODWLRQ
In the case of a new link, VISUM generates all possible turning relations at the FromNode and at the ToNode of the link. Thus, the definition of turning relations results from the definition of permitted transport systems, i.e. turning relations are inserted with SHUPLW WUDQVSRUW V\VWHPV and deleted with FORVH WUDQVSRUW V\VWHPV Turning relation attributes: permitted PrT and PuT systems and for PrT-TSys: time penalty and capacity in passenger car units. VISUM generates the turning relation type automatically If INSERT mode and TURNING RELATION network object are active: VISUM issues a warning
Activate INSERT /,1. and transfer link data: marked direction (FromNode-ToNode) LinkNr. Type, opposite direction (one-way road) or opposite direction : Type. %XWWRQ VISUM generates and adopts all attribute data for both directions of the link and for all turning relations at both nodes of the link from default values. VISUM generates all attribute data for both directions of the link and for all turning relations at both nodes of the link from default values. The dialog boxes are displayed on the screen. The user can check the default entries and make any necessary modifications before adopting them. ([DPSOH ,QVHUW D OLQN DQG DOO WXUQLQJ UHODWLRQV DW ERWK QRGHV Mark FromNode and ToNode with mouse click, Insert outward and return direction of link. 7UDQVSRUW 6\VWHPV button: authorise transport systems (2SS'LU) %DVLc, 3U76\V and 3X76\V tabs: check/modify link attributes. Click 2.: transfer link attributes (incl. TSys). VISUM automatically opens the following dialog box.
%XWWRQ
4-83
THE NETWORK EDITOR
Turning relations
0RGLI\ WXUQLQJ UHODWLRQ %DVLF WDE %DVLF
Mandatory input: TurnType, Cap-PrT in [Car units], TimePenalty-PrT Optional input: AddValues, Options for graphic display: Show closed turning relations or turning relations into closed links. The selected turning relation is highlighted on screen: FromLink, ViaNode, ToLink, Major flows. 2SS'LU button: Switch to opposite direction (all turning relations from other links via the selected node leading to the new link)
4-84
Turning relations
THE NETWORK EDITOR
%XWWRQV or : switch (counter-clockwise/clockwise) to other turning relations with mouse click on 7R button < or > for subsequent links (select other ToLink), )URP button < or > for previous links (select other FromLink) $OO button < or > for all directions. 0RGLI\ WXUQLQJ UHODWLRQ 76\V WDE 76\V
All transport systems defined for the network are listed. TSys permitted to use the turning relation are highlighted. Enable/Disable a transport system: Select a single TSys by left click, several TSys by <Ctrl> + left click.
4-85
THE NETWORK EDITOR
Turning relations
6HOHFW WXUQLQJ UHODWLRQ

Activate SINGLE SELECT mode and TURNING RELATIONS network object type.
To select a node (all turning relations at the node): Mark node with left mouse click. Search for node with right mouse click and <F3>. To select a link sequence: Mark FromNode-ViaNode-ToNode with left mouse click.
Then initiate desired processing step. Double-clicking a node (or <Enter>) immediately opens the dialog box for MODIFY TURNING RELATION.
'HOHWH WXUQLQJ UHODWLRQ

Activate SINGLE SELECT mode and TURNING RELATIONS network object type.
G
8
Turning relations are defined in VISUM for each transport system. Consequently, a turning relation can be deleted for one, multiple or all transport systems by closing it to each TSys. A turning relation can only be closed for a TSys if no public transport line specified for this TSys does use the FromLink-ToLink relation. Select turning relation. Delete turning relation with MODIFY in the EDIT menu: closed to transport system(s) or Shortcut <Del> (closed to all transport systems). The FromLink-ViaNode-ToLink relation is retained in the network and can be authorised for TSys again via the MODIFY TURNING RELATION edit command.
4-86
Turning relations
THE NETWORK EDITOR
(GLW PXOWLSOH WXUQLQJ UHODWLRQV

Activate MULTIPLE SELECT mode and TURNING RELATIONS network object type.
6SHFLI\ DFWLYH WXUQLQJ UHODWLRQV IRU HGLWLQJ by one of the methods described below or a combination of them. Active links are only those which satisfy all current specifications! Filter: specify link filter and/or MultiSelect selection specified in MULTI SELECT mode as rectangle: drag while holding down left mouse button; polygon: while holding down the <Ctrl> key, fix the polygon points one by one by clicking left mouse button. Release <Ctrl> prior to marking the last point. All turning relations with ViaNode within the polygon are set to active. AREA through : Call the 2EMHFWV ZLWKLQ $UHD 6HW DFWLYH function
and right-hand mouse-click or MULTISELECT command in the EXTRAS menu and select area. 0RGLI\ VWDWH RI VLQJOH REMHFW: set single turning relation in MULTI mode to active/passive by clicking left mouse button on FromNode-ViaNode-ToNode. This can also be used for fine editing of MultiSelect polygons. Turning relations which are passive because of current filter parameters cannot be set to active!
SELECT
,QYHUW: set all active links to passive and all passive turning relations to active. Click the right mouse button to call ,QYHUW. Set turning relations to active by reading the following file type(s): filter parameters *.fil, specified active network objects *.ane. If there are no passive turning relations in the network, the modifications are adopted for all turning relations. Turning relations which are passive because of turning relation filters or Area settings may be treated as active turning relations when editing in MULTISELECT mode: Disable &RQVLGHU RQO\ DFWLYH option accordingly.
4-87
THE NETWORK EDITOR
Turning relations

0RGLI\ DWWULEXWH IRU PXOWLSOH WXUQLQJ UHODWLRQV

Call up 0RGLI\ DWWULEXWH RI PXOWLSOH WXUQLQJ UHODWLRQV with Mouse click on MODIFY in the EDIT menu or Shortcut <Enter>.
G
)RUPXOD
Only those attributes can be edited which are neither identifiers of network objects (e.g. ViaNodeNo.) nor calculation results (e.g. volume) 0RGLI\ WXUQLQJ UHODWLRQV DWWULEXWHV GLDORJ )RUPXOD WDE
RQO\ DFWLYH All turning relations will be considered, if this option is disabled. $WWULEXWH Select the attribute to be modified via one of the buttons.
G
4-88
The selected attribute is irrelevant in case of changes performed using the 6SHFLDO IXQFWLRQV tab.
Turning relations
THE NETWORK EDITOR
Sequence: modify attribute for multiple turning relations Set option and select attribute to be edited, Activate button and enter or select value(s), Set $GG option to active/inactive, Confirm with OK, Close 7XUQLQJ UHODWLRQ DWWULEXWHV dialog box with OK . %XWWRQV &RQVWDQW enter constant attribute value, e.g. select TSys. )DFWRU: multiply current attribute values by factor. $WWULEXWH: adopt values of another attribute. )RUPXOD: indicate formula for transfer and calculation. 5RXQGLQJ: rounding factor for values of the selected attribute.
For the functionality provided with the buttons see Chapter 4.3.6.1 0RGLI\ DWWULEXWH RI PXOWLSOH QRGHV.
4-89
THE NETWORK EDITOR
Turning relations

$VVLJQLQJ GHIDXOW YDOXHV WR WXUQLQJ UHODWLRQ DWWULEXWHV

Call up 0RGLI\ DWWULEXWH RI PXOWLSOH WXUQLQJ UHODWLRQV with Click on MODIFY 6SHFLDO IXQFWLRQV tab in the EDIT menu or Shortcut <Enter> 7XUQLQJ UHODWLRQV DWWULEXWHV GLDORJ 6SHFLDO IXQFWLRQV WDE
6SHFLDO IXQFWLRQV
Set option: RQO\ DFWLYH Turning relations are to be considered. o all turning relations are to be modified.
$WWULEXWHV Select one or several attributes, die mit Standardwerten belegt werden sollen, mit <Strg> und Mausklick links. Button 8VH GHIDXOW YDOXHV: VISUM automaticaly assigns the predefined values of the selected atribute(s) to the selected turning relations.
G
4-90
The turning standard is held in the network file in the $TURNRELSTANDARD table : NodeType, TurnRel, TurnType, t0-PrT, Cap-PrT.
Zones
THE NETWORK EDITOR
=RQHV
Zones are the origin and destination of journeys within the network. They are connected to the network via connectors. Zones can be edited using the following commands: (GLW FRPPDQG 6HDUFK 0RGLI\ 'HOHWH 7H[W LQRXW 6SHFLI\ FRXUVH 6KLIW WH[W $JJUHJDWH 6SOLW &RS\ 6KRUWFXW <F3> <Enter> <Del> <F4> <F5> <F6> <F7> <F8> <F9> X X X X X X X X X
4-91
THE NETWORK EDITOR
Zones
=RQH DWWULEXWHV

7\SH PrT+PuT $WWULEXWH Nr Number (Input) Name (Input) Code (Input) Type (Input) X-Coord X-Coordinate (Input) Y-Coord Y-Coordinate (Input) NumConNodes NumConnectedNodes (connector) NumDConNode Num Dest.Conn.Nodes (connector) NumOConNode Num Orig.Conn.Nodes (connector) TotNumConNode Total number Conn.Nodes (connector) Area (calculated) 'HILQLWLRQ Number of zone. default: max. ZoneNr+1 range: 1-999999999 Name of zone. default: empty string range: Text20 Code of zone. default: empty string range: Text8 Type of zone. default: 0 range: 0 - 9 X-Coordinate. default: from mouse position range: Real Y-Coordinate. default: from mouse position range: Real Number of nodes which are connected with the zone (PrT or PuT, both directions). Number of nodes which are connected with the zone (dest. conn. only, PrT or PuT). Number of nodes which are connected with the zone (orig. conn. only, PrT or PuT). Total number of nodes which are connected with the zone (PrT and PuT, all directions). Area, defined by the zone polygon.
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
4-92
Zones
THE NETWORK EDITOR
7\SH PrT+PuT
$WWULEXWH AddVal1-3 AddValue1, 2, 3 (user-defined) OConTimeMax OrigConTimeMax (calculated) OConTimeMean OrigConTimeMean (calculated) OConTimeMin OrigConTimeMin (calculated) DConTimeMax DestConTimeMax (calculated) DConTimeMean DestConTimeMean (calculated) DConTimeMin DestConTimeMin (calculated) OTraffic OriginTraffic (O-D matrix) DTraffic DestTraffic (O-D matrix) FlowBundleO FlowBundleOrigin (flow bundle) FlowBundleD FlowBundleDest (flow bundle)
'HILQLWLRQ AddValue1, AddValue2, AddValue 3. range: Long Int Maximum origin connecting time by mode.
PrT+PuT
PrT+PuT
Mean origin connecting time by mode.
PrT+PuT
Minimum origin connecting time by mode.
PrT+PuT
Maximum destination connecting time by mode. Mean destination connecting time by mode. Minimum destination connecting time by mode. Originating traffic by private transport system or PuT mode. Terminating traffic by private transport system or PuT mode. Flow bundle of originating traffic (Private and/or Public transport systems). Flow bundle of destinating traffic (Private and/or Public transport systems).
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
4-93
THE NETWORK EDITOR
Zones
7\SH PrT
$WWULEXWH Perc_O Percentage Origin (Input) Perc_D Percentage Destination (Input) NumSLines Num sublines (line network) NumLines Num Lines (line network) NumService Num Services (timetable)
'HILQLWLRQ Distribution of the zones outbound (origin) and inbound (destination) PrT travel demand to connectors: absolute: free distribution, percentage: user-defined distribution. default: absolute range: absolute/percentage Number of sublines, which serve stops connected to the zone. Number of lines, which serve stops connected to the zone. Number of services (vehicle trips), which serve stops connected to the zone.
PrT
PuT
PuT
PuT
PuT
mSF-PuT mean service frequency of all PuT trips mean ServiceFrequ-PuT which begin in the zone. (assignment) LinTrips-PuT LineTrips-PuT (assignment) Line trips = passengers. number of boarding
PuT
PuT
mNT-PuT mean number transfers of all PuT trips mean NumTransfers- which begin in the zone. PuT (assignment) TotNT-PuT Tot. NumTransfer-PuT (assignment) TotPassKm-PuT Tot. PassKm-PuT (assignment) Total number of transfers of all PuT trips which begin in the zone. Total passenger-kilometers of all PuT trips which begin in the zone.
PuT
PuT
4-94
Zones
THE NETWORK EDITOR
7\SH PuT
$WWULEXWH PTripsPuT0 PassTrips-PuT 0 Transfer (assignment) PTripsPuT1 PassTrips-PuT 1 Transfer (assignment) PTripsPuT2 PassTrips-PuT 2 Transfers (assignment) PTripsPuT>2 PassTrips-PuT >2 Tranfers (assignment) PTripsPuTTot PassTrips-PuT Total (assignment) PTripsPuTWoCon PassTrips-PuT No Connection (assignment) PTripsPuTWoRide PassTrips-PuT Without Ride (assignment)
'HILQLWLRQ Number of transfers. passenger trips with 0x
PuT
Number of transfers.
passenger
trips
with
1x
PuT
Number of transfers.
passenger
trips
with
2x
PuT
Number of passenger trips with more than 2x transfers.
PuT
Total number of passenger trips.
PuT
Number of connection.
passenger
trips
without
PuT
Number of passenger trips without PuT ride.
PuT
PTripsPuTWRide Number of passenger trips with PuT ride. PassTrips-PuT WithRide (assignment)
4-95
THE NETWORK EDITOR
Zones
7\SH PuT
$WWULEXWH TotAT-PuT Tot. AccessTime-PuT (assignment) TotDD-PuT Tot. DirectDist-PuT (assignment) TotET-PuT Tot. EgressTime-PuT (assignment) TotIVT-PuT Tot. InVehicleTime-PuT (assignment) TotJD-PuT Tot. JourneyDist-PuT (assignment) TotJT-PuT Tot. JourneyTime-PuT (assignment) TotOWT-PuT Tot. OriginWTime-PuT (assignment) TotRT-PuT Tot. RideTime-PuT (assignment)
'HILQLWLRQ Total access time of all PuT trips which begin in the zone. Total direct distance of all PuT trips which begin in the zone. Total egress time of all PuT trips which begin in the zone. Total in-vehicle time of all PuT trips which begin in the zone. Total journey distance of all PuT trips which begin in the zone. Total journey time of all PuT trips which begin in the zone. Total origin waiting time of all PuT trips which begin in the zone. Total ride time of all PuT trips which begin in the zone.
PuT
PuT
PuT
PuT
PuT
PuT
PuT
PuT
TotTWT-PuT Total tansfer waiting time of all PuT trips Tot. TransferWaitTime- which begin in the zone. PuT (assignment) TotWT-PuT Tot. WalkTime-PuT (assignment) Total walk time of all PuT trips which begin in the zone.
PuT
4-96
Zones
THE NETWORK EDITOR
7\SH PuT
$WWULEXWH mAT-PuT mean AccessTime-PuT (assignment) mDD-PuT mean DirectDist-PuT (assignment) mDV-PuT mean DirectDistSpeedPuT (assignment) mET-PuT mean EgressTime-PuT (assignment) mIVT-PuT mean InVehicleTimePuT (assignment) mIVV-PuT mean InVehicleSpeedPuT (assignment) mJD-PuT mean JourneyDist-PuT (assignment) mJT-PuT mean JourneyTime-PuT (assignment) mJV-PuT mean JourneySpeedPuT (assignment) mOWT-PuT mean OriginWaitTimePuT (assignment)
'HILQLWLRQ mean access time of all PuT trips which begin in the zone. mean direct distance of all PuT trips which begin in the zone. mean direct distance speed of all PuT trips which begin in the zone.
PuT
PuT
PuT
mean egress time of all PuT trips which begin in the zone. mean in-vehicle time of all PuT trips which begin in the zone.
PuT
PuT
mean in-vehicle speed of all PuT trips which begin in the zone.
PuT
mean journey distance of all PuT trips which begin in the zone. mean journey time of all PuT trips which begin in the zone. mean journey speed of all PuT trips which begin in the zone.
PuT
PuT
PuT
mean origin wait time of all PuT trips which begin in the zone.
4-97
THE NETWORK EDITOR
Zones
7\SH PuT
$WWULEXWH mRD-PuT mean RideDist-PuT (assignment) mRT-PuT mean RideTime-PuT (assignment)
'HILQLWLRQ mean ride distance of all PuT trips which begin in the zone. mean ride time of all PuT trips which begin in the zone.
PuT
PuT
mTWT-PuT mean transfer wait time of all PuT trips mean TransferWaitTime- which begin in the zone. PuT (assignment) mWT-PuT mean WalkTime-PuT (assignment) mean walking time of all PuT trips which begin in the zone.
PuT
4-98
Zones
THE NETWORK EDITOR
,QVHUW ]RQH

Activate INSERT mode. Activate ZONES network object type.
Define co-ordinates of zone centroid with left mouse click. ,QVHUW ]RQH GLDORJ
1XPEHU 7\SH Mandatory input attributes. &RGH 1DPH $GG9DOXHV Optional input attributes 3RVLWLRQ [ \ The coordinates can be edited in this dialog or by mouse-click in the network display.
THE NETWORK EDITOR
Zones
The label of a zone is always displayed at the co-ordinates of its center of gravity (centroid). The co-ordinates can be edited. 6KLIW WH[W in the Edit menu modifies the co-ordinates of the centroid of the zone (label position). Thus also the length of the connectors from/to a zone need to be modified. 3U7 FRQQHFWRUV Select either relative or absolute distribution of the zones outbound and inbound travel demand to connectors. For CR functions see chapter 2.4.2 and 7.2.
As is shown by the mouse cursor, VISUM remains in INSERT mode after the zone attributes are entered, and expects the zone polygon to be marked. The zonal boundary is used to calculate the ,area of the zone and to show its spatial extent.
,QVHUW ]RQH ZLWKRXW ERXQGDU\ Click 2. to confirm and close ,QVHUW ]RQH . Click <Esc> to continue. ,QVHUW ]RQH ZLWK ERXQGDU\ Click OK to confirm and close ,QVHUW ]RQH . Mark polygon points around the zone centroid with left mouse click. Final double-click closes the polygon (VISUM connects the last marked polygon point to the first).
To connect the network with a single new zone call ,QVHUW &RQQHFWRU in SINGLE SELECT mode. several zones call *HQHUDWH FRQQHFWRUV in MULTI SELECT mode.
4-100
Zones
THE NETWORK EDITOR
6HOHFW ]RQH

Activate SINGLE SELECT mode and ZONE network object type.
To select a zone: Mark zone with left mouse click. Search for zone with right mouse click and <F3>.
Then call up the desired edit command. Double-click on a zone centroid or within a zone polygon or mark and <Enter>
immediately calls up the dialog box for the MODIFY ZONE command.
'HOHWH ]RQH

Select zone. Delete zone with DELETE in the EDIT menu or Shortcut <Del>. The connectors of the deleted zone are also deleted. A subsequently saved O-D matrix will contain neither the origin nor the destination demand of the deleted zone.
4-101
THE NETWORK EDITOR
Zones
(GLW ]RQH

0RGLI\ ODEHO SRVLWLRQ
Activate SINGLE SELECT mode and ZONES network object type.
Select zone. Call up 6KLIW zone centroid with SHIFT TE;T in the EDIT menu or Shortcut <F6>. The co-ordinates of the zones centroid can also be changed in the 0RGLI\ ]RQH DWWULEXWHV dialog.
Mark new position of zone centroid with mouse click. No automatic adjustment of zone connectors! Call up 0RGLI\ &RQQHFWRU : Adjust lengths of connectors and connector times. The centroid should lie within the zone polygon. Position and extent of the polygon remain unchanged.
4-102
Zones
THE NETWORK EDITOR

6SHFLI\ ]RQDO ERXQGDU\

Activate SINGLE SELECT mode and ZONES network object type.
Select zone. Call up 6SHFLI\ zonal boundary with SPECIFY COURSE in the EDIT menu or Shortcut <F5>. 6SHFLI\ a zone polygon allows to insert a zone polygon or to delete a polygon or to modify a polygon. See ,QVHUW ]RQH with boundary: An existing zone polygon is displayed as a rubber-band. Single polygon point Shift: Mark (left mouse key) and drag while holding down mouse key, Delete: press <Ctrl> and mark the polygon point simultaneously, Insert: press <Ctrl> simultaneously and mark the position of the polygon point on the boundary. Finally click right (these co-ordinates are not regarded for the polygon). Click ,QLWLDOL]H <F2> to delete an existing polygon. Specify boundary (see Insert zone).
GRAPHICS PARAMETERS - =RQHV: 'UDZ ERXQGDULHV must be active.
4-103
THE NETWORK EDITOR
Zones

0RGLI\ ]RQH DWWULEXWHV

Select zone. Call up 0RGLI\ ]RQH with MODIFY in the EDIT menu or Shortcut <Enter> or Double-click in selected zone. 0RGLI\ ]RQH GLDORJ %DVLF WDE
%DVLF
All input attributes except the number can be modified.
G
4-104
VISUM issues a warning if the type of distribution of the PrT transport volume is modified from DEVROXWH to SHUFHQWDJH. Continue with MODIFY CONNECTORS.
Zones
THE NETWORK EDITOR
0RGLI\ ]RQH 'HPDQG
GLDORJ 'HPDQG WDE
Displays the current demand per demand segment and direction from/to zone and totals for private and public transport (Prt, PuT and PrT+PuT).
Data management of demand matrices: FILE menu - OPEN/SAVE 2' PDWULFHV file type CALUCLATE menu - PROCEDURES 2'PDW5HDG or 2'PDW6DYH. Demand data processing: CALCULATE menu O-D MATRIX.
4-105
THE NETWORK EDITOR
Zones

6SOLW ]RQH
This feature makes it possible to divide an existing zone into two zones, i.e. the existing zone is deleted and 2 new zones are inserted. Origin demand and destination demand of the deleted zone are divided between the two new zones according to the specified percentages. Activate SINGLE SELECT mode and ZONES network object type.
Select zone. Call up VSOLW ]RQH with SPLIT in the EDIT menu or Shortcut <F8>. 6SOLW ]RQH GLDORJ
1XPEHU (Default: maxZoneNr in network +1 and +2), 7\SH (from original zone), 1DPH &RGH (optional), $GG9DOXHV (from original zone), 6SOLW IDFWRUV for the percentage of origin and destination travel demand of the original zone (default: 50% each). The splitting factors must add up to 1.0 per line (100% of the origin and destination amount respectively).
Zones
THE NETWORK EDITOR
After entering the attributes for the two new zones: for first new zone: mark centroid. for second new zone: mark centroid.
In VISUM 7.0 only the zones centroid has to be specified. To specify the zones boundary activate SINGLESELECT mode and call SPECIFY ZONE. The connectors of the split zone are adopted to each of the new zones. If necessary, continue with MODIFY CONNECTORS. The O-D matrix is adjusted according to the specified split factors. There is no traffic demand between the two new zones. If necessary, continue with CALCULATE - O-D MATRIX or FILE - SAVE command, file type O-D matrices. Save zones including polygons with 1HWZRUNV file type.
If three or more zones are to be formed from one zone, repeat the SPLIT ZONE command the appropriate number of times.
4-107
THE NETWORK EDITOR
Zones
(GLW PXOWLSOH ]RQHV

Activate MULTI SELECT mode and ZONES network object type.
6SHFLI\ DFWLYH ]RQHV IRU HGLWLQJ using one of the methods described below or a combination of them. Active zones are only those which satisfy all current specifications! Filter: define zone filter MultiSelect selection specified in MULTI SELECT mode as rectangle: drag while holding down left mouse button; polygon: while holding down the <Ctrl> key, fix the polygon points one by one by clicking left mouse button. Release <Ctrl> prior to marking the last point. All zones with the centroid within the polygon are set to active. AREA : Call the 2EMHFWV ZLWKLQ $UHD 6HW DFWLYH function through
and right-hand mouse-click or MULTISELECT command in the EXTRAS menu and select area. 0RGLI\ VWDWH of single object: set single zone in MULTI SELECT mode to active/passive with left mouse click. This can also be used for "fine editing" of fixed polygons. Zones which are passive because of current filter parameters cannot be set to active! ,QYHUW: set all active zones to passive and all passive zones to active. Clicking the right mouse button activates this dialog. Set zones to active/passive by reading the following file type(s): filter parameters: *.fil, specified active network object: *.ane. Zones which are passive because of zone filter or Area settings may be treated as active zones when editing in MULTISELECT mode: Disable &RQVLGHU RQO\ DFWLYH option accordingly. Display current status (number of active and passive zones) via PROGRAM STATUS in the EXTRAS menu. If at least one zone in the network is passive, the active zones can be aggregated to form one zone.
4-108
Zones
THE NETWORK EDITOR

0RGLI\ DWWULEXWH IRU PXOWLSOH ]RQHV

G
)RUPXOD
Call up the 0RGLI\ DWWULEXWH IRU PXOWLSOH ]RQHV command with MODIFY in the EDIT menu or Shortcut <Enter>. Attributes cannot be edited if they are identifiers of network objects (e.g. zone number) or calculation results. =RQH DWWULEXWHV GLDORJ )RUPXOD WDE
RQO\ DFWLYH If this option is disabled, all zones are modified. $WWULEXWH Select the attribute to be modified for active/all zones.
The highlighted attribute is not regarded for changes using the 6SHFLDO IXQFWLRQV tab.
4-109
THE NETWORK EDITOR
Zones
Follow this sequence to modify attribute for multiple zones: Set option and select attribute to be edited, Activate button and enter or select value(s), Set $GG option to active/inactive, Confirm with OK, Close =RQH DWWULEXWHV dialog box with OK %XWWRQV &RQVWDQW enter constant attribute value. )DFWRU: multiply current attribute values by factor. $WWULEXWH: adopts values of another attribute. )RUPXOD: enter formula to be adopted and calculated. 5RXQGLQJ: Enter runding facot for attribute values. ,QLW ERXQG ,QLW ERXQG excludes zonal boundaries from the network.
For the functionality of the buttons provided via )RUPXOD tab see chapter 4.3.6.1 0RGLI\ DWWULEXWH IRU PXOWLSOH QRGHV.
4-110
Zones
THE NETWORK EDITOR

,QLWLDOL]H ERXQGDULHV RI PXOWLSOH ]RQHV

6SHFLDO IXQFWLRQV
Call up the 0RGLI\ DWWULEXWH IRU PXOWLSOH ]RQHV command with MODIFY in the EDIT menu or Shortcut <Enter>. =RQH DWWULEXWHV GLDORJ 6SHFLDO IXQFWLRQV WDE
Click the ,QLWLDOL]H ERXQGDULHV button to initialize existing zone polygons (read from file or specified interactively). Existing data are kept until network or version will be saved to file again (overwriting existing file). To switch off the graphical display of zone boundaries disable the 'UDZ SRO\JRQ option under GRAPHICS PARAMETERS - =RQHV
4-111
THE NETWORK EDITOR
Zones

$JJUHJDWH DFWLYH ]RQHV WR IRUP RQH ]RQH

At least 1 zone in the network must be passive. All currently active zones are aggregated to form one zone. The O-D matrix is adjusted accordingly.
Call up $JJUHJDWH ]RQHV with AGGREGATE in the EDIT menu or Shortcut <F7>.
Enter the new zone number, confirm OK and double-click zone.
VISUM sums up AddValue data and demand data of the selected zones (total = attribute data of the new zone).
Click left to mark the centroid of the aggregated zone. Define the new polygon via SPECIFY COURSE ZONE. If necessary, continue with MODIFY CONNECTORS. If necessary, continue with CALCULATE - O-D MATRIX or FILE - SAVE 2' PDWULFHV file type.
4-112
Zones
THE NETWORK EDITOR
([DPSOH DJJUHJDWH ]RQHV IURP ]RQHV Zone 100 from Zone 1 + 2 + 3, Zone 200 from 4 + 5 + 8, etc.
In the network graphic, the connectors are highlighted by arrows. 3URFHGXUH MULTI SELECT - ZONES Set Zones 1 + 2 + 3 passive (with left mouse click); Click right mouse button: activate ,QYHUW command; Call up $JJUHJDWH: Enter zone number 100; Transfer attributes, centroid and polygon. adds the AddValue data; sets distribution to DEVROXWH; adopts all connector nodes and the higher zone type for the aggregated zone; sums the demand (without the internal traffic within an aggregated zone).
9,680 5HVXOW
4-113
THE NETWORK EDITOR
Zones

'HOHWH DFWLYH ]RQHV

Activate MULTISELECT mode and ZONE network object type.
Specify active and passive zones. Delete active zones with DELETE in the EDIT menu or Shortcut <Del>. Only active zones can be deleted. The connectors from/to deleted zones are also deleted. The assignment result is initialized. A subsequently saved O-D matrix will contain neither the origin nor the destination demand of the deleted zones.
4-114
Connectors
THE NETWORK EDITOR
&RQQHFWRUV
Connectors connect zones to the transport network. They represent the access and egress routes between centroid and PuT-stops or PrT-nodes. A connector has two directions, which can be used by PrT and/or PuT modes as access or egress routes: origin connector from zone to node. destination connector from node to zone.
Zones are origins and destinations of trips within the transport network. This means that an origin connector always represents the first part, and a destination connector always the last part of a trip. For assignment, every zone must be connected up to the network with at least one origin connector and at least one destination connector. A zone can be connected to the network with any number of connector nodes. PuT-connectors can only be used by passengers if they connect a served stop. PrT-connectors must be connected to a PrT-node. The PrT-node can also be a stop.
4-115
THE NETWORK EDITOR
Connectors
Connectors can be edited using the following commands: (GLW FRPPDQG 6HDUFK 0RGLI\ 'HOHWH 7H[W LQRXW 6SHFLI\ FRXUVH 6KLIW WH[W $JJUHJDWH 6SOLW &RS\ *HQHUDWH 6KRUWFXW <F3> <Enter> <Del> <F4> <F5> <F6> <F7> <F8> <F9> X X X X X X
4-116
Connectors
THE NETWORK EDITOR
&RQQHFWRU DWWULEXWHV

7\SH $WWULEXWH 'HILQLWLRQ Number of the zone which is connected. default: selected with mouse range: defined node numbers Name of the zone which is connected by the connector. Code of the zone which is connected by the connector. Type of zone which is connected by the connector. Number of node which is connected by the connector. default: selected with mouse range: defined node numbers Name of node which is connected by the connector. Code of node which is connected by the connector. Type of node which is connected by the connector. Type of connector. default: 0 range: 0 - 9 Connection permitted for O orgin traffic, D destination traffic, OD both directions. default: both directions permitted range: yes/no Length of connector. default: direct distance range: Long Int Direct distance between Zone and Node (as the crow flies).
PrT+PuT ZoneNr ZoneNumber (Input) PrT+PuT ZoneName (from ZoneNr) PrT+PuT ZoneCode (from ZoneNr) PrT+PuT ZoneType (from ZoneNr) PrT+PuT NodeNr NodeNumber (Input) PrT+PuT NodeName (from NodeNr) PrT+PuT NodeCode (from NodeNr) PrT+PuT NodeType (from NodeNr) PrT+PuT Type (Input) PrT+PuT Direction (Input)
PrT+PuT Length (Input) PrT+PuT LengthDir Length-direct distance (calculated)
4-117
THE NETWORK EDITOR
Connectors
7\SH PrT
$WWULEXWH PrT-Mode (Input) PuT-Mode (Input) t0-PrT t0-PrT (Input) t-PuT t-PuT (Input) Perc Percentage (Input) Vol-PuT Volume-PuT (assignment) Vol-PrT Volume-PrT (assignment) Imp-PrTSys Impedance-PrTSys (assignment)
'HILQLWLRQ Connector open for PrT (0 = No, 1= Yes). default: permitted range: yes/no Connector open for PuT (0 = No, 1 = Yes). default: permitted range: yes/no Private transport access and egress time. default: connector speed PrT (EXTRAS-OPTIONS) range: time interval Public transport access and egress time. default: connector speed PuT (EXTRAS-OPTIONS) range: time interval Percentage of travel demand from/to zone per mode which uses connector. range: 0 - 100 % Public transport [passengers]. volume on the connector
PuT
PrT
PuT
PrT
PuT
PrT
Private transport volume on the connector [vehicles]. PrT system-specific value of the capacity-based impedance function considering the current traffic volume. AddValue1, AddValue2, AddValue3, range: Long Int
PrT
PrT+PuT AddVal1-3 AddValue 1-3 (user-defined)
4-118
Connectors
THE NETWORK EDITOR
,QVHUW FRQQHFWRU
To link zones with the network connectors have to be inserted separately: SINGLESELECT mode: ,QVHUW &RQQHFWRU, MULTISELECT mode: *HQHUDWH &RQQHFWRUV. Activate INSERT mode. Activate the CONNECTORS network object.
Mark zone and desired connecting node. The sequence is not important since it is possible to switch between origin and destination connectors (zone node) in the dialog box. if a zone is marked first, all connectors from and to the zone are highlighted by directed arrows if a node is marked first, all connectors from/to the zones using the node are highlighted ,QVHUW FRQQHFWRU GLDORJ Modify the default values, if necessary. Then confirm. absolute distribution or proportional distribution
For the percentage of demand entry the option 3U72ULJ&RQQ and/or 3U7'HVW&RQQ needs to be active (see MODIFY ZONE).
4-119
THE NETWORK EDITOR
Connectors
7\SH 0..9, default value 0 /HQJWK Default value from centroid and node coordinates [m] 7LPH 3U7 7LPH 3X7 The default value is calculated using the connector length and connector speed (&RQQHFWRUV via OPTIONS in the EXTRAS menu). Each time a connector time is entered, the current time format must be considered or the unit (h, min, s) specified. 3HUFHQWDJH Proportion of the connector of 100% PrT travel demand for each zone and direction. For a zone, the proportions of all PrT connectors for each direction must amount to 100%. The 3HUFHQWDJH attribute for the proportional distribution of origin or destination PrT demand only appears if the distribution of the PrT traffic demand for the zone is proportionally defined with MODIFY or INSERT ZONE. 2SWLRQ 3U7 3X7 Define the connector separately for PuT and PrT. Opp.dir. 2SS'LU button: Switch to the opposite direction of the connector. Directions of a connector )URP7R: Orig. connector: FromZone ToNode, Dest. connector: FromNode ToZone.
4-120
Connectors
THE NETWORK EDITOR
6HOHFW FRQQHFWRU

Activate SINGLE SELECT mode and CONNECTOR network object.
For MODIFY and DELETE: Select a connector (zone node): Search with right mouse click for zone (name, code or number) or node (name, code or number). Then click on a highlighted network object. Mark with left mouse click on zone and a highlighted connecting node or node and one of the connected zones.
For MODIFY only: Select a zone and all connectors from/to the zone: search for / mark zone. node and all connectors to/from the node: search for / mark node. In the dialog box, the buttons and ! as well as 2SS'LU can be used to switch to each connector.
Double-clicking on a zone or a connecting node or Mark and <Enter>
immediately calls up the dialog box for MODIFY CONNECTOR.
'HOHWH FRQQHFWRU

Activate SINGLE SELECT mode and CONNECTORS network object.
Select connector (zone node, either inbound or outbound). Delete connector with DELETE in the EDIT menu or Shortcut <Del>. DELETE CONNECTOR deletes all connectors (inbound and outbound for Prt and PuT) between the selected zone and node. To delete a connector for only one direction or e.g., for PrT only, activate MODIFY CONNECTOR and disable the particular option.
4-121
THE NETWORK EDITOR
Connectors
(GLW FRQQHFWRU

0RGLI\ FRQQHFWRU DWWULEXWHV
Activate SINGLE SELECT mode and CONNECTORS network object
Select connector. Modify connector with MODIFY in the EDIT menu or <Enter> or Double-click on selected zone or node &RQQHFWRU GLDORJ Select connector (zone node) via < or > button. Select direction via 2SSGLU button. Modify length of connector, permit or close o type PrT and/or PuT, connector time, AddValues.

3URSRUWLRQDO GLVWULEXWLRQ RI WKH 3U7 GHPDQG

Activate SINGLE SELECT mode and ZONE network object.
MODIFY ZONE: Select zone and modify settings for PrT-connectors. VISUM issues a warning if the type of distribution of the PrT demand in the zone dialog box is modified from DEVROXWH to SURSRUWLRQDO The combination of DEVROXWH and SURSRUWLRQDO is admissible VISUM default values for proportions: 100 % : number of PrT-connectors of the zone by direction. Example: For 3 origin connectors, VISUM assigns 33%, 33% and 34%. Activate SINGLE SELECT mode and CONNECTORS network object.
MODIFY CONNECTORS: Select zone and direction, Select connectors one by one, make corrections if necessary.
4-122
Connectors
THE NETWORK EDITOR
(GLW PXOWLSOH FRQQHFWRUV

Activate MULTI SELECT mode and CONNECTORS network object type.
6SHFLI\ DFWLYH FRQQHFWRUV IRU HGLWLQJ using one of the methods described below or a combination of them. Active connectors are only those which satisfy all current specifications! )LOWHU: define connectors filter MultiSelect selection specified in MULTI SELECT mode as rectangle: drag while holding down left mouse button; polygon: while holding down the <Ctrl> key, fix the polygon points one by one by clicking left mouse button. Release <Ctrl> prior to marking the last point. All connectors from/to a zone with the centroid within the polygon are set to active. AREA : Call the 2EMHFWV ZLWKLQ $UHD 6HW DFWLYH function through
and right-hand mouse-click or MULTISELECT command in the EXTRAS menu and select area. 0RGLI\ VWDWH of single object: set single connector in MULTI SELECT mode to active/passive with left mouse click. This can also be used for "fine editing" of fixed polygons. Connectors which are passive because of current filter parameters cannot be set to active! ,QYHUW: set all active connectors to passive and all passive zones to active. Clicking the right mouse button activates this dialog. Set connectors to active/passive by reading the following file type(s): filter parameters: *.fil, specified active network object: *.ane.
If there are no passive connectors in the network, the modifications are adopted for all connectors. Connectors which are passive because of connector filter or Area settings may be treated as active connectors when editing in MULTISELECT mode: Disable &RQVLGHU RQO\ DFWLYH option accordingly. Display current status (number of active and passive connectors) via PROGRAM STATUS in the EXTRAS menu.
4-123
THE NETWORK EDITOR
Connectors

0RGLI\ DWWULEXWH IRU PXOWLSOH FRQQHFWRUV

Activate MULTI SELECT mode and CONNECTORS network object type.
Call up the 0RGLI\ DWWULEXWH IRU PXOWLSOH FRQQHFWRUV command with MODIFY in the EDIT menu or Shortcut <Enter>. Attributes cannot be edited if they are identifiers of network objects (e.g. zone number) or calculation results. &RQQHFWRU DWWULEXWHV GLDORJ )RUPXOD WDE
RQO\ DFWLYH Only active connectors are edited. $WWULEXWH Select the attribute, and sub-attribute, if applicable, to be modified.
G
4-124
For the general functionality of the buttons see chapter 4.3.6.1 0RGLI\ DWWULEXWH IRU PXOWLSOH QRGHV.
Connectors
THE NETWORK EDITOR
Follow this sequence to modify attribute for multiple connectors: Set option and select attribute to be edited, Activate button and enter or select value(s), Set $GG option to active/inactive, Confirm with OK, Close &RQQHFWRUV DWWULEXWHV dialog box with OK %XWWRQV &RQVWDQW enter constant attribute value. )DFWRU: multiply current attribute values by factor. $WWULEXWH: adopts values of another attribute. )RUPXOD: enter formula to be adopted and calculated. 5RXQG enter rounding factor for values of the selected attribute.
Constant
([DPSOH 3HUPLW 3XEOLF 7UDQVSRUW WR XVH DOO DFWLYH FRQQHFWRUV
Formula
The attribute selected for editing is 3X70RGH. Enter: Constant 1 = Permit PuT; Constant 0 = Do not permit PuT.
([DPSOH &DOFXODWH $GG9DO WKH GLIIHUHQFH EHWZHHQ WLPH UHTXLUHG LQ WKH ORDGHG DQG XQORDGHG QHWZRUN (Attention: Only, if distribution = percentages, else t0 = tCur)
4-125
THE NETWORK EDITOR
Connectors

'HOHWH DFWLYH FRQQHFWRUV

Activate MULTISELECT mode and CONNECTORS network object type.
Specify active and passive connectors. Delete active connectors with DELETE in the EDIT menu or Shortcut <Del>. The zones which were connected through the deleted connectors remain in the network. New connectors can be generated automatically.

*HQHUDWH FRQQHFWRUV
Activate MULTISELECT mode and CONNECTORS network object type.
To link new zones with the network connectors have to be inserted separately for PrT and PuT: SINGLESELECT mode: ,QVHUW &RQQHFWRU, MULTISELECT mode: *HQHUDWH &RQQHFWRUV. For *HQHUDWH FRQQHFWRUV only active nodes and zones are regarded. Passive and active links are only regarded, if option "&RQQHFW RQO\ QRGHV WRIURP DW OHDVW RQH DFWLYH OLQN" is active. In case, more nodes than specified under PD[ QXPEHU might be used for *HQHUDWLQJ FRQQHFWRUV, VISUM will prefer those with the minimum connector length (direct distance between zone centroid and node).
4-126
Connectors
THE NETWORK EDITOR
(',7PHQX *(1(5$7( &211(&7256
3U7 Only PrT connectors will be generated. 3X7 Generating only PuT connectors, zones are only connected to stops. PD[ OHQJWK GLUHFW GLVWDQFH Max. distance Node Zone in [m]. PD[ QXPEHU FXUUHQW VWHS During this step only the entered number of PrT (or PuT) connectors will be generated per zone. 7RWDO QXPEHU SHU ]RQH (separately for PrT and PuT) Limit number of PrT (and PuT) connectors per zone, if necessary. 7\S GHU HU]HXJWHQ $QELQGXQJHQ The type serves e.g., to indicate generated connectors. &RQQHFW RQO\ QRGHV IURPWR DW OHDVW RQH DFWLYH OLQN Use link filter, if necessary.
4-127
THE NETWORK EDITOR
Global zones

*OREDO ]RQHV
Any number of zones may be combined to form a global zone. Global zones can be used when working with AddValues and for displaying flow bundles. Global zones are units which include several zones, whereby each zone may only be a part of one global zone. Global zones can be edited using the following commands: (GLW FRPPDQG 6HDUFK 0RGLI\ 'HOHWH 7H[W RQRII 6SHFLI\ FRXUVH 6KLIW WH[W $JJUHJDWH 6SOLW &RS\ 6KRUW FXW <F3> <Enter> <Del> <F4> <F5> <F6> <F7> <F8> <F9> X X X X X X X
4-128
Global zones
THE NETWORK EDITOR
*OREDO ]RQH DWWULEXWHV

7\SH PrT+PuT $WWULEXWH Nr Number (Input) Name (Input) Code (Input) Type (Input) X-Coord X-Coordinate (Input) Y-Coord Y-Coordinate (Input) AddVal1-3 AddValue1, 2, 3 (user-defined) NumSubZones Num Subzones (Input) SumZoneAddV1,2,3 (calculated) Area (calculated) NumConNodes NumConnectedNodes (link network) 'HILQLWLRQ Number of global zone. default: max. GZoneNr+1 range: 1-999999999 Name of global zone. default: empty string range: Text20 Code of global zone. default: empty string range: Text8 (a..z in first place) Type of global zone. default: 0 range: 0 9 X-Coordinate of the global zones center of gravity. default: from mouse position range: Real Y-Coordinate of the global zones center of gravity. default: from mouse position range: Real AddValue1, AddValue2, AdValue3 range: Long Int Number of zones, which are part of the global zone Sum of AddValue1 data of zones, of AddVal2 data, of AddVal3 data of zones. Area of the global zone, defined by the global zone polygon. Number of nodes which are connected with the global zone.
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
4-129
THE NETWORK EDITOR
Global zones
7\SH PrT+PuT
$WWULEXWH OTraffic OriginTraffic (O-D matrix) DTraffic DestTraffic (O-D matrix) NumLines Num Lines (line network) NumSLines Num sublines (line network) NumService Num Services (timetable) OConTimeMax OrigConTimeMax (calculated) OConTimeMean OrigConTimeMean (calculated) OConTimeMin OrigConTimeMin (calculated) DConTimeMax DestConTimeMax (calculated) DConTimeMean DestConTimeMean (calculated) DConTimeMin DestConTimeMin (calculated)
'HILQLWLRQ Originating traffic by private transport system or public transport mode. Terminating traffic by private transport system or public transport mode. Number of lines, which serve stops connected to zones in the global zone. Number of sublines, which serve stops connected to zones in the global zone. Number of services (vehicle trips), which serve stops connected to zones in the global zone. Maximum origin connecting time by mode.
PrT+PuT
PuT
PuT
PuT
PrT+PuT
PrT+PuT
Mean origin connecting time by mode.
PrT+PuT
Minimum origin connecting time by mode (private/public transport). Maximum destination connecting time by mode. Mean destination connecting time by mode. Minimum destination connecting time by mode.
PrT+PuT
PrT+PuT
PrT+PuT
4-130
Global zones
THE NETWORK EDITOR
7\SH PrT+PuT
$WWULEXWH FlowBundleO FlowBundleOrigin (flow bundle) FlowBundleD FlowBundleDest (flow bundle)
'HILQLWLRQ Flow bundle of originating traffic volume (Private or public transport). Flow bundle of destinating traffic volume (Private or public transport).
PrT+PuT
,QVHUW JOREDO ]RQH

Activate INSERT mode. Activate GLOBAL ZONES network object type.
Left-click to specify coordinates of the centroid. The label of a global zone is always displayed at the coordinates of its centroid. ,QVHUW JOREDO ]RQH GLDORJ
4-131
THE NETWORK EDITOR
Global zones
1XPEHU 7\SH Mandatory input attributes. &RGH 1DPH $GG9DOXHV Optional input attributes. 3RVLWLRQ [ \ The co-ordinates of the centroid marked by mouse-click can be edited, either explicitely in the dialog box or interactively in the network display on screen.
The numbers of the subzones are entered by VISUM when the global zone polygon is then specified. Unlike inserting a traffic zone, specifying the polygon for a global zone, therefore, is not optional. Each zone can only be a subzone of RQH global zone. Modifications removing or adding a subzone - are not possible in the list box of the dialog box, but must be made interactively in the network display. The purpose of the boundary is to define subzones (all zones whose centroid is within the polygon) to calculate the area of the global zone, ie. to show the extension of its coverage.
Zones whose centroids lie within the global zone polygon do not have to remain subzones of the global zone. Likewise, traffic zones whose centroids lie outside the global zone polygon can be defined as subzones of a global zone. These modifications can be made using MODIFY - GLOBAL ZONE.
6SHFLI\ WKH ERXQGDU\ RI D JOREDO ]RQH The centroid should lie within the polygon, otherwise the global zone cannot be marked later in SINGLE SELECT mode with a mouse click within the polygon, but can only be selected by searching. Mark the polygon points around the centroid with left mouse click. A final double-click closes the polygon. VISUM connects the last marked polygon point to the first. The global zone polygon can be deleted and redefined or modified (insert, delete, shift polygon points). See chapter 4.6. 6SHFLI\ ]RQH SRO\JRQ.
4-132
Global zones
THE NETWORK EDITOR
6HOHFW JOREDO ]RQH

Activate SINGLE SELECT mode and GLOBAL ZONES network object type.
Selecting a global zone: mark it with left mouse click search for it with right mouse click
Then call up the required edit command. Double clicking within the polygon of a global zone or marking it and pressing <Enter>
GLOBAL ZONE
immediately calls up the dialog box for the MODIFY command.
'HOHWH JOREDO ]RQH

Select a global zone. Delete a global zone by clicking DELETE in the EDIT menu or using the shortcut <Del>.
4-133
THE NETWORK EDITOR
Global zones
(GLW JOREDO ]RQH

Select a global zone. Shift the centroid by clicking on SHIFT TEXT in the EDIT menu or using the shortcut <F6>. The global zone label can also be moved in the network display: Keep mouse-key pressed and drag label to another position.
Mark the new position of the centroid by clicking. The centroid should lie within the global zone polygon. The position and the extension of the polygon remain the same.
G

6SHFLI\ ERXQGDU\ RI JOREDO ]RQH

Select a global zone. Specify the course of the polygon by clicking the menu EDIT-6SHFLI\ FRXUVH or using the shortcut <F5>. The existing global zone polygon is deleted. Inserting a boundary: mark the polygon points around the centroid with left mouse click, a final double click closes the polygon: VISUM connects the last polygon point with the first marked polygon point, the centroid should lie within the polygon. See also Chapter 4.6.: Modify zonal polygon. - PARAMETERS- *OREDO ]RQHV: GUDZ ERXQGDULHV must be
G
4-134
GRAPHICS
active.
Global zones
THE NETWORK EDITOR

0RGLI\ JOREDO ]RQH DWWULEXWHV

Select a global zone. Modify a global zone by clicking menu EDIT-0RGLI\ or using the shortcut <Enter> or double clicking within the selected global zone. 0RGLI\ JOREDO ]RQH GLDORJ %DVLF WDE
%DVLF
Each zone can be part of RQO\ RQH global zone. Remove/Add a partial zone is possible by mouse-click on the particular zone in the network display.
THE NETWORK EDITOR
Global zones
0RGLI\ JOREDO ]RQH GLDORJ 'HPDQG WDE 'HPDQG
Display of matrix values for Private transport in [veh] and Public transport in [Pass]
4-136
Global zones
THE NETWORK EDITOR

0RGLI\ VXE]RQHV RI D JOREDO ]RQH

Select a global zone. Clicking the left mouse button alternately turns a traffic zone 2Q2II as a subzone of the current global zone: deactivate an active subzone by clicking on its centroid with the left mouse button (it will be removed from the list of subzones in the Modify Global zone dialog box)) activate a zone as an additional subzone by clicking on its centroid with the left mouse button each zone can only be a subzone of RQH global zone.
4-137
THE NETWORK EDITOR
Global zones
(GLW PXOWLSOH JOREDO ]RQHV

Activate MULTI SELECT mode and GLOBAL ZONES network object type.
'HILQH WKH DFWLYH JOREDO ]RQHV IRU DWWULEXWH HGLWLQJ by using one or a combination of the methods described below. )LOWHU: define global zone filter MultiSelect selection specified in MULTI SELECT mode as rectangle: drag while holding down left mouse button; polygon: while holding down the <Ctrl> key, fix the polygon points one by one by clicking left mouse button. Release <Ctrl> prior to marking the last point. All global zones with the centroid within the polygon are set to active. AREA through : Call the 2EMHFWV ZLWKLQ $UHD 6HW DFWLYH function
and right-hand mouse-click or MULTISELECT command in the EXTRAS menu and select area. Changing the status of a single object: set the particular global zone to the active/passive state in MULTI SELECT mode with left mouse click. This can also be done as subsequent "detailed editing" of defined reference areas. Global zones which are passive due to current filter parameters cannot be set to the active state! ,QYHUW: sets all active global zones to the passive state and all passive global zones to the active state simultaneously. Clicking the right mouse button activates the dialog box. file: set global zones to the active/passive state by reading in one or several of the following file types: filter parameters: *.fil, defined active network objects: *.ane. Output of current status (number of active or passive global zones) via EXTRAS-PROGRAM STATUS. If there are no passive global zones in the network, modifications of the attributes apply to all global zones.
4-138
Global zones
THE NETWORK EDITOR

0RGLI\ DWWULEXWHV IRU PXOWLSOH JOREDO ]RQHV

Activate MULTI SELECT mode and the network object type ZONES.
GLOBAL
G

Editing global zones in MULTI zones in MULTI SELECT mode.
SELECT
mode corresponds to editing
'HOHWH DFWLYH JOREDO ]RQHV

Activate MULTI SELECT mode and the network object type ZONES.
GLOBAL
Deleting active global zones in MULTI SELECT mode corresponds to deleting active zones in MULTI SELECT mode.
4-139
THE NETWORK EDITOR
Lines
/LQHV
A PuT-line consists of one or several line variants (sublines) which can have different line routes, timetables or running times between stops. A subline is defined by the name of the line, the variant identifier, the direction, the line route (sequence of served stops) with running times between stops and the timetable (vehicle trips with departure times). The sublines of a line must be part of the same transport system, can have different operators and different vehicle types. A main line can be generated from various sublines. (GLW FRPPDQG 6HDUFK 0RGLI\ 'HOHWH 7H[W RQRII 6SHFLI\ FRXUVH 6KLIW WH[W $JJUHJDWH 6SOLW &RS\ <F4> <F5> <F6> <F7> <F8> <F9> X X X X 6KRUWFXW <F3> <Enter> X X X X
4-140
Lines
THE NETWORK EDITOR
9HKLFOH W\SHV DQG RSHUDWRUV

3X7 YHKLFOH W\SHV
'HILQLWLRQ Type of public transport vehicle. range: 1-32767 Code of public transport vehicle type. range: Text8 Name of public transport vehicle type. range: Text20 Code of the PuT system to which the vehicle type belongs. range: defined transport systems Seat capacity: Number of seats by vehicle. range: 0-32767 Total capacity: Seats and standing capacity by vehicle. range: 0-32767 Cost per vehicle-kilometer. range: Real, 0 Cost per out-of-depot hour. range: Real, 0 Daily fixed cost per vehicle. range: Real, 0 Number of available vehicles. range: 0-32767 Cost per vehicle refer to 0 = one year 1 = one day range: 0 or 1
$WWULEXWH VehType VehicleType (Input) VehCode (Input) VehName (Input) TSysCode (Input) SeatCap (Input) TotalCap (Input) KmCost (Input) HourCost (Input) VehCost (Input) NumVeh NumVehicles (Input) RefTime Reference Time (Input)
4-141
THE NETWORK EDITOR
Lines
'HILQLWLRQ RI YHKLFOH W\SHV
PUT 9EHICLE TYPESin the EXTRAS PHQX
,QVHUW button
,QVHUW YHKLFOH W\SH: Select Transport system, the vehicle type belongs to, the time period (day/year), the vehicle cost refer to.
Lines
THE NETWORK EDITOR
0RGLI\ button
No changes to VehTypeNr. or TSys permitted.
4-143
THE NETWORK EDITOR
Lines

3X7 RSHUDWRUV
'HILQLWLRQ PuT operator number. range: 1-32767 PuT operator name. range: Text20 Public transport operator cost for depreciation and fixed costs Default: 0 range: Real Number of lines per operator.
$WWULEXWH OpNr OperatorNr (Input) OpName OperatorName (Input) Cost1 Cost2 Cost3 (Input) NumLines Num Lines (subline) NumSLines Num sublines (line network) NumService Num Services (subline) SeatKm (calculated) ServiceT ServiceTime (timetable) VehKm VehicleKm (subline)
Number of sublines.
Number of services (vehicle trips) of all sublines of operator. Seat kilometers = VehKm x number of seats. Service time for passenger transport.
Vehicle kilometers of all sublines = Line length x VehTrips.
4-144
Lines
THE NETWORK EDITOR
'HILQLWLRQ RI RSHUDWRUV
387 23(5$7256LQ WKH (;75$6PHQX
,QVHUW button
0RGLI\ button
4-145
THE NETWORK EDITOR
Lines
/LQH DWWULEXWHV

$WWULEXWHV RI VXEOLQHV OLQHV DQG 3X7 V\VWHPV
The attributes of a line (L) result from the attributes of its sublines (S). The line-related attributes of a public transport system are indicated by (T). Usually the attribute values refer to one Day, but also the interval specified through time filter or the result from projection to one Year (for line costing calculation) can be regarded as subattribute. Following the line naming conventions the attributes are listed in alphabetical order: / X 6 $WWULEXWH 'HILQLWLRQ Name of line. All sublines with identical line names belong to the same line. range: max. Text 18 (Standard: Text6) Variant of line. Range: max. Text 18 (Standard: Text2) Direction of subline (line variant), e.g. F = Forth, B = Back. Range: Text1 Specify direction indicators: OPTIONS-/LQHV: Code1;Code2. X SLinID SubLineID (calculated) Menu EXTRAS-
X Name (Input) X Variant (Input) X Direction (Input)
Subline identifier Subline = Name + Variant + Direction. Range: max. Text 20 Prior to ,QVHUW D /LQH: SLinID may not exceed 20 characters. Specify the max. permitted number of characters for Name and Variant first. Use a text processing editor for specification of the permitted number of characters in the network file *.net; Go to Block *Compounds of a line name $LINID:LinNameLength;LinVarLength;... 4;5;>;< * Here: 4 characters are permitted for the name of the line and 5 characters are available for the line variant indicator; For each direction only 1 character may be specified (e.g. > = Forth / < = Back).
4-146
Lines
THE NETWORK EDITOR
9DOLGLW\ S
$WWULEXWH AddVal1,2,3 AddValue1,2,3 (user-defined) AvSat AvSat (calculated)
'HILQLWLRQ AddValue1, AddValue2, AddValue3. range: Long Int Average saturation.
aLinRunT Average running time of vehicle trips. avg. running time of line (calculated) aVehTripLength Average length of vehicle trips. avg. vehicle trip length (calculated) S Cap-Seat Capacity-Seat (calculated) Cap-Total Capacity-Total (calculated) Cost (subline) Seat capacity of all vehicle trips = VehTrips x vehicle seat capacity.. Total capacity of all vehicle trips = VehTrips x vehicle total capacity. Cost = VehKm x KmCost + OpTime x HourCost + NumVeh x VehCost + CostLink + CostStop + CostOp = CostKm + CostHour + CostVeh + CostLink + CostStop + CostOp.
CostCovLinTrip Cost coverage of one line trip. Cost cover of one line trip (calculated) CostCovPerc Cost cover % (calculated) CostCovTot Cost cover total (calculated) Cost coverage [%] = Revenue / operational cost x 100. Total cost coverage = Revenue - operational cost.
4-147
THE NETWORK EDITOR
Lines
9DOLGLW\ T L S
$WWULEXWH CostHour Cost-Hour (subline) CostKm Cost-Km (subline) CostLink Cost-Link (subline) CostLink1 Cost-Link1 (link cost) CostLink2 Cost-Link2 (link cost) CostLink3 Cost-Link3 (link cost) CostOp Cost-Operator (subline) CostOp1 Cost-Operator1 (subline) CostOp2 Cost-Operator2 (subline) CostOp3 Cost-Operator3 (subline) CostStop Cost-Stop (subline)
'HILQLWLRQ Cost-Hour = OpTime x HourCost.
Cost-Kilometer = VehKm x KmCost.
Cost from link cost = CostLink1 + CostLink2 + CostLink3. Cost from link cost1.
Cost from link cost2.
Cost from link cost3.
Cost from operator cost = CostOp1 + CostOp2 + CostOp3. Cost from operator cost1.
Cost from operator cost2.
Cost from operator cost3.
Cost from stop cost CostStop2 + CostStop3.
CostStop1
4-148
Lines
THE NETWORK EDITOR
9DOLGLW\ L S
$WWULEXWH CostStop1 Cost-Stop1 (subline) CostStop2 Cost-Stop2 (subline) CostStop3 Cost-Stop3 (stop cost) CostVeh Cost-Vehicle (subline) DStopCode DestStopCode (from DStopNr) DStopName DestStopName (from DStopNr) DStopNr DestStopNr (Input) FirstDep First Departure (timetable) LastArr Last Arrival (timetable) LayoverT LayoverTime (Input) Length (line route)
'HILQLWLRQ Cost from stop cost1.
Cost from stop cost2.
Cost from stop cost3.
Cost-Vehicle = NumVeh x VehCost.
Node code of destination terminal.
Node name of destination terminal.
Node number of destination terminal.
Departure time of first line service (vehicle trip). Arrival time of last line service (vehicle trip).
Layover time, required after each vehicle trip for driver breaks, slack time and turn back. range: time interval Length between origin destination terminal. terminal and
4-149
THE NETWORK EDITOR
Lines
9DOLGLW\ T
$WWULEXWH LinNetLenCS LineNetLengthCrossSection (subline) LinNetLenDir LineNetLengthDir (subline)
'HILQLWLRQ Length of used network = sum of all used links, where both directions are calculated only once. Length of used network = sum of all used links, where both directions are calculated separately. Number of line trips per demand segment = number of boarding passengers. Total number of line trips = number of boarding passengers. Line trips with no transfers.
LinTrip-DSeg LineTrips - DSeg (assignment) LinTrips LineTrips total (assignment) LinTrips0 LineTrips 0xTransfer (assignment) LinTrips1 LineTrips 1xTransfer (assignment) LinTrips2 LineTrips 2xTransfer (assignment)
Line trips with one transfer.
Line trips with two transfers.
LinTrips>2 Line trips with more than two transfers. LineTrips > 2xTransfer (assignment) LinTrips-DSeg0 LineTrips-DSeg 0xTransfer (assignment) LinTrips-DSeg1 LineTrips-DSeg 1xTransfer (assignment) Line trips per demand segment with no transfers.
Line trips per demand segment with one transfer.
4-150
Lines
THE NETWORK EDITOR
9DOLGLW\ L S
$WWULEXWH LinTrips-DSeg2 LineTrips-DSeg 2xTransfer (assignment) LinTrips-DSeg>2 LineTrips-DSeg > 2xTransfer (assignment) MainLine (Input) mNT mean NumTransfers (assignment) NetLenCS NetLengthCrossSection (link network) NetLenDir NetLengthDir (link network) NumLines Num Lines (subline)
'HILQLWLRQ Line trips per demand segment with two transfers.
Line trips per demand segment with more than two transfers.
S L S
Name of the main line, the subline has been allocated to. Mean number of transfers for passengers of this subline. Length of permitted network = sum of all permitted links, where both directions are calculated only once. Length of permitted network = sum of all permitted links, where both directions are calculated separately. Number of lines which belong to the transport system. Number of services (vehicle trips) of all sublines. Number of sublines which belong to the transport system. Number of stops; Stops, which are served several times, are counted repeatedly. Number of required vehicles (result from roster calculation).
NumService Num Services (subline) NumSLines Num sublines (subline)
NumStop Num stops (line route) NumVeh Num vehicles (roster planning)
4-151
THE NETWORK EDITOR
Lines
9DOLGLW\ L S
$WWULEXWH OpName OperatorName (from OpNr) OpNr OperatorNr (Input) OpTime OperationTime (subline) OStopCode OriginStopCode (from OStopNr) OStopName OriginStopName (Input) OStopNr OriginStopNr (Input) Passh PassengerHours (assignment) PassKm PassengerKm (assignment) Passh-DSeg PassengerHoursDSeg (assignment) PassKm-DSeg PassengerKm-DSeg (assignment) RefNet Reference Network (Input)
'HILQLWLRQ Name of operator.
Number of operator. range: defined operator numbers Operating time (out-of-depot time) of all sublines. Node code of origin terminal.
Node name of orgin terminal.
Node number of orgin terminal.
Passenger hours = number of line trips x in vehicle time. Passenger kilometers = number of line trips x trip length. Passenger hours per demand segment = number of line trips per demand segment x in-vehicle-time. Passenger kilometers per demand segment = number of line trips per demand segment x trip length. Code of reference network for a demand type.
4-152
Lines
THE NETWORK EDITOR
9DOLGLW\ L S
$WWULEXWH RevLinTrip Revenue of 1 line trip (calculated) RevTot Revenue total (subline) RunTime Running Time (Input) SeatKm (subline) ServiceT ServiceTime (subline) Stop-all (line route)
'HILQLWLRQ Revenue of one line trip.
Total revenue of all lines.
Running time between orgin terminal and destination terminal. Seat kilometers = VehKm x number of seats. Service time for passenger transport of all lines. Number of stops traversed by the line (served and not served stops along the line route). Stops which are traversed several times within the line route are counted repeatedly. Number of served stops; stops which are served more than once within the line route are counted only once. Code of the transport system. range: one character, A-Z or 0-9 Name of the transport system. range: Text30 Passenger hours = number of line trips x in vehicle time. Default speed by transport system, e.g. PrT max. speed (Default 200 km/h), PuT: mean speed (Default 50 km/h), PuTWalk: average walking speed (Default = 4 km/h). range: Long Int
T T
L L
S S
Stop-ser Stop-served (line route) TSysCode (Input) TSysName (Input) Passh PassengerHours (assignment) TSys-v (Input)
T T T
L L L
S S S
4-153
THE NETWORK EDITOR
Lines
9DOLGLW\ T
$WWULEXWH TWT Transfer waiting time (assignment)
'HILQLWLRQ Transfer waiting time of all passengers boarding this Transport system. Average speed between origin terminal and destination terminal. Vehicle kilometers of all sublines = Line length x VehTrips. Name of vehicle type.
vAvg v avg. Speed (timetable) VehKm VehicleKm (subline) VehName VehicleName (from VehType) VehType VehicleType (Input)
Number of vehicle type. range: defined vehicle type
4-154
Lines
THE NETWORK EDITOR

$WWULEXWHV RI WKH OLQH URXWH

'HILQLWLRQ Name of line. range: defined line name Variant of line. range: defined line variants Direction of line. range: defined direction Identifier of a subline= Line name + line variant + direction. Maximum 20 characters permitted. Node code of current stop. Node name of current stop. Node number of current stop. range: defined node numbers Index of current stop in line route (sequence of served stops). range: Long Int 0 Passengers may not alight 1 Passengers may alight default: yes range: yes/no 0 Passengers may not board 1 Passengers may board default: yes range: yes/no Running time from departure from origin terminal till arrival at current stop. Running time from departure from origin terminal till departure from current stop.
$WWULEXWH Name (Input) Variant (Input) Direction (Input) SLinID SubLineID (Input) NodeCode (from NodeNr) NodeName (from NodeNr) NodeNr (Input) Index (Input) Alight (Input)
Board (Input)
Arr Arrival (calculated) Dep Departure (calculated)
4-155
THE NETWORK EDITOR
Lines
$WWULEXWH DwellTime (Input)
'HILQLWLRQ Dwell time at current stop. default: 0 range: time interval
CumLineRouteLen Cumulative length between origin terminal and current CumLineRouteLength stop. (line route) LineRouteRunTime Running time between last stop and current stop. LineRouteRunningTime default: values of link network (Input) range: time interval PassAlight (assignment) PassBoard (assignment) ToNode ToNodeNr (subline) ToNodeCode (subline) ToNodeName (subline) Length (Input) LinkLength (link) LinkRunT LinkRunTime (link) t0-PrTSys (link) tCur-PrTSys (link) Number of passengers alighting at current stop. Number of passengers boarding at current stop. ToNode number of a line section.
ToNode code of a line section. ToNode name of a line section. Length between two stops. default: values of link network range: Long Int Length of links traversed between FromStop and ToStop (link attribute). Running time of links between FromStop and ToStop.
PrT running time between FromNode and ToNode in unloaded network PrT running time between FromNode and ToNode in loaded network
4-156
Lines
THE NETWORK EDITOR
$WWULEXWH AddVal AddValue (user-defined) LinkAddVal1 LinkAddValue1 (link) LinkAddVal2 LinkAddValue2 (link) LinkAddVal3 LinkAddValue3 (link) Cap-Seat Capacity-Seat (calculated) Cap-Total Capacity-Total (calculated) CostLink1-3 Cost-Link1, 2, 3 (link) CostStop1-3 Cost-Stop1, 2, 3 (stop) NumService/TI Num Services/TI (Fahrplan) Vol-PuT Volume-PuT (assignment)
'HILQLWLRQ AddValue FromStop-ToStop. range: Long Int AddValue of links between FromStop and ToStop (link attribute). AddValue of links between FromStop and ToStop (link attribute). AddValue of links between FromStop and ToStop (link attribute). Seat capacity of all vehicle trips = VehTrips x vehicle seat capacity. Total capacity of all vehicle trips = VehTrips x vehicle total capacity. Cost for usage of links between FromStop and ToStop.
Cost for usage of ToStop.
Number of services (vehicle trips).
PuT passengers volume of the subline.
4-157
THE NETWORK EDITOR
Lines

$WWULEXWHV RI YHKLFOH WULSV

'HILQLWLRQ Name of line. range: defined line names Variant of line. range: defined line variants Direction of line. range: defined line directions Index. range: Long Int Departure time at origin terminal. range: hh:mm:ss Headway between two departures. range: time interval Last departure time in an interval with a fixed rhythm headway. range: hh:mm:ss Type of vehicle. range: Long Int Number of the vehicle running, resulting from roster calculation. range: Long Int Projection Factor. range: Real Key for operating days in weekly timetable. range: 0-127 Key for operating days in annual timetable. range: Text20
$WWULEXWH Name (Input) Variant (Input) Direction (Input) Index (Input) Dep Departure (Input) Headway (Input) LastDep Last Departure (Input) VehType VehicleType (Input) VehRunNr VehRunningNr (Input) ProjFac Projection Factor (Input) DKey Daily Key (Input) AKey Annual Key (Input)
4-158
Lines
THE NETWORK EDITOR
,QVHUW D VXEOLQH

VISUM provides several default parameters to be preset by the user for INSERT SUBLINE. All preset values may be changed at any time by the user (both, in SINGLESELECT or in MULTISELECT mode).
'HILQH 6WDQGDUG WLPHWDEOH EXTRAS menu OPTIONS 7LPHWDEOH tab
Fixed-time rhythm required for Standard timetable (up to 5 intervals). For ,QVHUW VXEOLQH only: Enable option 8VH 6WDQGDUG WLPHWDEOH. Layover time: to be defined either in minutes or as a percentage of the sublines running time between origin and destination terminal. VISUM will not regard layover time entry and current option status, when the Standard timetable is assigned to multiple sublines in the MULTISELECT mode.
THE NETWORK EDITOR
Lines
/LQHV WDE via 237,216 in the EXTRAS menu Set default parameters: direction flags for calculating attributes of the line route: min. running time in [s] enter "round to" in [s].
Activate INSERT mode and SUBLINES network object.
Left-click anywhere in the network. ,QVHUW VXEOLQH GLDORJ
4-160
Lines
THE NETWORK EDITOR
1DPH Name of line 9DULDQW Name of line variant; Name, variant and direction indicate the subline. 'LUHFWLRQ Select one of the directions (preset via EXTRAS OPTIONS - /LQHV) 76\V1DPH Select transport system (defined via EXTRAS TRANSPORT SYSTEMS - ,QVHUW) 2S1DPH Select operator (defined via EXTRAS - PUT-OPERATORS - ,QVHUW) 9HK1DPH Select the sublines vehicle type defined for the selected TSys (defined via EXTRAS PUT-VEHICLETYPES ,QVHUW) 0DLQ OLQH Optional: Select the main line, the subline is assigned to (defined via EXTRAS PUT-MAINLINES ,QVHUW) *HQHUDWH RSSRVLWH GLUHFWLRQ DXWRPDWLFDOO\ automatically generates the line variant for the opposite direction.
'HILQH OLQH URXWH VISUM supports searching for line routes by identifying and suggesting the shortest route between two marked (so-called fixated) nodes (route selection criterion = direct distance between used links). The parameters for the route search need to be set accordingly.
2.: Confirm line route finally. &DQFHO last operation. 8QGR last step. $XWR]RRP: Shift network section: Subline is placed in the centre of the screen. Set 3DUDPHWHUV for line route search.
4-161
THE NETWORK EDITOR
Lines
Parameters 6HW 3DUDPHWHUV IRU /LQH URXWH VHDUFK
LQFOXGH EORFNHG OLQNV LQ URXWLQJ Links closed for the TSys are considered, as if they were open for the TSys. Confirm 2SHQ EORFNHG OLQNV. LQFOXGH EORFNHG WXUQLQJ UHODWLRQV LQ URXWLQJ Turning relations closed for the TSys are considered, as if they were open for the TSys. Confirm 2SHQ EORFNHG WXUQLQJ UHODWLRQV. VHUYH QHZ VWRSV If this option is disabled, the new subline will serve only the fixated stops. For later line route modifications this option is to be disabled, if the same stops are to be served. VHUYH RQO\ DFWLYH VWRSV This option is only provided, if 6HUYH QHZ VWRSV is active. If 6HUYH RQO\ DFWLYH VWRSV is active, passive nodes will be ignored. Thus, low-ranking stops can be excluded via the node filter. XVH UXQQLQJ WLPH IURP 0HWHU0LQXWH3ODQ Select criterion for line route search (shortest running time between two stops).
4-162
Lines
THE NETWORK EDITOR
6SHFLI\ OLQH URXWH fixate origin terminal with left mouse click drag from the origin terminal while pressing the mouse button release the mouse button at a node along which the line route will run. The node will be fixated. the suggested line route is graphically displayed. The suggestion can be discarded with the 8QGR button, if necessary. mark the remaining line route by fixating further nodes to the destination terminal. the line route is confirmed by pressing the 2. button. if the line route contains links or turning relations which were previously blocked for the transport system of the line, you must confirm the unblocking of the respective network objects. the origin terminal node must be a stop! if the destination terminal node of a subline is not a stop, VISUM will display a warning. The destination node can then automatically be assigned the attribute "Stop". If the node is not to be transformed into a stop: press &DQFHO and edit the line route. subsequent modifications to a line route can be carried out using the SPECIFY COURSE command.
Editing line data: the following tabs are available: %DVLF 6WRSV 7LPHV /HQJWKV 7LPHWDEOH 6HUYLFHV 9ROXPH basic data of the subline (operator etc.) definition of served stops running times between stops and dwell times at stops distances between stops list of departure times (periodical/not periodical) list of all line services assignment result and AddVal FromStop-ToStop
4-163
THE NETWORK EDITOR
Lines
%DVLF WDE %DVLF All input attributes can be modified except TSys.
Num. of stops: Stops served twice are counted twice.
4-164
Lines
THE NETWORK EDITOR
6WRSV WDE 6WRSV Definition of served stops of the line route: DOORZ .
4-165
THE NETWORK EDITOR
Lines
%XWWRQ
6WRSV WDE 0RGLI\LQJ the settings: clicking the button opens the dialog box. Chlick a button for ALL sublines or Check box for any individual subline serving the stop
!
and
4-166
Lines
THE NETWORK EDITOR
/HQJWKV WDE /HQJWKV Editing the lengths between line stops.
([DPSOHV of different settings for the sections of the current line FromStop-ToStop: this section FromStop-ToStop is used by
= !
the current line only. No other line of the entered transport systems traverses this section. several lines whose line routes have the same length. several lines whose line routes have different lengths.
4-167
THE NETWORK EDITOR
Lines
%XWWRQ
/HQJWKV WDE 0RGLI\LQJ the length of a section: clicking the button opens the dialog box. the length of a section for all lines can be set to the length of the link network (Meter-Minute-Plan) or to the length of a line of the TSys.
!
and
4-168
Lines
THE NETWORK EDITOR
7LPHV WDE 7LPHV
([DPSOHV of different settings for sections traversed by the current line FromStop-ToStop: this section FromStop-ToStop is used by
= !
the current line this section FromStop-ToStop is only used. No other line of the entered transport systems traverses this section. several lines whose running times are the same. several lines whose running times are different.
4-169
THE NETWORK EDITOR
Lines
The format of dwell times and running times is determined by the current time format: )RUPDW via OPTIONS in the EXTRAS menu minutes entering 1 is interpreted as 1 minute seconds entering 1 is interpreted as 1 second both formats 0:01 is interpreted as 1 min. If the unit (h or min or s) is entered explicitly, the time format which is currently set is ignored (for example, 1 min 30 s). /LQHVSHFLILF GZHOO WLPH DQG UXQQLQJ WLPH EHWZHHQ VWRSV Make modifications by clicking on the buttons: RunTime between stops or Dwell time at the ToStop.
Button
!
and
The running time of a section for all lines can be set to the running time in the link network (Meter-Minute-Plan) or to the running time by TSys.
4-170
Lines
THE NETWORK EDITOR
7LPHWDEOH WDE Entering the timetable with special formats for regular and irregular 7LPHWDEOH line timetables (departures): not periodical: departure_1, departure_2, etc., last departure periodical: departure_1, regular headway, last departure
Right after switching to another tab in the Modify subline dialog, the departures are arranged in the correct order.
4-171
THE NETWORK EDITOR
Lines
Shift
6KLIW WLPHWDEOH GLDORJ shift the entire timetable forwards or backwards by the entered number of [min] or [s]. if no unit is entered, VISUM will use the currently set time format.
/LQH 6HUYLFHV WDE /LQH 6HUYLFHV
4-172
Lines
THE NETWORK EDITOR
G
9ROXPH
In case, several vehicle types have been defined for the TSys of the subline, the vehicle type can be modified by line service. 9ROXPHV WDE enter line AddVal data for FromStop-ToStop output of line-specific calculation results: number of boarding passengers per stop number of alighting passengers per stop line volume between 2 stops.
If a line is inserted, the volume is always 0. Following PuT assignment, the calculated volume values are displayed.
4-173
THE NETWORK EDITOR
Lines
Button
/LQH YROXPHV EHWZHHQ VWRSV GLDORJ Transport system-specific output line volume and Line-AddValues for all lines of the TSys which use the current section sum total of line volumes and Line-AddValues
>
4-174
Lines
THE NETWORK EDITOR
6HOHFW D VXEOLQH

Activate SINGLE SELECT mode and the LINES network object. All sublines of the network are listed in a selection box.
Select a subline in the network by entering the line name at the prompt or selecting the line by clicking the mouse inside the box or marking one or several stops with left mouse click in the network display on the monitor until the required line is selected.
VISUM graphically highlights the selected line. Adjust the default colour via %DVLF in the menu, color 0DUNLQJ
GRAPHICS-PARAMETER
By clicking the $XWR]RRP button the network section is shifted: the line is shifted to the cenre of the screen. the 'HVHOHFW button highlighting is turned off, that is, a different line to be searched for can be entered
Then, select the required edit command from the EDIT menu: Modify line route: Modify line data (including timetable): Delete line: Aggregate line: Copy line: SPECIFY COURSE <F5> MODIFY <Enter> DELETE <DEL> <F7> <F9>
'HOHWH D VXEOLQH

Activate SINGLE SELECT mode and the LINES network object.
Select line. Use edit command with DELETE in the EDIT menu
4-175
THE NETWORK EDITOR
Lines
(GLW D VXEOLQH

0RGLI\ OLQH URXWH
Select line. Use edit with SPECIFY COURSE in the EDIT menu or shortcut <F5>. 6HW SDUDPHWHUV IRU OLQH URXWH VHDUFK See chapter 4.9.3 ,QVHUW VXEOLQH
3DUDPHWHUV
Fixating a node: mark a free (non-fixated) node in the highlighted line course with left mouse click. VISUM graphically highlights fixated nodes: enter default values for the colour via GRAPHICS PARAMETERS - %DVLF with 0DUNLQJ. Canceling fixated nodes: mark the fixated node with left mouse click. free nodes are highlighted in the same colour as the highlighted line course, as set by 0DUNLQJ.
4-176
Lines
THE NETWORK EDITOR
VISUM differentiates between fixated and non-fixated nodes of a line on the line route: fixated nodes cannot be shifted. They are taken into account during the short route search procedure; the line route traverses these nodes. free nodes may be shifted, that is, instead of going via the free node, the line route goes via the node to which the free node was shifted. VISUM regards origin and destination stops of the line as fixated nodes in the line route as long as they are not shifted. PrT nodes can also be selected as destination stops. VISUM offers the following option:
If the node is not to be assigned the attribute "6WRS" click on &DQFHO, then move the cursor from the last fixated node to the new destination stop. Which section within the whole line route is to be modified? Define section with 2 fixated nodes or 1 fixated node for the section from origin (or to destination) stop. Click on a non-fixated node within this line section and move it to another node in the network by holding down the left mouse button. It will now become a fixated node. VISUM calculates the shortest route from one fixated node or from the origin stop of the line to the next fixated node or to the destination stop, and then displays the new course of the specified line section. This procedure might have to be repeated several times over, whereby the partial route for specifying the course of the line route can be bounded in different ways by other fixated nodes.
VISUM provides 4 route serach criteria for determination of the route with minimum time required between fixated stops.
4-177
THE NETWORK EDITOR
Lines
3RLQWV WR FRQVLGHU EHIRUH IL[DWLQJ QRGHV ,QFOXGH WKH HQWLUH OLQH URXWH LQ WKH URXWH VHDUFK" In this case, no nodes need to be fixated since VISUM regards the origin and destination stops as fixated nodes. 2QO\ VSHFLI\ WKH FRXUVH IRU D SDUW RI WKH OLQH URXWH" If the relevant SDUWLDO URXWH LV DW WKH EHJLQQLQJ RU DW WKH HQG of the current line route, only one node needs to be fixated. In this way, the partial route between the origin or the destination stop and the fixated node (the remainder of the current line flow) can be modified without changing the other partial route. If the relevant SDUWLDO URXWH LV LQ WKH FHQWUH of the line route, that is, if partial routes at the beginning and at the end of the current line flow will remain unchanged, 2 nodes need to be fixated which define the beginning and the end of the modifiable line route part (and simultaneously the beginning and the end of the fixated partial routes). /HQJWKHQ RU VKRUWHQ WKH OLQH URXWH" The line route can be lengthened or shortened at both ends. /HQJWKHQLQJ Fixate previous origin or destination stop. Move the line route from the current origin or destination stop to the required node by holding down the left mouse button. 6KRUWHQLQJ Fixate the node which will be the new origin or destination stop. Move the previous origin or destination stop to the fixated node by holding down the left mouse button.
4-178
Lines
THE NETWORK EDITOR
([DPSOH 6KRUWHQ WKH OLQH URXWH DW WKH EHJLQQLQJ Starting position Line route (stops): 1 2 3 8945
Action 1) Result 1)
Fixate node 3; Move OriginStop of node 1 to node 3. No short route search since fixated node 3 is the new OriginStop:
new line route: 3 8 9 4 5 lengths and running times of the sections FromStop-ToStop in the line flow between OriginStop3 and DestinationStop5 remain the same because the line route has not changed in these sections.
Action 2)
Do not fixate a node. Move the OriginStop from node 1 to node 3.
Result 2)
Execution of short route search procedure between OriginStop (node 3) and DestinationStop (node 5):
new line route: 3 4 5 for section Stop3Stop4, VISUM copies the length and the TSysspecific running time from the Meter-Minute-Plan (link network). length and running time for the unchanged section Stop4Stop5 remain the same since this partial line route is copied.
4-179
THE NETWORK EDITOR
Lines
([DPSOH 6KRUWHQ OLQH URXWH DW WKH HQG Starting position Action 1) Line route (Stops): 1 2 3 8 9 4 5 (as example 1)
Fixate node 9. Move DestinationStop from node5 to node 9.
Result 1)
No short route search since fixated node 9 is the new DestinationStop:
new line route: 1 2 3 8 9 lengths and running times of the sections in the line flow between OriginStop1 and DestinationStop9 remain the same because the line route has not changed in these sections.
Action 2) Result 2)
Do not fixate a node. Move the DestinationStop from node 5 to node 9. Execution of short route search procedure between the origin and destination stops:
new line route: 1 2 3 8 9 here, the remaining line route was copied because alternative sections such as Stop3Stop4 and Stop4Stop9 are not shorter than the previously used sections if the direct distance of the links Stop3Stop4Stop9 = direct distance of the links between Stop3Stop8Stop9, then this route can also be found by VISUM. lengths and running times of the sections in the line flow between stop1 and stop9 remain the same because the line route has not changed.
4-180
Lines
THE NETWORK EDITOR
([DPSOH 6KRUWHQ OLQH URXWH LQ WKH FHQWHU Starting position Action Line route (Stop): 1 2 3 8 9 4 5 (as example 1)
Either fixate node 3 and node 4 or do not fixate any node. Here, no node needs to be fixated since VISUM cannot find a shorter line route between the origin and destination stops.
Drag the line route while holding down the left mouse button from node 8 to node 3 or 4 or from node 9 to node 3 or 4.
Result
Execution of short route search between stop1 and stop5 if no node was fixated between the fixated nodes if nodes were fixated.
new line route: 1 2 3 4 5 the stops 8 and 9 are no longer part of the line route. The remaining stops of the line are copied. section stop3stop4: VISUM copies the length and the TSysspecific running time from the Meter-Minute-Plan of the link network. the lengths and running times of the other sections remain the same since the line route has not changed in these sections.
In the MODIFY SUBLINE 7LPHV dialog box, new sections in the line route are highlighted by .
4-181
THE NETWORK EDITOR
Lines
([DPSOH /HQJWKHQLQJ WKH OLQH URXWH DW WKH GHVWLQDWLRQ WHUPLQDO Starting position Action Line route (Stop): 1 2 3 8 9 4 5 (as example 1)
fixate DestinationStop5 in order to retain current line flow. drag the DestinationStop e.g. from Stop5 to node 10 (no stop) while holding down the left mouse button. In this way, node 10 is fixated and can be transformed into a stop if it is to be the DestinationStop.
or drag it further from node 10 to node 9 to make this the new DestinationStop.
Result
new line route: 1 2 3 8 9 4 5 10 9 for the new section stop5stop9, length and TSys-specific running times are copied from the Meter-Minute-Plan of the link network. the lengths and running times of the other sections remain the same because the line route has not changed in these sections.
4-182
Lines
THE NETWORK EDITOR
([DPSOH /HQJWKHQLQJ WKH OLQH URXWH IURP WKH FHQWHU Starting position Line route (Stops): 1 2 3 8 9 4 5
Action 1)
fixate stop2 and stop9. drag stop8 to stop12.
Result 1)
new line route: 1 2 7 12 13 14 9 4 5
4-183
THE NETWORK EDITOR
Lines
Action 2)
Intended new flow of line route: 1 2 7 12 13 8 9 4 5 fixate stop2 and stop8 drag stop3 to node7
Result 2)
cancel fixation of node7 stop2 and stop8 remain fixated now drag node7 to stop13 new line route: 1 2 7 12 13 8 9 4 5
for new sections, lengths and TSys-specific running times are copied from the Meter-Minute-Plan (line network). the lengths and running times of the other sections remain the same since the line route has not changed in these sections.
4-184
Lines
THE NETWORK EDITOR
Action 3) Stops which are traversed several times
Intended new flow of line route: 1 2 3 8 9 14 13 8 9 4 5 fixate stop8 and stop9 drag stop9 to stop14; stop14 is fixated. cancel fixation of stop9 in order to drag stop9 to stop13 Prompt: :KLFK SDVVDJH WR VSHFLI\ via node 9? Confirm second passage! now drag stop9 to stop13; the first assage remains fixated. fixate stop9 and stop8: Prompt: :KLFK SDVVDJH WR IL[DWH via node 8? Confirm both passages!
Result 3)
new line route: 1 2 3 9 14 13 8 9 4 5 Serving one section FromStop-ToStop several times in one line route is not permitted! If one section stopstop is traversed twice, VISUM automatically sets ToStop to "Boarding/alighting not allowed" for the second passage. The automatic adjustment by VISUM can be subsequently modified: Select SUBLINE - MODIFY - 6WRSV dialog box.
4-185
THE NETWORK EDITOR
Lines

0RGLI\ OLQH DWWULEXWHV

Select line. Use edit command with MODIFY in the EDIT menu or shortcut <Enter>. All entered data (except line identifiers) of the selected line can be modified; the dialog boxes for INSERTING and MODIFYING are identical. Editing line data: The following dialog boxes are available: %DVLF 6WRSV 7LPHV /HQJWKV Modify basic data of the subline (SublineID, vehicle type, layover time, operator) define stops to be served Modify running times between stops / dwell times at stops Modify lengths between stops
7LPHWDEOH Enter/shift departure times 6HUYLFHV Modify veh. type by line service 9ROXPH: AddVal FromStop-ToStop
4-186
Lines
THE NETWORK EDITOR

0RGLI\ WKH VHTXHQFH RI VHUYHG VWRSV

Select line. Use edit command with MODIFY in the EDIT menu or shortcut <Enter>. Activate/Deactivate the %RDUGLQJ SHUPLWWHG DQG $OLJKWLQJ SHUPLWWHG options for each stop on the line route.
4-187
THE NETWORK EDITOR
Lines
The list of served stops of a line contains all stops which are part of the line route, that is, all nodes whose node attribute VWRS iV set to active. The line halts at stops where boarding and/or alighting is permitted . Here, passengers can board, alight or transfer. The line does not halt at stops where boarding and alighting is not permitted o. Transforming a traversed PrT-node into a stop: activate SINGLE SELECT mode and the NODE network object select node and activate MODIFY NODE set node attribute "Stop" active
0RGLI\LQJ the settings: clicking the button opens the dialog box. Chlick a button for ALL sublines (entire column) or check box for any individual subline serving the stop.
4-188
Lines
THE NETWORK EDITOR

0RGLI\ OLQH WLPHWDEOHV
The timetable can be modified for the selected line at any stop (except DestinationStops) or at the selected node for one of the lines which serve the node. 6XEOLQH 1RGH
Activate SINGLE SELECT mode and the SUBLNES network object. Select line. Use edit command: MODIFY in the EDIT menu by clicking the mouse or use shortcut <Enter>.
Activate SINGLE SELECT mode and the NODES network object. Select node. Use edit command: MODIFY in the EDIT menu by clicking the mouse or use shortcut <Enter>.
Select node. Enter timetable
Select line.
The timetable of a line can be defined at every stop of the line (except at the destination stop). VISUM calculates the complete line timetable from the respective line running times FromStop-ToStop and the dwell times specified for the served stops on the line.
THE NETWORK EDITOR
Lines
(GLW PXOWLSOH OLQHV

Activate MULTI SELECT mode and the SUBLINES network object.
Use the "0RGLI\ DWWULEXWHV RI VHYHUDO OLQHV command with MODIFY in the EDIT menu or shortcut <Enter> or double clicking the left mouse button in the network display. 6SHFLI\ DFWLYH VXEOLQHV IRU HGLWLQJ using one of the methods described below or a combination of them. Active sublines are only those which satisfy all current specifications!
Call or define the filter parameters with /LQHV via FILTER in the EXTRAS menu for sublines, lines or TSys. Select within network display: Click left on stop in MULTISELECT MODE LINES. Only those sublines are listed in the current subline list which traverse the marked stop.
Select within list on screen to change status in MULTISELECT MODE. Click left on line(s): Mark several in a row with <> simultaneously. Mark several individual lines with <Ctrl> simultaneously. Sublines which are passive due to filter settings cannot be set to the active state. File: load the filter parameters from file (file type filter *.fil) or read active network objects from *.ane file.
G
8
See EXTRAS - PROGRAM STATUS for the number of active/passive sublines wiithin network..
Click right in MULTISELECT MODE to call the menu displayed to the left (different from other network objects in MULTISELECT MODE): ,QLWLDOL]H and ,QYHUW etc. are not available for lines.
4-190
Lines
THE NETWORK EDITOR

0RGLI\ DWWULEXWH RI PXOWLSOH VXEOLQHV

Use the "0RGLI\ DWWULEXWHV RI VHYHUDO OLQHV command with MODIFY in the EDIT menu or shortcut <Enter> or double clicking the left mouse button in the network display. 0RGLI\ DWWULEXWH RI PXOWLSOH VXEOLQHV )RUPXOD WDE
Set option: only the active lines are modified o all lines are modified. Selection list: Attributes are provided for Sublines and Line routes.
4-191
THE NETWORK EDITOR
Lines
Select a line attribute to be edited by using the buttons: &RQVWDQW enter constant value for the selected line attribute. )DFWRU: multiply current attribute values with factor. $WWULEXWHV: copy the values of a different attribute. 5RXQG: enter rounding factor for attribute values. )RUPXOD: enter a formula for attribute value calculation. The highlighted attribute is irrelevant if modifications are made using the 6SHFLDO IXQFWLRQV tab.
G
Line Route
For the functionality of the buttons provided via )RUPXOD tab see chapter 4.3.6.1 0RGLI\ DWWULEXWH IRU PXOWLSOH QRGHV. /LQH URXWH DWWULEXWHV RI VXEOLQHV
Generate and use data for the selected attribute using $WWULEXWH or )RUPXOD... button: /LQH URXWH UXQQLQJ WLPH: VISUM copies the times from the MeterMinute-Plan which are calculated from the transport systemspecific running times of the links FromStop-ToStop. /LQH URXWH OHQJWK VISUM copies the lengths from the MeterMinute-Plan (calculated from the lengths of the traversed links). Generate $GG9_Subline from summed up AddV_Links (1, 2 or 3) data, e.g. tCur-PrT to compare it with line route running time.
Lines
THE NETWORK EDITOR
5RXQG
Option for Round all time data ('ZHOO WLPH, /LQH URXWH UXQQLQJ WLPH) as specified (seconds) or Option: .HHS OLQH URXWH UXQQLQJ WLPHV (round only dwell times). Though rounding the current line route running time remains as summed up from running times between stops, for a section also running time = 0 can be assigned. Rounded time data may differ from original running time data. This option can also be applied if time format = min is active, as this time format also allows time input in seconds (see Info data block Time data in network file). 6SHFLDO IXQFWLRQV WDE Only, if $WWULEXWHV RI VXEOLQHV has been selected.
4-193
THE NETWORK EDITOR
Lines

$VVLJQ YHKLFOH W\SH WR OLQH VHUYLFHV
Set VehType
'HILQH YHKLFOH W\SHV EXTRAS menu OPTIONS 3X7 9HKLFOH W\SHV ,QVHUW See chapter 4.9.1.1

$VVLJQ 6WDQGDUG WLPHWDEOH WR VXEOLQHV
Standard timetable
4-194
Lines
THE NETWORK EDITOR

'HOHWH PXOWLSOH VXEOLQHV

8 8
Select sublines: in network display or in subline list or use line filter. Use the "'HOHWH PXOWLSOH VXEOLQHV command with DELETE in the EDIT menu or shortcut <Del> (only if all sublines are active) or click right to call context menu, click 'HOHWH.
Confirm OK: selected (active) sublines are deleted passive sublines will be set active immediately. The assignment result is deleted.
4-195
THE NETWORK EDITOR
Lines

$JJUHJDWH PXOWLSOH VXEOLQHV

This function forms one line from all sublines of a line or a transport system. Prerequisite: The sublines to be aggregated need to traverse the same stops in the same order. Activate MULTI SELECT mode and the SUBLINES network object: All active sublines are aggregated to the selected subline, if possible. Activate SINGLE SELECT mode and the SUBLINES network object: All matching sublines are aggregated to the selected subline, if possible.
G
8
For $JJUHJDWH VXEOLQHV either only the active or active and passive sublines can be regarded. If only active sublines are to be aggregated: Set sublines to active or passive state. Procedure: Select subline, To call $JJUHJDWH VXEOLQHV click left on AGGREGATE in EDIT menu or use shortcut <F7> or click right in network display and call $JJUHJDWH
4-196
Lines
THE NETWORK EDITOR
6HW 2SWLRQ DJJUHJDWH RQO\ DFWLYH OLQHV ( all sublines) 6HOHFW $JJUHJDWH YLD ... sublines of same TSys sublines of same line 6HOHFW For 1DPH RI DJJUHJDWHG VXEOLQH ... use name of subline with max. number of line services name of selected subline or generate new name 6HOHFW &ULWHULRQ ... identical run time profile identical order of served stops identical order of traversed stops 6HOHFW Consider for 5XQ WLPH GZHOO WLPH OHQJWK ... not- weighted mean weighted mean Profile of subline with minimum time. 6HOHFW Round time data to ... 5, 10, 15, 30 or 60 seconds. 'HILQH UHVWULFWLRQV For 2SHUDWRU 0DLQ/LQH and/or 9HKLFOH W\SH the same is required, the one that occurs most frequently is to be regarded or do not regard ... only the VDPH or any GLUHFWLRQ is to be regarded.
Specify new run time profile ,GHQWLFDO UXQ WLPH SURILOH Sublines serve stops in identical order and show identical run time between stops and dwell time at stops. 6DPH RUGHU RI VHUYHG VWRSV Sublines serve stops in identical order, but run time between stops and dwell time at stops may differ. 6DPH RUGHU RI VWRSV Sublines traverse stops in identical order, but service, run time and dwell time may differ.
4-197
THE NETWORK EDITOR
Lines
([DPSOH VHWWLQJV 2SWLRQ 6DPH UXQ WLPH SURILOH Use run time and dwell time data for new line. Length profile: Select option. Layover time: Select option: mean value (weighted by line services or not weighted) 2SWLRQ 6DPH RUGHU RI VHUYHG VWRSV Additionally to the mean value also 8VH SURILOH RI WKH OLQH ZLWK PLQLPXP WLPH UHTXLUHG is porvided. If this option is active, lengths, run times, dwell times and layover time are used. If this option is not active, the (weighted or not weighted) mean value is calculated for lengths, run times, dwell times and layover time according to the option settings and will be used. 2SWLRQ 6DPH RUGHU RI VWRSV The sublines do not serve the same stops, some of them may be traversed (or vice versa). 1. Specify order of served stops for aggregated subline (AGG) 2. For all sublines to be aggregated though showing a different order of served stops: serve also traversed stops and allocate time and length (shares) for line service. dwell time is set = 0 at additionally served stops. 3. For run times, dwell times, lengths and layover time the mean value is calculated, which can be weighted (according to current settings) and will be used. 4. If necessary, time data can be rounded for line route sections.
$JJUHJDWH VXEOLQHV 6DYH UHVXOWV The aggregation steps are recorded to the trace file trace.lst. See example (next page): NewSLin;OldSLin;RTNew;RTOld BUS1 1 R;BUS1 1 R;600;600 BUS1 1 R;BUS2 1 H;600;600 BUS1 1 R;BUS2 2 H;600;480
4-198
Lines
THE NETWORK EDITOR
Subline Bus1-1-R Bus2-1-H Bus2-2-H
([DPSOH 6XEOLQHV ZLWK GLIIHUHQW UXQ WLPH SURILOH Line route and running times
3
3
RunT
3
4
NumService 4 1 1
4
3
10 10 9
Aggregate Bus1-1-R
3 3:40 3:10
9:50
optional Rounding Bus1-1-R

3 4 3
10
Subline Bus1-1-R Bus2-1-H Bus2-2-H
([DPSOH 6XEOLQHV ZLWK GLIIHUHQW RUGHU RI VHUYHG VWRSV Line route and running times
3
3
3
RunT
3
4
NumService 4 1 1
4
3
5
10 10 8
Aggregate Bus1-1-R
3 3:35 3:05
9:40
optional Rounding Bus1-1-R

3 4 3
10
4-199
THE NETWORK EDITOR
Lines
0DLQ OLQHV

A user-defined Main line is formed by combining several sublines, neither direction nor transport system of the selected sublines need to be identical. Thus, main line attributes allow various analyses. The same attributes are provided for PuT lines and Main lines.
(;75$60(18 387 0$,1/,1(6
G
8
A subline can be assigned to ionly one main line. ,QVHUW and 0RGLI\ button
Via the < and > buttons a selected subline is added to (or removed from) the list of sublines assigned to the main line.
Modifications of assigned sublines may also be done via 0RGLI\ VXEOLQH in SINGLESELECT MODE (%DVLF tab) or in MULTISELECT mode (&RQVWDQW)
4-200
Areas
THE NETWORK EDITOR
$UHDV
An area is a network object which represents e.g. a district or county. Based on the polygon that describes an areas boundaries it is possible to determine indicators for each area. Areas and their boundaries are saved with the network file and the version file. An area is identified by a number, a name, a type (0..9), a boundary. Areas can be edited with the following commands: &RPPDQG 6HDUFK 0RGLI\ 'HOHWH 7H[W RQRII 6SHFLI\ FRXUVH 6KLIW WH[W $JJUHJDWH 6SOLW &RS\ 6KRUWFXW <F3> <Enter> <Del> <F4> <F5> <F6> <F7> <F8> <F9> X X X X X
4-201
THE NETWORK EDITOR
Areas
&DOFXODWLRQ RI DUHDUHODWHG LQGLFDWRUV Active areas break down the attributes as determined by the area boundary. The following rules apply: A link belongs completely to the area if both FromNode and ToNode are inside the area. A link does not belong to the area if both FromNode and ToNode are outside the area. If one node is inside and the other outside the area, then the part of the link stretching from the inner node to the first intersection (area-defining polygon) belongs to the area. A FromStop-ToStop line section is treated as a link, even if there are traversed nodes (non-served stops) inbetween.
4-202
Areas
THE NETWORK EDITOR
$UHD DWWULEXWHV

7\SH PrT+PuT $WWULEXWH Nr Number (Input) Code (Input) Name (Input) Type (Input) X-Coord X-Coordinate (Input) Y-Coord Y-Coordinate (Input) LinkLength (link network) 'HILQLWLRQ Number of area. default: Max. Nr+1 range: 1-999999999 Code of node. default: empty string range: Text8, no number as first character Name of area. default: empty string range: Text50 Type of area. default: 0 range: 00 - 99 X-Coordinate. default: from mouse position range: Real Y-Coordinate. default: from mouse position range: Real Length of all active links in area.
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT PuT
LinNetLenCS Length of line network = length of all links LineNetLengthCrossSection used by PuT-lines. Both directions are (subline) calculated only once. LinNetLenDir LineNetLengthDir (subline) NetLenCS NetLengthCrossSection (link network) NetLenDir NetLengthDir (link network) Length of line network = length of all links used by PuT-lines. Both directions are calculated separately. Length of network = length of all active links of one transport system within the area. Both directions are calculated only once. Length of network = length of all active links of one transport system within the area. Both directions are calculated separately.
4-203
PuT
PrT+PuT
PrT+PuT
THE NETWORK EDITOR
Areas
7\SH PrT+PuT PrT+PuT
$WWULEXWH Area (calculated) LinkAddVal1 LinkAddValue1 (user-defined) LinkAddVal2 LinkAddValue2 (user-defined) LinkAddVal3 LinkAddValue3 (user-defined) NodeAddVal1 NodeAddValue1 (user-defined) NodeAddVal2 NodeAddValue2 (user-defined) NodeAddVal3 NodeAddValue3 (user-defined) VehH-PrT VehicleHours-PrT (assignment) VehKm-PrT VehicleKm-PrT (assignment) NumLines Num Lines (subline) NumSLines Num sublines (subline) NumService Num Services (subline)
'HILQLWLRQ Area, defined by the area polygon. Sum of AddValue for all active links in area. range: Long Int Sum of AddValue for all active links in area. range: Long Int Sum of AddValue for all active links in area. range: Long Int Sum of AddValue 1 for all nodes in area. range: Long Int Sum of AddValue 2 for all nodes in area. range: Long Int Sum of AddValue 3 for all nodes in area. range: Long Int PrT-vehicle hours of all active links. Considers link filter! PrT-vehicle kilometers of all active links. Considers link filter! Number of lines in area. Considers line filter! Number of sublines in area. Considers line filter! Number of services (vehicle trips) in area. Considers line filter!
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
PrT
PrT
PuT
PuT
PuT
4-204
Areas
THE NETWORK EDITOR
7\SH PuT
$WWULEXWH NumVeh-PuT Num Vehicles-PuT (roster planning) Stop-all (line route) Stop-ser Stop-served (subline) PassAlight (assignment) PassBoard (assignment) PassTransfer (assignment)
'HILQLWLRQ Share of vehicle numbers of all PuT lines in area. Considers line filter! Number of stops in area. Number of served Considers line filter! stops in area.
PuT PuT
PuT PuT PuT
PuT passengers alighting the vehicle at stop. PuT passengers boarding the vehicle at stop. PuT passengers, who transfer to another PuT line at that stop. Transfer passengers, who use a PuT Walk link (transfer link), are only counted, when they board another line. Transfer waiting time of all passengers transfering within the area. PuT-passenger hours in area. Considers line filter! PuT-passenger kilometers Considers line filter! Cost of all active lines in area. Hourly costs of all active lines in area. in area.
PuT
TWT Transfer waiting time (assignment) PassH-PuT Passengerhours-PuT (assignment) PassKm-PuT PassengerKm-PuT (assignment) Cost-PuT (subline) CostHour Cost-Hour (subline)
PuT
PuT
PuT PuT
4-205
THE NETWORK EDITOR
Areas
7\SH PuT
$WWULEXWH CostKm Cost-Km (subline) CostLink Cost-Link (subline) CostOp Cost-Operator (subline) CostStop Cost-Stop (subline) CostVeh Cost-Vehicle (subline) SeatKm-PuT (subline) VehKm-PuT VehicleKm-PuT (subline) OpTime-PuT OperationTime (subline) ServiceT-PuT ServiceTime-PuT (subline) RevTot Revenue total (subline) CostCovTot Cost cover total (calculated)
'HILQLWLRQ Kilometer costs of all active lines in area.
PuT
Link costs of all active lines in area.
PuT
Operator costs of all active lines in area.
PuT
Stop costs of all active lines in area.
PuT
Vehicle costs of all active lines in area.
PuT PuT
Seat kilometers of all PuT lines in area. Considers line filter! Vehicle kilometers of all PuT lines in area. Considers line filter! Operating time of all PuT lines in area. Considers line filter! Service time of all PuT lines in area. Considers line filter! Total revenue of all active lines in area.
PuT
PuT
PuT
PuT
Total cost coverage of all active lines in area.
4-206
Areas
THE NETWORK EDITOR
,QVHUW DUHD

Activate INSERT mode and AREAS network object type.
Left-click to fix co-ordinates of label position. ,QVHUW DUHD GLDORJ
As indicated by the pointer, VISUM remains in INSERT mode after the area attributes have been transferred, waiting for the area polygon to be marked. The area boundary enables a precise calculation of area-related indicators to be made. ,QVHUW DUHD SRO\JRQ Left-click to mark (minimum 3) polygon points; VISUM shows the current polygon as a rubber band. Right-click to finish.
6HOHFW DUHD

Activate SINGLE SELECT mode and AREAS network object type.
Left-click in area polygon to select area.
'HOHWH DUHD

Activate SINGLE SELECT mode and AREAS network object type. Select area.
Delete area with Click on DELETE in EDIT menu or Shortcut <Del>.

THE NETWORK EDITOR
Areas
(GLW DUHD

0RGLI\ DUHD DWWULEXWHV
Call up modify area with MODIFY in EDIT menu or Shortcut <Enter> or Double-click in the selected area. 0RGLI\ DUHD GLDORJ Nr, Name, Code, Type and co-ordinates can be modified.

Shift label position by, dragging area identifier to the desired position, or call explicitly SHIFT TEXT in EDIT menu or Shortcut <F6>. Left-click to mark new position. The polygon itself (shape, dimensions) remains unchanged.
6SHFLI\ DUHD ERXQGDU\

Call up digitise area boundary with SPECIFY in EDIT menu or Shortcut <F5>. VISUM highlights current polygon points. shift point: left-click to mark and drag to new position, delete point: hold down <Ctrl> and left-click on point, insert: hold down <Ctrl> and left-click on area boundary to mark position of the new point. Minimum number = 3 points; Maximum number = 1022 points: If applicable, delete area polygon via <F2> and re-digitise.
G
4-208
Areas
THE NETWORK EDITOR
(GLW PXOWLSOH DUHDV

Activate MULTI SELECT mode and AREAS network object type.
'HILQH DFWLYH DUHDV using one or more of the methods below. Active areas are only those areas which meet all current specifications! MULTISELECT: definition in MULTISELECT mode as rectangle: left-click and drag; polygon: hold down <Ctrl> and mark the MULTISELECT polygon points in sequence with left-click, releasing <Ctrl> prior to the last point. All areas whose label is inside the polygon are set to active. Single object status change: set individual area active/passive in MULTISELECT mode with left-click. File: Read *.ane fie (file type: defined active network objects) to set area(s) active or passive. Enable or disable option 5HDG DGGLWLRQDOO\ accordingly to replace or add active network objects.
See PROGRAM STATUS in the EXTRAS menu for the current number of active and passive areas in the network.
Click right mouse-key to call the context menu in the MULTISELECT MODE which provides further area processing commands.
4-209
THE NETWORK EDITOR
Areas
,QLWLDOL]H set passive network objects of the selected category to active.
,QYHUW: invert status of network objects of the selected object categories (set active network objects to passive and passive network objects to active).
6HW REMHFWV LQ DUHD WR DFWLYH all network objects which are completely inside the selected area are set to active. For zones/global zones, the centroid is valid, for links, both nodes must be inside; lines are not activated as a result. Option: keep or modify current status of those network objects outside the area.
File: set areas to active/passive by opening an *.ane file (UHDG aFWLYH QHWZRUN REMHFWV).
4-210
Areas
THE NETWORK EDITOR
'HOHWH DFWLYH DUHDV

Activate MULTI SELECT mode and AREAS network object type..
Call 'HOHWH DFWLYH DUHDV through DELETE in the EDIT menu or Shortcut <Del> . Click OK to confirm:
Only active areas can be deleted.
4-211
THE NETWORK EDITOR
Areas
6HOHFWLRQ RI QHWZRUN REMHFWV E\ DUHD

$FWLYDWH 0XOWL 6HOHFW PRGH via MULTI SELECT in EDIT mode or Toolbar button.
G
8
The commands for network objects selection via MULTI SELECT are not supported for sublines. Call 6HW REMHFWV LQ DUHD WR DFWLYH via MULTI SELECT in EXTRAS menu - or context sensitive menu with right-click in network display. Select area. If a selection of objects has already been made via Multi Select, the following request appears:
If the answer is No, a new selection takes place and the previous one is discarded. All objects which are completely inside the area are set to active. For zones and global zones, the co-ordinates of the centroid are valid. For turning relations, the 9LD1RGH is valid. A series of areas can be marked one after another.
4-212
Areas
THE NETWORK EDITOR
$UHDV 3X7 H[DPSOH
4-213
THE NETWORK EDITOR
Areas
%XV+ %XV5 Line route length: Running time: Layover time: Cycle time: Services/direction: min. headway: Vehicles required: Zone10 to Zone20: Zone10 to Zone40: Revenue/PassTrip: 18.000 m 53 min 7 min 120 min 60 15 min 120/15 = 8 100 passengers 100 passengers 2 DM
$UHD $UHD
Stops total Stops served Line length VehKm Running time Layover time Service time Operating time Required vehicles Pass. boarding Pass. alighting PassKm Revenue
3 2 12,000 m 120 x 12 km =1,440 km 30.5 min 7 min x 30.5/53 = 4.0 min 120 x 30.5 min = 61 h 120 x 34.5 min = 69 h 8 veh x 61h / (61h + 45h) = 4.6 200 100 100 x 10 km + 100 x 12 km =2,200 km 100 x 2 DM + 100 x 2 DM x 12/18 = 333 DM
4 2 6,000 m 120 x 6 km =720 km 22.5 min 7 min x 22.5/53 = 3.0 min 120 x 22.5 min = 45 h 120 x 25.5 min = 51 h 8 veh x 45h / (61h + 45h) = 3.4 0 100 100 x 6 km = 600 km 100 x 2 DM x 6/18 = 67 DM
4-214
Census Points
THE NETWORK EDITOR
&HQVXV 3RLQWV
Census points serve for data management and display of counted link data, are network objects allocated to a particular link at a particular position. Several census points can be defined per link. A census point is described by the following attributes: Number (max. 9 digits) Type (00..99) Code (Text 8) Name (Text 50) AddValue1 - AddValue5 (Integer) Number of the link the CP has been specified for Position on link (0.0 ... 1.0) FromNodeNr (Position 1.0 = at ToNode of link)
&RPPDQG 6HDUFK 0RGLI\ 'HOHWH 7H[W RQRII 6SHFLI\ FRXUVH 6KLIW WH[W $JJUHJDWH 6SOLW &RS\
6KRUWFXW <F3> <Enter> <Del> <F4> <F5> <F6> <F7> <F8> <F9> X X X X X X X X
4-215
THE NETWORK EDITOR
Census Points
&HQVXV SRLQW DWWULEXWHV

7\SH PrT $WWULEXWH Nr Number (Input) Name (Input) Code (Input) PrT Type (Input) AddVal1 AddValue1 (user-defined) AddVal2 AddValue2 (user-defined) AddVal3 AddValue3 (user-defined) AddVal4 AddValue4 (user-defined) AddVal5 AddValue5 (user-defined) LinkNr (Input) TextShift Text shifted (Input) 'HILQLWLRQ Number of census point. default: max. CPNr+1 range: 1-999999999 Name of census point. default: empty string range: Text50 Code of census point. default: empty string range: Text8, no number as first character Type of census point. default: 0 range: 00 - 99 AddValue1. range: Long Int AddValue2. range: Long Int AddValue3. range: Long Int AddValue4. range: Long Int AddValue5. range: Long Int Number of link. range: 1-999999999 Place census point label at census point (=0) or shift label position (=1). default: 0 range: 0=no, 1=yes
PrT
PrT
PrT
PrT
PrT
PrT
PrT
PrT PrT
4-216
Census Points
THE NETWORK EDITOR
7\SH PrT
$WWULEXWH TextX-Coord Text-X-Coordinate (Input) TextY-Coord Text-Y-Coordinate (Input) X-Coord X-Coordinate (Input) Y-Coord Y-Coordinate (Input) RelPos relative position (Input) FromNodeNr (Input) FromNodeCode (from FromNode) FromNodeName (from FromNode) ToNodeNr (Input) ToNodeCode (from ToNode) ToNodeName (from ToNode)
'HILQLWLRQ X-Coordinate of label. default: from mouse position range: Real Y-Coordinate of label. default: from mouse position range: Real X-Coordinate of census point. default: from mouse position range: Real Y-Coordinate of census point. default: from mouse position range: Real Relative position of census point on link (0.0 ... 1.0). default: 0 range: 0-1 Number of the FromNode of a link. default: selected with mouse range: defined node numbers Code of the FromNode of a link. Name of the FromNode of a link. Number of the ToNode of a link. default: selected with mouse range: defined node numbers Code of the ToNode of a link. Name of the ToNode of a link.
PrT
PrT
PrT
PrT
PrT
PrT PrT PrT
PrT PrT
4-217
THE NETWORK EDITOR
Census Points
,QVHUW FHQVXV SRLQW

Activate INSERT mode. Activate CENSUS POINTS network object type.
G
8
Census points are provided as VISUM add-on. Prerequisite: Activate the Census points add-on under LICENCE in the EXTRAS menu. Select link (direction). Click left on the census point position desired on link. This position can be edited in the dialog box. ,QVHUW FHQVXV SRLQW Enter attributes: Nr, Type, and optionally Name, Code, AddVal 1-5.
Census point position: VISUM enters the marked position under Rel.Pos. (relative position) compared to the complete link length between FromNode (0.0) and ToNode (1.0). Position Text / Columns (AddValues): at Census point (Default: 0.0000) or user-defined (Text-coordinates X and Y).
Census Points
THE NETWORK EDITOR
6HOHFW FHQVXV SRLQW

Activate SINGLE SELECT mode and CENSUS POINTS network object type.
Select census point: Click left on census point or label position. 6HDUFK IRU FHQVXV SRLQW with <F3> or click right for context menu. Select processing command. Call up 0RGLI\ FHQVXV SRLQW with MODIFY in the EDIT menu, or <Enter> shortcut, or Double-click on selected census point.
'HOHWH FHQVXV SRLQW

Activate SINGLE SELECT mode and CENSUS POINTS network object type.
Select census point. Delete census point with Delete in the EDIT menu or Shortcut <Del>.
4-219
THE NETWORK EDITOR
Census Points
(GLW FHQVXV SRLQW

0RGLI\ FHQVXV SRLQW SRVLWLRQ
Activate SINGLE SELECT mode and CENSUS POINTS network object type
Select census point. Define new position for selected census point: either hold down mouse-key while dragging the pointer to new position or modify the Rel.Pos. entry (relative position) in the 0RGLI\ dialog box. Call 6KLIW &HQVXV SRLQW with SPECIFY in the EDIT menu, or Shortcut <F5>. To modify the census point position interactively, activate MODIFY in the EDIT menu, or Shortcut <Enter> or click twice on selected census point.
8 8
0RGLI\ FHQVXV SRLQW ODEHO SRVLWLRQ

Select census point. Modify the position of the census point label interactively: either hold mouse-key down while dragging the label to the desired position, or modify co-ordinates in the dialog box or set option DW FHQVXV SRLQW accordingly. To shift census point label, activate SHIFT TEXT in the EDIT menu, or Shortcut <F6>. To modify census point label position, call MODIFY in the EDIT menu, or Shortcut <Enter> or click twice on selected census point.
8 8
4-220
Census Points
THE NETWORK EDITOR
0RGLI\ FHQVXV SRLQW DWWULEXWHV

Select census point. To modify census point attributes, click MODIFY in the EDIT menu, or Shortcut <Enter> or click twice on selected census point. 0RGLI\ FHQVXV SRLQW The Input attributes can be modified (except Nr).
&HQVXV SRLQW ODEHOV Census point can be displayed with text or with labelled vertical bars according to the settings under GRAPHICS PARAMETERS &HQVXV SRLQWV in the GRAPHICS menu: set text , see &HQVXV 3RLQWV tab (only, if 'UDZ pillars) vertical bars, see &KDUW dialog (only, if 'UDZ pillars). If option DW FHQVXV SRLQW is disabled, VISUM enters the co-ordinates of the current position. They are modified automatically, when the census point label is shifted, and can be modified directly.
4-221
THE NETWORK EDITOR
Census Points
(GLW PXOWLSOH FHQVXV SRLQWV

Activate MULTI SELECT mode and CENSUS POINTS network object type.
'HILQH DFWLYH FHQVXV SRLQWV IRU HGLWLQJ using one or more of the methods below. Active census points are only those census points which meet all current specifications! Filter: define census point filter MultiSelect selection specified in MULTI SELECT mode as rectangle: drag while holding down left mouse button; polygon: while holding down the <Ctrl> key, fix the polygon points one by one by clicking left mouse button. Release <Ctrl> prior to marking the last point. All nodes within the polygon are set to active. AREA : Call the 2EMHFWV ZLWKLQ $UHD 6HW DFWLYH function through
and right-hand mouse-click or MULTISELECT command in the EXTRAS menu and select area. Modify state of single object: set single census points in MULTI mode to active/passive by clicking left mouse button. This can also be used for fine editing of MultiSelect polygons. Census points which are passive because of current filter parameters cannot be set to active!
SELECT
Invert: set all active census points to passive and all passive census points to active. Click the right mouse button to call ,QYHUW. File: set census points to active by reading the following file type(s): filter parameters *.fil, specified active network objects *.ane. If there are no passive census points in the network, the modifications apply to all census points. Census points which are passive due to census points filter or Area settings can be treated as active census points when editing in MULTISELECT mode: Disable the 2QO\ DFWLYH option. Display of current status (number of active or passive census points) via PROGRAM STATUS in the EXTRAS menu.
4-222
Census Points
THE NETWORK EDITOR
0RGLI\ DWWULEXWH IRU PXOWLSOH FHQVXV SRLQWV

To modify an attribute of multiple census points, click MODIFY in the EDIT menu, or Shortcut <Enter>. 'LDORJ ER[ &HQVXV SRLQW DWWULEXWH
Set option: consider only active census points. o consider all census points. Attribute Select census point attribute to be modified and click on button &RQVWDQW enter constant attribute value, e.g. select Type. )DFWRU: multiply current attribute values by factor. $WWULEXWH: adopt values of another attribute. 5RXQG: Enter rounding factor for attribute values. )RUPXOD: indicate formula for transfer and calculation.
4-223
THE NETWORK EDITOR
Census Points
Sequence: modify attribute for multiple census points Set option and select attribute to be edited, Activate button and enter or select value(s), Set $GG option to active/inactive, Confirm with OK, Close FHQVXV SRLQW DWWULEXWHV dialog box with OK
'HOHWH DFWLYH FHQVXV SRLQWV

To 'HOHWH DFWLYH FHQVXV SRLQWV click DELETE in the EDIT menu, or Shortcut <Entf>.
Only active census points can be deleted from the network.
4-224
THE NETWORK EDITOR
2SWLRQV IRU ,QVHUW QHWZRUN REMHFW
8
/LQNV
0HQX (;75$6 237,216 Further options for calculation of length and distance data are provided under NETWORK PARAMETERS in the EXTRAS menu. 2SWLRQV /LQNV WDE
Define for ,QVHUW OLQN: Rounding of PuT running times to 1, 5, 10, 15, 30 or 60 seconds.
4-225
THE NETWORK EDITOR
2SWLRQV &RQQHFWRUV WDE &RQQHFWRUV
Define for ,QVHUW FRQQHFWRU: Speed by transport type (PuT, PrT) and Rounding of conn. time data. 2SWLRQV /LQHV WDE /LQHV
Define for ,QVHUW VXEOLQH: ID per direction, Rounding of PuT running times to 1, 5, 10, 15, 30 or 60 [s] Minimum running time FromStop ToStop for line route construction.
4-226
THE NETWORK EDITOR
2SWLRQV 7LPH IRUPDW WDE 7LPH IRUPDW
Select seconds or minutes for all time data entries without unit. 2SWLRQV 6WDQGDUG WLPHWDEOH WDE 6WDQGDUG WLPHWDEOH
Only regular headway permitted (max. 5 intervals). Define layover time dependent from running time (orig. terminal dest. terminal) or as absolute time period for new sublines.
4-227
THE NETWORK EDITOR
4-228
O-D MATRICES
2' 0$75,&(6
O-D matrices contain travel demand data which is the number of trips desired from origin zone L to destination zone M. A demand matrix refers to a time interval (analysed period) and thus only contains the trips within a given time interval. The time distribution of the trips within a time interval is described by means of a pattern which is taken into account during PuT-assignment. Every demand segment specified for PrT or PuT a single O-D matrix is to be assigned in VISUM.
For detailed modelling of travel demand (Fij-matrices), PTV AG offers the VISEM program system (Activity chain-based Demand Forecasting Model) which also includes the MUULI matrix processor: VISEM can be used to calculate O-D matrices for user groups with homogeneous behaviour (e.g. company employees with or without a car, schoolchildren, students) for specific means of transport using structure data, and compare them to traffic census data. MUULI allows existing matrix data to be processed, and calculations to be made, e.g. based on the gravity approach.
5-1
O-D MATRICES
O-D matrices
2' PDWULFHV
0DWUL[ IRUPDWV

O-D matrices (*.fma) can be saved in the following formats: %LQDU\ IRUPDW memory-efficient format, especially for large matrices. 2IRUPDW: ASCII-format where every origin-destination relation is saved in the form origin zone, destination zone, number of trips. 9IRUPDW: ASCIIformat where trips of Fij-Relations are saved in sequence. 2IRUPDW
Note on the time interval specification: e.g. 13.00 for 1 pm, 23.00 for 11 pm. ([DPSOH
$O * From Till 06.00 22.00 * Factor 1.0 * MeansOfTransport-No. 3 * 3 = Public transport * 4 = Car-PrT * 100 200 180 100 300 200 100 400 170 100 500 60 100 600 120 100 700 150 100 800 200 200 100 170 200 300 190 200 400 140 200 500 110 200 600 160 200 700 120 ......
5-2
O-D matrices
O-D MATRICES
([DPSOH
9IRUPDW
$VR * From Till 6.00 22.00 * Factor 1.00 * * MeansOfTransportNo. 4 * 3 = Public Transport * 4 = Private Transport * Number of Zones 8 100 200 300 *Zone 100 Total = 1080 0 180 200 *Zone 200 Total = 1070 170 0 190 *Zone 300 Total = 1060 190 250 0 *Zone 400 Total = 1090 200 200 180 *Zone 500 Total = 880 150 100 120 *Zone 600 Total = 880 20 180 260 .......
400 170 140 90 0 130 100
500 60 110 130 140 0 10
600 120 160 170 110 30 0
700 150 120 130 110 190 140
800 200 180 100 150 160 170
2SHQ 2' PDWUL[ ILOH
Select file type 2' PDWULFHV via OPEN in the FILE menu. Select or enter file name in dialog box Select O-D matrix. Confirm 2SHQ
'LDORJ ER[ 6HOHFW GHPDQG VHJPHQW Select demand segment the opened O-D matrix is valid for:
5-3
O-D MATRICES
O-D matrices
5HDGLQJ 2' 0DWUL[ GLDORJ
6HW H[LVWLQJ 2' 0DWUL[ WR ]HUR Possibly existing O-D matrix is deleted. o The O-D matrix is added to an existing matrix. )DFWRU IRU QHZ PDWUL[ The matrix values to be read from file are multiplied by factor. 5DQGRP 5RXQG random rounding up or down for matrices with real values. o mathematical rounding up or down for matrices with real values. 2' 0DWUL[ GLDORJ
Number of relevant trips for assignment; these include all trips except internal transport demand. Number of internal trips. Rounding difference for reading real matrices.
Zone-internal traffic (e.g. from =RQH to =RQH ) is read, but is not taken into account for assignment.
5-4
O-D matrices
O-D MATRICES
9,680 PHVVDJHV
If the time interval the matrix is valid for differs from the time interval specified for the temporal distribution of PuT passengers: VISUM will assume homogeneous distribution, the given pattern will be ignored.
An O-D matrix can also be read via PROCEDURES in the CALCULATE menu: Page 2SHUDWLRQV 2SHUDWLRQ Select "ODMatrixRead", Select demand segment via '6HJ button, Select file name and directory via %URZVH button, Click ([HFXWH button.
(GLW PDWUL[

O-D matrices can be edited in VISUM in the following way: Create a new matrix or edit an existing matrix by entering a constant value into the matrix cells (Page &RQVWDQW). Initialize a matrix by entering value = 0 into the matrix cells (Page &RQVWDQW). Edit an existing matrix by projecting Fij-relations by factor (Page )DFWRU). Specify a time interval for the matrix (Page 7LPH ,QWHUYDO). For PuT demand matrices: Create/Modify pattern of temporal demand distribution (Page Pattern is only provided for PuT demand matrices).
5-5
O-D MATRICES
O-D matrices
O-D MATRIX in CALCULATE PHQX 'LDORJ 6HOHFW GHPDQG VHJPHQW Select the demand segment the matrix is to be created or edited for.
OK
0RGLI\ 2' PDWUL[ GHPDQG VHJPHQW GLDORJ Output of matrix sum and relevant time interval For private transport demand segments only Page )DFWRU, &RQVWDQW and 7LPH ,QWHUYDO are provided, for public transport demand segments also Page 3DWWHUQ.
5-6
O-D matrices
O-D MATRICES
(GLW 2' 0DWUL[ 3DJH )DFWRU )DFWRU Project Fij-relations by factor. )URP =RQH WR =RQH Select the matrix cells to be edited: 1 O-D relation: )URP ]RQH 7R ]RQH = Nr of origin zone = Nr of destinat. zone = Nr of origin zone = empty field = empty field = Nr of destinat. zone = empty field = empty field
From one zone )URP ]RQH 7R ]RQH to all zones: From all zones )URP ]RQH 7R ]RQH to one zone: entire matrix: )DFWRU )URP ]RQH 7R ]RQH
Enter a projection factor for the selected O-D relations )URP =RQH 7R=RQH. 5DQGRP 5RXQG The matrix elements of an O-D matrix must always contain absolute values. To round up real values, two procedures can be selected: o 5DQGRP 5RXQG: mathematical rounding up or down of real numbers or 5DQGRP 5RXQG: random rounding up or down of real numbers. Show 6KRZ EXWWRQ No matrix modification, but output of the number of trips for currently selected relation(s) from the current matrix. Apply $SSO\ EXWWRQ The selected matrix elements are projected with the entered factor. The new total number of trips is displayed in the "Sum" result field.
([DPSOH With a factor of , the matrix value becomes , and thus would always be rounded down to 0 without the 5DQGRP 5RXQG option. If the 5DQGRP 5RXQG option is active, VISUM rounds up to with a 10% chance and rounds down to with a 90% chance.
5-7
O-D MATRICES
O-D matrices
&RQVWDQW
(GLW 2' 0DWUL[ 3DJH &RQVWDQW Enter constant value or enter 0 to initialize current values for the currently selected Fij-relations.
&RQVWDQW YDOXH Specify the constant value which is to be entered for the selected relations in the matrix. $SSO\ EXWWRQ The selected matrix cells are assigned the constant value, original matrix data are replaced. The new total demand is calculated and displayed in the "Sum" result field.
5-8
O-D matrices
O-D MATRICES
(GLW 2' 0DWUL[ 3DJH 7LPH ,QWHUYDO 7LPH ,QWHUYDO
Define time interval for O-D matrix. Examples: 13:00 for 1pm and 23:00 for 11pm.
Modifying the time interval has no effect on the values of the matrix elements. If, for example, the time interval is reduced, the values must be adjusted using a projection factor < 1 ()DFWRU button). The specified PrT-capacity of the network objects in the network file must be adapted to the assignment time interval.
5-9
O-D MATRICES
O-D matrices
(GLW 2' 0DWUL[ 3DJH 3DWWHUQ 3DWWHUQ Generate a new or modify an existing pattern of temporal distribution of public transport demand.
The 3DWWHUQ Page is only provided for PuT matrices. See Chapter 5.2 for editing a PuT pattern.
Save O-D matrix. After changes to the assignment time interval a warning will be displayed on screen:
5-10
O-D matrices
O-D MATRICES
6DYH PDWUL[

O-D matrices can be saved as total demand matrices or partial demand matrices: IORZ EXQGOH PDWUL[ with regard to the current flow bundle or WUDIILF W\SH PDWUL[ with regard to the current traffic type filter. in *.fma files in binary format or in two ASCII-formats.
6HOHFW ILOH W\SH2' PDWULFHVYLD 6$9(LQ WKH ),/(PHQX 6HOHFW GHPDQG VHJPHQW GLDORJ Select the demand segment the matrix is valid for, click OK.
6DYLQJ 2' PDWUL[ GHPDQG VHJPHQW GLDORJ
5-11
O-D MATRICES
O-D matrices
7LPH )URP 7LPH 7LOO Enter time interval relevant to matrix. )DFWRU The projection factor for multiplying the matrix values to be saved to file. The specified factor does not become active during saving, but is only saved in the file header. This factor is not suggested in a dialog box until the matrix is loaded, when it can still be modified. Matrix values are multiplied with the entered/modified factor when the O-D matrix data are read from file. 5DQGRP 5RXQG o 5DQGRP 5RXQG: mathematical rounding up or down 5DQGRP 5RXQG: random rounding up or down (default setting). 0DWUL[ Select the matrix type to be saved: O-D matrix (default). flow bundle matrix (if flow bundle has been activated via )ORZ %XQGOH in the GRAPHICS menu). traffic type matrix (if relation filter has been activated via FILTERS5HODWLRQV in the EXTRAS menu or via the 5HODWLRQV filter symbol in the icon bar).
)RUPDW ELQDU\ memory-efficient format, especially for large matrices. 2IRUPDW: ASCII-format in which every O-D relation is saved like origin zone, dest. zone, number of trips 9IRUPDW: ASCII with trips of Fij-relations written in sequence.
O-D matrices can also be saved via PROCEDURES in the CALCULATE menu: Page 2SHUDWLRQV, 2SHUDWLRQ Select "O-DMatrixSave Select demand segment Specify file name and directory via %URZVH button Click ([HFXWH button.
5-12
Patterns of temporal PuT demand distribution
O-D MATRICES
3DWWHUQV RI WHPSRUDO 3X7 GHPDQG GLVWULEXWLRQ
The time distribution of public transport demand within the analysed time interval is described by patterns which are taken into account during PuT-assignment. For different time sub-intervals within the analysed time interval, the pattern determines the percentage of trips wishing to leave the traffic zone L (GLW SDWWHUQV VISUM assumes as a standard an equal distribution of demand for the given time interval, i.e. the following default settings: assumed equal distribution between all origin and destination zones (100%). time interval: 0:00-24:00.
This pattern can be edited in the following way:
2' 0$75,; LQ &$/&8/$7(PHQX 6HOHFW GHPDQG VHJPHQW GLDORJ Select a PuT demand segment. 0RGLI\ 2' PDWUL[ GLDORJ Select Page 3DWWHUQ 3DJH 3DWWHUQV
5-13
O-D MATRICES
Modify
0RGLI\ SDWWHUQ GLDORJ
Insert
Enter Pattern name (optionally) Insert (or Modify/Delete) time sub-intervals.
,QVHUW D QHZ WLPH VXELQWHUYDO
Specify the end of the first sub-interval and the percentage of demand for this interval.
For any following sub-interval enter the cumulative percentage of demand. VISUM calculates the remaining share.
5-14
O-D MATRICES
OK
Modify Delete
0RGLI\ 'LVWULEXWLRQ RI VHOHFWHG SDWWHUQ 'HOHWH 3DWWHUQ RU VSHFLILHG WLPH VXELQWHUYDO VISUM calculates the resulting sub-interval and the cumulative demand. If the time range of the matrix is oldred, VISUM displays a warning message:
The change results in a constant assignment of all patterns; the assignment to the zones remains unchanged.
)LOH PDQDJHPHQW PuT patterns are saved as ASCII files *.fga: Load data via FILE - OPEN: Temporal demand distribution Save file via FILE - SAVE: 7HPSRUDO GHPDQG GLVWULEXWLRQ

O-D MATRICES
$ * Time interval * Tfrom Ttill 07.00 09.00 * Pattern intervals $ 1 07.00 07.30 08.00 08.30 09.00 -1 1 0 30 40 20 10 -1 $ * Allocation of pattern Nr to zones 100 1 200 1 * ....etc. $ (GLW PXOWLSOH SDWWHUQV DQG DVVLJQ WKHP WR ]RQHV ZLWK DQ H[WHUQDO WH[W HGLWRU The editing functions ,QVHUW and 'HOHWH for patterns (see above: dialog box "3DWWHUQV RI WHPSRUDO GHPDQG GLVWULEXWLRQ") and the allocation of patterns to zones are not included in VISUM 7.00. It is nevertheless possible to create patterns and patternzone allocations in the relevant *.FGA file using an external text editor. In this way multiple patterns can be opened and edited in VISUM. See the example for details: $ * TFrom TTill 07.00 09.00 $ 1 07.00 07.30 08.00 08.30 09.00 -1 1 0 30 40 20 10 -1 2 07.00 07.30 08.30 09.00 -2 2 0 10 80 10 -2 * ....etc. $ 100 1 200 2 * ....etc. $
5-16
Updating O-D matrix using VStromFuzzy
O-D MATRICES
8SGDWLQJ 2' PDWUL[ XVLQJ 96WURP)X]]\
Matrix correction methods are used to adjust a given O-D matrix in such a way that the result of the assignment closely matches the latest figures link volumes or origin/destinaton travel demand that were actually counted (see schematic of procedure): An empirically by surveys - gained O-D matrix data is no longer valid and needs to be updated without another complete survey to be performed for origins and destinations of trips. The update is to be based on census data. A matrix generated from the transport network model is to be calibrated, therefore counted volume data are to be used. A matrix generated from incomplete or not reliable data is to be improved by more comprehensive/reliable volume data couted simultaneously.
VStromFuzzy will solve this probelm for Public as well as for Private Transport. The flow of information always follows the given order:
O ld m atrix N ew counts (A ddV al)
Counted data may be: link volumes, origin/destination travel demand by zone, any combination of link and zone data.
V Strom /Fuzzy
N ew M atrix
Note: For public transport origin and destination demand determination boarding/alighting volumes may be used only, if transfers are not contained in the data.
Compared to other procedures the outstanding features of VStromFuzzy are: Link volumes and orig./dest. travel demand can be combined for correction purposes. Counted data need not to be available for all links and/or zones. The statistical uncertainty of the count figures can be modelled explicitly by interpreting the figures as Fuzzy sets of input data.
O-D MATRICES
%DVLF SULQFLSOHV

For some 20 years now, primarily in English-speaking countries, so-called matrix correction (or matrix update) techniques have been used to produce a current travel demand matrix from an earlier travel demand matrix (base matrix) using current traffic count values. Based on research by VAN ZUYLEN / WILLUMSEN [3, 4], BOSSERHOFF [5] and ROSINOWSKI [6] which focuses on matrices for private transport, PTV has extended the application of these techniques to public transport. Starting point of the classic approach is the travel demand WLM for o-d pairs. Travel demand is usually described as a matrix, but for our purposes a vector representation containing all non-zero o-d trips is more suitable:
t12 t13 t1n t1n t 2n t 21 t 3n = t 23 0 t 2n t 31
0 t12 t 21 0 t 31 t 32 t n1 t n2
L L t 0 L M M M O M L t
t13
23 n3
M M M
This vector describes the travel demand of an earlier state. Vector value WN describes th the number of trips for the k o-d pair with non-zero trips. Index p gives the total number of non-zero o-d pairs Considering the current travel demand, it is assumed that no o-d specific information is available but only traffic counts. For public transport such traffic counts may be available either as counts of boarding and alighting passengers at transit stops or as link counts. In case of boarding/alighting counts it is important to note, that only initial boardings at the origin stops and final alightings at the destination stop may be employed to update a matrix, i.e. the counts must not include transferring passengers. The following vector Y denotes traffic counts at m locations:
v T = (v1 v 2 v3
vl
vm )
where: m ... number of traffic count locations
The trips of any o-d pair contribute a certain share to each traffic count. In case of boarding and alighting passengers the marginal sums of the demand matrix are known. In case of link counts the counted volumes correspond to the sum of all o-d trips travelling on this link. In general there is a linear relation between the demand on the o-d pairs and the traffic counts:
O-D MATRICES
a11 L a1p M O M t= A t= v am1 L amp $ is called the share-matrix. The number of columns of this share-matrix refers to the number of non-zero o-d pairs, the number of rows corresponds to the number of traffic counts. Each element alk of this share-matrix expresses the share of trips of one o-d pair k which uses link l. The share-matrix $ has an exceptionally regular form in case of boarding and alighting counts. The following example shows the share-matrix $ for a network with 3 zones (n = 3) and 6 counts (m = 6), i.e. 3 boarding and 3 alighting counts:
1 0 0 0 1 0 1 0 0 0 0 t12 board1 1 1 0 0 t13 board2 0 0 1 1 t 21 board3 = 1 0 1 0 t 23 alight1 0 0 0 1 t 31 alight 2 0 1 0 0 t 32 alight 3
0 0 0 0 1
For boarding and alighting counts the share-matrix $ does not depend on the transit supply, i.e. the line routes and timetables. In case of link counts, however, the sharematrix $ needs to consider the route choice of passengers which is affected by the transit supply. To create a share-matrix for link counts one can assign any demand matrix, e.g. the outdated base matrix, onto the current network. It is also possible to combine boarding/alighting counts and link counts. The chief problem of matrix correction methods results from the fact that typically m << n2 , so that the new matrix is underconstrained by the counts. The consequence of this is an extremely large number of combinations for the o-d values (WLM) matching with the counts. In order to select the best of all possible matrices an evaluation function q is applied as objective function:
maximize q( t ) so that A t = v
5-19
O-D MATRICES
Usually a combination of entropy and weighting with the structure of the outdated matrix serves as evaluation function. Maximizing q in the following evaluation function favours matrices which differ least from the base matrix: q( t ) = tk ln
k =1 p
tk tk t
k
where:
tk ...
tk ...
travel demand on one o-d pair in the base matrix travel demand on one o-d pair in the new matrix
7KH IX]]\ DSSURDFK The formulation of the matrix-correction-problem, as it is described above, has one serious weakness: the vector Y of traffic counts is assumed to be a known input value without any uncertainty. As a result the traffic counts obtain an inappropriate weight since any count only provides figures, that represent a snapshot situation which are subject to considerable sampling error. For this reason, PTV decided to employ an approach developed by ROSINOWSKI [6] who models the counts as imprecise values based on Fuzzy Sets theory. If one knows, for example, that the number of alighting passengers in an area fluctuates by up to 10 % on a day-to-day basis, but in other areas by up to 20 %, then this is represented by appropriate bandwidths. To consider this in the matrix-correction-problem the exact count values v s with varying bandwidths: are replaced by Fuzzy Sets ~
maximize q( t ) such that A t = ~ v
Compared to simple intervals, representing counts as Fuzzy Sets allows to favour count values close to the mean value. Values which are closer to the bandwidth border are also accepted, if the decrease in the fuzzy membership function is more than offset by the increase in the entropy function. Unfortunately in the general case fuzzy membership functions do not have the analytic properties (continuous, differentiable) that are required for an efficient solution algorithm. The compromise taken in this approach resembles a straightforward representation of counts as intervals with upper and lower bounds. However, the entropy function is extended to cover also the slack variables introduced by the inequality constraints. Just like the outdated matrix values are used as weights for the o-d relations, the fuzzy bandwidths are used as weights for the slack variables, i.e. solutions are preferred in which the counts are matched exactly.
5-20
O-D MATRICES
Hence the maximization problem becomes:

maximize q( W ) + q( V ) + q( V )
such that $ W + V = Y $W V = Y
V V
where:
q( V ) = sl ln
l =1 m
sl sl s
l
q( V) = sl ln
l =1
sl sl l s maximum/minimum of Fuzzy Set slack variables upper bandwidth for traffic count lower bandwidth for traffic count
v, v ... V V ... = Y Y ... V = Y Y ... V
Incorporating the slack variables V V into the weighted entropy maximization gives preference to matrices which achieve A t= v within the bandwidth as good as possible. Thus the introduction of Fuzzy Sets expands the solution space and produces generally better values for the evaluation function q which maximizes entropy. The new formulation of the problem is structurally identical to the original formulation of the problem with exact constraints. The non-linear maximization problem with equality constraints is solved by the Lagrange multiplier method, solving for zeros in the (non-linear) first partial derivatives using Newtons method. By exploiting the symmetry in the structure of the constraints the computational effort can be reduced to little more than in the original (exact) problem. ([DPSOH IX]]\ VHW A fuzzy set in the normal case is characterised as a set of possible values (the data set), and a membership function with values ranging between 0 and 1, indicating "to what extent an element of the carrier set is considered to be included in the fuzzy set". If the membership function is 0, the element is not included in the fuzzy set. With a value of 1, the element is "fully" included in the set, with values in-between expressing the quality of the approximation. If, for example, the value "approximately 4" is to be expressed as a fuzzy set, the carrier set could include the interval [3.5] and the membership function of the value 0 would increase to a maximum of 4 at the limits of the interval.
O-D MATRICES
Membership function
0 3 4 5
In order to make the modelling of the bandwidth in VStromFuzzy more manageable, it is assumed for practical purposes that the membership function has a specific shape: from value 1, which is assumed to be the actual counted value, it drops symmetrically on both sides to produce a triangle defined by the followed values:
Membership function
0 z- *s z z+ *s
z s
= the actual counted value at which the membership function reaches its maximum. = the deviation from the counted value at which the membership function drops to 0. = a specified scaling factor ( > 0 )
Values z, s and are the input data for VStromFuzzy (cf. section on VStromFuzzy operation Ch. 5.3.3): ] and V are given separately for each counted value (link volume, O-D traffic), whereas is a global parameter for the procedure.
5-22
O-D MATRICES
3UHSDULQJ GDWD IRU PDWUL[ FRUUHFWLRQ
,QLWLDO VWHS Load network or a version file with the service valid at the time the count was made. Load "old" O-D matrix.
3UHSDULQJ GDWD IRU PDWUL[ FRUUHFWLRQ XVLQJ FRXQWHG OLQN YDOXHV
5HDG FRXQWHG YDOXH ] DV /LQN$GG9DOXH FILE menu - OPEN: $GG9DOXHV OLQNV If counted values are not available for all links, those links with valid counted values must be active. This can be done as follows: 0XOWL 6HOHFW mode Network object type /LQNV For all links Edit function 0RGLI\: $GG9DOXH Load counted values in LinkAddValue1. Set link filter and enter "AddValue1 from 0 to <leave empty> as filter criterion.
,QVHUW EDQGZLGWKV V LQ /LQN$GG9DOXH RU $GG9DOXH Empirically obtained bandwidths (from mutliple counts of the link volume): Prepare AddValue file FILE menu OPEN: $GG9DOXHV OLQNV Make sure that V indicates at which deviation from ] the membership function drops to the value 0; V in this case is still scaled with the $OSKD /HYHO procedure parameter, which by default should be set to 1. Bandwidths as a fixed percentage (e.g. 5%): 0XOWL 6HOHFW mode Network object type /LQNV For all links Edit function 0RGLI\: AddValue2 = AddVal1 x 0.05
CALCULATE menu PROCEDURES Carry out an assignment of the "old" O-D matrix for the current service. The link volumes obtained in the process form the basis for the flow matrix calculated by VStromFuzzy.
5-23
O-D MATRICES
The steps described above have no influence on the assignment result. The assignment can thus be calculated beforehand. The only thing that is important is that the assignment result has already been loaded.
3UHSDULQJ GDWD IRU PDWUL[ FRUUHFWLRQ XVLQJ FRXQWHG RULJLQGHVWLQDWLRQ WUDIILF YROXPHV IRU HDFK ]RQH
G
8
,QLWLDO VWHS If you intend to use PuT stop-related boarding/alighting figures and have not yet defined any zones, begin by creating a zone for each stop. In this case, to simplify the process, use the same numbers for zones and stops. 2SHQ FRXQWHG YDOXHV ] DV =RQH$GG9DOXHV FILE menu -OPEN: $GG9DOXHV ]RQHV Open origin traffic as $GG9DOXH and destination traffic as $GG9DOXH If counted values are not available for all zones in the network, those zones with valid counted values must be active. This can be done as follows: 0XOWL 6HOHFW mode Network object type =RQHV For all zones Edit function 0RGLI\: $GG9DOXH $GG9DOXH and 0RGLI\:
Open counted values in ZoneAddValue1 and ZoneAddValue2. Set zone filter and enter "from 0 to <leave empty> as filter criterion for AddValue1 and AddValue2.
6HW FRPPRQ EDQGZLGWKV V IRU RULJLQ DQG GHVWLQDWLRQ WUDIILF LQ =RQH$GG9DOXH Empirically obtained bandwidths (from multiple counts in the same zone): Prepare AddValue file FILE menu -OPEN: $GG9DOXHV =RQHV
Make sure that s indicates at which deviation from z the membership function drops to the value 0; s in this case is still scaled with the Alpha Level procedure parameter, which by default should be set to 1.
5-24
O-D MATRICES
Bandwidths as a fixed percentage (e.g. 5%): 0XOWL 6HOHFW mode Network object type =RQHV For all zones Edit function 0RGLI\:
AddVal 3 = AddVal 1 + AddVal 2 0 .05 2
Preparing data for matrix correction using link volumes DQG counted origin/destination traffic volumes for each zone: Perform both of the above procedures LQ VXFFHVVLRQ
96WURP)X]]\ RSHUDWLRQ
&$/&8/$7(PHQX 0$75,;&255(&7,2196WURP)X]]\ 'LDORJ 96WURP)X]]\
5-25
O-D MATRICES
Operate 96WURP)X]]\ via settings in the dialog boxes Input (counted values), Parameters (process control) and Output (result matrix) use buttons to open and save all settings, click &DOFXODWH button to start matrix correction process.
Files generated using 96WURP)X]]\ for protocols, settings, flow matrices and O-D matrices are not integrated into VISUM file management (see FILE menu DIRECTORIES. When saving the above files, therefore, the correct path must be entered, including the file name extension.
0RGLI\LQJ SDUDPHWHUV DQG VHWWLQJV
&$/&8/$7(PHQX 0$75,;&255(&7,21 96WURP)X]]\ 'LDORJ 96WURP)X]]\ ,QSXW WDE
,QSXW
5-26
O-D MATRICES
'HPDQG VHJPHQW Select demand segment from lists box. 2ULJLQ GHVWLQDWLRQ WUDIILF XVH FRXQWHG RULJGHVW WUDIILF DV D EDVLV: use ZoneAddValues. When specifying the origin /destination traffic, PuT boarding/alighting figures may only be used if they do not include transfers. RQO\ DFWLYH ]RQHV: consider active zones only if counted values are not available for all zones, and the zone filter was applied accordingly beforehand. In the four drop-down list boxes, select which ZoneAddValues contain origin /destination traffic ] and which bandwidths V (in the example above, origin traffic in $GG9DOXH, destination traffic in $GG9DOXH and common bandwidths in $GG9DOXH). /LQN YROXPHV XVH FRXQWHG YROXPHV DV D EDVLV: use LinkAddValues. 2QO\ DFWLYH OLQNV: consider active links only if counted values are not available for all links, and the link filter was applied accordingly beforehand.
In the two drop-down list boxes, select which LinkAddValues contain counted values ] and which bandwidths V (in the example above, volumes in $GG9DOXH and bandwidths in $GG9DOXH)
The notation "+/-" between the drop-down list boxes is an abbreviation; the precise meaning of AddValues can be found in the figure at the end of Ch. 5.3.1, on basic principles, in conjunction with the $OSKD /HYHO procedure parameter.
5-27
O-D MATRICES
'LDORJ ER[ 96WURP)X]]\ 3DUDPHWHUV WDE 3DUDPHWHUV
3URWRFRO Select degree of protocol detail with "Level". A higher /HYHO value represents more detailed program output data. Protocol output is deactivated with "Aus (Off). It is recommended that the precise directory path and filename be entered, including file name extension. 3URFHGXUH SDUDPHWHUV A default setting exists for all parameters, which should not be changed by the novice user: &DQFHO LI FKDQJH The calculation is cancelled if the O-D matrix has not changed from one iteration to the next in any trip relation by more than the specified number of trips. 1R RI LWHUDWLRQV the calculation stops when the specified number of iterations has been reached.
5-28
O-D MATRICES
(VWLPDWHG QR RI WULSV: the number of required iterations can be reduced if an accurate approximation of the number of trips has been made for the new matrix. The default setting for this is the number of trips of the "old" matrix (i.e. the PuT O-D matrix which is opened when the procedure is launched). 0D[ FRUUHFW IDFWRU: the correction factor limits any change in a trip relation from the "old" matrix to the new one to the factor e . This applies to the default setting (20) only in the event that the procedure can find no solution within the specified counted values and becomes numerically unstable. $OSKD /HYHO: this factor is used to scale the bandwidth settings entered in the "Input" tab (see description at the end of Ch. 5.3.1). ([FOXGH RG UHODWLRQV ZLWKRXW FRXQW GDWD If link volumes are used and none of the routes of an o-d relation uses any of the counted links, data for matrix updating is missing for this o-d relation. Enable the check box for unmodified entry of the given o-d data in the new matrix. Disable the check box for projection of given o-d data according to mean changes to other o-d relations.
The impact of this option: If e.g. counts regard only a corridor within an extensive network, as only those corridor-using o-d relations are to be updated, it is recommended to set only the links of the corridor to the active state and to enable the check box. If only some individual o-d relations of lower priority do not use any of the counted links, these should be updated according to the general data changes -> disable check box. )ORZ PDWUL[ The flow matrix options influence how the route information from the previous assignment is to be used for updating the matrix: If only one calculation run has been performed, the setting UHFDOFXODWH is recommended. If several calculation runs are to be performed on the same "old" matrix, using different counted values (unchanged set of links or zones) and/or procedure parameters, however, it is recommended for the first run that the matrix be recalculated and saved ( UHFDOFXODWH DQG VDYH DV), and for all subsequent runs that the saved matrix be reloaded ( ORDG IURP). This can result in a significant reduction in the amount of computing time required. It is also recommended that the precise directory path and filename be entered, including file name extension.
5-29
O-D MATRICES
Using the old flow matrix saves computing time, but is a dangerous source of error, because the program is often unable to identify an unsuitable flow matrix! Be absolutely certain that the following applies: The original matrix is the same as the run in which the flow matrix was saved, or has at least the same trip relations with the number of trips > 0. The links/ zones are identical. 'LDORJ ER[ 96WURP)X]]\ 2XWSXW WDE
2XWSXW
6DYLQJ UHVXOWV 5HSODFH FXUUHQW 2' PDWUL[ the "old" matrix, which must be loaded when the procedure is launched, is replaced by the results of the calculation. The "new" matrix then can be used for an assignment. 6DYH DV filenames for the new O-D matrix, which are saved in the output format $O.
It is recommended that the precise directory path and filename be entered, including file name extension. To reformat the matrix file, load matrix via FILE menu -OPEN:2' PDWUL[ and save in another format. 7URXEOHVKRRWLQJ LQIRUPDWLRQ Diagnostic reports can be accessed in this section to identify error sources in the event that VStromFuzzy is unable to solve the problem due to contradicting counted values.
G
5-30
The content of the protocol files in the above implementation is oriented very much to the needs of the developer. More user-friendly content will be available in a later version.
O-D MATRICES
3HUIRUPLQJ PDWUL[ FRUUHFWLRQ
8 8
&$/&8/$7( 0$75,;&255(&7,21 96WURP)X]]\ 'LDORJ ER[ 96WURP)X]]\ &DOFXODWH button to start the calculation. 'LVSOD\ 1HZ PDWUL[ LV EHLQJ FDOFXODWHG The progress indicator displays information on the current status.
When the calculation has been completed, if there are no errors, the new matrix will be saved under the specified filename or placed in VISUM as the current O-D matrix. If VStromFuzzy is unable to find a solution with the counted values provided, a message appears: In this case, check the AddValues on which the calculation is based for entry errors or increase the bandwidth. If you cannot find an error, select 7URXEOHVKRRWLQJ LQIRUPDWLRQ in the third (output) tab and contact PTV for an interpretation (provided the protocol output has not yet been formatted for the user).
Change parameters for another calculation run and either calculate new matrix correction or close dialog box.
2SHQLQJ DQG VDYLQJ 76WURP)X]]\ VHWWLQJV
&$/&8/$7(PHQX 0$75,;&255(&7,21 96WURP)X]]\ 'LDORJ ER[ 96WURP)X]]\ 2SHQ VHWWLQJV DQG 6DYH VHWWLQJV EXWWRQV Save or open VSTROMFuzzy settings of all three tabs.
5-31
O-D MATRICES
&DOFXODWLRQ H[DPSOH

A calculation example is used to illustrate the matrix correction procedure. A PuT service is defined in the very simple network with four zones shown here. The volume bars show the assignment result for the following matrix, from which we can assume that they were obtained a long time ago by means of a passenger survey:
$VR * PTV * Time interval 0.00 24.00 * Factor 1 * * Mode of transport No 3 * 3 Mode of transport PuT * 4 Mode of transport PrT * No. of zones 4 1 2 3 *Zone 1 Total = 0 100 100 *Zone 2 Total = 100 0 100 *Zone 3 Total = 100 100 0 *Zone 4 Total = 100 100 100
4 300 100 300 100 300 100 300 0
Counts have since been completed on all links of the network, and the following volumes obtained:
5-32
O-D MATRICES
The counted values for this example are based on the assumption that the O-D matrix has since changed as follows:
$V * PTV * Time interval 0.00 24.00 * Factor 1 * * Mode of transport No. 3 * 3 Mode of transport PuT * 4 Mode of transport PrT * No. of zones 4 1 2 3 *Zone 1 Total = 0 150 100 *Zone 2 Total = 150 0 100 *Zone 3 Total = 100 100 0 *Zone 4 Total = 100 80 100
4 350 100 330 80 300 100 280 0
The counted values from the figure are loaded into VISUM LinkAddValues. Additionally, for each individual counted value or collectively, a random sample fuzzy value can be added, i.e. a bandwidth, within which the counted values actually fluctuate from one survey date to another. This fuzzy value can be accepted as is or obtained empirically by counting the same o-d relations on different dates. VStromFuzzy now calculates a new matrix, which on the one hand exhibits to a very high degree similar ratios between the number of trips in the individual O-D relations as in the old matrix (by maximizing the weighted entropy), and on the other hand, during assignment matches the counted values from the new survey withinthe specified bandwidth. In the above example VStromFuzzy, with a random sample accuracy of 5%, calculates the following matrix, which matches the assumed "ideal solution" very well.
$VN 4 * * * * * 1: 2: 3: 4: 1 346 346 0 331 148 298 99 281 99 2 331 148 0 100 83 3 298 99 100 0 99 4 281 99 83 99 0
* 1256
5-33
O-D MATRICES
Projecting PrT route volumes
3URMHFWLQJ 3U7 URXWH YROXPHV
The "Routes Projection" command adjusts the O-D matrix of a PrT-transport system to the counted data of particular links. In this process, all relations Fij for a PrTtransport system are projected in such a way that the link volume corresponds to the census data (AddValue). The relations used in this process are the result of an assignment in which all used routes are saved along with their volumes.
3UHUHTXLVLWHV Assignment result (routes which use the link) and either LinkAddValue or random sample factor. Census data must be available as Link-AddValue1..3.
5-34
O-D MATRICES
3URFHGXUH &$/&8/$7(PHQX 0$75,;&255(&7,21 5287(6352-(&7,21. 5RXWHV 3URMHFWLRQ GLDORJ '6HJB3U7 select PrT demand segment &HQVXV GDWD IURP use counted data which are available as Link-AddValue1, AddValue2 or AddValue3. Select link (mouse-clicks on nodes):
! (Opposite direction button): Select opposite direction of link.
VISUM will display /LQN 1U )URP1RGH YROXPH'6HJB3U7 DQG FHQVXV YDOXH of the selected link as well as the )DFWRU calculated by VISUM automatically (quotient from census value and current link volume of the PrT-DSeg):
e.g. Factor = 1000 : 750 = 1.333.
This projection factor can either be adopted as a suggestion or be replaced by ones own entry. The factor is calculated each time a new link is selected. ([HFXWH button: Recalculates O-D matrix with the projection factor determined for the selected link; recalculation for all relations Fij which use the selected link.
5-35
O-D MATRICES
The current assignment result is not deleted. Instead, the previous values are replaced by the projected values. Both route volume and O-D matrix are adjusted. Rounding errors (e.g. 2 * 1.3 trips = 2.6 trips, this rounded up to 3 trips) can result in a mathematical deviation from the rounded result. New projection for other relations Fij by selecting further link or Exit the command with &ORVH button. After exiting command, save the projection as a version or O-D matrix. Graphic display of all relations Fij which use the counted or projected link as link flow bundle via FLOW BUNDLE in the GRAPHICS menu.
5-36
Calibrating a PrT O-D matrix
O-D MATRICES
&DOLEUDWLQJ D 3U7 2' PDWUL[
The &DOL add-on module offers a calibration function which generates projection factors for origin and destination sums of a PrT O-D matrix based on available assignment results. Using a balancing procedure the matrix is then projected to the sum values.
3UHUHTXLVLWH IRU 2' PDWUL[ FDOLEUDWLRQ Census data must be available as Link-AddValue1, 2 or 3. Assignment result. The available O-D matrix must be an optimally generated matrix which may have resulted from previous censuses or calculations. Its inner structure must correctly represent the impedance situation in the network. Representative cross-sections can be used to compensate for significant changes (e.g. closing of a company with a large work force or the construction of a new residential area). Completely new traffic flows cannot be generated because Fjj relations which were 0 in the matrix remain 0 after projection. With regard to route selection, the network should be calibrated as accurately as possible.
5-37
O-D MATRICES
PROCEDURES,n theCALCULATE PHQX 6HH &KDSWHU IRU 352&('85( RSHUDWLRQV DQG SDUDPHWHU VHWWLQJ 3URFHGXUH GLDORJ 2SHUDWLRQV SDJH
3DUDPHWHUV
Enable $FWLYH check box. Select RSHUDWLRQ: "O-DMatrixCalibr. '6HJ button: Select one of the demand segments. 3DUDPHWHUV button: specify parameters. 3DUDPHWHUV 0DWUL[ FDOLEUDWLRQ /RKVH GLDORJ Census data either from AddVal1, AddVal2 or AddVal3 The parameters "Max. No. of Iterations and "Threshold of precision are described below in the context of the detailed description of the &DOLEUDWLRQ SURFHGXUH DFFRUGLQJ WR /RKVH.
Execute
3URFHGXUH GLDORJ 2SHUDWLRQV Start calculation. Save calibrated matrix with 2' PDWULFHV via SAVE in the FILE menu. Execute assignment of the calibrated matrix to the network.
5-38
O-D MATRICES
*HQHUDO SULQFLSOH RI WKH FDOFXODWLRQ SURFHGXUH The projection of the matrix corresponds to the "Increase factor model" with justification, known in traffic planning. By comparing the calculated volume with the census data, the counted cross sections supply information about "adjustment factors" which need to be taken into account. Here it has to be taken into account that a origin/destination relation can traverse several counted cross sections, that is, it might be influenced by several adjustment factors. The calculation process has two stages: Determining the adjustment factors: First, the calibration command generates an adjustment factor NL for every counted value ]L. These apply to all relevant flow bundles. This results in modification potentials for all relevant origin and destination traffic. Since the adjustment factors belonging to a zone might have to be calculated from different counted value adjustment factors ]LQ, these factors must be averaged and balanced. In this way, adjustment factors for origin and destination traffic are generated for those origins (rows) and destinations (columns) which were found by flow bundles. Rows and columns which were not found by flow bundles are assigned a mean adjustment factor determined by the adjustment factors for traffic flow elements. Projection of the matrix using the projection factors generated as explained above.
5HFRPPHQGDWLRQ IRU YHULI\LQJ WKH FDOLEUDWLRQ display the difference between the assigned link volume and the AddValues with OLQN ODEHOV or by 'LIIHUHQFH 'LVSOD\ (link volume) via PARAMETERS in the GRAPHICS menu. display statistical deviations via PRT ASSIGNMENT ANALYSIS in the CALCULATE menu.
5-39
O-D MATRICES
([DPSOH PDWUL[ SURMHFWLRQ The Fij-matrix of the last assignment here serves as the basic matrix: Zone 1 2 Destination traffic 1 20 40 60 2 30 50 80 Origin traffic 50 90 140
If the traffic of Zone 1 is to be increased by 10% and the traffic of Zone 2 by 20 %, the following matrix (for a projection of the origin only) will result: Zone 1 2 Destination traffic 1 22 48 70 2 33 60 93 Origin traffic 55 108 163
It can be seen that, although the origin traffic increased by the required amount, the destination traffic did not, because 1.1 * 60 = 66 and 1.2 * 80 = 96 For this reason, as in the case of MUULI, an iterative procedure - WKH PXOWL SURFHGXUH DFFRUGLQJ WR /RKVH (1980) - is used for the origin and destination projection which, in an iterative process, searches for that one solution that will achieve the desired values in the best possible way. The above example results in the following solution: Zone 1 2 Destination traffic 1 21 45 66 2 34 62 96 Origin traffic 55 107 162
The PXOWLSURFHGXUH DFFRUGLQJ WR /RKVH is an iteration procedure which calculates new origin/destination relations ) for every iteration step, as a result of which the results are extremely close to the desired values of the traffic demand matrix.
LM
5-40
O-D MATRICES
The iteration formula applied is as follows:

Fij (n+1) = Fij(n) * qi(n) * zj(n) * f(n) ; with: Qip qi(n) = ----------------- ( Fij * Zjp/Zj(n)) j Zjp zi(n) = ------------------- ( Fij * Qip/Qi(n)) i Gp f(n) = -------G(n) Qip Zjp Gp Fij(n) Qi(n) Zj(n) G(n) : : : : : : : required origin traffic zone i required destination traffic zone j required total traffic demand traffic flow from zone i to zone j in iteration n origin traffic zone i, iteration n destination traffic zone j, iteration n total traffic, iteration n
This iterative calculation is performed until all the following conditions are met for marginal sums (desired values for origin and destination):
Qi(n)/Qip -1 ; for all zones i and Zj(n)/Zip -1 ; for all zones j
The threshold suggested by Lohse was used, which states that:

= 1/(<GF> * Qip) i.e. = 1/(<GF> * Zjp)
When activating the calibration process, the user can set the following parameters for this multi-procedure: Maximum number of iterative steps Precision threshold 1..9999 (as required); the default is 10 1..99 (as required); the default is <GF> = 3 The higher the <GF>- value, the longer the computing time and the higher the precision of the calculations.
5-41
O-D MATRICES
5-42
FILTERS AND MULTISELECT SPECIFICATIONS
),/7(56 $1' 08/7,6(/(&7 63(&,),&$7,216
In the process of editing the network or for further analyses it can be advantageous to restrict the entire network to specific selected areas or to select or to exclude network objects via freely definable value ranges of attributes: via QHWZRUN REMHFW ILOWHUV object selection according to content (value ranges of their attributes) and/or via 0XOWL VHOHFW: object selection according to location via areas or polygon definition object selection by individual or global selection. active objects = selected objects passive objects = non-selected objects.
The result are DFWLYHSDVVLYH network objects:
The multi select and contents (filter) criteria can also be combined with an $1' RSHUDWLRQ which means that only network objects that fulfil both the filter and multi select area criteria are selected (for example: all links in the area FLW\ with a free flow speed of Y3U7= 50 km/h).
The active network objects and the filter selection criteria themselves, can be saved in files to be used in subsequent applications: filter selection criteria: *.fil active network objects: *.ane For an overview about the number of active/passive objects for each network object type see EXTRAS menu - PROGRAM STATUS. In addition to network object filters, there are a relation filter and a time filter: 5HODWLRQ ILOWHU: selection of particular origin-destination relations according to origin, destination, through, and internal traffic. 7LPH ILOWHU: selection of particular line trips which depart from an origin stop within a given time interval.
6-1
Filters
The following table provides an overview of possibilities for specifying active network objects: &RQWHQWV Specify filter criteria. /RFDWLRQ Specify spatial filter: Specify the polygon as Activates all objects located com- a rectangle: drag pointer while pletely within the polygon. The holding down left mouse following co-ordinates apply: button centroid for zones, global a polygon: while holding down zones and areas, <Ctrl> key, fix polygon points ViaNode for turning relations, one by one with left mouse FromNode and ToNode for click; release <Ctrl> key prior links. to marking the last point. Select area and apply the 2EMHFWV ZLWKLQ DUHD 6HW DFWLYH function (call via EXTRAS - MULTISELECT or context menu or right-click). The current state of each object can still be redefined individually. ,QGLYLGXDO Change state of individual object: set active object to passive or passive object to active state. *OREDO For all objects: ,QYHUW: set all active objects to the passive state and all passive objects to the active state simultaneously, ,QLWLDOLVH: reactivate all objects. Mark an individual object of the active object type as described for SINGLESELECT mode. Right mouseclick activates (left mouseclick closes) the context menu. *.fil *.ane
or
Read filter parameters or active Filter parameters network objects from file: Active network objects
6-2
Filters
)LOWHUV
The following filter types can be activated individually or in combination: %XWWRQ )LOWHU W\SH Link filter Node filter Zone filter Global zone filter Connector filter Turning relation filter Line filter Census points filter Relation filter for selecting origin-destination relations. Time filter for selecting vehicle trips.
The colour of the "Filter bag of the symbol button indicates if a filter is currently active: red: filter is set. white: filter is not set.
An overview of current filter types and the number of active and passive network objects can be had via PROGRAM STATUS in the EXTRAS menu. Node filter, link filter and line filter criteria can be combined (connected by AND, see Chapter 6.1.3).
6-3
Filters
6HW ILOWHUV

The general procedure for specifying filter criteria which is applicable to all filter types will be explained using the example of a link filter. Filter-specific features - in the case of the link filter, the )LOWHU UHIHUV WR option - are described individually for each filter. &DOO XS OLQN ILOWHU via LINKS under FILTERS in the EXTRAS menu or symbol button /LQN ILOWHU GLDORJ The following link filter activates all links of the "Car" transport system whose saturation exceeds 90%:
$SSO\ ILOWHU The filter settings are activated (default). o The filter settings are deactivated. Deactivated filter criteria do not take effect but are retained can be saved to file can be reactivated at any time
6-4
Filters
&RPSOHPHQW o Network objects which fulfil all set filter criteria become active (default). Network objects which fulfil at least one of the set filter criteria become passive. 6SHFLI\ YDOXH RU YDOXH UDQJH IRU HDFK DWWULEXWH Select attribute; select subattribute (e.g. transport system). Specify value or value range (see example next page).
7\SH OLVW ER[ Select link types 0..99. 7UDQVSRUW V\VWHP OLVW ER[ Select transport system Car, HGV etc.. $SSO\ EXWWRQ Filter becomes active (graphics/listings) while filter dialog box is open; serves to check the filter effect interactively without continually having to open and close the dialog box. ,QLWLDOL]H EXWWRQ Delete all filter criteria set in the dialog box. 2. EXWWRQ Confirm current filter status, close dialog box.
Set and activate further filter criteria for other filter types. &RPELQDWLRQ UXOH IRU DFWLYDWLQJ VHYHUDO ILOWHU W\SHV Active filter types are combined with AND. Saving to *.fil saves the filter parameters of all set filter types.
6-5
Filters
([DPSOHV: SURFHGXUH IRU OLVW ER[ VHOHFWLRQ Selection Select an entry Function Click on entry
Selecting several consecutive entries, e.g. link types .
Mark entire range while holding down left mouse button. Mark with left mouse button while holding down <Ctrl>-key.
Selecting several non-consecutive entries individually or as consecutive groups, e.g. link types , .
([DPSOHV SURFHGXUH IRU YDOXH UDQJH LQSXW For every attribute, there are two input fields "From" and "To" which can be set in the following way. Here, an example using link numbers: Input: Attrib. Nr Nr Nr Nr Nr Nr 400 Value range from - to 200 200 400 200 400 400 400 400 200 o o o o o 200 Nr 400 Nr < 200, Nr > 400 1) Nr < 200, Nr > 400 2) Nr 200 Nr 400 Nr = 400 Effect: Complement Active links
1) &RPSOHPHQWRSWLRQapplies to all value ranges of all set attributes. 2) The FRPSOHPHQWDU\ condition only applies to the respective attribute.
6-6
Filters
([DPSOH: 6SHFLI\ VWULQJV WR ILOWHU IRU QDPHV HWF To select all links startings from the node with the node code 0DUNHW: Select attribute )URP1RGH&RGH and specify filter criterion: Enter a complete string (sequence of characters): "0DUNHW, Enter one or some characters in the correct order and the wildcard * in the correct position, e.g. "Mark*. Only one wildcard is permitted which may be entered either in the first or in the last position. Blanks are not permitted. Entries like 0 NH are not permitted; Entered strings may not include blanks such as "0DUNHW 6TXDUH. All links starting from the node whose code is "0DUNHW " will be set to the active state.
([DPSOH 25FRPELQDWLRQ IRU VHYHUDO ILOWHU FULWHULD In the following example, all links which fulfil at least one of the two criteria are to be activated: Volume PuT 200 or Saturation PuT Total < 10 %
An OR-operation on the two filter criteria is accomplished by setting complementary conditions in the input fields of the attribute value ranges in the respective filter dialog boxes:
The input logic follows 0RUJDQ

V /DZ: A or B = not (not A and not B) Accordingly, the value range fields of each attribute line are input as an individual complement condition from which the total complement is then taken ( &RPSOHPHQW): Attribute Sat-PuT-Tot Vol-PuT Condition A = from 0 to 9 B = from 0 to 200 Complement condition Not A = from 10 to ... Not B = from 201 to ...
6-7
Filters
'HDFWLYDWH RU LQLWLDOL]H ILOWHUV

Set filters can be initialized (entered filter conditions are deleted) in two ways: ,QLWLDOL]LQJ D SDUWLFXODU ILOWHU &DOO XS WKH DFWLYH ILOWHU Via symbol button or FILTERS in the EXTRAS menu HJ LINKS )LOWHUV GLDORJ ER[ HJ /LQN )LOWHU ,QLWLDOL]H button 2. button ,QLWLDOL]LQJ VHYHUDO ILOWHUV
$FWLYDWH HGLW FRPPDQG ,QLWLDOL]H under EXTRAS menu FILTERS in the
All active filters which can be initialized individually or globally are displayed in the dialog box: in this example, the link, node, and turning relation filters are active, the node filter is QRW be initialized.
In contrast to deactivating a filter Option o $SSO\ )LOWHU in the filter parameter dialog box or DISABLE FILTER under FILTERS in the EXTRAS menu,
where the effect of the filter IS merely surpressed, in this case the current filter definition is not initialized to the default settings.
6-8
Filters
)LOWHU W\SHV

1RGH ILOWHU
1RGH )LOWHU GLDORJ The following node filter activates all stops with more than 50 transfers:
2QO\ LVRODWHG QRGHV All isolated nodes are selected. All other nodes are in a passive state. 2QO\ VWRSV All stops are selected. All other nodes are in a passive state. &RQVLGHU OLQH ILOWHU o Default setting: Do not consider active line filter, connect line and node filter criteria by AND. &RQVLGHU OLQN ILOWHU connect link and node filter by AND (see also example below).
Filters
/LVW ER[ Select 7\SH(s) 00 ... 99
([DPSOH DSSOLFDWLRQ &RQVLGHU DOVR OLQH RU OLQN ILOWHU allows selection of e.g. all stops served by particular lines with e.g. min. 500 passengers boarding the selected line. If option FRPSOHPHQW is active, while other filter types are considered, the complement rules apply to linking filters (see Chapter 6.1.1.).
/LQN ILOWHU

/LQN )LOWHU GLDORJ The following link filter activates all links of the "Car" transport system whose saturation exceeds 90%:
)LOWHU UHIHUV WR RQH GLUHFWLRQ: only the link direction which fulfils the filter criterion is selected. ERWK GLUHFWLRQV: both directions are selected if one direction fulfils the filter criterion. &URVVVHFWLRQ YDOXHV: only the links whose total value of both directions (= cross-section value) fulfil the filter criterion are selected.
Filters
([DPSOH A link with the volumes: )URP1RGH 7R1RGH = 500 )URP1RGH 7R1RGH 30 = 700 can be selected in three ways with the filter criterion Vol-PrT 500 )LOWHU UHIHUV WR ERWK GLUHFWLRQV: both directions are selected because one of the two directions fulfils the filter criterion. )LOWHU UHIHUV WR RQH GLUHFWLRQ only the direction FromNode 30 ToNode 13 with a volume of 500 is selected. )LOWHU UHIHUV WR FURVVVHFWLRQ YDOXHV no selection; only a filter criterion of "Volume-PrT 1200 would result in a selection.
7\SH OLVW ER[ Filtered according to link types 7UDQVSRUW V\VWHP OLVW ER[ Filtered according permitted TSys &RQVLGHU OLQH ILOWHU o Default setting: Do not consider active line filter, connect line and node filter criteria by AND.
6-11
Filters
=RQH DQG JOREDO ]RQH ILOWHU

Zone and global zone filter are identical, therefore, only a zone filter is displayed below: =RQH LH JOREDO ]RQH ILOWHU GLDORJ This zone filter activates all zones served by 1 or 2 sublines:
7\SH /LVW ER[ Filtered according to zone or global zone type
6-12
Filters
&RQQHFWRU ILOWHU

&RQQHFWRUV )LOWHU GLDORJ The following filter activates all origin connectors permitted for PuT:
'LUHFWLRQ Filtered according to origin and/or destination connectors. 76\V0RGH Filtered according to private or public transport type.
6-13
Filters
7XUQLQJ UHODWLRQ ILOWHU

7XUQLQJ UHODWLRQ ILOWHU GLDORJ The following filter activates all left turns (type=3) of the bus transport system from a lower-ranking link to a higher-ranking link:
9LD1RGH Filtering can be done according to the type of right of way (default: all variants). 7\SH OLVW ER[ Filtered according to turning relation types 7UDQVSRUW V\VWHP OLVW ER[ Filtered according to transport system &DU +*9 %XV 7UDLQ HWF
6-14
Filters
/LQH ILOWHU

/LQH ILOWHU GLDORJ These filter settings will set all sublines active which are run by operator 1.
Particular sublines are set active or passive via the line filter according to selected attributes and values and/or list box selection. /LVW ER[ VHOHFWLRQ RI VXEOLQHV
76\V: select lines of selected transport systems. /LQHV: select sublines of selected lines. 6XEOLQHV: select individual line variants. 0DLQ/LQH: select individual user-defined main lines. If Complement is active ( FRPSOHPHQW) all switched off sublines etc. are active.
6-15
Filters
Select ...
6HOHFW GLDORJ Recommended for networks with numerous lines or sublines respectively exceeding the List box display.
6HOHFW OLQHV RU VXEOLQHV E\ DWWULEXWHV DOO: Select all lines or sublines. 76\V1DPH and 76\V&RGH: Select PuT transport system. String attributes 1DPH 2S1DPH 9HK1DPH 26WS&RGH 26WS1DPH '6WS&RGH '6WS1DPH: Enter either the complete string or a part of the string (characters in the correct order) with * as a wildcard. The attributes 9DULDQW and 'LUHFWLRQ identify a subline, e.g.: %XV % (Opposite direction B, not )orth, Variant of line %XV). other attributes: Select by attribute value or value range.
6HW VHOHFWHG OLQHVVXEOLQHV WR Set all lines/sublines active, which meet the filter criterion. o Set all lines/sublines passive, which meet the filter criterion.
This option may be applied for each filter criterion. Click on OK to confirm, select next attribute and specify filter criterion. Thus filter criteria are connected as an AND term. For lines or TSys whose sublines are partially active and partially passive, the following rules apply for calculating the aggregated line attributes: The attributes which can be calculated for each subline (e.g. vehicle kilometres, service time, number of passengers using the line, etc.) correspond to the sum of the attributes of all active sublines. The attributes which can only be calculated for one line or transport system (number of vehicles, vehicle costs, etc.) are distributed over the sublines via vehicle kilometres and are then added up for active sublines. The line filter can be applied with the node and/or link filter (AND connection). Thus e.g. only those stops can be set active, where more than 500 passengers board a selected line.
6-16
Filters
&HQVXV SRLQW ILOWHU

&HQVXV SRLQW ILOWHU GLDORJ This way only census points with counted values 2000 are set active:
5HODWLRQ ILOWHU

The relation filter is used to filter types of traffic (Fij-relations) between zones. To do this, zones must be defined as external or internal zones via zone types within the selected area. This makes it possible to analyse traffic between external and internal zones according to origin, destination, internal and external traffic or in combination with each other, and to display the results in a table or graph. The relation filter is fundamentally different from network object filter types since it filters exclusively according to types of traffic, and thus does not serve to set network objects active or passive.
Filters
5HODWLRQ )LOWHU GLDORJ The following filter displays the destination traffic between the zones of type 3 (external zones) and the zones of type 2 (internal zones): 'HILQH WKH ORFDWLRQ IRU HDFK =RQH W\SH LQWHUQDO ]RQH. H[WHUQDO ]RQH. QHXWUDO ]RQH
)URP LQWHUQDOH[WHUQDO WR LQWHUQDOH[WHUQDO Select the traffic type(s) via a Fij-relation matrix: internal traffic (from LQWHUQDO to LQWHUQDO) origin traffic (outbound) (from LQWHUQDO to H[WHUQDO) destination traffic (inbound) (from H[WHUQDO to LQWHUQDO) external traffic (from H[WHUQDO to H[WHUQDO) &RPSOHPHQW All Fij-relations which are not selected due to the current setting of the relation filter are output.
The relation filter has an effect on all volumes in the graphic display and in listings: flow bundles and node flows volume of links, connectors, turning relations and PuT-lines boarding, alighting, and transfer passengers at stops. The relation filter has no effect on difference networks. Traffic which originates or ends in neutral zones is not taken into account when transport types are output. The currently filtered relations are taken into account for the following, further VISUM functions: Saving partial O-D matrices (TrafficType and FlowBundle) Generating Link-AddValues.
6-18
Filters
7LPH ILOWHU

Time filters are used to select line trips whose departures from origin stops lie within the time interval. 7LPH ILOWHU GLDORJ The specified time filter activates all vehicle trips which depart from the origin terminal between 8:30:00 and 10:00:00.
7LPH LQWHUYDO Specify a time interval with "From hh:mm:ss" and "Till hh:mm:ss"
The time filter has an effect on all attributes which refer to a time interval and are marked with $WWULEXWH7,, e.g.: VehKm/TI, VehTrips/TI SeatsKm/TI OperatT/TI
6-19
Multiselect
0XOWLVHOHFW
6HOHFWLRQ RI QHWZRUN REMHFWV E\ SRO\JRQ GHILQLWLRQ

$FWLYDWH 08/7,6(/(&7 PRGH via MULTI SELECT in EDIT menu or Toolbar button and one of the network object types.
'HILQH D 08/7,6(/(&7 SRO\JRQ DV D UHFWDQJOH Left-click and drag. Select rectangular section, release mouse button. D SRO\JRQ RI GHVLUHG VKDSH hold down <Ctrl> and define the polygon points in sequence with left-click, releasing <Ctrl> prior to the last point.
All objects which are completely inside the polygon are set to active. For zones, global zones and areas, the co-ordinates of the centroid are valid. For turning relations, the 9LD1RGH LV YDOLG. For links, both nodes have to be inside. PuT lines are not regarded. A series of polygons can be defined one after another.
G
6-20
The commands for network objects selection via MULTI SELECT in EXTRAS menu are not supported for PuT lines.
Multiselect
6HOHFWLRQ RI QHWZRUN REMHFWV E\ DUHD

$FWLYDWH 08/7,6(/(&7 PRGH via MULTI SELECT in EDIT mode or Toolbar button.
Call 6HW REMHFWV LQ DUHD WR DFWLYH via MULTI SELECT in EXTRAS menu - or context sensitive menu with right-click in network display. Select area.
If a selection of objects has already been made via Multi Select, the following request appears:
6-21
Multiselect
If the answer is No, a new selection takes place and the previous one is discarded. All objects which are completely inside the area are set to active. For zones and global zones, the co-ordinates of the centroid are valid. For turning relations, the 9LD1RGH is valid. A series of areas can be marked one after another. 3UHFLVH FDOFXODWLRQ RI DUHDUHODWHG LQGLFDWRUV Active areas break down the attributes as determined by the area boundary. The following rules apply: A link belongs completely to the area if both FromNode and ToNode are inside the area. A link does not belong to the area if both FromNode and ToNode are outside the area. If one node is inside and the other outside the area, then the part of the link stretching from the inner node to the first intersection belongs to the area. A FromStop-ToStop line section is treated as a link, even if there are traversed nodes (non-served stops) inbetween.
6-22
Multiselect
The following table shows how the area-related attributes are broken down and which filter can be applied: $WWULEXWH LinkLength NetLengthDir (TSys) NetLengthCS (TSys) LinNetLenDir LinNetLenCS NumSLines NumLines NumServ Stop-all Stop-ser VehKm-PuT SeatKm-PuT ServiceT-PuT OpTime-PuT NumVeh-PuT VehKm-PrT PassKm-PuT PassH-PuT VehH-PrT TWT PassBoard PassAlight PassTransfer Cost-PuT CostHour CostKm CostVeh RevTot CostCovTot %UHDNGRZQ Length Length Length Length Length Every subline stopping in area Every subline stopping in area Services stopping in area Number of stops in area Number of stops served in area Length Length Line running time Line running time Line running time Length Length Line running time Link running time Stops in area Stops in area Stops in area Stops in area CostHour + CostKm + CostVeh Line running time Length Time Length Revenue/Cost x x x x x x x x x x x x x x x x x x x x /LQN ILOWHU /LQH ILOWHU x x x x x x x x
6-23
Multiselect

6HOHFWLRQ RI QHWZRUN REMHFWV E\ LQGLYLGXDO VHOHFWLRQ

$FWLYDWH 0XOWL 6HOHFW PRGH via MULTI SELECT in EDIT mode or Toolbar button.
Mark individual object as described for SINGLE SELECT mode. By mouse-click on a network object an active object is set to passive, a passive object is set to active. The commands for network objects selection via MULTI SELECT in EXTRAS menu (or context sensitive menu in MULTI SELECT mode) are not supported for sublines. Since in the default state the entire network is made up of active network objects only, it is recommended when only a small number of network objects is to be selected that all active network objects of the entire network be set initially to the passive state (invert) and to subsequently re-activate the required network objects by selecting them individually.
6SHFLDO FDVH VHOHFWLRQ RI VXEOLQHV LQ 08/7,6(/(&7 PRGH Activate MULTI SELECT mode and SUBLINES network object type.
6HOHFWLRQ RI VXEOLQHV Clicking on one (or more) stop(s) in the network display selects all sublines serving the selected stop(s). Selection of sublines in the dialog box: Mark in list box (mark multiple sublines by holding down <Shift>), With 6HOHFW DOO button. The number of selected sublines and the total number of sublines in the network are shown beneath the list box selection. The selection of sublines is optimally positioned in the centre of the network display screen with the $XWR]RRP button.
Setting the sublines active via Multi Select works in conjunction with the subline filter, with the filter taking priority, i.e. a filter selection can be restricted further by means of Multi Select. When, e.g., only the bus TSys is set to active via the filter, then only the selection of bus sublines can be made via Multi Select. The selection of sublines via Multi Select is linked to the process of setting sublines active by means of a defined area. Line-based attributes of areas can then be displayed in the area list for all active sublines.
6-24
Multiselect
,QYHUWLQJ DFWLYHSDVVLYH QHWZRUN REMHFWV
&DOO XS ,QYHUW FRPPDQG Inversion (reversal of all specified conditions) Set all active objects of the entire network to the passive state, and vice versa. INVERT via MULTISELECT in the EXTRAS menu. Right mouse click in 0XOWL 6HOHFW mode activates dialog with the ,QYHUW button
,QYHUW VWDWXV RI QHWZRUN REMHFWV GLDORJ
6-25
Multiselect
&KHFN OLQN V\PPHWU\ IRU ERWK GLUHFWLRQV

This command compares the symmetry of the input values of selected link attributes for both directions of each link in the current network. Links whose opposite directions have different values for at least one of the compared attributes become active links.
&DOO XS &KHFN OLQN V\PPHWU\ FRPPDQG CHECK LINK SYMMETRY via MULTISELECT in the EXTRAS menu. Right mouse click in 0XOWL 6HOHFW mode activates the dialog with /LQN V\PPHWU\ button
6\PPHWU\ RI OLQN DWWULEXWHV GLDORJ
The dialog box also includes input data for add-on modules.
Passive network objects are set to the active state prior to the check routine (might have to save active network objects beforehand). Active link filters are taken into account, that is, only links in the network which fulfil the current filter criteria are checked.
6-26
Multiselect
,QLWLDOLVLQJ 0XOWL6HOHFW
&DOO XS ,QLWLDOL]H FRPPDQG Set passive network objects to the active state. INITIALIZE via MULTISELECT in the EXTRAS menu. Right mouse click in 0XOWL 6HOHFW mode activates dialog with the ,QLWLDOL]H button
,QLWLDOL]H SDVVLYH VWDWH RI QHWZRUN REMHFWV GLDORJ
6-27
Partial network generator
3DUWLDO QHWZRUN JHQHUDWRU
With the 3DUWLDO QHWZRUN JHQHUDWRU add-on module, a partial network together with the associated partial matrices can be generated from the overall network in such a way that, generally speaking, comparable assignment results are obtained for the partial network. The partial network is generated on the basis of the following rules: Generation begins with the active links and the active lines. All FromNodes and ToNodes of the active links are transferred to the partial network. All lines stopping at one of these nodes are transferred, or cut if necessary. All nodes and links traversed by lines included in MultiSelect are transferred to the partial network. All connectors at a node located in the partial network are transferred. All zones with connectors at a node located in the partial network are transferred. Turning relations whose FromLink and ToLink are included in the partial network are transferred.
The partial network generator considers the routes of an existing assignment and generates new zones at the networks interfaces at which traffic flows enter or leave the network. These "virtual" boundary zones are added to the partial matrices of the demand segments so that no traffic demand in the partial network is lost: PrT O-D matrices: Virtual connectors are generated at all boundary nodes. Boundary nodes are nodes at which active and passive links meet, i.e. at which at least one link is not included in the partial network. A virtual zone is generated for each virtual connector. VISUM can then supplement the O-D matrix by adding routes. This requires performing an assignment. PuT O-D matrices: Virtual connectors are generated from the routes. A virtual zone is generated for each virtual connector. This requires performing an assignment.
6-28
'HILQLQJ D SDUWLDO QHWZRUN To define a partial network, the network objects of the partial network are set to active. VISUM includes three methods for this: 3RO\JRQ set objects in polygon active (MULTISELECT mode) or $UHD set objects in area active (MULTISELECT mode) )LOWHU apply link or line filter.
&$/&8/$7(PHQX 3$57,$/1(7:25.*(1(5$725 'LDORJ 3DUWLDO QHWZRUN
1HWZRUN Save partial network under the specified filename and directory path. 0DWULFHV Save partial matrices (from internal traffic and "virtual traffic") for the activated demand segments under the specified filename and directory path.
6-29
9LUWXDO ]RQHV To create virtual (cordon) zones, select one of the options: Continuous (define the lowest zone number +1 ... +n)
Offset to be added to connector node Nr. of virtual zones
and define zone type for virtual zones.
Be careful when specifying the minimum zone Nr or the Offset from NodeNr! Make sure that no zone Nr will occur twice in the network.
6-30
2SWLRQV /LQH URXWH RI DFWLYH OLQHV Settings for cutting PuT lines: &RPSOHWH OLQH URXWH IURP RULJLQ WR GHVWLQDWLRQ WHUPLQDO
'6WRS
26WRS
&XW OLQH URXWH DW SRO\JRQ ERXQGDU\:

/DVWVWRSVHUYHG
'6WRS
26WRS
)LUVWVWRSVHUYHG
The line begins at the first stop and ends at the last stop served of those stops transferred to the partial network
&XW OLQH URXWH LQFOXGH FRUGRQ VWRSV LQ SDUWLDO QHWZRUN: If the first transferred node of a line is a stop served by this line, the line begins here. If, on the other hand, the line is traced back to a stop it serves, then it 26WRS begins there. If the last transferred node is a stop served by the line, the line stops here. Otherwise it ends at the next stop served. The new nodes and links that result are also transferred.
'6WRS
/DVWWUDYHUVHGVWRS 1H[WVWRS VHUYHG FRUGRQ VWRS )LUVWWUDYHUVHGVWRS
1H[WVWRSVHUYHG FRUGRQVWRS
6-31
File management
)LOH PDQDJHPHQW
The active network objects of an entire network selected via reference areas and filters, and the selection criteria themselves, can be saved in binary files to be used in subsequent applications: )LOH W\SH )LOWHU ([WHQVLRQ *.fil 'HVFULSWLRQ Contains the filter criteria of all active filter types.
G
$FWLYH QHWZRUN REMHFWV
If only the conditions of SDUWLFXODU filter types are to be saved, it is meaningful to indicate this in the file name, e.g. by calling a node filter file n_exl.fil. Loading a filter file after having modified network object attributes can result in a different selection of active network objects. Contains DOO active network objects resulting from location DQG content criteria ZLWKRXW the respective filter criteria and reference area boundaries.
*.ane
3URFHGXUH )LOWHU ILOH PDQDJHPHQW
2SHQ ILOH )LOWHUV under OPEN in the FILE menu or READ FILTER FILE under FILTERS in the EXTRAS menu 6DYH ILOH )LOWHUV under SAVE in the FILE menu or SAVE FILTER FILE under FILTERS in the EXTRAS menu
6-32
File management
3URFHGXUH $FWLYH QHWZRUN REMHFWV ILOH PDQDJHPHQW
2SHQ ILOH $FWLYH 1HWZRUN (OHPHQWV under OPEN in the FILE menu READ ACTIVE NETWORK ELEMENTS under MULTISELECT in the EXTRAS menu or MULTISELECT mode and right mouse click in the display area: 5HDG DFWLYH QHWZRUN HOHPHQWV button 5HDG DFWLYH QHWZRUN HOHPHQWV GLDORJ Selection of network object types to be read:
Option $GG can be enabled, when there is at least one passive network object in the current network. Only the active network objets read from file will be active. The active network objets read from file will be active additionally to the network objects which are already active in the current network state.
6DYH ILOH $FWLYH 1HWZRUN (OHPHQWV under SAVE in the FILE menu SAVE ACTIVE NETWORK ELEMENTS under MULTISELECT in the EXTRAS menu or MULTISELECT mode and right mouse click in the display area: 6DYH DFWLYH QHWZRUN HOHPHQWV button
6-33
File management
6-34
ASSIGNMENTS AND INDICATOR MATRICES
$66,*10(176 $1' ,1',&$725 0$75,&(6
The so-called assignment is one of the main methods to determine and analyse the effects of transport supply. Assignment helps to calculate the volumes of nodes, links and lines and indicators for assessing connection quality between traffic zones. To make a trip, a PrT trip maker selects a route i.e. a series of links which appear most convenient. A PuT-passenger not only selects a route for his journey, but also a departure time from the timetable i.e. he looks for a connection.
To do this, the passenger trips are simulated.
Assignment procedures are based on search algorithms which determine routes or connections between origin and destination. The search procedure is followed by choice and split procedures which distribute the travel demand of an origin-destination relation (O-D pair) onto the routes/connections. The routes and connections also carry the necessary information for calculating indicators, such as times, distances and number of transfers. VISUM offers various assignment procedures for private and public transport. They differ by the search algorithm and by the procedure used for distributing trips. Assignment results in volume values for the used network objects (nodes, links, connectors, turning relations, lines). As a unique feature VISUM stores all routes for post assignment analysis, e.g. flow bundle calculation and display. Due to memory capacity, PuT-connections can only be saved as routes after assignment i.e. only information about the used sequence of lines is stored. The departure time and exact transfer times are not stored. .
7-1
Dialog for assignments
'LDORJ IRU DVVLJQPHQWV
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV WDE Any number of actions can be configured. An action consists of an operation, for which demand segment(s) and procedure parameters or a file path are required. Select the $FWLYH button for all actions to be subsequently carried out by clicking the ([HFXWH button.
7-2
Insert Delete
Use this button to insert a new action below the currently selected action. Use this button to delete the selected action. Clicking one of the buttons moves the selected action one line up or down in the list of actions. 2SHUDWLRQ Selecting an operation: O-DMatrixRead O-DMatrixSave Assignment* IndicatorMatrix O-DMatrixCalibr Save version LinBlockCalc* PuT revenues* Infrastructure costs*
Read O-D matrix Save O-D matrix Calculate assignment Calculate/save indicator matrix Calibrate O-D matrix using counted data Save version file Calculate rosters Calculate revenues Calculate infrastructure costs
*) For actions identified with *, an ,QLW action can also be selected. This returns the result of the current calculation for the action selected to its previous status. '6HJ Demand segment(s) for the current operation. 3URFHGXUH Procedure for the current operation. )LOHQDPH Path and filename for the current operation. DSeg Parameters Browse Execute Save Open Use this button to select one or more demand segments. Use this button to set the parameters for the currently selected operation. Use this button to select path and filename. (For indicator matrices, the path is to be specified as a parameter.) The ([HFXWH button starts the operation: all actions selected as $FWLYH are carried out in the specified sequence. Saves the current settings in the 3URFHGXUH dialog (2SHUDWLRQV tab and )XQFWLRQV tab) as assignment parameter file. Reads assignment parameter file *.par.
7-3
5HDGLQJ DQG VDYLQJ DVVLJQPHQW SDUDPHWHUV The assignment parameters include all settings under 2SHUDWLRQV and )XQFWLRQV. Assignment parameter file management is carried out via buttons 2SHQ and 6DYH. This functionality corresponds to the file management commands in the FILE menu. 5HDG DQG VDYH 2' PDWUL[ Select 2SHUDWLRQ O-DMatrixRead or O-DMatrixSave. Select '6HJ: %URZVH: specify drive\directory\filename. Select 2SHUDWLRQ Assignment. Select one or more demand segments. Select 3URFHGXUH PuT: Transport system-based, line-based or timetable-based procedure 1, 2 or 3, PrT: Equilibrium, incremental, Tribut or learning procedure. 3DUDPHWHUV: specify procedure-specific assignment parameters. )XQFWLRQV tab: specify PrT impedance functions. Select 2SHUDWLRQ IndicatorMatrix. Select one or more demand segments. specific settings: PuT: Select 3URFHGXUH, PuT assignment results are not deleted. PrT: Select '6HJ, a PrT assignment result must exist. Specify 3DUDPHWHUV. Select 2SHUDWLRQ O-DMatrixCalibr. Select '6HJ. Specify 3DUDPHWHUV.
6HOHFW DVVLJQPHQW SURFHGXUH DQG VSHFLI\ SDUDPHWHUV
&DOFXODWH LQGLFDWRU PDWULFHV
&DOLEUDWLQJ D 3U7 2'PDWUL[
7-4
)XQFWLRQV WDE Use this tab to set global parameters and functions for all procedures. PrT functions: CR curves: Defines CR functions for link types, turning relations and connections. Impedance: Defines transport system-specific impedance functions for the PrT route search. Volume: Specifies whether a basic volume should be considered. Type factor: Defines type factors for impedance calculations (link types, turning relations and connections). Erased Flow: Additional module. The PuT functions for the calculation of costs and revenues are described in Chapter 9. )XQFWLRQV WDE
5RXQGLQJ 3U7 WLPH DQG LPSHGDQFH like in VISUM 6.0 - 6.3: integer values t0/tCur, assignment results generated with VISUM 6 can be reproduced like VISUM 5.1 and before: integer value t0/tCur, assignment results generated with VISUM 4 and 5 can be reproduced real values (t0/tCur)
7-5
PrT Assignment procedures
3U7 $VVLJQPHQW SURFHGXUHV
All assignment procedures are based on a short-route algorithm which determines low impedance routes. The impedance of a PrT-route is volume-dependent and consists of the impedances of used links, used turning relations and of used connectors. ,PSHGDQFHV RI OLQNV For every PrT-transport system of a link, a TSys-specific travel time (t0-TSys) for free flow is defined which is calculated from the link length the permitted speed (v0-PrT) for the traversed link and the maximum speed of the transport system (v0-TSys). A capacity-dependent impedance function continuously adapts this basic travel time depending on the current traffic volume. ,PSHGDQFHV RI WXUQLQJ UHODWLRQV VISUM calculates turning relation impedances for every turning relation permitted at a node. A turning relation impedance includes an impedance time penalty t0 which increases in dependence on volume and capacity. ,PSHGDQFHV RI FRQQHFWRUV Connector impedances of absolute connectors are regarded as being volume-independent i.e. the connector time is regarded as a constant impedance which is volumeindependent. of proportional connectors are regarded as being volume-dependent i.e. with increasing volume the actual connector time will exceed the connector time t0 of each connector. By combining a high value for parameter b in the CR-function with the use of the equilibrium procedure, a relatively exact distribution of traffic over connectors can be achieved.
7-6
,PSHGDQFH IXQFWLRQV

The impedance of links, turning relations, and proportional connectors is determined with an impedance function which consists of a time factor and a cost factor. impedance = time factor tCur + factor Attribute (e.g. Cost-AddValue) The default value for the time factor is 1.0, and for the attribute factor 0.0. The time proportion depends on traffic volume. The attribute proportion is volume-independent and can contain any impedance value, e.g. link lengths or road tolls.
The time tCur of a network object is calculated with capacity restraint functions (CRfunctions). Based on the assumption that the travel time (impedance) of network objects increases with increasing traffic volume, all assignment procedures are in turn based on the assumption that travel times of network objects are a monotone incremental function of traffic volume. Thus, in case of increased traffic in the network the effect of deterrence to alternative routes can be represented. During assignment the impedances are calculated for all links, which are not blocked for usage by a CR function, connectors, for which a relative distributionhas been specified, and turning relations, if t0 > 0, as long as not a CR graph of the FRQVWDQW type has been allocated to them.
7-7
'HILQLQJ &5 IXQFWLRQV IRU WKH LPSHGDQFHV RI QHWZRUN REMHFWV
&$/&8/$7(PHQX 352&('85(6 )XQFWLRQV 3U7 IXQFWLRQV &5 FXUYHV GLDORJ
&5)XQFWLRQV ,QVHUW: Define a new CR function. Select type, define Nr and parameters. Parameters are only regarded if this function is not blocked. 0RGLI\: Edit CR function parameters. 'HOHWH: Delete selected CR function: A CR function which has been selected for a link type, cannot be deleted.
/LQNV Assigning a CR function to a link type Select one or several lines/columns/cells by clicking and holding down <> to select a block or <Ctrl> for separate cells. SelectHG FHOOV: Enter CR number. VISUM enters the curve number into the selected fields. 7XUQLQJ UHODWLRQV &RQQHFWLRQV E\ SHUFHQW
Enter number of CR curve for all turning relations or connections by percent. &RQVLGHU Y0LQ This option limits the minimum speed of a link to the minimum speed of the link type. See menu EXTRAS LINK TYPES: vMin (backup speed / congestion). ,QVHUW HGLW D &5 FXUYH
7-9
7\SH Select a function type for the CR curve: BPR: Bureau of Public Roads function, BPR2: modified BPR function with a different parameter b for the not saturated / saturated state, BPR3: modified BPR function, for which an additional supplement d per vehicle can be specified in the saturated state INRETS: the INRETS function of the French Institut National de Recherche sur les Transports et leur Scurit a constant function, in which the capacity has no impact on the journey time (tCur = t0).
The formulas are described in Chapter 2.4.2 of this manual. %ORFNLQJ If links are blocked by a CR function please make sure, that the network consistency is kept for relations O-D with demand > 0. EORFNHG For simple blocking, blocked links may be used if no alternative route exists, e.g. for residential traffic. VISUM assigns a high virtual time penalty which, for example, has to be considered in the travel time indicator matrix when interpreting route times. KDUG: Hard blocked links are not included in the route search for assignment.
6HH )XQFWLRQV WDE 3U7 IXQFWLRQV 5RXQGLQJ WLPHV DQG LPSHGDQFHV Rounding as in VISUM version 6: whole number value t0/tCur for reproducing assignment results from VISUM 6 Rounding as in VISUM version up to 5.1: whole number value t0/tAct for reproducing assignment results from VISUM 4 and 5 Times as real: real value t0/tCur
7-10
6SHFLI\LQJ SDUDPHWHUV IRU WKH LPSHGDQFH IXQFWLRQ
&$/&8/$7(PHQX 352&('85(6 )XQFWLRQV 3U7 IXQFWLRQV ,PSHGDQFH GLDORJ Defining the impedance function for PrTSys assignment:
Impedance A1..A4: Type factor:
= A1 type factor tCur + A2 type factor Attr.2 + A3 type factor Attr.3 + A4 type factor Attr.4 Global parameters, user-defined for each TSys Parameters, user-defined for each link type
Attribute2..4: Attributes: Road toll, Length, t0, tCur, AddValue1, 2, 3
$GG9DOXHV of links, connectors, turning relations: If e.g. cost or basic volumes are to be regarded, which are available as AddValue data, the same AddValue (AddV_1 or AddV_2 or AddV_3) has to be used for identical data.
7-11
&RQVLGHULQJ D EDVLF YROXPH
&$/&8/$7(PHQX 352&('85(6 )XQFWLRQV 3U7 IXQFWLRQV 9ROXPH GLDORJ
,QWHUQDO YROXPH PDQDJHPHQW Travel demand is available as integer values. During assignment real values can be produced, as demand between zones can be allocated to several routes. %DVLF YROXPH Taking calculated PrT volume into consideration as impedance: If a basic volume is available as an AddValue, this volume can either be ignored (IL[ o not active) or be fixed as a basic volume for assignment (IL[ active). The basic volume must be available as an identical AddValue for loaded network objects (e.g. as Link-AddVal2, TurnRel-AddVal2 and Connector-AddVal2). For the impedance calculation, the AddValues are treated like PrT-volume q. If several assignments are carried out, e.g. first +*9 assignment, then &DU assignment, the option does not have to be activated.
7-12
'HILQH IDFWRUV E\ OLQN W\SH IRU LPSHGDQFH FDOFXODWLRQ
&$/&8/$7(PHQX 352&('85(6 )XQFWLRQV 3U7 IXQFWLRQV 7\SH IDFWRU GLDORJ Defines a factor per link type, for connectors and turning relations.
Procedure for link types: Select one or several lines/columns/fields by clicking and holding down <> to select a block or <Ctrl> for separate cells. Enter factor in the )DFWRU IRU selectHG FHOOV field. VISUM enters that factor into the selected cells. It is also possible to enter the factor directly into a single cell.
7-13

,QFUHPHQWDO SURFHGXUH
The matrix is incrementally assigned to the network in the form of several parts. In this process the entire demand is proportionally distributed over the number of iteration steps defined by the user (max. 12). The default is an incremental assignment with three iteration steps (33%, 33% and 34%). The first step determines lowest impedance routes for all required O-D-relations of the current network for either a free network or based on a basic volume. The defined percentage of the first incremental step of the matrix is then assigned to these routes. Then, the new network impedances resulting from these volumes are calculated via the CR-function. On this basis, the next iteration step again calculates lowest impedance routes. This procedure is continued until the entire matrix has been assigned to the network.
If 100% is entered for the first iteration step, VISUM calculates the impedances of the current network and carries out a so-called best-route assignment.
7-14
3URFHGXUHVSHFLILF DVVLJQPHQW SDUDPHWHUV IRU WKH LQFUHPHQWDO SURFHGXUH
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
3DUDPHWHUV ,QFUHPHQWDO DVVLJQPHQW SURFHGXUH GLDORJ ER[ Proportional distribution of demand over iteration steps:
These parameters apply in combination with the general PrTassignment parameters which are set via the )XQFWLRQV tab under 3U7 IXQFWLRQV. 1XPEHU RI LWHUDWLRQ VWHSV DQG SHUFHQWDJHV Maximally 12 iteration steps can be calculated. The sum of percentages must amount to 100 %. If one step is set to 0%, further proportions are ignored. If less than 100% of an O-D-matrix is to be assigned, generate partial matrix with )DFWRU < 1.0 via O-D MATRIX in the CALCULATE menu. 5DQGRP URXQG For the incremental procedure, small traffic volumes in the matrix result in rounding problems, e.g. a three-step assignment where each step is a third of the matrix, a 1 is assigned during the last step because 0.33 was always rounded to 0 during the first two iteration steps. Appropriate calculation can only be carried out during the last iteration step. Because of this, a disproportional number of trips are assigned during the last iteration step. If the 5DQGRP 5RXQG button is active, the following applies to every iteration step: the value 0.33 is rounded up to 1 with 33% probability and it is rounded down to 0 with 67% probability. Recommendation for fairly empty matrices: activate random round .

(TXLOLEULXP SURFHGXUH
The equilibrium procedure calculates a state of balance according to Wardrops first principle: (YHU\ URDG XVHU VHOHFWV KLV URXWH LQ VXFK D ZD\ WKDW WKH WUDYHO WLPH RQ DOO DOWHUQDWLYH URXWHV LV WKH VDPH DQG WKDW VZLWFKLQJ WR D GLIIHUHQW URXWH ZRXOG LQFUHDVH SHUVRQDO WUDYHO WLPH XVHURSWLPL]HG EHKDYLRXU The resulting volumes can be interpreted as a state which assumes that every user has complete information about the network. The equilibrium procedure in VISUM is carried out based on an assignment result where the incremental assignment specified by the assignment parameters is always used as the initial solution. The state of balance is reached by multiple step iteration. For each inner iteration step, two coupled routes of a relation are brought to a state of balance by shifting vehicles. These iteration steps are carried out for all relations until all relations are in a state of balance. Every shift of vehicles from one route to another has an immediate effect on the impedances of the traversed network objects. The outer iteration checks if due to the current network state, new routes with lower impedances can be found. If this is the case for at least 1 relation, another state of balance must be calculated. Termination condition: a state of balance has been reached if the inner iteration step did not need to shift vehicles, and no new routes were later found by the outer iteration step. Since VISUM only uses integer vehicles and the CR-function is continuous, permitted tolerances must be specified in order to define the "equality" of route impedances. For highly overloaded networks or for the use of restrictive capacity restraints it is advisable to increase the iteration steps from three (default) to five or six.
7-16
3URFHGXUHVSHFLILF DVVLJQPHQW SDUDPHWHUV IRU WKH EDODQFLQJ SURFHGXUH
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
3DUDPHWHUV (TXLOLEULXP DVVLJQPHQW SURFHGXUH GLDORJ ER[ Defining the initial solution and the termination criteria.
These parameters apply in combination with the general PrT assignment parameters which are set via the )XQFWLRQV tab under 3U7 IXQFWLRQV. 8VH FXUUHQW DVVLJQPHQW DV LQLWLDO VROXWLRQ If an assignment result is already available, these routes and volumes can be used as an initial solution for the equilibrium procedure. To do this, activate the option . The initial solution may have been determined by any procedure.
7-17
If this option is not active, the initial solution is calculated using the settings under &DOFXODWH LQLWLDO VROXWLRQ ZLWK LQFUHPHQWDO DVVLJQPHQW. Multiple network modifications and repeated use of this option result in a different assignment result than a new assignment without this option would have resulted in since there are numerous states which fulfil Wardrops first principle of the balancing procedure. ,QLWLDO VROXWLRQ ZLWK LQFUHPHQWDO DVVLJQPHQW 1XPEHU RI LWHUDWLRQ VWHSV DQG GHPDQG VKDUH SHU LWHUDWLRQ VWHS distribute proportional shares of total demand over max. 12 iterations, the sum of the percentages must amount to 100%. 5DQGRP URXQG this option is recommended for fairly empty matrices because rounding errors can occur if the incremental procedure is used, thus resulting in a disproportional amount of trips being assigned in the last iteration step. 7HUPLQDWLRQ FRQGLWLRQV IRU HTXLOLEULXP DVVLJQPHQW VISUM terminates the iteration process for determining the balance if a network equilibrium, i.e. a permitted deviation of impedance has been reached or undercut or the maximum number of iterations has been reached without achieving a network equilibrium. 3HUPLWWHG GHYLDWLRQ RI LPSHGDQFHV RI DOWHUQDWLYH URXWHV DEVROXWH termination condition for iteration of coupled equalisation if the impedances of alternative routes deviate from each other by this maximum value. UHODWLYH termination condition of iteration of coupled equalisation if the impedances of alternative routes deviate from each other by this maximum percentage. 0D[LPXP QXPEHU RI LWHUDWLRQV In very highly loaded networks it is possible that the permitted deviations which were specified do not result in a state of balance because only integer vehicles are shifted. In this case, the procedure is terminated after the specified number of iterations.
7-18

/HDUQLQJ SURFHGXUH
This procedures simulates the "learning process" of road users using the network. To do this, the total traffic flow is assigned to the shortest routes found so far for every iteration step. During the first iteration step only the network impedances in the free network are taken into account (compare 100% best-route assignment). The calculation of the impedance in every further iteration step is carried out using the current mean impedances calculated so far and the impedances resulting from the current volume, i.e. every iteration step Q is based on the impedances calculated at Q. The assignment of the O-D-matrix to the network corresponds to how many times the route was found ("kept in mind" by VISUM). The procedure only terminates when the estimated times underlying the route choice and the travel times resulting from these routes coincide to a sufficient degree; there is a high probability that this stable state of the traffic network corresponds to the route choice behaviour of drivers. To estimate the travel time for each link of the following iteration step n+1, the estimated travel time for n is added to the difference between the (calculated from the CR-function) calculated actual travel time of n and the estimated travel time of n. This difference is then multiplied by the value DELTA (0.15...0.5) which results in attenuated sine wave. The termination condition arises from the requirement that the estimated travel times for iteration steps n and n-1, and the calculated actual travel time of iteration step n, sufficiently correspond to each other. This is defined by the precision threshold EPSILON.
7-19
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
3DUDPHWHUV /HDUQLQJ DVVLJQPHQW SURFHGXUH GLDORJ Select: Heuristic rule or Lotka-Volterra rule
7-20
6HOHFW PHWKRG RI HVWLPDWLQJ LPSHGDQFHV It is recommended to carry out a test calculation with both methods before the actual calculation. The Lotka-Volterra method is mostly faster than the heuristic method; however, the quality of the calculation results depends on the used network.
7-21

0XOWLSURFHGXUHV
For each of the PrT assignment procedures also the simultaneous assignment procedure variant is available. Multi_Incremental, Multi_Equilibrium, Multi_LearningProcedure.
By a Multi-Procedure several PrT demand matrices can be assigned to the network simultaneously. Define a particular impedance calculation formula for each PrT-TSys.
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
7-22
75,%87 SURFHGXUH
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
2SHUDWLRQ select assignment. '6HJ select PrT demand segments (defined under EXTRAS TRANSPORT SYSTEMS). Select SURFHGXUH Tribut (WARDROP) or Tribut Learning procedure 3DUDPHWHUV: specify procedure-specific assignment parameters. 3U7 IXQFWLRQ: specify impedance functions.
These parameters apply in combination with the general PrT assignment parameters which are set via the 3U7 IXQFWLRQV tab. The 7ROO attribute must be defined for links. The procedure automatically considers the Toll attribute together with the impedance (tCur, length), so the attribute should not be used for calculating impedance. )XQFWLRQV - 3U7 IXQFWLRQV 9ROXPH dialog: specify number of decimal places (= 3 is recommended) ,PSHGDQFH dialog: Define formula for calculating impedance. The formula should not contain the Toll attribute. 3DUDPHWHU 7ULEXW DVVLJQPHQW GLDORJ Definition of termination criteria (cf. balancing assignment) and the matrix-specific distribution function of the Value of Time. The settings are valid for selected demand segments. Menu EXTRAS TRANSPORT SYSTEMS: Define Demand Segments, e.g. HGV (L), Car-private (P), Car-business (B).
6SHFLILF DVVLJQPHQW SDUDPHWHUV IRU WKH 75,%87 SURFHGXUH
7-23
7HUPLQDWLRQ FRQGLWLRQV $EVROXWH LPSHGDQFH GHYLDWLRQ Balancing between alternative routes of a toll level is only canceled if Im pRoute1 Im pRoute2 < absolute Im pedance 5HODWLYH LPSHGDQFH GHYLDWLRQ Termination condition for the iteration relating to paired balancing, if the impedances on alternative routes of a toll level have a maximum deviation from each other of this percentage.
1
Im pRoute1 Im pRoute 2
< relative Im pedance
0D[LPXP QXPEHU RI LWHUDWLRQV Should it not be possible to to achieve a balanced state with the deviations that were set, VISUM cancels the procedure after completion of the number of iterations entered.
7-24
0D[LPXP YROXPH GHYLDWLRQ RI D WROO OHYHO The current volume of the toll level (sum of the route volumes per toll level) is compared with the distribution function curve. The calculations are continued until the deviation (preset/actual values) per toll level is the same as the displayed value. The parameter relates to the selected number of decimal places for volumes, i.e. if 3 decimal places are selected, 5 stands for 5/1000 vehicle units.
0DWUL[VSHFLILF GLVWULEXWLRQ IXQFWLRQ RI WKH 9DOXH RI 7LPH 7ULEXW SURFHGXUH VISUM lists all demand segments defined for the network; the DSeg selected for the action only are considered. The following settings are valid for the selected DSeg: 0HGLDQ median of the Value of Time for the LogN distribution of the random variable VT 6WG'HYLDWLRQ standard deviation for the Value of Time for the LogN distribution of the random variable VT 2ULJLQ IDFWRU and ]RQH ZHLJKWLQJ Weighting factor for the Value of Time of the zones origin demand.
Destination factor = 1 - origin factor. The weighting factor is applied with the type-specific zone factors. The median of the Value of Time is thus calculated for trips from one i zone (type i) to a j zone (type j). VTij = VT (OFactor ZoneTypeFactorL + DFactor ZoneTypeFactorM 3URFHGXUHVSHFLILF SDUDPHWHUV IRU WKH 75,%87/HDUQ SURFHGXUH 'LDORJ 3DUDPHWHU 7ULEXW/HDUQ DVVLJQPHQW Define number of iteration steps, function to estimate the impedances of network objects and termination conditions. The assignment parameters for the /HDUQLQJ SURFHGXUH are valid.
7-25
Matrix
LotkaVolterra Rule
7-26
(VWLPDWHG LPSHGDQFHV Select Heuristic Rule or Lotka-Volterra Rule and enter parameters.
/LQN VHTXHQFHV IRU 75,%87 are used to model road usage fees for several links along one route, which thus do not rise proportionally to the length of the covered link (see Chapter 2), are managed as entry data (see Chapter 15) and put out as a list in VISUM (see Chapter 10).
7-27

,QGLFDWRU PDWULFHV 3U7
Indicator matrices contain an indicator for every origin-destination relation determined from the best-route search or from the routes resulting from assignment. By combining the route search criterion with the output indicator data, different indicator matrices can be generated. Note that the same network supply data and network demand data for the same output indicator, e.g. distance, can result in different indicators depending on the route search criterion.
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
3DUDPHWHUV 3U7 LQGLFDWRU PDWULFHV GLDORJ
7-28
2SHUDWLRQ JHQHUDWH LQGLFDWRU PDWUL[ Enter filename or complete path. Set parameters and confirm with 2.. Start (calculate and save data) with ([HFXWH button.. )LOHQDPH For filename only: default settings (path and file extension) are copied from DIRECTORIES in the FILE menu. complete path: if drive, directory, filename, and extension are entered, current path is ignored. 7UDQVSRUW PHDQV QR (for VISEM) Confirm default value 4. VISEM uses: 1 = walking link 2 = car passenger 3 = PuT, 4 = car driver (including HGV) etc. )RUPDW $V Format (ASCII) $O Format (ASCII) $B (binary) For matrix data formats (ASCII) see chapt. 15. 6HSDUDWRU Blank Semicolon Tab For data export to a data base or spreadsheet program the $OFormat is recommended (separator: semicolon). 9DOXH IRU GLDJRQDO Default: 0; enter constant value for diagonal matrix. The internal traffic for each zone is not considered. 'LVSOD\ DFWLYH ]RQHV RQO\ If option is active, the number of rows and columns in the indicator matrix which is to be generated is reduced to active zones. &DOFXODWH RQO\ UHODWLRQV ZLWK 2' PDWUL[ ! If option is active, only O-D relations with demand > 0 are considered. O-D relations with demand = 0 are given the output value = 0 in the indicator matrix.
7-29
5RXWH FKRLFH FULWHULRQ IRU URXWH VHDUFK The following are available t0 tCur Distance AddVal1..3 Impedance o without routes from assignment Route with minimal impedance for Prt-TSys according to current impedance function; use routes from assignment The following options are available if the routes from assignment are used i.e. all routes for each O-D relation: PLQLPDO LPSHGDQFH: the route with the lowest impedance is used PD[LPXP LPSHGDQFH: the route with the highest impedance is used. 0HDQ RYHU URXWHV weighting: the output value is the mean of all routes. 0HDQ RYHU URXWH YROXPHV weighting: the output value is the mean of all routes weighted with the volume. The route with the lowest impedance is determined for relations for which no routes were calculated during assignment. 2XWSXW LQGLFDWRU GDWD An indicator is calculated for every O-D relation: ,QGLFDWRU Time_0 Time_cur Distance Speed_0 Speed_cur AddValue1..3 free-flow travel time t0 travel time tCur in loaded network length mean free flow speed v0 mean speed vCur in loaded network sum of AddValue for best route Route with shortest free flow travel time; Route with shortest travel time in loaded network; Route with shortest length; Route with minimum AddValue;
6XP XS YDOXHV IURP The indicator can include values from origin connectors, links, turning relations and destination connectors.
7-30
3U7 DVVLJQPHQW DQDO\VLV

Calculation of correlation between the current assignment result and counted volumes. Prerequisites: AddValue_Link data containing counted volumes. From the assignment result either the total volume or volumes of demand segments can be considerd.
&$/&8/$7(PHQX 357 $66,*10(17$1$/<6,6 6WDWLVWLFDO DQDO\VLV RI 3U7 DVVLJQPHQW GLDORJ
Select demand segment(s) to be considered (assignment result required). Select AddVal1, 2 or 3 for comparison. VISUM will immediately update the dispayed values when settings are modified..
At least 2 AddVal-Link values > 0 need to be available. In case of 2 values > 0 the correlation coefficient is -1 or 1. For 3 or more AddVal-Link values > 0 the correlation coefficient is displayed with 4 decimal places. The counted value of the link needs to be different from the volume that has been calculated for the link. Counted values may not be the same for all links.
7-31
If there is no assignment result available for a selected demand segment no correlation coefficient will be displayed. From the value of the correlation coefficient one cannot determine whether all or only some AddValue data are greater (or smaller) than the calculated volumes.
2XWSXW SDUDPHWHUV 1XPEHU Number of links with AddVal > 0. $GG9DOXHV VXP XS WR Total counted volume (selected AddVal). $VVLJQHG OLQN YROXPH VXP XS WR Total calculated volume (assignment result of links with AddVal > 0) for selected demand segments. &RUUHODWLRQ FRHIILFLHQW Ratio AddVal/calcuate volume; should be closed to 1. Range of values: -1 .. 1, where -1: AddValue opposed to calculated volume 0: no correlation (randomly) +1: very good correlation 6WDQGDUG GHYLDWLRQ Degree of deviation (fits best if = 1.0). 0HDQ GHYLDWLRQ RI DEVROXWH YDOXHV Mean difference between counted and calculated volumes. 1
D
( a ) =
L =1
=L 8 L / 1
0HDQ GHYLDWLRQ RI DEVROXWH YDOXHV LQ Mean deviation of absolute values in % according to 1

S
( ) = L
p
=1
1 8 L / =L / 1 * 100
6TXDUH URRW HUURU Significant differences between counted and calculated volumes have a higher impact according to 1
( ) = ( =L 8 L ) 2 / 1 1/ 2
L =1
where:
Z = Counted value, U = Calculated volume, N = Number of links with AddVal > 0
7-32
PuT Assignment procedures
3X7 $VVLJQPHQW SURFHGXUHV
For PuT assignment, VISUM offers five different procedures which differ in the required input data, computing time, and the accuracy of results: TSys-based procedure, Line-based procedure, 1 timetable-based procedure, 2
nd rd st
timetable-based procedure,
3 timetable-based procedure.
The flow bundle analyses and especially the connection list are very helpful for understanding the results (PUT-RELATIONS Type CONNECTIONS in the LISTINGS menu).
7-33
7UDQVSRUW V\VWHPEDVHG SURFHGXUH

The transport system-based assignment procedure calculates exactly one route between each source and target zone, which consists of one source connection and one target connection for the PuT as well as of links and turning relations, which are valid for a PuT transport system. Transfers are changes of transport system which are considered in the route search in form of a time supplement. t-PuTSys is considered for links. A transport system change can only take place at stops, not at nodes. At stops, at which a transport system change is necessary, a transfer wait time penalty TP is assigned. TP = node type-specific time penalty + penalty per each transfer. At stops, at which no turning relation for the PuT transport system is defined between the links, the time penalty TP is also assigned, if the option &RQVLGHU WXUQLQJ SURKLELWLRQV is active.
7-34
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7V\VEDVHG %DVLF GLDORJ %DVLF Specify basic parameters for transport system-based assignment.
2ULJLQ ]RQHV Restricts the calculation to the demand of selected origin zones i.e. to one row of the O-D matrix. &DOFXODWH DVVLJQPHQW If button is active , new PuT routes are searched and loaded. &DOFXODWH LQGLFDWRU PDWULFHV If button is active , indicator matrices selected under ,QGLFDWRU 0DWULFHV are calculated.
7-35
3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7V\VEDVHG 6HDUFK GLDORJ 6HDUFK Defines parameters for transport system-based route search.
7UDQVIHUV 0D[ QXPEHU: maximum permitted number of transfers for a route from origin zone to destination zone. 3HQDOW\ SHU WUDQVIHU: for the connection search the impedance of a connection is increased by a fixed transfer penalty [min] for each transfer. %ORFN FRQQHFWRUV ! :DONLQJ OLQNV This option is used to decide if a walking link is or is not permitted to be a possible first route section after the origin connector or a last route section before the destination connector in the route search. &RQVLGHU WXUQLQJ SURKLELWLRQV This option defines whether the existing turning prohibitions in the network are to be considered or ignored.
7-36
8VH RQO\ 3X7 OLQH QHWZRUN This option defines whether the total number of valid links and turning relations per transport system network or only the line network is to be considered in the transport system-based route search. 8VH OLQH VHOHFWLRQ This option is used to select sublines for the assignment. /LQH VHOHFWLRQ EXWWRQ The current settings are only valid if the option 8VH OLQH VHOHFWLRQ is active. The highlighted lines are considered. Select lines by clicking and holding down <> to select a block or <Ctrl> to select single lines. .
1RGH W\SHVSHFLILF SDUDPHWHUV IRU WUDQVSRUW V\VWHP FKDQJHV For each node type, a transfer penalty can be defined for transport system changes, if 7UDQVIHUV DUH SHUPLWWHG. 0RGLI\ EXWWRQ The attributes 7UDQVIHUV SHUPLWWHG and 7UDQVIHU WLPH SHQDOW\ can be modified for selected node types.
7-37
/LQHEDVHG SURFHGXUH

The line-based procedure considers the line network and only uses timetables for determining mean wait times i.e. the co-ordination of the timetable is not considered. The wait time at the departure stop and the transfer wait time are regarded as a function of the line's headway (e.g. factor 0.5 results in transfer wait time = mH).
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
G
%DVLF
If the line-based assignment is to be calculated for several demand segments, then the DSegs must belong to the same mode. 3DUDPHWHUV DVVLJQPHQW SURFHGXUH /LQHEDVHG %DVLF GLDORJ Set basic parameters for line-based assignment.
G
7-38
7LPH SHQDOWLHV if the unit (h or min or s) is not explicitly specified, VISUM uses the currently specified time format (7LPH IRUPDW under OPTIONS in the EXTRAS menu).
$VVLJQPHQW WLPH LQWHUYDO Only parts of the timetable and traffic demand are considered for assignment which lie within the assignment time interval. 2ULJLQ ]RQHV Restricts the calculation to the demand of selected origin zones i.e. to one row of the O-D matrix. &DOFXODWH DVVLJQPHQW If button is active , a new assignment is carried out. &DOFXODWH LQGLFDWRU PDWULFHV If button is active , indicator IndicatorMatrices are calculated. matrices selected under
3URFHGXUH Procedure1: Rounding as in DOS, i.e. times are rounded from seconds to whole minutes. Procedure 2: gives the same results as VISUM 6 Procedure 3: improved calculation of indicators Procedure 4: the maximum iteration depth of the route section permutation has been raised from 5 to 30 steps. 7LPH LQWHUYDOV IRU GHWHUPLQDWLRQ RI WKH PHDQ KHDGZD\ The mean headway (mH) of a line is calculated from the number of departures within a time interval, e.g. mH = 20 min with 3 departures in 1 hour, since 60 : 3 = 20. For the line-based procedure the mH of every line is calculated for the specified time interval (max. 10 time intervals). For every time interval, the mean headway of the time interval is used to carry out a route search, a route choice, and a route split. If less than 2 times are specified, the assignment time interval is used. 1RGH W\SHVSHFLILF VHWWLQJV The settings apply to route search and route split: Transfers permitted: specify if transferring at stops of node type is permitted. Transfer time penalty: stop type-specific penalty which increases the impedance of a route with every line transfer. 0RGLI\ EXWWRQ IRU VHOHFWHG QRGH W\SHV Modifies transfer attributes for selected node types.
7-39
3DUDPHWHUV DVVLJQPHQW SURFHGXUH /LQHEDVHG 6HDUFK GLDORJ 6HDUFK Specify parameters for determination of PuT routes:
0D[ 1R RI WUDQVIHUV Maximum permitted number of transfers for a route from origin zone to destination zone. %ORFN FRQQHFWRUV ! :DONLQJ OLQNV This option is used to decide if a walking link is or is not permitted to be a possible first route section after the origin connector or a last route section before the destination connector in the route search. 8VH OLQH VHOHFWLRQ Option: select sublines for assignment. 0RGLI\ OLQH VHOHFWLRQ EXWWRQ The highlighted lines are considered. Select lines by clicking and holding down <> to select a block or <Ctrl> to select single lines.
7-40
3DUDPHWHUV IRU VHDUFKLQJ IRU DOWHUQDWLYH URXWHV The route search searches for the route between two traffic zones with the lowest impedance with using a best-route algorithm. The impedance considers the access and egress times the mean origin wait time at the departure stop in-vehicle times the walking time for each transfer walking link the mean transfer wait time and transfer penalties consisting of the time penalty per node type of the transfer stop and the time penalty for the generation of alternative routes. The mean wait times (wait time at departure stop, transfer wait time) depend on the mean headway (mH) of the PuT-line to be boarded and the wait time factor: mean wait time at departure stop = wait time factor mH mean transfer wait time = wait time factor mH

Different transfer penalties and wait time factors may result in deviating routes. Depending on the specifications of the user, up to 10 best-route searches with different penalties and wait time factors can be carried out to determine not only one, but several alternative routes for each relation. 3DUDPHWHU IRU SHUPXWDWLRQ RI URXWH VHJPHQWV If several alternative route sections (direct lines without transfers or walking links) exist between two stops, only the route sections are considered for permutation, to which the following applies: PD[ URXWH VHFWLRQ WLPH PLQ 56HFWLRQ WLPH IDFWRU FRQVWDQW WLPH
7-41
3DUDPHWHUV DVVLJQPHQW SURFHGXUH /LQHEDVHG &KRLFH GLDORJ &KRLFH Specify parameters for selecting found routes.
All routes found by the route search procedure for a O-D relation and not deleted are evaluated by the route splitting procedure. 0D[LPXP SHUPLWWHG LPSHGDQFH Routes with a relatively high impedance (e.g. long journey time) are not attractive and can be eliminated by the route splitting procedure. To do this, the maximum permitted impedance for a connection must be specified in dependence on the minimum impedance for each relation. A route is not considered by the route splitting procedure if FXUUHQW LPSHGDQFH ! PLQLPXP LPSHGDQFH IDFWRU FRQVWDQW WLPH 0D[LPXP SHUPLWWHG QXPEHU RI WUDQVIHUV Routes with a relatively high number of transfers are not attractive and can be eliminated by the route splitting procedure. To do this, the maximum permitted number of transfers for a connection must be specified in dependence on the minimum number of transfers for each relation. A route is not considered by the route splitting procedure if FXUUHQW QXPEHU RI WUDQVIHUV RI URXWH ! PLQLPXP 17FRQVWDQW 17
$VVLJQPHQW SURFHGXUH /LQHEDVHG 'HPDQG VHJPHQWV GLDORJ This tab is only visible if several PuT demand segments have been 'HPDQG selected. VHJPHQWV
If the line-based assignment is to be calculated for several demand segments, then the DSegs must belong to the same mode. ,PSHGDQFH SDUDPHWHUV Specifies, whether individual or unified search parameters are to be used for each demand segment in route search. 6SOLW SDUDPHWHUV Specifies, whether individual or unified split parameters are to be used for each demand segment in route split. 'HPDQG VHJPHQW IRU LQGLFDWRU PDWULFHV Select demand segment. The split parameters of this demand segment are used for the calculation of indicators.
7-43
$VVLJQPHQW SURFHGXUH /LQHEDVHG ,PSHGDQFH GLDORJ ,PSHGDQFH Parameters for the distribution of demand over routes.
,PSHGDQFH RI D URXWH The impedance of a route results from the perceived journey time and the fare; a specific evaluation factor can be considered for both 3-7 and IDUH. 3HUFHLYHG MRXUQH\ WLPH The perceived journey time PJT has the unit [min] and consists of the following times, for which a time-specific factor can be considered: Access time factor, E Origin wait time (=wait time factor (mH) ) factor, In-vehicle time factor subline AddValue, Egress time factor, Walking time factor, NumTransfers factor [min], E mean transfer wait time (=wait time factor (mH) ) factor and Transf.Penalty by NodeType factor.
7-44
By using the subline AddValue for the in-vehicle time, line-specific features (preference to tram over bus) can be considered. 2ULJLQ ZDLW WLPH 7UDQVIHU ZDLWLQJ WLPH Origin wait time and transfer waiting time result from the mean headway of the line, which the passenger boards at the origin or the transfer stop. (See Chapter 2) $VVLJQPHQW SURFHGXUH /LQHEDVHG 6SOLW3URFHGXUH GLDORJ The distribution of traffic demand trips over individual routes 6SOLW depending on impedance is carried out according a distribution SURFHGXUH model (see Chapter 2.5.5). There are four different distribution models: 5 5 8
L
Kirchhoff Logit BoxCox Lohse Impedance of a route i minimum impedance of all routes of a relation Utility of a route distribution parameters
PLQ
7-45
.LUFKKRII
/RJLW
7-46
%R[&R[
/RKVH
7-47
7LPHWDEOHEDVHG SURFHGXUH
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7LPHWDEOH %DVLF GLDORJ Specify basic parameters for timetable-based assignment. %DVLF
$VVLJQPHQW WLPH LQWHUYDO Only parts of the timetable and traffic demand are considered for assignment which lie within the assignment time interval. 2ULJLQ ]RQHV Restricts the calculation to the demand of selected origin zones i.e. to one row of the O-D matrix. &DOFXODWH DVVLJQPHQW If button is active , a new assignment is carried out. &DOFXODWH LQGLFDWRU PDWULFHV If button is active , the selected indicator matrices are calculated.
3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7LPHWDEOH 6HDUFK GLDORJ 6HDUFK Specify parameters for the determination of PuT connections.
6HDUFK,PS IDFWRU -7 >PLQ@ WLPH SHQDOW\ QXPEHU RI WUDQVIHUV IDFWRU ,PS76\V The search uses an impedance which considers the journey time, the number of transfers and transport system-specific fare supplements. The search impedance defined here differs from the impedance used by the connection split procedure. ImpTSys 7UDQVSRUW V\VWHPVSHFLILF LPSHGDQFHV GLDORJ ER[
7-49
,PSNP >IDUH@ The TSys-specific km fare is multiplied by the number of km covered in the TSys. &RQVW VXSSOHP The TSys-specific fare supplement can be considered for each route section or for the whole connection. 6XSSOHPHQW SHU URXWH VHFWLRQ The specified supplement can be considered for each route section used by the transport system or once for the whole route. $ FRQQHFWLRQ LV GHOHWHG LI A connection found in the search exceeding one of the specified maximum values is deleted. 6HDUFK,PS Connections with a very high search impedance are not attractive and can be eliminated. To do this, the maximum permitted search impedance for a connection must be specified in dependence on the minimum search impedance of a connection for each relation. A connection is deleted if VHDUFK LPSHGDQFH RI WKH FRQQHFWLRQ ! PLQLPXP 6HDUFK,PS FRQVWDQW 1XPEHU RI WUDQVIHUV Connections with many transfers are not attractive and can be eliminated. To do this, the maximum permitted number of transfers for a connection must be specified in dependence on the minimum number of transfers of a connection for each relation. A connection is deleted if QXPEHU RI WUDQVIHUV ! PLQ QXPEHU RI WUDQVIHUV FRQVWDQW 17 -RXUQH\ WLPH Connections with very long journey times are not attractive and can be eliminated. To do this, the maximum permitted journey time for a connection must be specified in dependence on the minimum journey time of a connection for each relation. A connection is deleted if MRXUQH\ WLPH RI FRQQHFWLRQ ! PLQLP MRXUQH\ WLPH IDFWRU FRQVWDQW WLPH
7-50
0D[ 1R RI WUDQVIHUV Maximum permitted number of transfers for a connection from origin zone to destination zone. %ORFN FRQQHFWRUV ! :DONLQJ OLQNV This option is used to decide if a walking link is or is not permitted to be a possible first route section after the origin connector or a last route section before the destination connector in the route search. 8VH OLQH VHOHFWLRQ Option: select sublines for assignment. /LQH VHOHFWLRQ EXWWRQ The highlighted lines are considered. Select lines by clicking and holding down <> to select a block or <Ctrl> to select single lines 1RGH W\SHVSHFLILF WLPHV IRU WUDQVIHUV For every node type, a minimum transfer time and a maximum transfer wait time can be specified which will be considered for transfers at stops of the respective type for the connection search. PLQ WUDQVIHU WLPH The minimum transfer time specifies the minimum time required for transfers between arrival and departure. For a minimum transfer time of, say, 10 min and time of arrival 6:48 a.m., only connections departing at 6:58 a.m. or later can be reached. PD[ WUDQVIHU ZDLW WLPH The maximum transfer wait time indicates the maximum time for a stay at a transfer stop. For a maximum transfer wait time of, say, 60 minutes and time of arrival 6.48 a.m., departures after 7:48 a.m. are not considered. 0RGLI\ EXWWRQ IRU VHOHFWHG QRGH W\SHV Modifies transfer attributes for selected node types.
7-51
3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7LPHWDEOH &KRLFH GLDORJ &KRLFH Specify parameters for the selection of found connections.
All routes found by the route search procedure for a O-D relation and not deleted are evaluated by the route splitting procedure in two steps. $ FRQQHFWLRQ LV GHOHWHG LI Connections with a very high impedance are not attractive and can be eliminated. To do this, the maximum permitted impedance for a connection must be specified in dependence on the minimum impedance of a connection for each relation. A connection is deleted, if 6HDUFK,PSHGDQFH RI D FRQQ ! PLQ 6HDUFK,PS IDFWRU FRQVWDQW YDOXH The impedance applied here corresponds to the 6HDUFK,PS specified in the 6HDUFK tab.
7-52
)RU DOO UHPDLQLQJ FRQQHFWLRQV D FRQQHFWLRQ LV GHOHWHG LI The second stage of evaluation of found connections comprises two conditions: a connection is deleted, if it fulfils both conditions. Attention: the connection is not deleted, if it has the minimum value for the other condition. 1XPEHU RI WUDQVIHUV Connections with many transfers are not attractive and can be eliminated. To do this, the maximum permitted number of transfers for a connection must be specified in dependence on minimum number of transfers of connection for each relation. A connection is deleted, if QXPEHU RI WUDQVIHUV ! PLQ QXPEHU RI WUDQVIHUV QXPEHU RI WUDQVIHUV -RXUQH\ WLPH Connections with very long journey times are not attractive and can be eliminated. To do this, the maximum permitted journey time for a connection must be specified in dependence on the minimum journey time of a connection for each relation. A connection is deleted, if MRXUQH\ WLPH RI FRQQ ! PLQLPXP MRXUQH\ WLPH IDFWRU FRQVWDQW WLPH 1R FRQQHFWLRQ ZLWKLQ WLPH LQWHUYDO ! XVH HDUOLHVW SRVVLEOH FRQQHFWLRQ For low service frequencies it is possible that there are no departures from all connected stops of a zone within an assignment time interval. o If option is not active, the traffic demand of this zone is not assigned. If option is active, the traffic demand is assigned to the earliest possible departure time after the assignment time interval.
7-53
$VVLJQPHQW SURFHGXUH 7LPHWDEOH 'HPDQG VHJPHQWV GLDORJ This tab is only visible if several PuT demand segments have been 'HPDQG selected: VHJPHQWV
'HPDQG VHJPHQW IRU LQGLFDWRU PDWULFHV Select demand segment. The split parameters of this demand segment are used for the calculation of indicators.
7-54
$VVLJQPHQW SURFHGXUH 7LPHWDEOH ,PSHGDQFH GLDORJ ,PSHGDQFH Parameters for the distribution of demand over connections.
The distribution of a relations trips over the found connections is based on a decision model (see Chapter 2), which includes the perceived journey time and the fare of a connection and compares the desired departure time of the passengers with the available departure time. ,PSHGDQFH RI D URXWH Imp = PJT factor3-7 + fare factor)DUH + T late late T factor T
early
factor T
early
The factors are used to weight the time components and the number of transfers. By using the subline AddValue for the journey time, linespecific features (e.g. preference to tram over bus) can be considered.
7-55
3HUFHLYHG MRXUQH\ WLPH 3-7 The perceived journey time of a connection results from: in-vehicle time IDFWRU VXEOLQH $GG9DOXH + access time IDFWRU + egress time IDFWRU + walking time IDFWRU origin wait time IDFWRU + transfer waiting time IDFWRU + number of transfers IDFWRU 7KH RULJLQ ZDLW WLPH 2:7 is the same for all connections of an O-D pair, is calculated from the service frequency of all connections using the following formula: OWT = A (assignment time interval/service frequency)
E
with A = 0.5 and E = 1 the origin wait time corresponds to half the mean headway. with A = 1.5 and E = 0.5 a root function is created which assumes that passengers have better knowledge of timetables in case of low service frequency.
7LPH JDS 'HOWD7 7 7 is the absolute time gap between the desired departure time (or the desired departure time interval) and the actual departure time of a connection. The system also distinguishes whether the actual departure takes place before or after the desired departure time. T
early
:=
{ {
desired dep.Time actual dep.T 0 actual dep.Time desired dep.T 0
if actual < desired else if actual > desired else
late
:=
([DPSOH For the time interval [6:00;7:00] 'HSDUWXUH 5:30 6:00 6:40 7:00 7:10 7 30 0 0 0 10 7 30 0 0 0 0
HDUO\
7 0 0 0 0 10
ODWH
7-56
&RQVLGHU FRQQHFWLRQV ZLWK 7 ! LI DW OHDVW RQH FRQQHFWLRQ ZLWK 7 H[LVWV o Option not active: only connections which depart within this time interval are available to passengers within a time interval of the temporal demand. Option active: all connections which depart within the assignment time interval are available to passengers within a time interval of temporal demand. $VVLJQPHQW SURFHGXUH 7LPHWDEOH 6SOLW3URFHGXUH GLDORJ 6SOLW SURFHGXUH
The distribution of traffic demand trips over individual routes depending on impedance is carried out according a distribution model (see Chapter 2.5.5). There are four different distribution models: Kirchhoff Logit BoxCox Lohse
7-57
5 5 8
Impedance of a route i minimum impedance of all routes of a relation Utility of a route distribution parameters
PLQ
,QGHSHQGHQFH The independence of a connection shows whether it is possible for potential passengers to choose adjacent connections. Departure and arrival time and optionally also the qualitative indicators of SHUFHLYHG MRXUQH\ WLPH and IDUH are considered If the option 8VH LQGHSHQGHQFH is active, then independence = 1 There is no impact from other connections. independence = 0 Strong impact (passenger flow) due to other connections.
If PJT and fare are to be considered in the calculation of independence, then a weighting factor (0.0000-1.0000) can be entered for the impact of the qualitative indicators.
7-58

The 2 timetable-based procedure assumes that passengers first inform themselves about PuT-services with a passenger information system. From all offered connections within a given time interval they choose the connection which in terms of time, journey time, and number of transfers seems best. Since the timetable-based procedures 1 and 2 only differ in the distribution of passenger trips over found connections, the parameters for 6HDUFK '6HJ and &KRLFH are identical.
nd
&$/&8/$7(PHQX 352&('85( 2SHUDWLRQV with current settings and 3DUDPHWHUV button
3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7LPHWDEOH %DVLF GLDORJ Specify basic parameters for timetable-based assignment. %DVLF
7-59
$VVLJQPHQW WLPH LQWHUYDO Only parts of the timetable and traffic demand are considered for assignment which lie within the assignment time interval. 2ULJLQ ]RQHV Restricts the calculation to the demand of selected origin zones i.e. to one row of the O-D matrix. &DOFXODWH DVVLJQPHQW If button is active , a new assignment is carried out. &DOFXODWH LQGLFDWRU PDWULFHV If button is active , indicator matrices are calculated according tu current setting in the ,QGLFDWRU0DWULFHV tab. 3URFHGXUHV Procedure 1 provides the same results as VISUM version 6. Procedure 2 provides better indicator data. 3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7LPHWDEOH 6HDUFK GLDORJ 6HDUFK Specify parameters for the determination of PuT connections.
7-60
1XPEHU RI GHSDUWXUHV ZLWKLQ DVVLJQPHQW WLPH LQWHUYDO To determine the connections of a zone, the timetable-based procedure carries out a best-route search for different departure times at departure stops. The departure times at the departure stops result from the departures (max. 1/min, thus max. 1440/day) of the PuT-lines from the connected stops. 6KDUH: to reduce computing time, the number of departure times from departure stops can be reduced by specifying a percentage < 100. In this case, only part of the departure times is evaluated which changes the result of the assignment. 0LQ GHSDUWXUHV (value range 1-1440): to guarantee that a minimum number of departures is always calculated for zones with few departures, a minimum number of departures to be considered can be specified. For zones where this minimum number is larger than the actual number of departures (low service frequency), the actual number of departures is considered. 0D[ GHSDUWXUHV (value range 1-1440): by specifying a maximum number of departures, the number of departure times at departure stops for zones with many departures can be further reduced.
If only part of the departure times at departure stops (share < 100%) is considered in the connection search, the assignment and the indicator calculation does not include all connections, but only randomly selected connections. Since not all connections must be determined, computing time is reduced. The result will differ from the result of a full search, and the quality of the results depends on traffic demand. The restriction has a smaller influence in case of regular, fixed-rhythm headway service than for networks with few, irregular services. The correct calculation of service frequency is only possible if all departure times at departure stops are considered.
Example:Share = 30%, MinDepartures = 5, MaxDepartures = 20 actual number of departures 3 6 10 30 100 analysed departures from departure stop 3 5 5 10 20
For restricted search , backwards correction should be activated.
7-61
7UDQVIHUV 0D[ QXPEHU: maximum permitted number of transfers for a connection from origin zone to destination zone. 3HQDOW\ SHU WUDQVIHU: for the connection search the impedance of a connection is increased by a fixed transfer penalty for each transfer. %ORFN FRQQHFWRUV ! ZDONLQJ OLQNV This option is used to decide if a walking link is or is not permitted to be a possible first partial route after the origin connector or a last partial route before the destination connector in the route search. &RUUHFWLRQ EDFNZDUGV If this option is active, a backward search based on the arrival time at the destination stop in the destination zone is conducted to find a later departure of the same line or a different line for every part of the found connection. This reduces travel and transfer times. In this way, a better connection with identical stops (origin, all transfer stops, destination) for the calculated arrival time may be found which has a later departure time. VISUM then uses the connection found by the backward correction instead of the connection found originally. 8VH OLQH VHOHFWLRQ Option: select sublines for assignment. /LQH VHOHFWLRQ EXWWRQ The highlighted lines are considered. Select lines by clicking and holding down <> to select a block or <Ctrl> to select single lines. 1RGH W\SHVSHFLILF WLPHV IRU WUDQVIHUV For every node type, a minimum transfer time and a maximum transfer wait time can be specified which will be considered for transfers at stops of the respective type for the connection search. PLQ WUDQVIHU WLPH The minimum transfer time specifies the minimum time required for transfers between arrival and departure. For a minimum transfer time of, say, 10 min and time of arrival 6:48 a.m., only connections departing at 6:58 a.m. or later can be reached. PD[ WUDQVIHU ZDLW WLPH The maximum transfer wait time indicates the maximum time for a stay at a transfer stop. For a maximum transfer wait time of, say, 60 minutes and time of arrival 6.48 a.m., departures after 7:48 a.m. are not considered. 0RGLI\ EXWWRQ IRU VHOHFWHG QRGH W\SHV Modifies transfer attributes for selected node types.
3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7LPHWDEOH &KRLFH GLDORJ Specify parameters for the selection of found connections. &KRLFH
All routes found by the route search procedure for a O-D relation and not deleted are evaluated by the route splitting procedure. -RXUQH\ WLPH Connections with very long journey times are not attractive and can be eliminated. To do this, the maximum permitted journey time for a connection must be specified in dependence on the minimum journey time of a connection for each relation. A connection is deleted, if -RXUQH\ WLPH RI FRQQ ! PLQLPXP MRXUQH\ WLPH IDFWRU FRQVWDQW WLPH 1XPEHU RI WUDQVIHUV Connections with many transfers are not attractive and can be eliminated. To do this, the maximum permitted number of transfers for a connection must be specified in dependence on minimum number of transfers of connection for each relation. A connection is deleted if FXUUHQW 1U RI WUDQVIHUV ! PLQ 17 IDFWRU 1U RI WUDQVIHUV
7-63
1R FRQQHFWLRQ ZLWKLQ WLPH LQWHUYDO ! XVH HDUOLHVW SRVVLEOH FRQQHFWLRQ For low service frequencies it is possible that there are no departures from all connected stops of a zone within an assignment time interval. o If option is not active, the traffic demand of this zone is not assigned. If option is active, the traffic demand is assigned to the earliest possible departure time after the assignment time interval. $VVLJQPHQW SURFHGXUH 7LPHWDEOH 'HPDQG VHJPHQWV GLDORJ 'HPDQG VHJPHQWV This tab is only visible if several PuT demand segments have been selected:
'HPDQG VHJPHQW IRU LQGLFDWRU PDWULFHV Specifies, whether individual or unified split parameters are to be used for each demand segment in route split. The split parameters of the selected demand segment are used for the calculation of indicators.
7-64
$VVLJQPHQW SURFHGXUH 7LPHWDEOH ,PSHGDQFH GLDORJ ,PSHGDQFH Parameters for the distribution of demand over routes.
The distribution of a relations trips over the found connections is based on a decision model (see Chapter 2), which includes the perceived journey time and the fare of a connection and compares the desired departure time of the passengers with the available departure time. Impedance of a connection: Imp = PJT / U factor 3-7 + fare factor IDUH The factors are used to weight the time components and the number of transfers. By using the subline AddValue for the journey time, linespecific features (preference to tram over bus) can be considered.
7-65
3HUFHLYHG MRXUQH\ WLPH 3-7 The perceived journey time of a connection results from: in-vehicle time IDFWRU VXEOLQH $GG9DOXH + access time IDFWRU + egress time IDFWRU + walking time IDFWRU origin wait time IDFWRU + transfer waiting time IDFWRU + number of transfers IDFWRU 7KH RULJLQ ZDLW WLPH 2:7 is the same for all connections of an O-D pair, is calculated from the service frequency of all connections using the following formula: OWT = A (assignment time interval/service frequency)
E
with A = 0.5 and E = 1 the origin wait time corresponds to half the mean headway. with A = 1.5 and E = 0.5 a root function is created which assumes that passengers have better knowledge of timetables in case of low service frequency.
7HPSRUDO XWLOLW\ 8 Since both the total required time and the departure time are important for the evaluation of a PuT-connection, a function is introduced which describes the temporal utility of a connection.
Ui=e
-(
VF) 2 / 2
The temporal utility of a connection depends on the desired departure time, specified by temporal demand distribution pattern 7: time difference between desired departure time and actual departure time and 9(: sensitivity factor for early/late departure
&RQVLGHU FRQQHFWLRQV ZLWK 7 ! LI DW OHDVW RQH FRQQHFWLRQ ZLWK 7 H[LVWV o Option not active: only connections which depart within this time interval are available to passengers within a time interval of the temporal demand. Option active: all connections which depart within the assignment time interval are available to passengers within a time interval of temporal demand.
Time interval 9 - 10 10 - 11 11 - 12
Number of departures 2 0 1
Option is not active
Option is active
Consider all connections.
Two connections considered. All connections considered. One connection considered.
$VVLJQPHQW SURFHGXUH 7LPHWDEOH 6SOLW3URFHGXUH GLDORJ Parameters for the distribution of demand over routes. 6SOLW See Parameters assignment procedure: 7LPHWDEOH 6SOLW3UR SURFHGXUH FHGXUH dialog box and Chapter 2.5.3 Distribution models
,QGHSHQGHQFH The independence of a connection shows whether it is possible for potential passengers to choose adjacent connections. Departure and arrival time and optionally also the qualitative indicators of SHUFHLYHG MRXUQH\ WLPH and IDUH are considered If the option 8VH LQGHSHQGHQFH is active, then independence = 1 There is no impact from other connections. independence = 0 Strong impact (passenger flow) from other connections. If PJT and fare are to be considered in the calculation of independence, then a weighting factor (0.0000-1.0000) can be entered for the impact of the qualitative indicators.
7-67

The timetable-based procedure considers the exact departure and arrival times of all trips with PuT-lines. Timetable-based procedures are suitable for assignments and indicator calculations if a line network plan and a detailed timetable are available for the analyzed PuT-demand. They take the timetable coordination into account and thus ensure exact results of the indicator calculation. The timetable-based procedure 1 assumes that passengers have no knowledge of the timetable and arrive at the origin stop accidentally. At the origin stop they use the next available connection (e.g. dep. 7:00 a.m., arrv. 7:45 a.m.). A faster connection at a later departure time (e.g. dep. 8:00 a.m., arrv. 8:30 a.m.) is not considered since passengers will reach their destination faster if they use the next but longer connection rather than the later, faster connection.
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQV
3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7LPHWDEOH %DVLF GLDORJ ER[ %DVLF Specify basic parameters for timetable-based assignment: same as for timetable-based assignment 2. 3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7LPHWDEOH 6HDUFK GLDORJ 6HDUFK Specify parameters for the determination of PuT-connections (the same as for timetable-based assignment procedure 2). A full search is always carried out for the timetable-based procedure 2. )XOO VHDUFK IRU DOO GHSDUWXUHV This option allows to reduce the calculation time by limiting the possible number of departure times for each relation, for which connections are searched, within the assignment interval according to timetable.
7-68
Connections are searched for each O-D relation with a demand > 0 (passenger volume of the O-D relation and passenger distribution of the origin zone) in the partial interval, but not for each departure time. VISUM selects the departure times of the origin zone per relation at random; the actual demand in the partial interval as well as the number and frequency of departure times are considered. Generally, only so many departure times are searched for each O-D relation as there are passenger requests. For each O-D relation with a demand > 0 a connection is searched for each departure time; the number of passenger requests in the assignment interval and the passenger volume per partial interval are not considered. The complete search is recommended; the calculation time can be limited by the 0D[ GHSDUWXUHV switch, which is evaluated for each origin zone. 3DUDPHWHUV DVVLJQPHQW SURFHGXUH 7LPHWDEOH &KRLFH GLDORJ &KRLFH Specify parameters for the selection of found connections: same as for timetable-based assignment 2. $VVLJQPHQW SURFHGXUH 7LPHWDEOH 'HPDQG VHJPHQWV GLDORJ 'HPDQG VHJPHQWV This tab is only visible if several PuT demand segments have been selected (see 7LPHWDEOHEDVHG SURFHGXUH DQG ).
7-69

,QGLFDWRU PDWULFHV 3X7
Service indicators are calculated to carry out accessibility analyses for zones calculate the analyses for standardized assessment carry out impact analyses within the traffic planning process For every route/connection which is found by the VHDUFK, the following indicators can be determined, from which the indicators per O-D relation are derived: ,QGLFDWRUV FRPSXWHG E\ SURFHGXUH Journey time Ride time Access time Origin wait time In-vehicle time Transfer wait time Walking time (transfer walk links) Egress time Perceived journey time In-veh. time per PuTSys Journey distance Ride distance Length of access connector In-vehicle distance Direct distance Dist. covered walking for transfer Length of egress connector Distance covered in TSys TSys-Percentage of total dist. Journey speed Direct distance speed Number of transfers Service frequency Fares Impedance Number of tariff zones Number of tariff subzones Journey time equivalent (defined by the user) $EEUY JT RT AT OWT IVT TWT WT ET PJT TS JD RD AD IVD DD WD ED DS PS JV DV NT SF FA IMP TZ SZ AE 0 RZ BZ ZZ SZ FZ UZ GZ AZ ERZ TS RW BW ZW FW LW GW AW WS PS RV LV UH BH FA WI TG UT AE TSys Line TT1 TT2 TT3 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
*) Standard extensions of indicator matrix files (e.g. M*+RZ=MRZ) are grey-shaded.
7-70
Depending on the chosen search procedure there are different possibilities to reduce the indicators (Indic) of the connections to mean indicators (mIndic) for each relation: Weighting possibilities: Weighted with passengers:
NumConn
Line-based
Timetable-based
mIndic =
Indic i i =1
x passengers i
passengers
Weighted with Service frequency (SF):

NumConn
mIndic
Indic i x SF i i =1 SF
Equal weighting:
NumConn
Indic i i =1
mIndic =
numberofco nnections
mIndic= indicator for route with minimum impedance mIndic = indicator for connection with minimum equivalent journey time
The service frequency indicator SF does not refer to a particular connection, but to an O-D relation. For the timetable-based procedure, the service frequency results from the number of different arrival times. For the line-based procedure, the service frequency along with the transfer wait time can only be roughly estimated because the service frequency enters the calculation as an input value via the mean headway (mH) and thus via the transfer wait time.
7-71
&$/&8/$7(PHQX 352&('85(6 2SHUDWLRQ WDE Select 2SHUDWLRQ '6HJ and 3URFHGXUH enable 2SHUDWLRQ.
An indicator calculation can be carried out in two ways for one or several PuT demand segments: Indicator calculation without simultaneous assignment. Select ,QGLFDWRU0DWUL[ action and 3X7 procedure. The current assignment is not deleted. Indicator calculation with simultaneous assignment. Select $VVLJQPHQW action 3X7 procedure and activate the &DOFXODWH LQGLFDWRU PDWULFHV option in the %DVLF parameters tab. The current assignment is deleted.
2SHUDWLRQ JHQHUDWH 3X7LQGLFDWRU PDWULFHV Select 2SHUDWLRQ 'HPDQG VHJPHQWV and 3URFHGXUH, as applicable. 3DUDPHWHUV button: call up tabs %DVLF tab: possible restraints FromZone-ToZone Assignment time interval ,QGLFDWRU0DWUL[ tab: Activate indicators for output to matrix files Enter filename, VISUM will add particular extensions Select format and weighting (except TSys-based) Enter parameters for active indicators Confirm 2.. ([HFXWH button: start calculation
The ,QGLFDWRU0DWUL[ tab is identical for all PuT assignment procedures.
7-72
$VVLJQPHQW SURFHGXUH 7LPHWDEOH ,QGLFDWRU0DWULFHV WDE ,QGLFDWRU PDWULFHV
The dialog box contains other indicators; use the mouse to scroll through the complete list.
Depending on the size of the network the computing time for calculating indicators increases the files may become very large. )LOHQDPH for filename: the default path is copied from DIRECTORIES in the FILE menu. complete path: if the drive, directory, filename, and extension are entered, current path is ignored. ([W each PuT-indicator has a default file extension which can be modified (see also Table "Indicators computed by procedure"). 0HDQV RI WUDQVSRUW QXPEHU (for VISEM) Confirm default value 3. VISEM uses: 1 = pedestrians 2 = car passengers 3 = public transport, 4 = car drivers (including HGV) etc.
7-73
)RUPDW options (ASCII/binary, see chapt. 15) V-Format, Partial-V-Format, O-Format CSV (comma-separated values) Binary The data formats of matrix files are described in chapter 15 and 5. 6HSDUDWRUV options Blank Semicolon Tab CSV-Format with semicolon is recommended for exporting files into databases or spreadsheets. &RQILUP RYHUZULWLQJ If option is not active o, current indicator matrices with this name and respective file extension are overwritten without prompting. :HLJKWLQJ indicators computed per O-D relation are weighted for line-based assignment with passengers service frequency (SF estimated from meanHeadway) min. impedance route (route with minimum impedance). for timetable-based procedures: with passengers equal (SF = 1 per connection) min. journey time connection (conn. with min. equivalent JT) For relations without demand, VISUM uses 10000 for weighting with passengers i.e. an O-D matrix is not absolutely necessary. ,QGLFDWRU for every active indicator , an indicator matrix with the name specified for all indicator matrix files and the particular extension is saved on file in the selected format. For preset path call up FILE menu DIRECTORIES... command. 'HIDXOW if no connection is found for a relation, VISUM enters the default value. 0LQ 9DOXH and 0D[ 9DOXH for indicators < min. value, VISUM enters the min. value; and for indicators > max. value, VISUM enters the max. value. 'HF number of decimal places in matrix
G
7-74
Mouse click on the (TXLYDOHQW MRXUQH\ WLPH button opens the dialog box in which a formula for the calculation of a further indicator per OD relation can be defined. This calculation is based on PuTindicators which can be weighted differently.
3X7LQGLFDWRUV 7LPHV >PLQ@ Journey time JT = AT + SWT + IVT + TWT + WT + ET Time from origin zone to destination zone. Ride time RT = IVT + TWT + WT Time from origin stop to destination stop. Access time AT Time for access route from origin zone to origin stop. Wait time at dep. stop SWT Wait time at the departure stop in origin zone (only for line-based procedure, for both timetable-based procedures SWT = 0). In-vehicle time IVT Time in the vehicle including dwell times at stops without transfer times. Transfer wait time TWT Wait time at transfer stops. Walking time WT Walking time for transfers with walk links between two stops. Egress time ET Time for egress route from destination stop to destination zone. In-veh. time / PuTSys TS In-vehicle time per PuTSys. Perceived journey time PJT = f(AT, ET, SWT, TWT, IVT, WT) Perceived journey time.
6SHHGV >NPK@ Travel speed JV Quotient of journey time and journey distance. DirectDist.-speed DDV Quotient of journey time and direct distance.
7-75
'LVWDQFHV >P@ Journey distance JD = AD + IVD + WD + ED Covered distance from origin zone to destination zone. Ride distance RD = IVD + WD Covered distance from origin stop to destination stop. Access distance AD Length of access route from origin zone to origin stop. In-vehicle distance IVD Distance covered in vehicle without transfer walk links. WalkDist WD Length of transfer walk links (between two stops each). Egress distance ED Length of egress route from destination stop to destination zone. Direct distance DD Direct distance between origin and destination zone. Distance covered in TSys Distance covered per PuTSys. DS
Distance covered in TSys as percentage PS Distance covered in TSys as a percentage of the total in-veh. distance of the connection (derivated indicator).
)UHTXHQFLHV Number of transfers NT per connection: number of transfers between origin and destination stop. Service frequency [number of services] SF per O-D relation: Number of different arrival times for connections departing within the assignment time interval: Line-based: estimation based on mean headway mH Timetable-based: number of arrival times
7-76
2WKHUV Impedance IMP Impedance of a connection = f (perceived journey time, fares) Fare FA Fare for the ride (PuT) between origin and destination zone. Num Tariff zones Number of traversed tariff zones. TZ
Number Tariff subzones SZ Number of traversed tariff subzones. Journey time equivalent AE The unit of the equivalent journey time indicator is determined by the userdefined formula. Parameter settings for calculating the equivalent journey time from origin zone to destination zone, including wait time at departure stop inferred from service frequency (compare example):
7-77
2SHUDWRU Addition or subtraction can be specified. ,QGLFDWRU Specify PuT-indicator. ([S Positive and negative values are permitted as exponent. )DFWRU Indicator weighting factor for calculating equivalent journey time. 0LQ 9DOXH and 0D[ YDOXH For indicators < min. value, VISUM uses the min. value for the calculation; for indicators > max. value, VISUM uses the max. value. The unit depends on the unit of the respective indicator. ([DPSOH Note: SF stands for service frequency Assignment time interval TIV Estimated max. wait time Estimated wait time at dep. stop SWT = = = = = = = 120 min 10 min 1.5 1.5 1.5 16.4 /
TIV/SF 120/SF
120 / SF
SF
-0.5
16.4 SF
Wait times at departure stops determined from service frequency: SF 1 2 3 6 12 16.4 SF 16.4 min 11.6 min 9.5 min 6.7 min 4.7 min
-0.5
SWT 10.0 min 10.0 min 9.5 min 6.7 min 4.7 min
7-78
2' PDWUL[ IRU LQGLFDWRU FDOFXODWLRQ (all procedures) VISUM uses demand = 10000 if no O-D matrix is available or for O-D-relations without demand. :HLJKWLQJ RI LQGLFDWRUV VISUM does QRW ZHLJKW if the following have been selected the line-based procedure and PLQ ,PSHGDQFH URXWH or a timetable-based procedure and PLQ MRXUQH\ WLPH FRQQHFW. With this setting, VISUM uses the indicator values from the respective best route or connection for each relation determined according to the following criteria: Timetable 1: connection with minimum journey time PJT Timetable 2: connection with min. perceived journey time PJT Line-based: route with minimum impedance
:HLJKWLQJ with SDVVHQJHUV or HTXDO ZHLJKWLQJ: Example: indicator matrix *.MUH (number of transfers) For an O-D-relation, 3 connections are determined: Connection Volume NT Weighting equal with pass. 1 5000 1 2 2000 3 3 3000 2
1 1 5000
1 3 2000
1 2 3000
Indicator for O-D-relation with equal weighting weighting with passengers 2.0 = (1+3+2) : 3 1.7 = 1 5000 + 3 2000 + 2 3000 10000
7-79
Assignment report
$VVLJQPHQW UHSRUW
&$/&8/$7( $66,*10(175(3257 'LVSOD\ IRU WKH FXUUHQW QHWZRUN VWDWH
2XWSXW Procedure used for assignment by demand segment.
7-80
ENVIRONMENTAL IMPACT ANALYSIS
(19,5210(17$/ ,03$&7 $1$/<6,6
The (QYLURQPHQWDO LPSDFW DQDO\VLV add-on module is used to calculate the environmental impact - noise and pollutant emissions - caused by motorised traffic. The results can be displayed in both tabular and graphic form. In VISUM, four models for calculating environmental impact are available: 1RLVH,PPLV: noise calculation under consideration of immission parameters in accordance with 5/6 (guideline on noise reduction for roads by the Federal Minister for Traffic). 1RLVH(PLV: calculation of noise emission levels in accordance with 5/6 without considering immission parameters. 3ROOXWLRQ(PLV: calculation of pollution emission level in accordance with emission factors of the Federal Office for the Environment of Switzerland (BUS). 0/X6: calculation of air pollution emissions in accordance with 0/X6 (leaflet of the Society for Roads and Transport for air pollution near roads, section: roads without or few surrounding developments).
The VISUM environmental impact analysis also includes two interfaces to external pollution calculation programs for which VISUM determines link volumes: ,00,6/8)7 pollution diffusion program for calculating immissions caused by traffic (creator: IVU, Berlin/Freiburg). 0RELOHY "Measure-oriented calculation equipment for local pollution emissions of automobile traffic" developed for the Federal Office for the Environment (manufacturer: FiGE GmbH, Herzogenrath; licence: Federal Office for the Environment, Berlin).
8-1
General procedure
*HQHUDO SURFHGXUH
The general methodology applicable to all environmental calculation procedures is explained in brief below. Particularities of the individual calculation procedures are explained in detail in the subchapters.
(19,5210(17$/,03$&73$5$0(7(56LQ WKH &$/&8/$7(PHQX (QYLURQPHQWDO 3DUDPHWHUV %DVLF Specify basic parameters for environmental calculation procedures:
G
8-2
For particular parameters for Noise calculation see %DVLF tab, Pollutants calculation procedures see 3ROOXWDQWV tab.
General procedure
Environmental impact analysis
&DOFXODWLRQ EDVHG XSRQ The calculation of DOO environmental calculation procedures is based on private transport volume: 9ROXPH3U7>9HK@: volume values are taken over from assignment; YB&XU of a link and of a TSys results from WB&XU from the link type-specific CR-functions (compare assignment parameters). $GG9DOXHV: volume values are taken over from AddValues; YB&XU is determined from the CR function assigned to the link type.
)DFWRU P$'7 Specification of a factor for every global link type for converting the mean average daily traffic (P$'7) to applicable hourly values (normal hourly values). YDOLG VSHHG YDOXHV RQO\ LI Y&XU LV WR EH UHJDUGHG Specification of valid range for Y&XU for cars and HGV with the following consequences for the calculation: vMin is considered if vCur < vMin. vMax is considered if vCur > vMax.
5HDGLQJ DQG VDYLQJ HQYLURQPHQWDO SDUDPHWHUV Managing environmental calculation parameters in a *.upa file (binary format): (QYLURQPHQWDO SDUDPHWHUV under SAVE in the FILE menu. (QYLURQPHQWDO SDUDPHWHUV under OPEN in the FILE menu.
&$/&8/$7((19,5210(17$/,03$&7LQ WKH &$/&8/$7(PHQX 1RLVH,PPLV 1RLVH(PLV 3ROOXWLRQ(PLV 0/X6 The environmental impact is calculated on the basis of the selected procedure and is displayed in the respective output units.
,1,7,$/,=((19,5210(17$/,03$&7LQ WKH &$/&8/$7(PHQX Reset calculated environmental results to zero. Display calculated environmental impact graphically. Output calculated environmental impact (lists, attribute files).
8-3
Noise
1RLVH
To calculate noise volumes based on traffic volumes, VISUM offers the 1RLVH,PPLV and 1RLVH(PLV procedures. Both procedures are based on 5/6 (guideline on noise reduction for roads by the Federal Minister for Traffic). Both models are fairly simple, but are sufficient to identify relative variations, that is, how, where, and to what extent traffic-routing and road construction measures affect traffic volumes and, as a consequence, the noise situation of particular roads.
8-4
Noise
1RLVH(PLV SURFHGXUH This procedure determines the average emission level of "long and straight roads" in accordance with RLS-90. For the calculation of Lm,E in decibels, VISUM considers the following operations: Calculation of the average level /P using equation 5/6:

/P
0 S

= 373 , +10 lg[ 0(1+ 0082 , S)]
UHOHYDQWKRXUO\WUDIILFYROXPHFDUK@ UHOHYDQW+*9SURSRUWLRQLQSHUFHQWRIWRWDOWUDIILFDERYHWWRWDOSHUPLVVLEOHZHLJKW
In contrast to calculating pollution emissions, calculating noise is not carried out with reference to FURVVVHFWLRQV, but to GLUHFWLRQV.
Determination of correction factor '6WU2 for different road surfaces in accordance with WDEOH 5/6. VISUM keeps the correction factors listed in this table as an ASCII file rls.dat in the background. Determination of speed correction 'Y for permissible maximum speeds other than 100 km/h using HTXDWLRQ 5/6. Determination of correction factor '6WJ for inclinations and gradients using HTXD WLRQ 5/6.
The correction factor '( for taking absorption characteristics of reflecting areas into account is not calculated.
The final result for every active link is the emission level Lm,E which is calculated through an addition using HTXDWLRQ 5/6:
/P, ( = /P + 'Y + '6WU2 + '6WJ
8-5
Noise
1RLVH,PPLV SURFHGXUH This procedure determines the average immission level /P of "long and straight roads" (one-way roads) and "multi-lane roads" in accordance with RLS-90. The calculation is based on the final result /P( of the 1RLVH(PLV procedure: Calculation of an average level /P of a "long and straight road": Determination of the correction factor DV to take level variations due to distance and air absorption using HTXDWLRQ 5/6 into account. Determination of the correction factor '%0 to take level variations due to surface and meteorology absorption in accordance with HTXDWLRQ 5/6 into account. The emission level /P for every active link is finally calculated using HTXDWLRQ , 5/6 as an addition of the correction factors with the final result of the 1RLVH(PLV procedure /P(: /P / 'V '%0
P(
The correction factor '% which takes level variations due to topographical conditions and construction measures into account is not calculated here.
Determination of average level Lm of "multi-lane roads":
The average level for the FORVH RXWHU ODQH /PI and the IDU RXWHU LQQHU ODQH /PQ result from the calculation of /P for "long and straight roads using HTXDWLRQ 5/6 and are combined energetically using HTXDWLRQ RLS-90 for multi-lane roads: /P OJ > @
/PQ /PI
Because noise calculation in VISUM does not consider level variations due to topographical conditions, construction measures, and other reflections, the model corresponds to free and equal noise distribution in all directions on level ground.
8-6
Noise
/LQN DWWULEXWHV IRU 1RLVH FDOFXODWLRQV

Both noise calculation procedures require different input attributes. To understand these input attributes please refer to the explanations and illustrations in the *XLGH OLQHV RQ 1RLVH 3UHYHQWLRQ IRU 5RDGV 5/6. The output value 1RLVH is returned as a result. Activate SINGLE SELECT mode and LINK network object.
Select a link and call up 0RGLI\ 0RGLI\ OLQN 1RLVH
Or activate MULTI SELECT mode and LINK network object for modification of an input attribute of all (or all active) links.
8-7
Noise
1RLVH 1RLVH $WWULEXWH (PLV ,PPLV

X X
'HVFULSWLRQ HGV-proportion S (above 2,8 t total permissible weight) of total traffic [%]. Standard value: 0 Value range: 0 to 100 Lengthways link slant J in [%] for specifying correction factor '6WJ for inclinations and gradients where the following rules apply: D6WJ = 0,6 |g| -3 for |g| > 5% for |g| 5% D6WJ = 0 Standard value: 0 Value range: -50 to 50 For different road surface types, correction penalties are generated and added in accordance with 5/6 7DE. The respective data are stored in the parameters file rls.dat (see below). Standard value: 1 Value range: 1 to 5 Width of outer right-hand lane in [m].
HGV-% HGV-proportion (Input) Steep road inclination (Input)
Surface Surface type (Input)
Lane width (Input)
Noise-mH Arithmetical mean value of the height of the Noise immission height immission and emission source above (Input) ground on flat land in [m]. Standard value: 2,25 Value range: Real > 0 Center-Kerb DistanceMiddleVerge Distance between the middle of the road and the verge in [m]; for one-way roads, this corresponds to road width. Standard value: 3 Value range: Real > 0
8-8
Noise
1RLVH 1RLVH $WWULEXWH (PLV ,PPLV

X
'HVFULSWLRQ Distance between verge and immission place in [m]. Standard value: 25 Value range: Real > 0 1RLVH(PLV: mean emission level /P( of "long and straight roads" in [dB]. 1RLVH,PPLV: mean immission level /P of "long and straight roads" (one-way roads) or "multi-lane roads" in [dB].
Emis-Imm DistanceEmissImmiss (Input) Noise (Output)
3DUDPHWHUV ILOH rls.dat: FRUUHFWLRQ SHQDOWLHV SHU VXUIDFH W\SH

*Surface types permissible maximum speed * 30 km/h 40 km/h 50 km/h >= 60km/h * non-porous cast-asphalt, * asphalt concrete * Type 1 0 0 0 0 * porous cast-asphalt * Concrete * Type 2 1.0 1.5 2.0 2.0 * Paving with * level surface * Type 3 2.0 2.5 3.0 3.0 * other paving * * Type 4 3.0 4.5 6.0 6.0 * ZTV Beton 93 * Type 5 0 0 0 1.0 * ZTV Beton 93 * Type 6 0 0 0 -2.0 * Asphalt concrete 0/11 * Splittmastixasphalt * Type 7 0 0 0 -2.0 * Asphalt * Kornaufbau 0/11 * Type 8 0 0 0 -4.0 * Asphalt * Kornaufbau 0/8 * Type 9 0 0 0 -5.0 *
8-9
Noise
&DUU\LQJ RXW QRLVH FDOFXODWLRQV
Calculation of HGV proportion S, if this is not yet available as an attribute value. Modification of standard values for noise-specific link attributes, if necessary.
([DPSOH FDOFXODWLRQ IRU +*9 SURSRUWLRQ Read Car O-D matrix. Read HGV O-D matrix. Execute simultaneous assignment for &DU and +*9 (multiincremental, multi-equilibrium or multi-learning procedure). Calculate HGV proportions (via )RUPXOD under EDIT-MODIFY LINKS in MULTI SELECT mode):
(19,5210(17$/,03$&73$5$0(7(56LQ WKH &$/&8/$7(PHQX (QYLURQPHQWDO 3DUDPHWHUV %DVLF
8-10
Noise
&DOFXODWLRQ EDVHG XSRQ Select 9ROXPH3UW>9HK] or counted data volume (Link-AddValue1..3). P$'7 Noise calculation in accordance with 5/6 is based upon the socalled UHOHYDQW KRXUO\ WUDIILF YROXPH 0 in [car/h]. Since volumes are generally available as average daily traffic volumes or ADT in [car/24h], they have to be converted to standard hourly values. For this purpose table 3 on page 14 in 5/6 lists the conversion factors P$'7. If suitable project-specific analysis results for determining hourly traffic volume M are available (no peak hour values), these can be used. If this is the case, the standard setting P$'7 must be specified. 1RLVH &DOFXODWLRQ EDVHG RQ IUHH IORZ VSHHG (standard setting): Noise calculation is carried out with permissible maximum speed v0 in accordance with 5/6. Value range for minimum and maximum Y: 30-130 km/h for cars 30-80 km/h for HGVs. o &DOFXODWLRQ EDVHG RQ IUHH IORZ VSHHG: Noise calculation is carried out with specific, volume-dependent speed vCur contrary to the default model calculation values of 5/6 . In this case, the specified patterns and valid speeds apply.
6HOHFW 1RLVH,PPLV RU 1RLVH(PLV XQGHU (19,5210(17$/,03$&7LQ WKH &$/&8/$7(PHQX Start noise calculation.
&$/&8/$7(
Links with volumes < 10 car/h are not regarded in noise calculation.
8-11
Noise
'LVSOD\LQJ QRLVH YROXPHV
*UDSKLF GLVSOD\ Menu GRAPHICS - PARAMETERS. 'LDORJ 0RGLI\ JUDSKLFV SDUDPHWHUV /LQNV %DUV $WWULEXWHV
Select "1RLVH" link attribute.
7DEXODU GLVSOD\ LINKS in the LISTINGS menu. Insert 1RLVH attribute as column. ([DPSOH 'LVSOD\LQJ QRLVH FDOFXODWLRQ EDVHG RQ 1RLVH(PLV
G
8-12
To display noise volumes of links in traffic networks, the 1 bar display classified in accordance with ',1 3DUW 1RLVH 3UHYHQWLRQ LQ 8UEDQ 'HYHORSPHQW 1RLVH PDSV UHSUHVHQWDWLRQ RI QRLVH LPPLV VLRQV LQ PDS IRUP is recommended 6DYLQJ QRLVH YROXPHV Save as version file *.ver. Save as attribute file *.att for /LQNV listings type.
Air pollutants
$LU SROOXWDQWV
In VISUM, road traffic air pollution emissions are determined on the basis of two calculation procedures: 0/XV (based on the Leaflet on Air Pollution near Roads, section: Roads Without or Few Surrounding Developments) and 3ROOXWLRQ-(PLV (based on emission factors of the Swiss Federal Office for the Environment). The calculation of the pollution emission values is carried out internally by the program on the basis of direction, volume values for both directions are later added. The result is displayed as a FURVVVHFWLRQ YROXPH The emissions are calculated for every car and every truck (HGV), with every value multiplied by the number of vehicles (link volume for HGVs or cars). These partial sums are then totalled. &DOFXODWLRQ EDVHG RQ 0/X6(PLVV This calculation procedure is used to determine air pollution based on a diffusion model for two-lane or multi-lane roads ZLWKRXW or DW PRVW with little development near the road. The following boundary conditions apply: Traffic volumes > 5000 vehicles/day Y&XU > 50 km/h, slant < 6 %, hollows and embankments < 15 m, HGV proportion < 50 %. The results for every pollutant (CO, NOx, SO2, Pb, H6C6) are listed as Annual mean value or 98 percentiles (98% of all observed values are < percentile value).
Differentiation is made between cars and HGVs. The emission factors for 1985 serve as the basis for calculation. Because recent research has shown that the actual emission values have dropped as a result of changes in vehicle fleets (more vehicles have been equipped with a catalytic converter), reduction factors can be used for 1986 to 2000.
8-13
Air pollutants
The simplicity of the model does not allow inferences to be made about absolute local actual pollution volumes. It does, however, identify relative changes due to different traffic volumes. Because the model is restricted to links with v 50 km/h and because of the changing composition of fleets, MLus is not suited to inner-city areas. &DOFXODWLRQ EDVHG RQ 3ROOXWLRQ(PLV This calculation model is based on emission factors issued by the Swiss Federal Office for the Environment (BUS) for pollutants NOx, CO, HC and SO2, for both cars and HGVs. For every pollutant a regression curve is used. Emiss:= a + b * v + c * v2 + d * v3 + e * v4 + f * v5 The parameters a,b,c,d,e and f of the polynome were determined separately for different pollutants for cars and HGVs for the reference years 1990, 1992, and 2000 and are contained in the ASCII parameter files emi1990.dat, emi1992.dat and emi2000.dat. For the reference year 1990, e.g., the following values are used:
** Input file for flexible emission formulas for Switzerland 1990 ** a + bx + cx2 + dx3 + ex4 + fx5 (the numbers are exponential) * (x is the speed of cars or HGVs) * a + bx + cx2 + dx3 + ex4 + fx5 * NOx CAR 0.75860 2.8004e-2 -9.9187e-4 1.4276e-5 -5.6655e-8 0.0 * NOx HGV 24.216 -0.70194 1.5878e-2 -1.5996e-4 7.1751e-7 0.0 ** * CO CAR 16.425 -0.38357 2.8706e-3 -4.5425e-6 0.0 0.0 * CO HGV 45.380 -3.0729 9.7880e-2 -1.6116e-3 1.3138e-5 -4.1410e-8 ** * HC CAR 2.2155 -6.6593e-2 8.7930e-4 -5.1330e-6 1.1381e-8 0.0 * HC HGV 46.490 -3.7859 0.13382 2.3153e-3 1.9258e-5 -6.1410e-8 ** * SO2 CAR 101.80 -3.0309 4.4557e-2 -2.8928e-4 7.7300e-7 0.0 * SO2 HGV 1980.4 -87.564 2.9120 -5.0701e-2 4.3285e-4 -1.3577e-6
Recent measurements have shown that actual emission values are generally overestimated by 1990 calculation factors, because the change in vehicle fleets (more vehicles have now been equipped with catalytic converters) has contributed to decreasing volumes per vehicle. The latest Swiss emission factors take this change into account with modifications for the years 1992 and 2000.
8-14
Air pollutants
The polynome approximation of emissions relative to speed show the following developments for CO for different reference years:
&2HPLVVLRQYROXPHLQJNP
20,0 18,0 16,0 14,0 12,0 10,0 8,0 Car 1992 6,0 4,0 2,0 0,0 0 10 20 30 40 50 60 70 80 90 100 110
6SHHGNPK +*9VDPHYDOXHVIRUDOO\HDUV
Car 1990
Car 2000
8-15
Air pollutants
3ROOXWDQW(PLV DQG 0/XV OLQN DWWULEXWHV

For the two emission calculation procedures, 3ROOXWDQW(PLV and 0OX6, the HGV proportion is required as input link attribute. The following link attributes (pollution volumes) are returned as output values. 0/XV
X
3ROOXWDQW $WWULEXWH (PLVV

X
'HVFULSWLRQ
HGV proportion Relevant HGV proportion in percent of total (Input) traffic (above 2.8 t total permissible weight). MLuS-Pb (Output) MLuS-NO (Output) Lead [g/km] Nitrous oxide [g/km] Nitric oxides [g(km] Sulphur dioxide [g/km]
EDat-NOx (Output) MLuS-SO2 (Output)
EDat-SO2 (Output) MLuS-CO (Output) Carbon monoxide [kg/km]
EDat-CO (Output) MLuS-HC (Output) Hydrocarbons [g/km]
EDat-HC (Output)
8-16
Air pollutants
&DUU\LQJ RXW SROOXWLRQ FDOFXODWLRQV
For calculations based on 3ROOXWLRQ(PLV, it may be necessary to load the emission factors for a different reference year: Reference year 1990: emi1990.dat, Reference year 1992: emi1992.dat, Reference year 2000: emi2000.dat.
3URFHGXUH Rename desired file to automatically loaded file emiss.dat or Enter name and directory of desired file in standard configuration file visum.cfg under option ( instead of standard emission file emiss.dat.
(19,5210(17$/,03$&73$5$0(7(56LQ WKH &$/&8/$7(PHQX (QYLURQPHQWDO 3DUDPHWHUV %DVLF
8-17
Air pollutants
&DOFXODWLRQ EDVHG RQ Select calculated or counted volume. P$'7 Conversion factor for every global link type from medium average daily traffic (P$'7) to normal hourly values (important for noise calculation). For factor = 1.00 per GlobLinkType the pollutants for the time interval for which the traffic volumes are available are calculated. 9DOLG VSHHG UDQJHV The procedures require the following value ranges for speeds in order to carry out a correct calculation: 0/XV: 50-150 km/h (car) i.e. 50-80 km/h (HGV). 3ROOXWLRQ-(PLV: 10-130 km/h (car); 10-100 km/h (HGV) Y0LQ is considered, if vCur < vMin. Y0D[ is considered, if vCur > vMax. (QYLURQPHQWDO SDUDPHWHUV 3ROOXWDQWV
The value range has the following effect on the calculation:
8-18
Air pollutants
Y IUHH IORZ VSHHG Free flow speed is used for calculation. Y&XU Speed resulting in the loaded network is used for calculation in one step (total link volume = 100%). Y&XU ZLWK YROXPH SDWWHUQV Users specify the procedure for calculating speed via the percentages of every global link type: Calculation is based on v0 Standard setting: calculation is based on vCur and is carried out in one step (total traffic volume of link). Calculation is based on vCur and is carried out in several steps. In the example given, the total pollution volume is determined by adding the three calculated partial pollution volumes:
The first pollution calculation is carried out for 50% traffic volume (1. partial volume) with resulting vCur. The second pollution calculation is carried out for further 30% of vehicles (2. partial volume) with vCur at 80% of traffic volume. The third pollution calculation is carried out for the remaining 20% of vehicles with vCur at 100 % traffic volume. 5HIHUHQFH \HDU The emission factors for 1985 serve as the basis of calculation. For 1986-2010 reduction factors can be set by entering the respective year. &DOFXODWLRQ PRGH 3HUFHQWLOe: volume calc. with 98percentile values 0HDQ YDOXH: volume calc. with annual mean values
0/X6
8-19
Air pollutants
'LVSOD\LQJ SROOXWLRQ HPLVVLRQV
The following link attribute can be selected as pollution volumes: Based on MLus procedure: Based on Emis procedure: MLuS-CO, EDat-CO, MLuS-HC, EDat-HC, MLuS-NO, EDat-NOx and MLuS-Pb and EDat-SO2. MLuS-SO2.
/LVW RXWSXW RI SROOXWLRQ HPLVVLRQV Based on individual links (LINKS in the LISTINGS menu) or global link types (/LQN W\SHV under STATISTICS in the LISTINGS menu). Insert attributes as columns: same labels as in link attribute display in form of volume bars (see above). 6DYLQJ SROOXWLRQ HPLVVLRQV 6DYH DV version file *.ver. attribute file *.att for /LQNV and 6WDWLVWLFV /LQN W\SHV lists. ([DPSOH QLWURJHQ PRQR[LGH YROXPHV EDVHG RQ 0/XV
8-20
Mobilev interface
0RELOHY LQWHUIDFH
The &LWDLU software package consisting of several program modules was commissioned by the Federal Office for the Environment on the basis of VHFWLRQ RI )HGHUDO (PLVVLRQ 3UHYHQWLRQ /HJLVODWLRQ with which the effects of traffic measures for reducing harmful environmental effects caused by automobile exhaust emissions can be determined. One of the modules of &LWDLU is the 0RELOHY emission model (measure-oriented calculation instrument for local automobile exhaust emissions) developed by Messrs. FIGE in Herzogengrath. Mobilev determines the pollution emissions from single lanes of a link section via individual roads to a main traffic network (as line sources) or a by-road network (as area sources) with different degrees of accuracy. The calculation model provides the following results: Fuel consumption All hydrocarbons as well as methane, benzene, and non-methane hydrocarbons Carbon monoxide (CO) Nitric oxide (NOx) Carbon dioxide (CO2), Lead (Pb) and sulphur dioxide (SO2). Particle mass for diesel vehicles and resulting diesel soot.
Pollution calculation depends on current traffic volumes of respective links. VISUM can provide the assignment result for the entire traffic network via the shared 0R ELOHY interface. VISUM can also determine the effects of prohibitions or restrictions in the road network on traffic which can be included in the emission model for comparison with the initial set of conditions.
8-21
Mobilev interface
For emission calculations, 0RELOHY considers the following database: (PLVVLRQ IDFWRUV IRU YHKLFOH OD\HUV (vehicle layer = group of vehicle types of same category and size i.e. weight class with similar emission behaviour) classified by: Road type and the traffic situation (no disruptions; small, medium, large disruptions; stop and go traffic) Slant class Diverse influential factors, such as cold start penalties (in dependence on ambient temperature patterns, journey time, and journey length), performance correction factors for "G-Kat" vehicles etc..
3HUIRUPDQFH ZHLJKWLQJV for considering different performance proportions within individual vehicle layers classified by: Reference year (1980 to 2010), Area (Germany West/East) and Road category (motorway, urban roads, rural roads).
3DWWHUQV IRU WUDIILF YROXPH DQG FRPSRVLWLRQ for considering daytime variations classified by: Days of the week (Weekdays, Saturdays, Sundays) Type of road use/location (inner-city area; inner-city boundaries; outskirts with access roads and connection roads. Traffic direction types (both directions, more traffic into city, more traffic leaving city) Area (Germany West/East) and Transport system (car, HGV).
8-22
Mobilev interface
0RELOHY OLQN DWWULEXWHV

VISUM imports and exports the following link attributes on the basis of link number and link co-ordinates via the interface: $WWULEXWH M_RTyp M RoadType (Export) 'HVFULSWLRQ Road types for Mobilev-Emission calculation:
IO_Neben: IO_Kern: IO_HVS_LSA: urban (inner-city), secondary road. urban, city centre. urban, signalized priority road.
IO_HVS_Vorfahrt urban, priority road (right of way).
IO_HVS_TL>50: urban, priority road with max. speed > 50 km/h. AO_1: AO_2: AO_3: BAB_60: BAB_80: BAB_100: BAB_120: BAB_130: BAB>130: rural (highways, country roads), in good condition, straight. rural, in good condition, regular curves. rural, in good condition, irregular curves. German Federal motorway with maximum speed = 60 km/h German Federal motorway with maximum speed = 80 km/h German Federal motorway with maximum speed = 100 km/h German Federal motorway with maximum speed = 120 km/h German Federal motorway with maximum speed = 130 km/h German Federal motorway with no speed limit
Standard setting: IO_Neben.
8-23
Mobilev interface
$WWULEXWH v0-PrTSys v0 speed-PrTSys (Export) Cap-PrT/h capacity-PrT/h (Export) DTV_w DTV weekdays (Import/Export) Length (Import/Export) Steep track Inclination (Import/Export)
'HVFULSWLRQ Speed with free traffic flow (free network) for every PrTtransport system (car, HGV) in [km/h]. Value range: Int; 0..200 PrT-capacity of link in one hour in [car units /h]. Standard value: 0 Value range: Int; 0 Average daily traffic volume on weekdays in [car units/24h); is calculated in VISUM from assignment result or from AddValues and multiplied by factor, if necessary. Link length in [m]. Standard value: direct distance. Value range: Int; 0 Link length inclination in [%]. If the inclination is read in one direction, the opposite direction is set to a negative inclination (e.g. Forth 5 %, Back -5 %). Standard value: 0. Value range: Int; -50..50 Proportion of light HGVs of total traffic in [%]. Standard value: 3.0 Value range: Real; 0.00..100.00 Proportion of heavy HGVs of total traffic in [%]. Standard value: 5.0 Value range: Real; 0.00..100.00 Line haul bus proportion. Standard value: 0.0 Value range: Real; 0.00..100.00 Number of lanes. Standard value: 1. Value range: Int; 1..9
LHGV light HGV (Import/Export) HHGV heavy HGV (Import/Export) LBus-% LineBus-% (Import/Export) Lanes Number of lanes (Import/Export)
8-24
Mobilev interface
$WWULEXWH M_TS_free M TS free (Import) M_TS_small M TS small (Import)
'HVFULSWLRQ Traffic situation in [%]: without disruptions. small disruptions. medium disruptions. large disruptions. stop & go traffic.
M_TS_medium M TS medium (Import) M_TS_large M TS large (Import) M_TS_StopGo M TS stop+go (Import)
Value range: Real; 0..100 The sum of the 5 traffic situations - IUHHVPDOOPHGLXP ODUJHVWRSJR - is 100 %. Pollution emissions and fuel consumption for cold motors (on the first 5 kilometers): Nitric oxides in [g/(km * h)].
M_NOx_c M NOx cold start (Import)
M_CO_c M CO cold start (Import) M_CO2_c M CO2 cold start (Import) M_soot_c M soot cold start (Import) M_Ben_c M benzene cold start (Import)
Carbon monoxide in [g/(km * h)].
Carbon dioxide in [g/(km * h)].
Diesel soot in [g/(km * h)].
Benzene in [g/(km * h)].
Fuel consumption in [g/(km * h)]. M_consump_c M fuel consumption cold start Value range: Real; 0 (Import)
8-25
Mobilev interface
$WWULEXWH M_NOx M NOx (Import) M_CO M CO (Import) M_CO2 M CO2 (Import) M_Soot M Soot (Import) M_Ben M Benzene (Import) M_Consum M Consumption (Import)
'HVFULSWLRQ Pollution emission and fuel consumption with warm motor: Nitric oxides in [g/(km * h)]. Carbon monoxide in [g/(km * h)].
Carbon dioxide in [g/(km * h)].
Diesel soot in [g/(km * h)].
Benzene in [g/(km * h)].
Fuel consumption in [g/(km * h)].
Value range: Real; 0. The emission values for hydrocarbons output by Mobilev for cold and warm motors (HC, HC_K) as well as the particle mass for warm diesel motors can be loaded into VISUM via AddValues. The interface does not include emissions of methane, non-methane hydrocarbons, sulphur dioxide and lead. The Mobilev results are saved as direction-specific data.
8-26
Mobilev interface
'DWD H[SRUW DQG LPSRUW
([SRUW RI 9,680 OLQN YROXPHV DQG RWKHU OLQN DWWULEXWHV 0RELOHY LQWHUIDFH under SAVE in the FILE menu. 6DYLQJ 02%,/(9 OLQN DWWULEXWHV
2XWSXW VWDWLVWLFV Displaying the number of links not contained in the output provides an overview of how many links could not be transferred according to 0RELOHY. 7UDQVSRUW V\VWHP Saving attributes for transport system: Car or HGV. $YHUDJH GDLO\ WUDIILF ZRUNGD\V UHVXOWV IURP Multiply: MDT_W Assignment or AddValue1..3. with factor. The data are stored as a *.mob file (ASCII format).
0RELOHY emission calculation.
8-27
Mobilev interface
,PSRUWLQJ 0RELOHY UHVXOWV 0RELOHY LQWHUIDFH under OPEN in the FILE menu. 5HDG OLQN DWWULEXWHV GLDORJ
Returning Mobilev results to VISUM makes many evaluations and graphic representations possible.
8-28
Mobilev interface
'LVSOD\LQJ SROOXWLRQ HPLVVLRQV

*UDSKLF GLVSOD\
The values are displayed according to direction. For the display of pollution emissions, the use of classified values is recommended.
2XWSXW LQ OLVWV DQG WR ILOH
Lists can be displayed on the basis of individual links (LINKS in the LISTINGS menu) or global link types (/LQN W\SHV under STATISTICS in the LISTINGS menu). All input and result attributes described in chapter 8.4.1 can be output. 6DYLQJ SROOXWLRQ YROXPHV Save as version file *.ver. Save as attribute file *.att for /LQNV and 6WDWLVWLFV /LQN W\SHV.
8-29
IMMIS-LUFT(AIR) interface
,00,6/8)7$,5 LQWHUIDFH
The IMMIS-LUFT interface is not included in the Environmental impact calculation Add-on module. It is provided as a separate Add-on module.
In contrast to the emission calculation models in VISUM, the IMMIS-LUFT pollution diffusion program from IVU, Berlin, models LPPLVVLRQV, i.e. air pollution at ground level calculated on the basis of concentrations absorbed by living beings. IMMIS-LUFT estimates volumes in built-up areas, with the main focus on modelling "canyons". Concentration values are calculated for diesel soot, benzene, and NO2 in accordance with the newly introduced paragraph VHFWLRQ of )HGHUDO ,PPLV VLRQ 3UHYHQWLRQ /HJLVODWLRQ and the accompanying )HGHUDO ,PPLVVLRQ 3UHYHQWLRQ $FW The calculation of immission values is based on the &3% &DQ\RQ 3OXPH %R[) model for canyons on the one hand and on the simple %R[ PRGHO on the other which can only be applied for open developments and extreme traffic volumes and is not described in more detail here. The &3% model takes factors such as the following into account Meteorological conditions (wind and propagation conditions) Surrounding buildings Traffic volume and speed Traffic mix. The meteorological conditions and the traffic volume interact with turbulence conditions: in heavy traffic pollutants are distributed more strongly and turbulence on roads changes depending on global radiation. The CPB model produces immission half-hour values. By assuming certain frequency distributions of traffic volumes and meteorological conditions, they are subsequently extrapolated to annual mean values (for soot and benzene), i.e. annual 98 percentile values (for nitrogen dioxide). The values are displayed for road crosssections.
8-30
In addition to this special DGGLWLRQDO SROOXWLRQ YROXPH which is caused by automobile traffic emissions, the LQLWLDO OHYHO RI SROOXWLRQ must also be considered. This is the result of all other emission sources (automobile traffic in the entire traffic network, all non-automobile pollution-causing groups as well as extensive EDFNJURXQG SROOXWLRQ YROXPHV. ,QLWLDO YROXPH and DGGLWLRQDO YROXPH added together result in the WRWDO YR OXPH.
,00,6 /8)7 OLQN DWWULEXWHV

VISUM imports and exports the following link attributes via the interface on the basis of link number and co-ordinates: $WWULEXWH 'HVFULSWLRQ
Vol-PrT Average daily traffic volume [car/24h]; link-specific traffic volVolume -PrT ume determined in VISUM via the assignment and is output (Assignment; Exp.) for IMMIS-LUFT as a cross-section value (for both directions). Cap-PrT capacity-PrT (Export) I_Oneway I_Oneway (Export) PrT-capacity of link in [car units/ time interval]. Value range: LongInt, 0 One-way road identifier: link whose opposite direction is blocked for all transport systems (1=yes / 0=no). The identifier is required for data export to IMMIS-LUFT because the VISUM link volume is output as a cross-section value. Value range: Int; 0..1 TrafMod Traffic Mode (Import/Export) Road types with different emission behaviour:
Inner-city/subcentres (average speed. 19,9 km/h; ca. 42 % cold
start share; focus on mornings)
Outer areas/residential roads (average speed 32 km/h; ca. 58 %

cold start proportion)
Access roads (average speed 37,5 km/h; ca. 44 % cold start proportion; focus on mornings)
Federal motorway 1 (70-80 km/h) Federal motorway 2 (80-90 km/h) Federal motorway 3 (90-100 km/h)
Standard value: 0 Value range: Int; 0..5
8-31
$WWULEXWH CSGrad Grad.: CrossSect. (Import/Export)
'HVFULSWLRQ Link slant in [%] as cross-section value. The inclination must be specified for IMMIS-LUFT > 0, whereby the value per link must be identical for both directions. Standard value: 0 Value range: Int; -50..50 Partial sections of link excluding buildings [%]. Standard value: 20 Value range: Int; 0..100 Height of building in metres excluding roof (e.g. 3 m per storey). Standard value: 20.00 Value range: Real; 0..9999.99 Distance between buildings on either side in [m]. Standard value: 20.00 Value range: Real; 0..9999.99 Share of line haulage bus operation Standard value: 0.0 Value range: Real; 0..100 Share of light HGVs of total traffic [%]. Standard value: 3.0 Value range: Real; 0..100 Share of heavy HGVs of total traffic [%]. Standard value: 5.0 Value range: Real; 0..100 Probable congestion time in percent of a day. Standard value: 10.0 Value range: Real; 0..100 Share of cars with catalytic converter of car fleet [%]. Standard value: 40.0 Value range: Real; 0..100 Share of cars with diesel motor of car fleet [%]. Standard value: 13.0 Value range: Real; 0..100
Poros Porosity (Import/Export) Cave_vert CanyonVertic (Import/Export) Cave_hor CanyonWidth (Import/Export) LBus LineHBus-% (Import/Export) SHGV Small HGV (Import/Export) LHGV Large HGV (Import/Export) Cong Congestion (Import/Export) Cat Catalyst % (Import/Export) Diesel Diesel-% (Import/Export)
8-32
$WWULEXWH I_BNO2_98 I_NO298P Basic (Import) I_BBEN_M I_Benzene Basic (Import) I_BSOOT_M I_Soot Basic (Import) I_ANO2_98 I_NO298P Addit. (Import) I_ABEN_M I_Benzene Addit. (Import) I_ASOOT_M I_Soot Addit. (Import) I_TNO2_98 I_NO298P (Import) I_TBEN_M I_Benzene (Import) I_TSOOT_M I_Soot (Import)
'HVFULSWLRQ Basic immission volume caused by traffic of total transport network and other emission sources: Nitrogen dioxide [g/m ; 98 percentile of all half-hour values of the year].
3
Benzene [g/m ; annual mean value].

3
Soot [g/m ; annual mean value].

3
Additional immission volume caused by traffic on link: Nitrogen dioxide [g/m ; 98 percentile of all half-hour values of a year].
3

3

3
Total immission volume (Basic imm. vol.+ Add. imm. vol.): Nitrogen dioxide [g/m ; 98 percentile of all half-hour values of a year].
3

3

3
8-33
'DWD H[SRUW DQG LPSRUW
VISUM generates the database as a traffic model for the immission calculation with IMMIS-LUFT by determining traffic volumes for every link as cross-section values. ([SRUWLQJ 9,680 OLQN YROXPHV DQG RWKHU OLQN DWWULEXWHV ,PPLV/XIW under SAVE in the FILE menu. 6DYH ,00,6/XIW /LQN DWWULEXWHV GLDORJ
2XWSXW VWDWLVWLFV Displaying the number of links not contained in the output provides an overview of how many links could not be transferred on the basis of ,00,6/8)7. /LQN YROXPHV IURP Copy link volumes for IMMIS-Luft from: Current assignment result or Additional values $GG9DOXH The data are saved as an *.imm file (ASCII format).
After the attributes have been transferred to IMMIS-LUFT, the pollution immissions can be calculated for every link.
8-34
,PSRUWLQJ LPPLVVLRQ YDOXHV DQG RWKHU ,00,6/8)7 DWWULEXWHV ,PPLV/XIW under OPEN in the FILE menu. 5HDGLQJ /LQN $WWULEXWHV GLDORJ
Returning IMMIS-LUFT results to VISUM makes many evaluations and graphic displays possible.
8-35
'LVSOD\LQJ SROOXWLRQ LPPLVVLRQV
*UDSKLF GLVSOD\ Menu GRAPHICS - PARAMETERS. 'LDORJ 0RGLI\ JUDSKLFV SDUDPHWHUV /LQNV %DUV $WWULEXWHV Select one of the following link attributes Basic volume of pollution immissions: ,B6RRW %DVLF 9ROXPH ,B%HQ]HQH %DVLF 9ROXPH ,B123 %DVLF 9ROXPH.
Additional volume of pollution immissions: ,B6RRW $GGLWLRQDO 9ROXPH ,B%HQ]HQH $GGLWLRQDO 9ROXPH ,B123 $GGLWLRQDO 9ROXPH.
Total volume (basic vol. + addit. vol.) of pollution immissions: ,B6RRW, ,B%HQ]HQH ,B123.
/LVW RXWSXW RI SROOXWLRQ LPPLVVLRQV List output can be carried out on the basis of individual links (LINKS in the LISTINGS menu) or global link types (/LQN W\SHV under STATISTICS in the LISTINGS menu). The output values refer to cross-sections (both link directions). For the display of pollution immissions, the use of classified values is recommended.
6DYLQJ SROOXWLRQ YROXPHV Save as version file *.ver. Save as attribute file *.att for /LQNV and 6WDWLVWLFV /LQN W\SHV.
8-36
PUBLIC TRANSPORT ANALYSES, LINE COSTING
38%/,& 75$163257 $1$/<6(6 /,1( &267,1*
VISUM User Manual (April 2001 Version 7.50
9-1
Operational indicators
2SHUDWLRQDO LQGLFDWRUV
Operational indicators can be divided into the following categories: General indicators Performance indicators Vehicle requirement indicators Travel demand indicators Cost indicators Revenue indicators.
Most operational indicators are calculated for a vehicle trip (e.g. vehicle kilometers) or a subline (e.g. passenger kilometers) and are then aggregated to line indicators or transport system indicators. The indicators QXPEHU RI YHKLFOHV and YHKLFOH FRVW, however, can only be calculated for one line or one transport system. To determine these indicators for a subline, they are distributed over vehicle kilometers. Operational indicators are displayed in the following lists (see Chapter 10): zones, global zones and areas, nodes or stops, links, lines and sublines, also line routes and main lines, PuT transport systems, PuT operators and statistics (link types, PuT assignment statistics, line blocks)
9-2
*HQHUDO LQGLFDWRUV 3X7 PRGXOH Indicators: Calculation: Number of stops, mean speed, running time, first departure, last arrival etc. The calculation is carried out automatically after every modification to line data, no demand data are required.
3HUIRUPDQFH LQGLFDWRUV 3X7 PRGXOH Indicators: Calculation: Vehicle kilometers, service time, time in action, seat kilometers. The calculation is carried out automatically after every modification to line data, no demand data required.
9HKLFOH UHTXLUHPHQW LQGLFDWRUV RQO\ ZLWK /LQH FRVWLQJ DGGRQ PRGXOH Indicators: Calculation: Number of required vehicles. 9HKLFOH EORFNLQJ required in Menu CALCULATE - PROCEDURES 2SHUDWLRQV Operation:/LQH%ORFNLQJ.
7UDYHO GHPDQG LQGLFDWRUV 3X7 PRGXOH Indicators: Calculation: Line trips, saturation, passenger kilometers. Indicators are calculated automatically during assignment. Requires demand data.
9HKLFOH FRVW LQGLFDWRUV 3X7 PRGXOH Indicators: Calculation: Vehicle cost from hourly cost and kilometer cost. The calculation for hourly and kilometer cost is carried out automatically after every modification to line data or to cost for vehicle types. No demand data necessary.
,QIUDVWUXFWXUH FRVW LQGLFDWRUV RQO\ ZLWK /LQH FRVWLQJ DGGRQ PRGXOH Indicators: Calculation: Link cost, stop cost, operator cost. /LQN FRVW, 6WRS FRVW, 2SHUDWRU FRVW calculations required in Menu CALCULATE - PROCEDURES - 2SHUDWLRQV Operation:,QIUDVWUXFWXUH&RVW.. No demand data required.
5HYHQXH FDOFXODWLRQ LQGLFDWRUV RQO\ ZLWK /LQH FRVWLQJ DGGRQ PRGXOH Indicators: Calculation: Total revenue, revenue per line trip, cost coverage. 5HYHQXH calculation required in Menu CALCULATE - PROCEDURES 2SHUDWLRQV Operation:3X7 5HYHQXHV.
9-3

([DPSOH
This example is to illustrate, how to to prepare a tariff model, to plan line blocking, to calculate operational and performance indicators, as well as cost, revenues and cost coverage by line.
9-4
7UDQVSRUW VXSSO\ The transport system consists of three lines with two variants per line (outward and return subline ):
6XEOLQH 26WRS '6WRS /HQJWK )LUVW'HS +HDGZD\ /DVW'HS 5XQ7 /D\RYHU7
BUS1 O BUS1 R BUS2 O BUS2 R RAIL O RAIL R
10 40 30 40 20 40
40 10 40 30 40 20
30000 30000 10000 10000 10000 10000
06:00:00 06:20:00 06:35:00 06:20:00 06:25:00 06:45:00
00:40:00 00:40:00 00:40:00 00:40:00 00:40:00 00:40:00
18:00:00 18:20:00 18:35:00 18:20:00 18:25:00 18:45:00
00:45:00 00:45:00 00:13:00 00:13:00 00:16:00 00:16:00
00:15:00 00:15:00 00:12:00 00:02:00 00:04:00 00:04:00
9HKLFOHV XVHG
9HKLFOHW\SH 6HDWFDSDFLW\ 7RWDOFDSDFLW\
Standard bus Train
35 200
90 400
7DULII PRGHO The tariff model includes two tariff zones and five tariff subzones, to which the following nodes and stops have been assigned:
1U 1DPH 6WRS 7= 7=
10 11 20 30 40 50
A village A stop C village B village X town Tariff node
x x x x x
x x x x x x x x x
9-5
Stop (B village) is located between the tariff zones 7= and 7=, and is therefore assigned to both tariff zones. Additionally, "tariff node is inserted between stop and stop , and is assigned to both the tariff subzones 76= and 76=. Thus, the trip by rail covers more than two tariff subzones (up to 2 TSZ = short haul tariff). 7LFNHWV DQG IDUHV
7DULII]RQHV 2QHZD\WLFNHW )RXUWULSWLFNHW 0RQWKO\SDVV
Price up to 2 tariff subzones up to 1 tariff zone up to 2 tariff zones 1.00 2.00 3.00 3.20 6.40 12.80
One-way fare 0.80 1.60 3.20
Price 40.00 40.00 80.00
One-way fare 1.00 1.00 2.00
A supplement of 3.00 CU (currency units) is required for each rail ticket. 7UDYHO GHPDQG
)URP=RQH 7R=RQH /LQH /LQH 'HPDQG
A village X town A village C village C village X town B village X town
X town A village C village A village X town C village X town B village
Bus1 Rail Bus1 Bus1 Rail Rail Bus2 Bus2
Rail Bus1
200 200 20 20 500 500 200 200
Total:
= 1840
9-6
&RVWV Link costs: track utilization charge of 10 CU/km on railway track between stop and stop . Vehicle costs:
&RVWV 6WDQGDUGEXV 5DLO
Cost per hour [CU/h] Cost per km [CU/km] Daily cost per vehicle [CU/Veh]
42.00 1.00 100.00
42.00 5.00 200.00
Operating costs: annual administration costs of 100,000 CU for PXQLFLSDO VHUYLFHV and UDLOZD\ FRPSDQ\.
For the calculation of operational indicators, costs, revenues and cost coverage, the following steps are to be carried out: 1. Generate tariff model (Ch. 9.1.2). 2. Define projection factor (Ch. 9.1.3). 3. Vehicle blocking (Ch. 9.1.4). 4. Calculate performance indicators (Ch. 9.1.5). 5. Calculate travel demand indicators (Ch. 9.1.6). 6. Calculate costs (Ch. 9.1.7). 7. Calculate revenues (Ch. 9.1.8). 8. Calculate cost coverage from costs and revenues (Ch. 9.1.9).
9-7
7DULII PRGHO

The tariff model allows modeling of tariff zones by tariff zones and tariff subzones. The number of traversed zones can be determined, fares and revenues can be calculated by tariff zone. 7DULII ]RQHV DQG VXE]RQHV The stops within the PuT network can be assigned to one or several tariff subzones, a tariff subzone is part of only one tariff zone. Based on this input data, the number of traversed tariff zones and subzones can be calculated by VISUM. These indicators and the fares are output during PuT assignment as an indicator matrix, in the 3X7 URXWHV list, in the 3X7 URXWH VHDUFK list in the 3X7 UHODWLRQV list.
Usually tariff subzones are used for short haul tariff modeling. If modeling in detail is not necessary, tariff zones need not be specified, as tariff subzones serve as tariff zones. 7LFNHW W\SHV A ticket type is defined by the ticket name, fares based on zone or distance, the utility rate which specifies the converting factor (from season tickets to oneway trip tickets), a supplement factor by public transport system, e.g. for express train.
Fares can be considered for connection split during assignment and for revenue calculation during line costing calculation. For tariff model modeling (see example Ch. 9.1.1) the following steps are required: 1. Define tariff subzones: Assign stops , , to the tariff subzones 76=, 76= and 76=. Assign stop to the tariff subzones 76= and 76=. Assign tariff node 5 to the tariff subzones 76= and 76=.
9-8
2. Define tariff zones: Assign tariff subzones 76=, 76= and 76= to tariff zone 7= Assign tariff subzones 76= and 76= to tariff zone 7=.
3. Define ticket types: See example: Insert three ticket types with zone-related fares and supplementary cost for rail: RQHZD\ WLFNHW, PXOWLSOHWULS WLFNHW and PRQWKO\ SDVV.

7DULII VXE]RQHV
0HQX (;75$6 387 7$5,))=21(6 7DULII ]RQHV GLDORJ
Insert tariff subzones with the ,QVHUW button.
9-9
,QVHUW WDULII VXE]RQH GLDORJ ,QVHUW button
Assigns stop or node to tariff subzone: in the example, stop (A village) is assigned to tariff subzone 76=. Removes stop or node from tariff subzone. DOO VWRSV: all stops in the network are provided in the selection list. Thus it is possible to assign multiple tariff subzones to those VWRSV located precisely on tariff subzone boundaries. RQO\ IUHH VWRSV: only those stops which have not yet been assigned to a tariff subzone are available for selection. DOO QRGHV: all nodes within the network are available for selection. RQO\ IUHH QRGHV: only those nodes which have not yet been assigned to a tariff subzone are available for selection.
9-10
See example: insert further tariff subzones and assign stops/node. To assign stop 30 (B village) to both tariff subzones 76= and 76= and tariff node to both tariff subzones 76= and 76=, enable DOO QRGHV. The following list results:
Assigning nodes to tariff subzones can also be carried out by node (SINGLE SELECT mode; SELECT - NODE and EDIT - MODIFY): "Modify node (Basic)" dialog 7DULII ]RQHV page ,QVHUW button:
Assignments can be cancelled with the 'HOHWH button.
9-11

7DULII ]RQHV
0HQX (;75$6 387 7$5,))=21(6 7DULII ]RQHV GLDORJ
8
7DULII ]RQHV
Insert WDULII ]RQHV with the ,QVHUW button. ,QVHUW WDULII ]RQH GLDORJ ,QVHUW button
9-12
Assigns selected tariff subzone to tariff zone: in the example above, the tariff subzones 76=, 76=, 76= and 76= 130 and 76= are assigned to tariff zone 7=. Removes tariff subzone from tariff zone. DOO 76=: all tariff subzones of the network are available for selection. RQO\ IUHH 76=: only those tariff subzones which have not yet been assigned to a tariff zone are available for selection.
A tariff subzone may only be assigned to one tariff zone. If option DOO 76= is active, a tariff subzone previously assigned to another trafiff zone and thus removed from the can be re-assigned with button originally specified tariff zone. Therefore it is recommended to use standard option RQO\ IUHH 76= be selected.
See example: tariff zone 7= is inserted and assigned to the remaining tariff subzones. The following list of tariff zones and subzones is displayed in the "Tariff subzones dialog:
9-13

3X7 7LFNHW W\SHV

0HQX(;75$6 387 )$5(6 387 7LFNHW W\SHV GLDORJ
Insert ticket types with ,QVHUW button. ,QVHUW WLFNHW W\SH GLDORJ ,QVHUW button
([DPSOH For the example given in Ch. 9.1.1 the ticket type 2QHZD\ WLFNHW is defined in the following way: Number: 1 Name: One-way ticket Use frequency: 1.0 Supplement factor: 1.0 (multiplied by TSys-supplement).
9-14
7DULII W\SH =RQHEDVHG WDULII: Defining basic fare levels based on the number of traversed tariff zones or subzones (for short haul tariff) by ,QVHUW button: ,QVHUW button
'LVWDQFHEDVHG WDULII: Defining basic fare levels based on distance by ,QVHUW button:
([DPSOH For the example given in Ch. 9.1.1 the following zone-based tariff is specified: up to 2 TSZs (=2 stops): up to 1 TZ: up to 2 TZs: 1.00 CU (short haul tariff) 2.00 CU 3.00 CU
9-15
Beyond the one-way ticket, the following changes are to be made: "Four trip ticket: Utility rate: 4.0 Price category up to 2 TSZ up to 1 TZ up to 2 TZ Monthly pass: Utility rate: 40.0 Price category up to 1 TZ up to 2 TZ Price of ticket 40.00 80.00 One-way fare 1.00 2.00 Price of ticket 3.20 6.40 12.80 One-way fare 0.80 1.60 3.20
If demand matrices are not available by ticket type, it is recommended to define a virtual "combined ticket type based on the mean fare calculated from the ticket types and fares specified for the tariff model. ,QVHUW VXSSOHPHQW E\ WUDQVSRUW V\VWHPV "PuT Ticket types" dialog
6XSSOHPHQWV button
9-16
76\VVSHFLILF VXSSOHPHQWV GLDORJ 6XSSOHPHQWV button
Fare supplements for the use of transport systems can be set in different ways: )L[HG VXSSOHPHQW Assigns a fixed fare supplement for a transport system. In addition, different ranks can be defined. Thus only the fixed supplement of the transport system with the highest rank is charged. For example, when TSys ICE (rank 1) is used, no IC supplement (rank 2) is required. If the ranks are equal, only the highest supplement is charged. It is recommended to set an unambiguous order of the ranks. For supplement-free transport systems the lowest rank should be specified. 'LVWDQFHEDVHG VXSSOHPHQW Assigns a supplement, which reflects the distance-based additional cost for the use of a transport system. The fare classes depending on the covered distance in meters are inserted using: the 3DUDPHWHUV button, the "distance-based fares" dialog: the ,QVHUW EXWWRQ
9-17
,QVHUW button
The defined distance-based supplement can be applied or ignored if necessary:
Here, distance-based supplements are defined for %XV and 5DLO, but only the 5DLO supplement is applied.
A global evaluation of all defined supplements for the calculation of the total fare for a ticket type can be carried out using the supplement factor (default: 1.0) (menu EXTRAS - PUT FARES ,QVHUW or 0RGLI\ button). In the menu CALCULATE - METHODS - )XQFWLRQV 3X7 IXQFWLRQV IDUHV you can define how fare parameters such as ranks are to be applied for calculating the fare (see Chapter 9.1.2.4). The fare has an influence on the impedance definition of a route in the PuT assignment parameters of the line-based method as well as the timetable-based methods 2 and 3 (see Chapter 7).
9-18
([DPSOH For the application example in Chapter 9.1.1, a fixed supplement of 3.00 CU is charged for the 5DLO transport system.

)DUH FDOFXODWLRQ
The fare for a ticket type consists of: the basic fare: zone-based: based on the number of traversed tariff zones, distance-based: based on the number of kilometres covered, fixed supplements for the use of a transport system, if applicable, distance-based supplements for the use of a transport system, if applicable.
Then, revenues can be calculated and divided (see Chapter 9.1.8).
6HWWLQJ D WLFNHW W\SH WR DFWLYH Menu EXTRAS - PUT FARES 3X7 7LFNHW W\SHV GLDORJ
3X7 WLFNHW W\SHV
For fares calculation and display, select and activate a ticket type, e.g. the previously defined ticket type 2QHZD\ WLFNHW.
6HWWLQJ SDUDPHWHUV IRU IDUH FDOFXODWLRQ Menu CALCULATE - PROCEDURES )XQFWLRQV page
9-19
3X7 IXQFWLRQV )DUHV GLDORJ
+DQGOLQJ RI VXSSOHPHQWV $GG IL[HG VXSSOHPHQW SHU URXWH VHFWLRQ The fixed supplement of a transport system is charged for each partial route of a connection rather than only once, i.e. if two partial routes use the same transport system for which a supplement is required, the supplement is charged twice (see calculation examples below). &RQVLGHU UDQN RI IL[HG VXSSOHPHQWV If no fixed supplement is charged for each partial route (o $GG IL[HG VXSSOHPHQW SHU URXWH VHFWLRQ, then with this option activated, the user-defined transport system ranks can be used for calculating the fare (see calculation examples below). +DQGOLQJ RI WDULII ]RQHV &RXQW WDULII ]RQHV DV RIWHQ DV WKH\ DUH WUDYHUVHG When a passenger traverses a tariff zone more than once, the tariff zone is counted each time, which results in a higher fare.
The fare has an influence on the impedance definition in the PuT assignment parameters of the line-based method as well as the timetable-based methods 2 and 3 (see Chapter 7).
9-20
&DOFXODWLRQ H[DPSOHV IRU WKH KDQGOLQJ RI VXSSOHPHQWV The data concerning fixed supplements for ICE: 0.00 CU (rank 1) IC: 7.00 CU (rank 2) EC: 7.00 CU (rank 2) IR: 0.00 CU (rank 3) distance-based basic fare, degressive: 0-100 km: 0.12 CU/1000m 100-200 km: 0.10 CU/1000m 200-300 km: 0.08 CU/1000m ICE km supplement, degressive: 1/3 of the basic fare
result in different fares, depending on the defined calculation parameters:

([DPSOH
o Add fixed supplement per route section o Consider rank of fixed supplements
FRQQHFWLRQ WUDYHO GLVWDQFH GLVWDQFHWRWDO EDVLFIDUH IL[HG GLVWDQFHEDVHG VXSSOHPHQW VXSSOHPHQW,&(
ICE IC ICE
WRWDO
100000 100000 100000
100000 200000 300000 (*) 30.00 CU

&8
0.00 CU 7.00 CU 0.00 CU

&8
(**) 4.00 CU 0.00 CU (***) 3.33 CU

&8
(*) 30.00 (**) 4.00 (***) 3.33

([DPSOH
CU = 0.12 CU x 100 + 0.10 CU x 100 + 0.08 CU x 100 CU = 1/3 x 0.12 CU x 100 (for 0-100 km) CU = 1/3 x 0.10 CU x 100 (for 100-200 km)
o Add fixed supplement per route section Consider rank of fixed supplements
FRQQHFWLRQ WUDYHO GLVWDQFH GLVWDQFHWRWDO EDVLFIDUH IL[HG GLVWDQFHEDVHG VXSSOHPHQW VXSSOHPHQW,&(
ICE IC ICE
WRWDO
100000 100000 100000
100000 200000 300000 30.00 CU

&8
0.00 CU 7.00 CU 0.00 CU

&8
4.00 CU 0.00 CU 3.33 CU

&8
(*) the fixed supplement for IC is ignored because the ICE has a higher rank
9-21
([DPSOH
FRQQHFWLRQ WUDYHO GLVWDQFH GLVWDQFH WRWDO EDVLFIDUH IL[HG VXSSOHPHQW GLVWDQFHEDVHG VXSSOHPHQW,&(
EC IC IR
WRWDO
100000 100000 100000
100000 200000 300000 30.00 CU

&8
7.00 CU 7.00 CU 0.00 CU

&8
0.00 CU 0.00 CU 0.00 CU

&8
(**) Because the ranks are equal, only the highest supplement (here: 7,00 CU) is charged.
([DPSOH
Add fixed supplement per route section o Consider rank of fixed supplements
FRQQHFWLRQ WUDYHO GLVWDQFH GLVWDQFH WRWDO EDVLFIDUH IL[HG VXSSOHPHQW GLVWDQFHEDVHG VXSSOHPHQW,&(
IC IR IC
WRWDO
100000 100000 100000
100000 200000 300000 30.00 CU

&8
7.00 CU 0.00 CU 7.00 CU

&8
0.00 CU 0.00 CU 0.00 CU

&8
9-22
/LVW RXWSXW RI WDULII PRGHO LQGLFDWRUV The calculated indicators of the tariff model: 1XP7=: Number of tariff zones traversed. 1XP76=: Number of tariff subzones traversed. )DUH: Fare by selected ticket type. can be listed (results refer to the example in Ch. 9.1.1): 3X7 5HODWLRQV OLVW
8
3DUWLDO FRQQ
0HQX /,67,1*6 387 5(/$7,216
Fare calculation: Fare 3.00 CU: two tariff zones traversed by bus line %XV. Fare 6.00 CU: two tariff zones traversed by bus DQG rail (rail supplement 3 CU). &RQQ
5H ODWLRQV
Fare calculation:
NumConn i =1
ODTripsi Farei
ODTrips total
(8018 3.00 ) + (1982 6.00) = 3.59 10000

9-23
5RXWHV 3X7 OLVW
0HQX /,67,1*6 5287(6387
5RXWH VHDUFK 3X7 OLVW
0HQX *5$3+,&6 5287(6($5&+
0HQX /,67,1*6 5287(6($5&+
9-24
387 DVVLJQPHQW ,QGLFDWRU PDWUL[ FDOFXODWLRQ
G
8
Prerequisite: Select active ticket type (here: 2QHZD\ WLFNHW). 0HQX &$/&8/$7( 352&('85(6 2SHUDWLRQV Operation: ,QGLFDWRU0DWUL[, DSeg: any PuT demand segment, Procedure: OLQHEDVHG, 3DUDPHWHUV button 3DUDPHWHUV DVVLJQPHQW SURFHGXUH ,QGLFDWRU0DWULFHV SDJH
0HQX &$/&8/$7( 352&('85(6 ([HFXWH EXWWRQ
9-25
([DPSOH Indicator matrix file indicator.csv in CSV format

$VISION $VERSION:VersNr;FileType;Language 1.0;Matrix;E * *FileInfo $INFO:TEXT Means of Transport Number 3 Time interval 0.00 24.00 VISUM Version 7.50 20/03/01 O:\Visum\example.ver with passengers
saved with: saved on: Network/VersionFile: Weighted: $
Assignment procedure: line-based
* Indicators calculated: * NumTSZ * NumTZ * Fare Num Tariff subzones Num Tariff zones Fare
$Relations:OZonNr;DZonNr;NumTSZ;NumTZ;Fare 100;200;5.0;2.0;3.00 100;300;4.0;1.0;2.00 100;400;3.0;1.0;2.00 200;100;5.0;2.0;3.00 200;300;2.0;2.0;1.00 200;400;3.0;2.0;5.65 300;100;4.0;1.0;2.00 300;200;2.0;2.0;1.00 300;400;2.0;1.0;1.00 400;100;3.0;1.0;2.00 400;200;3.0;2.0;5.65 400;300;2.0;1.0;1.00
9-26
3URMHFWLRQ
Supply data in the network model describe PuT supply only for one day. To project daily operational indicators for a year, projection factors are necessary. Projection can be carried out with Line Revenue Calculation add-on module. Projection can be carried out using general projection factor. Indicator-specific projection calculates each of the following indicators with specific factors: travel demand indicators (demand share, revenue), transport supply indicators (performance, cost), costs per hour.
This calculation takes into account that travel demand, for example, can decrease more strongly than PuT supply on weekends. At the same time, higher personnel costs, i.e. higher hourly costs, can arise on Sundays.
8
3X7 )XQFWLRQV
0HQX &$/&8/$7( 352&('85(6 )XQFWLRQV SDJH 3XW)XQFWLRQV
9-27
3URMHFWLRQ FRQVWDQW Projection of daily values to annual values can be carried out via constant factor. 3URMHFWLRQ GD\VSHFLILF Projection can be carried out as well via factor which takes dayspecific differences in demand share, transport supply, and hourly costs into account: 7\SH RI GD\ day type1 Mo-Fr: corresponds to a day represented in network model day type2, Mo-Fr: e.g. for working days with no school day type3, Saturdays. day type4, Sundays and public holidays.
Days/Year: Number of days of "Day type" per year. 'HPDQG VKDUH: Factors for every day type which indicate relation between demand share of day type 1 to other day types. demand share indicators (e.g. passenger kilometers) and revenue indicators are calculated using demand share projection factor. 7UDQVSRUW VXSSO\: Factors for every day type which indicate relation between transport supply of day type 1 to other day types. Performance indicators (e.g. vehicle kilometers) and cost indicators are calculated using transport supply projection factor. &RVW+RXU: Factors for every day type which specify proportion between hourly costs of day type 1 to other day types. This projection factor is used to calculate hourly cost indicators (personnel cost). Projection function is activated by executing an operation via ([HFXWH button in Menu CALCULATE - PROCEDURES - 2SHUDWLRQV. Revenue lists for sublines, lines, PuT transport systems and areas (Menu LISTINGS - LINES / - SUBLINES / - PUT TRANSPORT SYSTEMS AREAS).
9-28
/LQH %ORFNLQJ

The objective of line blocking is to assign the total number of vehicle trips (services) of an operational day to vehicles in such a way that a minimum number of vehicles is required. The basis for line blocking is the WLPHWDEOH. It consists of individual vehicle trips which are described by subline, direction, and departure times from first stop of line. The required number of vehicles (OLQH EORFNV) results from the concatenation of individual services into VHUYLFH FKDLQV which can each be serviced by one vehicle. In the simplest case a vehicle trip is concatenated at its last stop with a subsequent service which starts at the same stop. If such a concatenation is not possible or not meaningful, the vehicle can be transferred (moved) to a different stop. This results in an inWHUOLQLQJ WULS. /LQH EORFNLQJ SDUDPHWHUV
0HQX&$/&8/$7( 352&('85(6 2SHUDWLRQV Operation: LinBlockCalc 3DUDPHWHUV button /LQH%ORFNLQJ3DUDPHWHUV /LQH VHOHFWLRQ
/LQH VHOHFWLRQ
9-29
/LQH %ORFNV o $FWLYH OLQHV RQO\ line blocking is computed for all lines of network. $FWLYH OLQHV RQO\ line blocking is computed only for lines set active via line filter. $OO RSHUDWRUV: line blocking is computed for lines of all operators. 2SHUDWRU: line blocking is computed only for lines of operators marked in list box. /LQH%ORFNLQJ3DUDPHWHUV 3DUDPHWHUV 3DUDPHWHUV
9-30
6XFFHHG YHK WULS 6DPH RSHUDWRU IRU QH[W WULS: Only vehicle trips of same operator are used for next vehicle trip. o Vehicle trips of different operators are used for next vehicle trip. 6DPH 76\V IRU QH[W WULS Only vehicle trips of same transport system are used for next vehicle trip. o Vehicle trips of different transport systems are used for next vehicle trip. 6DPH YHK W\SH IRU QH[W WULS Only vehicle trips of same vehicle type are used for next vehicle trip. o Vehicle trips of different vehicle types are used for next vehicle trip. 6DPH OLQH IRU QH[W WULS: Only vehicle trips of same line are used for next vehicle trip. o Vehicle trips of different lines are used for next vehicle trip. 1R LQWHUOLQLQJ: no vehicle is to be assigned to different stop during line blocking. 5RXWH VHDUFK: during line blocking, vehicles may also be moved to different stop. Connecting routes are determined via route search.
,QWHUOLQLQJ
Options: /D\RYHU WLPH RI OLQH PLQLPXP OD\RYHU WLPH only after layover time has passed, a vehicle is available for further trips. In this way, necessary driver breaks, for example, can be considered during line blocking.. 6DPH RSHUDWRU IRU LQWHUOLQLQJ WULS for possible interlining trips of vehicles, only links are used which are used by lines of this operator. 6DPH 76\V IRU LQWHUOLQLQJ WULS for possible interlining trip of vehicles, only links permitted for same transport system are used. 6DPH OLQH IRU LQWHUOLQLQJ WULS for possible interlining trip of vehicles, only links of same line are used. 7LPH SHQDOWLHV Define time penalty in [hh:mm:ss] for a line change or interlining:
/LQH FKDQJH: Penalty per subline change (e.g. /2XW -> /5HW) ,QWHUOLQLQJ: Penalty per line move from DestTerminal to another stop (OriginTerminal).
G
8
Time of begin of PuT operation is set via Menu CALCULATE PROCEDURES - )XQFWLRQV - 3X7)XQFWLRQV
/LQH EORFNLQJ FDOFXODWLRQ 0HQX &$/&8/$7( 352&('85(6 2SHUDWLRQV Operation: /LQ%ORFN&DOF ([HFXWH button Already existing line blocks can be initialised at beginning via Menu CALCULATE - PROCEDURES - 2SHUDWLRQV Operation: 5HVHW /LQH%ORFNLQJ
Depending on the number of departures to be considered, memory requirements can become very large for this calculation. Line blocking can be cancelled with &DQFHO button, if necessary. /LVW RI ,QGLFDWRUV
0HQX /,67,1*6 67$7,67,&6 /LQH %ORFNV /LQH %ORFNV OLVW W\SH
Every line of the /LQH %ORFNV list describes a vehicle trip, and contains the following information:
/LQH EORFN QXPEHU: this corresponds to a vehicle number, because every blocking requires exactly one vehicle. 9HKLFOH WULS QXPEHU every blocking consists of a trip chain which consists of one or more vehicle trips. The trip number describes the order of vehicle trips. 6XEOLQH: line name, variant identifier, and direction. 'HSDUWXUH WLPH of vehicle trip from origin terminal. 2ULJLQ WHUPLQDO of vehicle trip (name, number or code). $UULYDO WLPH of vehicle trip at destination terminal. 'HVWLQDWLRQ WHUPLQDO of vehicle trip (name, number or code): the vehicle turns at this stop, and next vehicle trip begins here, or the vehicle moves to another stop (starts an interlining trip). /HQJWK between origin and destination terminal (line route) 5XQQLQJ WLPH: time required for trip from origin to destination terminal. Running time describes productive service time for passenger transportation. 0LQ /D\RYHU WLPH: layover time specified by subline (considered if option /D\RYHU WLPH RI OLQH PLQLPXP WLPH). /D\RYHU WLPH: time spent at turning stop. If vehicle is moved, layover time also contains time required for interlining trip. WARNING! The layover time mentioned here is the DFWXDO layover time which may differ from the minimum layover time specified by planner (see Chapter 4.9.2.1).
The indicator QXPEHU RI UHTXLUHG YHKLFOHV (1XP9HK) for every line or for every transport system is displayed in /LQHV list or 3X7 WUDQVSRUW V\VWHPV list
9-33
([DPSOH /LQH EORFNLQJ For the example given in Ch. 9.1.1 line blocking is calculated for all operators with the following options:
By setting the option /D\RYHU WLPH RI OLQH PLQLPXP OD\RYHU the number of required vehicles depends on the layover time of lines. For that reason e.g. the number of required vehicles increases from 1 to 2 if the layover time exceeds 5 minutes. Results:
/LQH %ORFN1U 9HK 7ULS1U 6XEOLQH 'HSDUWXUH 7LPH 2ULJ 7HUP1U $UULYDO 7LPH 'HVW 7HUP1U 5XQQLQJ 7LPH /D\RYHU7LPH
1 1 1 1 1 1 1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 10 11 12 13
BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F
06:00:00 07:00:00 08:00:00 09:00:00 10:00:00 11:00:00 12:00:00 13:00:00 14:00:00 15:00:00 16:00:00 17:00:00 18:00:00
10 40 10 40 10 40 10 40 10 40 10 40 10
06:45:00 07:45:00 08:45:00 09:45:00 10:45:00 11:45:00 12:45:00 13:45:00 14:45:00 15:45:00 16:45:00 17:45:00 18:45:00
40 10 40 10 40 10 40 10 40 10 40 10 40
00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00
00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00
9-34
/LQH %ORFN1U
9HK 7ULS1U
6XEOLQH
'HSDUWXUH 7LPH
2ULJ 7HUP1U
$UULYDO 7LPH
'HVW 7HUP1U
5XQQLQJ 7LPH
/D\RYHU7LPH
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F BUS2 B BUS2 F
06:20:00 06:35:00 07:00:00 07:15:00 07:40:00 07:55:00 08:20:00 08:35:00 09:00:00 09:15:00 09:40:00 09:55:00 10:20:00 10:35:00 11:00:00 11:15:00 11:40:00 11:55:00 12:20:00 12:35:00 13:00:00 13:15:00 13:40:00 13:55:00 14:20:00 14:35:00 15:00:00 15:15:00 15:40:00 15:55:00 16:20:00 16:35:00 17:00:00 17:15:00 17:40:00 17:55:00 18:20:00 18:35:00
40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30
06:33:00 06:48:00 07:13:00 07:28:00 07:53:00 08:08:00 08:33:00 08:48:00 09:13:00 09:28:00 09:53:00 10:08:00 10:33:00 10:48:00 11:13:00 11:28:00 11:53:00 12:08:00 12:33:00 12:48:00 13:13:00 13:28:00 13:53:00 14:08:00 14:33:00 14:48:00 15:13:00 15:28:00 15:53:00 16:08:00 16:33:00 16:48:00 17:13:00 17:28:00 17:53:00 18:08:00 18:33:00 18:48:00
30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40 30 40
00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00 00:13:00
00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00 00:12:00 00:02:00
9-35
/LQH %ORFN1U
9HK 7ULS1U
6XEOLQH
'HSDUWXUH 7LPH
2ULJ 7HUP1U
$UULYDO 7LPH
'HVW 7HUP1U
5XQQLQJ 7LPH
/D\RYHU7LPH
3 3 3 3 3 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F
06:20:00 07:20:00 08:20:00 09:20:00 10:20:00 11:20:00 12:20:00 13:20:00 14:20:00 15:20:00 16:20:00 17:20:00 18:20:00 06:25:00 06:45:00 07:05:00 07:25:00 07:45:00 08:05:00 08:25:00 08:45:00 09:05:00 09:25:00 09:45:00 10:05:00 10:25:00 10:45:00 11:05:00 11:25:00 11:45:00 12:05:00 12:25:00 12:45:00 13:05:00 13:25:00 13:45:00 14:05:00 14:25:00
40 10 40 10 40 10 40 10 40 10 40 10 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20
07:05:00 08:05:00 09:05:00 10:05:00 11:05:00 12:05:00 13:05:00 14:05:00 15:05:00 16:05:00 17:05:00 18:05:00 19:05:00 06:41:00 07:01:00 07:21:00 07:41:00 08:01:00 08:21:00 08:41:00 09:01:00 09:21:00 09:41:00 10:01:00 10:21:00 10:41:00 11:01:00 11:21:00 11:41:00 12:01:00 12:21:00 12:41:00 13:01:00 13:21:00 13:41:00 14:01:00 14:21:00 14:41:00
10 40 10 40 10 40 10 40 10 40 10 40 10 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40 20 40
00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00
00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00
9-36
/LQH %ORFN1U
9HK 7ULS1U
6XEOLQH
'HSDUWXUH 7LPH
2ULJ 7HUP1U
$UULYDO 7LPH
'HVW 7HUP1U
5XQQLQJ 7LPH
/D\RYHU7LPH
4 4 4 4 4 4 4 4 4 4 4 4 4 5 5 5 5 5 5 5 5 5 5 5 5
26 27 28 29 30 31 32 33 34 35 36 37 38 1 2 3 4 5 6 7 8 9 10 11 12
RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B RAIL 1 F RAIL 1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B BUS1 F BUS1 B
14:45:00 15:05:00 15:25:00 15:45:00 16:05:00 16:25:00 16:45:00 17:05:00 17:25:00 17:45:00 18:05:00 18:25:00 18:45:00 06:40:00 07:40:00 08:40:00 09:40:00 10:40:00 11:40:00 12:40:00 13:40:00 14:40:00 15:40:00 16:40:00 17:40:00
40 20 40 20 40 20 40 20 40 20 40 20 40 10 40 10 40 10 40 10 40 10 40 10 40
15:01:00 15:21:00 15:41:00 16:01:00 16:21:00 16:41:00 17:01:00 17:21:00 17:41:00 18:01:00 18:21:00 18:41:00 19:01:00 07:25:00 08:25:00 09:25:00 10:25:00 11:25:00 12:25:00 13:25:00 14:25:00 15:25:00 16:25:00 17:25:00 18:25:00
20 40 20 40 20 40 20 40 20 40 20 40 20 40 10 40 10 40 10 40 10 40 10 40 10
00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:16:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00 00:45:00
00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:04:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00 00:15:00
9-37
&DOFXODWLRQ RI SHUIRUPDQFH LQGLFDWRUV

Performance indicators are calculated automatically following any change in the line data, demand data not required. They are calculated from all the line trips modelled in the network - i.e. for one day. The number of vehicles is obtained from the vehicle blocking (see Ch. 9.1.4). /LVW RI LQGLFDWRUV
0HQX /,67,1*6 68%/,1(6 /,1(6 387 75$1632576<67(06 $5($6 ([DPSOH 6XEOLQHV OLVW
([DPSOH For the example given in Ch. 9.1.1, the indicator values are projected over a period of one year by multiplying throughout by a factor of 300 (see Ch. 9.1.3). See table:
6XEOLQH 9HK.P < 6HDW.P ' 6HDW.P < 6HUYLFH 7LPH' 6HUYLFH 7LPH< 2SHUDWLRQ 7LPH' 2SHUDWLRQ 7LPH<
BUS1 F BUS1 B BUS2 F BUS2 B RAIL1 F RAIL1 B
171000 171000 57000 57000 57000 57000
19950 19950 6650 6650 38000 38000
5985000 5985000 1995000 1995000 11400000 11400000
14:15 14:15 04:07 04:07 05:04 05:04
4275:00 4275:00 1235:00 1235:00 1520:00 1520:00
19:00 19:00 07:55 04:45 08:14 08:14
5700:00 5700:00 2375:00 1425:00 2470:00 2470:00
9-38
Examples of calculations for subline %XV): Vehicle-km per day:

9HKNP' /HQJWK[1XP6HUYLFH NP[ NP
Service time per day:

6HUYLF7' 5XQQLQJ7[1XP6HUY PLQ[ PLQ KUV
Operation time per day:

2S7LPH' 6HUYLF7/D\RYHU7[1XP6HUYLFH PLQ[PLQ KUV
Seat-km per day:

6HDW.P' 6HDW&DS[/LQH/HQJWK[1XP6HUYLFH [NP[ NP
Projected over one year:

6HUYLF7< 2S7LPH< 6HDW.P< 6HUYLF7' 2S7LPH' 6HDW.P' [ [ [ KUV KUV NP
&DOFXODWLRQ RI GHPDQG LQGLFDWRUV

The travel demand indicators result from passengers using the lines. They are based on PuT demand data and are calculated automatically during assignment. /LVW RI LQGLFDWRUV
0HQX /LVWLQJV 68%/,1(6 /,1(6 387 75$1632576<67(06 $5($6 ([DPSOH 6XEOLQHV OLVW
([DPSOH For the example given in Ch. 9.1.1, the indicator values are projected over a period of one year by multiplying by a constant factor of 300 (see Ch. 9.1.3). Travel demand indicators of the sublines are displayed in the list above.
9-39
The indicators are as follows: /LQ7ULSV indicates the total number of /LQH WULSV, i.e. the number of boarding passengers of a line. /LQ7ULSV indicates the number of line trips with RQH WUDQVIHU:
5RXWH 9ROXPH )URP=RQH 7R=RQH 6XEOLQH /LQ7ULSV
Bus1F A-Village X-Town 60 Rail1F Rail1B X-Town A-Village 60 Bus1B
60 60 60 60
D17 indicates the PHDQ QXPEHU RI WUDQVIHUV of a line, and is calculated using the following formula, e.g. for subline %XV):
MaxNT
aNT =
NT =0
LinTrips NT NT
LinTrips
(0 200 ) + (1 60) = 0.1875 320
3DVV+ indicates the SDVVHQJHU KRXUV of a line. This is the total number of hours passengers spend in PuT vehicles of the line or transport system.
3DVV+ /LQ7ULSV[5XQ7LPH%RDUG6WRS$OLJKW6WRS
Method of calculation using the line route of subline %XV) as an example:

1RGH 1U 3DVV%RDUG 3DVV$OLJKW 9ROXPH >SDVV@ 5XQQLQJ 7LPH>PLQ@ 9RO[5XQ7 >SDVV[PLQ@
10 11
220 0
0 0
220
00:06
1320
220 20 0 80 140 30 100 0 240 40 0 240
00:06
+ 1320
00:20
+ 2800
00:13
+ 3120
= 8560 PassMin = 143 PassH
9-40
3DVV.P indicates the passenger kilometers of a line:

3DVV.P /LQHWULSV[7ULS/HQJWK%RDUG6WRS$OLJKW6WRS
Method of calculation using the line route of subline %XV2 as an example:

1RGH 3DVV%RDUG 3DVV$OLJKW 9ROXPH 7ULS/HQJWK 9RO[7ULS/HQJWK >SDVV[PHWHUV@
1U
>SDVV@
>PHWHUV@
10 11
220 0
0 0
220
5000
1100000
220 20 0 80 140 30 100 0 240 40 0 240
5000
+ 1100000
10000
+ 1400000
10000
+ 2400000
= 6000000 Pass-m = 6000 PassKm
9-41
&DOFXODWLRQ RI FRVWV

The total costs of a line or a line service include: 9HKLFOH W\SH FRVWV hourly costs kilometer costs vehicle costs ,QIUDVWUXFWXUH FRVWV stop costs link costs operator costs costs for the use of stops (debt service and maintenance) costs for the use of links (debt service and maintenance) debt service and maintenance as well as costs for administration and distribution time-dependent costs for personnel service time kilometer-dependent costs for fuel, repair, etc. fixed costs for a vehicle (debt service as well as other fixed costs such as insurance costs)
The line performance evaluation compares the costs of a PuT offer to the revenues from fares (see Ch. 9.1.8). The difference between revenues and costs results in the cost coverage or the deficit (see Ch. 9.1.9): + = line revenue line costs cost coverage
The application example from Chapter 9.1.1 is used to explain the calculation of costs and revenues.
9-42

9HKLFOH W\SH FRVWV
Vehicle costs (hourly costs, kilometer costs and fixed costs) depend on the the vehicle type and the operator (public or private operator).
8
0RGLI\ button
0HQX (;75$6 3879(+,&/(7<3(6 0RGLI\ EXWWRQ 0RGLI\ 3X7 YHKLFOH W\SHV GLDORJ Entries by vehicle type:
From these cost entries the daily cost for vehicles can be calculated: per hour per km per vehicle = hourly cost x operation time = kilometer cost x vehicle kilometers = daily/yearly cost per vehicle number of vehicles
9-43
/LVW RI LQGLFDWRUV
0HQX /,67,1*6 38775$1632576<67(06 68%/,1(6 /,1(6 $5($6 ([DPSOH /LQH OLVW
Automatic recalculation following any change in the line data.
Prerequisite for fixed vehicle costs calculation: Carry out vehicle blocking (Menu CALCULATE - PROCEDURES - RSHUDWLRQV operation: YHKLFOH EORFNLQJ) to calulate the number of required vehicles (1XP9HK). Daily cost can be projected to a period of one year by multiplication by 300, see 3URMHFWLRQ in Chapter 9.1.3.
([DPSOH For the example given in Ch. 9.1.1, the indicator values are projected over a period of one year (multiplied by of 300, see Ch. 9.1.3). Vehicle cost indicators and performance indicators required for cost calculation are displayed in the tables below.
3HUIRUPDQFHLQGLFDWRUV /LQH 1XP9HK 9HK.P' 2S7LPH<
BUS1 BUS2 RAIL
3.00 1.00 1.00
1140 380 380
38:00:00 12:40:00 16:28:00
9HKLFOHFRVWLQGLFDWRUV /LQH &RVW+RXU' &RVW+RXU< &RVW.P' &RVW.P< &RVW9HK' &RVW9HK<
BUS1 BUS2 RAIL
1596 532 692
478800 159600 207480
1140 380 1900
342000 114000 570000
300 100 200
90000 30000 60000
9-44
Example calculations for line 5$,/: Hour-Costs per day:

&RVW+RXU' FRVWSHUKRXU[2S7LPH' &8K[K &8
Kilometer-Costs per day:

&RVW.P' FRVWSHUNLORPHWHU[9HK.P' &8NP[NP &8
Fixed vehicle costs per day:

&RVW9HK' IL[HGFRVWV[1XP9HK &89HK[9HK &8
Projection to a period of one year:

&RVW+RXU< &RVW.P< &RVW9HK< &RVW+RXU' &RVW.P' &RVW9HK' [ [ [ &8 &8 &8

,QIUDVWUXFWXUH FRVWV VWRS FRVWV
Stop costs are infrastructure costs assigned to a line for using the stop. The stop costs are divided equally between the line trips which use the stop. Three types of costs can be distinguished: GHSW VHUYLFH: annual costs for amortization and interest rates UXQQLQJ FRVW: maintenance and operating costs XWLOL]DWLRQ FRVW track fees (QWHULQJ FRVW YDOXHV
Allocation of up to three cost values: for a single stop via 02',)<12'( in SINGLE SELECT MODE or for a group of stops via 02',)<12'(6in MULTI SELECT MODE. 0RGLI\ QRGH 6WRS FRVW 0RGLI\ QRGHV )RUPXOD
9-45
&DOFXODWLRQ RI VWRS FRVW
0HQX &$/&8/$7( 352&('85(6 )XQFWLRQV 3X7)XQFWLRQV 6WRS FRVW GLDORJ
&RVW YDOXH Select a cost value (6WRS&RVW ). The numbers refer to the cost values saved for stops. 1DPH Name the cost. $PRUWL]DWLRQ Depreciation time '7 for depreciation cost ,QWHUHVW UDWH Interest rate S for the depreciation cost 7LPH UHI WR <HDU: running costs calculated for one year. 'D\: running costs calculated for one day.
G
9-46
Projection of daily cost values to annual cost values and vice versa is defined by the constant projection factor )DF76 and respectively )DF76 (see Chapter 9.1.3).
7\SH RI FRVW Select a cost type: 'HSUHFLDWLRQ FRVW (debt service for the annual cost of amortization and interest). The cost per vehicle trip (&RVW6WRS97) results from:
$' 6WRS& R V W < T T & R V W6 WR S 9 7 = $' T
9HK7ULS
)DF76
+ S Z K H UH T =
5XQQLQJ FRVW (maintenance and operating costs). The costs per vehicle trip result from the annual running cost according to:
&RVW6WRS9
6WRS&RVW < 9HK7ULS '$<
)DF76
8WLOL]DWLRQ FRVW (fees for using a stop). The costs per vehicle trip correspond to the stop cost value:
6WRS&RVW97 6WRS&RVW
0HQX &$/&8/$7( 352&('85(6 2SHUDWLRQV Operation: ,QIUDVWUXFWXUH&RVW Procedure: 6WRSV Button: 3DUDPHWHUV &DOFXODWH LQIUDVWUXFWXUH FRVW GLDORJ
3DUDPHWHUV Button
Select the cost values to be calculated (see status output): FDQ EH FDOFXODWHG: cost values are available. FDQQRW EH FDOFXODWHG: cost values are not available.
0HQX &$/&8/$7( 352&('85(6 ([HFXWH EXWWRQ Start stop cost calculation
9-47
/LVW RI LQGLFDWRUV
0HQX /,67,1*6 12'(6
Cost value1..3 for each stop: Stop&RVW etc Cost value1..3 for each stop per vehicle trip: 6WRS&RVW97, etc.
0HQX /,67,1*6 68%/,1(6 /,1(6 387 75$1632576<67(06
Daily and annual stop cost: 6WRS&RVW'D\<HDU etc
Stop costs arise for DOO traversed stops, i.e. not only for served stops.
$SSOLFDWLRQ H[DPSOH For the stops No. , , , , (see example in Chapter 9.1.1) the following stop costs are estimated:
7\SHRIFRVW $PRXQW>&8@ 5HI7LPH '7>\HDUV@ S>@
Cost1 Cost2 Cost3
Depreciation cost Running cost Utilization cost
100000 1000 10 year
10
9-48
The costs resulting for sublines, lines or transport systems using a stop are calculated as follows: First, the costs per line trip are calculated for each stop (with the constant projection factor )DF76 = 300; see Chapter 9.1.3), e.g. for stop No. 10: Depreciation cost (&RVW):
97 6WS&RVW
6WRSW&RVW T $' T = $' T
9HK7ULS 'D\
)DF76
ZKHUH
= +
S
&8 =

&8
Running cost (&RVW):

6WS&RVW 97
6WRS&RVW 9HK7ULS
<
'D\
)DF76
= &8
&8
Utilization cost (&RVW):

6WRS&RVW97 6WRS&RVW &8
9-49
From this, the total daily or annual cost for stop usage per line or transport system is calculated, e.g. for the lines: Calculating the daily stop cost for a bus line %XV (used stops: and ): = + + %86 'D\
&RVW6WRS ' 1XP9HK7ULSV 6WRS&RVW 97 6WRS&RVW 97 6WRS&RVW 97

&8
&8

&8
&8
=
+ &8 + &8 = &8
Calculating the daily stop cost for a rail line 5DLO (used stops: and ): = + + 5DLO
&RVW6WRS ' 1XP9HK7ULSV 6WRS&RVW 97 6WRS&RVW 97 6WRS&RVW 97
= =

&8
&8
+
&8
+
&8

&8
+
&8
=
&8
The same costs arise for the bus line %XV as for the rail line, as only two stops (No. and ) are used in each case.
9-50

,QIUDVWUXFWXUH FRVW OLQN FRVW
Link costs are infrastructure costs assigned to a line for using the link. The link costs are divided equally between the line trips which use the link. Three types of costs can be distinguished: GHEW VHUYLFH: annual costs for amortization and interest rates FXUUHQW FRVWV: maintenance and operating costs XVDJH FRVWV route fees
(QWHULQJ FRVW YDOXHV
$OORFDWLRQ RI XS WR WKUHH FRVW YDOXHV SHU WUDQVSRUW V\VWHP for a single link via EDIT - MODIFY in SINGLE SELECT mode, for multiple links via EDIT - MODIFY in MULTI SELECT mode. 0RGLI\ OLQN 3X76\V /LQN $WWULEXWHV )RUPXOD
9-51
&DOFXODWLRQ RI OLQN FRVW
0HQX&$/&8/$7( 352&('85(6 )XQFWLRQV 3X7 IXQFWLRQV /LQN FRVW GLDORJ
&RVW YDOXH Choice of cost values 1 to 3 (&RVW3X76\V). The numbers refer to the cost values saved for links. 1DPH Designation of the cost, e.g. "Investment cost" for the cost type 'HSUHFLDWLRQ FRVW. $PRUWL]DWLRQ Depreciation time '7 for depreciation cost. ,QWHUHVW UDWH Interest rate S for the depreciation cost. OHQJWK UHI WR /LQN OHQJWK: the cost values refer to the total link length. .LORPHWHUPHWHU: the cost values refer to one kilometer/meter of the link length. In this case, the cost value of each cost type must be multiplied with the link length. 7LPH UHI WR <HDU: running costs calculated for one year. 'D\: running costs calculated for one day.
9-52
Projection of daily cost values to annual cost values and vice versa is defined by the constant projection factor )DF76 and respectively )DF76 (see Chapter 9.1.3). 7\SH RI FRVW Choice of three cost types: Depreciation cost (annual costs for amortization and interest rates). The cost per vehicle trip - e.g. based on the link length results from:
&RVW973X76\V
&RVW3X76\V T $' T = $' T
9HK7ULS
'$<
)DF76
ZKHUH T

S
Running cost (maintenance and operating cost). The cost per vehicle trip - e.g. based on the link length and the annual running cost results from:
&RVW973X76\V
9HK7ULS
&RVW3X76\V
)DF76
<
Utilization cost (route fees). The cost per vehicle trip - e.g. based on the link length - correspond to the link cost value:
&RVW973X76\V
/LQN/HQJWK
= &RVW3X76\V
0HQX &$/&8/$7( 352&('85(6 2SHUDWLRQV Operation: ,QIUDVWUXFWXUH&RVW Procedure: /LQNV Button: 3DUDPHWHUV &DOFXODWH LQIUDVWUXFWXUH FRVW GLDORJ
3DUDPHWHUV Button
Selection of the cost values to be calculated and their status: FDQ EH FDOFXODWHG: The cost values are available. FDQQRW EH FDOFXODWHG: The cost values are not available.
0HQX &$/&8/$7( 352&('85(6 ([HFXWH EXWWRQ Start the calculation of link cost
9-53
/LVW RI LQGLFDWRUV
0HQX /,67,1*6 38775$1632576<67(06 68%/,1(6 /,1(6 $5($6 ([DPSOH 6XEOLQHV OLVW
$SSOLFDWLRQ H[DPSOH For the 10 km rail link between stop and stop (example in Chapter 9.1.1) the following link cost (for both directions) is estimated:
7\SHRIFRVW $PRXQW OHQJWKUHIWR
$3
>\HDUV@
>@
Cost1 Cost2
Utilization cost Depreciation cost
0.01 CU/km 100000 CU
meters link length 10 years 7
The link cost for the rail line (PuTSys Z )are calculated as follows: Utilization cost &RVW Calculation of the link cost per vehicle trip:
&RVW973X76\V= &RVW3X76\V=[OHQJWK &8P[P &8
9-54
From this, the total daily link cost for using the route between stop No. and No. can be calculated, e.g. for the rail subline 5DLO):
&RVW/LQN'OLQN1R &RVW973X76\V=[1XP/LQH7ULSV &8[ &8
&RVW/LQN'OLQN1R
&RVW973X76\V=[1XP/LQH7ULSV
&8[
&8
&RVW/LQN'5DLO+
&RVW/LQN'OLQN1R&RVW/LQN'OLQN1R
&8
The annual link cost for the rail sublines result from the projection factor 3URM)DF = 300 (see Chapter 9.1.3):
CostLink1(Y) = CostLink1(D) x 300 = 950 CU x 300 = 570000 CU
Depreciation cost &RVW): Calculation of the link cost per vehicle trip:
&RVW973X76\V=
&RVW3X76\V= T $' T = $' 9HK7ULS )DF76 T

&8
ZKHUH
= + S
&8 =
The daily and annual link cost for using the route between stops No. and No. for the rail sublines 5DLO) and 5DLO%, are calculated in the same way as &RVW. The result is:
9-55

,QIUDVWUXFWXUH FRVW RSHUDWRU FRVW
Infrastructure costs resulting for a line also include operator costs, i.e. depreciation costs and running costs. The distribution of operator costs to lines or vehicle trips can be specified by the indicators 9HKLFOH NLORPHWHUV, 6HDW NLORPHWHUV, 6HUYLFH WLPH, 9HKLFOH WULSV, 3DVVHQJHU NLORPHWHUV and /LQH WULSV.
8
2SHUDWRU
0HQX(;75$6 387 23(5$7256 2SHUDWRU GLDORJ
0RGLI\ RSHUDWRU GLDORJ 0RGLI\ button
For an operator, up to three cost values can be specified.
9-56
8
2SHUDWRU FRVW
0HQX &$/&8/$7( 352&('85(6 )XQFWLRQV 3X7)XQFWLRQV
&RVW YDOXH Select cost value 1-3 (&RVW2). The number refers to the operatorspecific cost values. 1DPH User-defined cost name $PRUWL]DWLRQ Depreciation time '7 for depreciation cost. ,QWHUHVW UDWH Interest rate S for depreciation cost. 7LPH UHI WR <HDU: the running costs refer to one year. 'D\: the running costs refer to one day.
Projection of daily cost values to annual cost values and vice versa is defined by the constant projection factor )DF76 and respectively )DF76 (see Chapter 9.1.3).
9-57
:HLJKWLQJ Specify weighting key for distribution of cost to the individual vehicle trip (weighted indicators: YHKLFOH NLORPHWHUV VHDW NLORPHWHUV VHUYLFH WLPH YHKLFOH WULSV SDVVHQJHU NLORPHWHU OLQH WULSV):
6KDUH YHK7ULS 9HK.P 9HK7ULS 1XP9HK7ULS V
L
=
:HLJKW9HK .P +
1XP9HK7ULS V
6HDW.P 9HK7ULS
9HK.P L
L
=
:HLJKW6HD W.P
6HDW.P L
+ 1XP9HK7ULSV
6HUYLFH7 9HK7ULS
L
=
:HLJKW6HUYLFH7 +
1XP9HK7ULS V
:HLJKW9HK7ULS
6HUYLFH7 L
PassKmVehTrip
NumVehTrips i =1
PassKm
WeightPassKm +
LineTripsVehTtrip
NumVehTrips i =1
LineTrips
WeightLineTrips
The weightings must sum up to 100 %. 7\SH RI FRVW Select cost type: Depreciation cost; operator costs for one vehicle trip by operator 2 are calculated via
&RVW2S 9HK7ULS 2
&RVW T T 6KDUH = T )DF76

'7 2 '7
9HK7ULS 2
ZLWKT
= + S
Running cost; operator costs for one vehicle trip by operator O are calculated via
&RVW2S
9HK7ULS2
&RVW
6KDUH
)DF76
9HK7ULS 2
0HQX &$/&8/$7( 352&('85(6 2SHUDWLRQV Operation: ,QIUDVWUXFWXUH&RVWV Procedure 2SHUDWRU 3DUDPHWHUV button &DOFXODWH LQIUDVWUXFWXUH FRVW GLDORJ
3DUDPHWHUV button
Select cost value 1-3 (the number refers to the operator-specific cost values) for operator cost calculation: FDQ EH FDOFXODWHG: Cost values are available. FDQQRW EH FDOFXODWHG: Cost values are not available.
0HQX &$/&8/$7( 352&('85(6 ([HFXWH button: Start of operator cost calculation.
/LVW RI LQGLFDWRUV
0HQX /,67,1*6 38775$1632576<67(06 68%/,1(6 /,1(6 $5($6 ([DPSOH 6XEOLQH OLVW
([DPSOH See example in Chapter 9.1.1: For the operators 0XQLFLSDO VHUYLFH and 5DLO DVVR FLDWLRQ 100000 CU/year have been specified for management and administration. Enter cost values for every operator and specify parameters for operator cost calculation. For distribution of cost to the lines and sublines the share per line service is used which results from the weighting parameters (see above). For 5DLO (Operator: 5DLOZD\ &RPSDQ\) the annual administration costs are distributed to the 2 sublines (50 % each = 50000 CU), as relevant indicators do not differ. For %XV (Operator: 0XQLFLSDO VHUYLFH) cost are distributed with regard to 9HKLFOH NLOR PHWHUV and 6HUYLFH WLPH, both values are weighted by 50%. Line route length and service time of the bus lines differ:
9-59
Calculation for line %XV:
6KDUH/,1(
6KDUH/,1(
9HK.P /,1( :HLJKW9HK. P 9HK.P WRWDO

6HUYLFH7/,1( :HLJKW6HUYLFH7 6HUYLFH7WRWDO
+

=
&8[ &8
&RVW2S<
&RVW[6KDUH
/,1(

7RWDO FRVWV
The total costs are summed up from the calculated individual costs, they are displayed for one day and for one year (daily value multiplied by 300, see example). /LVW RI LQGLFDWRUV
0HQX /,67,1*6 38775$1632576<67(06 /,1(6 68%,1(6 $5($6 ([DPSOH /LQH OLVW In the sublines, lines and PuT transport systems lists all cost indicators are output. Here stop costs and CRVW/LQN are not regarded.
([DPSOH $UHD OLVW In the areas list, the vehicle-related costs (&RVW+RXU, &RVW.P, &RVW9HK) and the total &RVW value are output, cost for links, stops and operators are not calculated by area. See example: list output of indicators for tariff zones TZ100 and TZ200:
9-60
Display of sublines:
5HYHQXH FDOFXODWLRQ DQG UHYHQXH JHDULQJ

In VISUM, revenues can be calculated and then distributed over the individual lines. There are four methods available for revenue calculation: 1. &DOFXODWLQJ UHYHQXHV XVLQJ D WDULII PRGHO the fare is calculated for each passengers current ticket type. This fare is then distributed over those lines used by the passenger. 2. 6SHFLI\LQJ D IL[HG EDVLF UHYHQXH SHU SDVVHQJHU WULS a standard fare is assumed for each passenger and distributed over those lines used by the passenger. 3. 6SHFLI\LQJ D EDVLF UHYHQXH SHU ULGH NLORPHWHU the revenue results from the basic revenue/km multiplied by the passenger kilometers. As passenger kilometers are available by line, no revenue distribution details are required. 4. 6SHFLI\LQJ D WRWDO UHYHQXH from a specified total revenue for all lines, or a selection of lines, and from the passenger-km of the selected lines the revenue per ride kilometer is calculated, which then is multiplied by passenger-km of the selected lines. See example in Ch. 9.1.1: all types of revenue calculation are performed: 1. Calculating the revenues using the tariff model (Ch. 9.1.2) for the VLQJOH WLFNHW ticket type, 2. Specifying a fixed basic revenue of 4.00 CU per passenger trip, 3. Specifying a basic revenue of 0.20 CU per ride kilometer, 4. Distribution of a total revenue of 10000 CU over all sublines by passenger-km. The daily revenues can be projected over a period of one year (in the application example by multiplying by a factor of 300).

*HQHUDO 3URFHGXUH
0HQX&$/&8/$7( 352&('85(6 )XQFWLRQV 3X7)XQFWLRQV 5HYHQXH GLDORJ
5HYHQXH FDOFXODWLRQ DQG GLVWULEXWLRQ RI UHYHQXHV
5HYHQXH FDOFXODWLRQ 5HYHQXH IURP 7DULII PRGHO IRU WLFNHW W\SH: Revenue calculation from a tariff model. To do this, a ticket type must be set to active in menu EXTRAS - PUT FARES. IL[ UHYHQXH SHU OLQH WULS: Revenue calculation by specifying a fixed basic revenue per line trip. UHYHQXH SHU ULGH NLORPHWHU: Revenue calculation by specifying a basic revenue per ride kilometer. 7RWDO UHYHQXH: Revenue calculation by specifying a total basic revenue for all lines or for a selection of lines (/LQH VHOHFWLRQ button).
6WDUW UHYHQXH FDOFXODWLRQ DQG UHYHQXH GLVWULEXWLRQ Menu CALCULATE - PROCEDURES - 2SHUDWLRQV Operation:3X7 UHYH QXHV Menu CALCULATE - PROCEDURES ([HFXWH button
9-62
G
8
Revenue distribution is performed with different parameter settings. The 4 models are described in detail in the following subchapters.
/LVW RI LQGLFDWRUV 0HQX /,67,1*6 38775$1632576<67(06 /,1(6 68%/,1(6 $5($6 /LVW IRU /LQHV FDOFXODWHG IURP WDULII PRGHO VHH EHORZ
9-63

5HYHQXH FDOFXODWLRQ XVLQJ WDULII PRGHO

The calculated fare consists of basic fare and supplements: 1. Distribution of basic fare by :HLJKW NLORPHWHU and :HLJKW 1XPEHU RI URXWH VHFWLRQV The length of a route section can be regarded and/or the number of route sections. 2. Distribution of supplements: o 'LVWULEXWH VXSSOHPHQWV E\ WUDQVSRUW V\VWHP (method 1): When this option is disabled, the supplements are distributed according to the distribution key defined in step 1 to DOO route sections - regardless of the transport system. In this way, each train profits from each supplement, e.g. an IR profits from an ICE supplement. 'LVWULEXWH VXSSOHPHQWV E\ WUDQVSRUW V\VWHP (method 2): When this option is enabled, the supplements charged for a transport system are distributed only to those route sections, which are used by that transport system. The distribution key defined in step 1 is then used for the individual route sections. Thus, if IC and IR are used, IR gets no share of the IC supplement.
9-64
Exception: VHYHUDO transport systems having the highest rank of fixed supplements (defined via EXTRAS - PUT FARES). In this case, the calculated maximum supplement is distributed to DOO these transport systems. $GGLWLRQDO RSWLRQ: Prior to distribution of revenues from basic fare and supplements a fix amount per route section can be defined. Then the remaining amount (= revenue fixed amount x number of route sections) is distributed according to the description above.
A detailed example to illustrate revenue gearing including fixed costs is described in Chapter 2.
&DOFXODWLRQ H[DPSOH IRU GLVWULEXWLQJ WKH VXSSOHPHQWV
FRQQHFWLRQ WUDYHO GLVWDQFH GLVWDQFH WRWDO EDVLFIDUH IL[HG UHYHQXH UHYHQXH VKDUH PHWKRG VXSSOHPHQW VKDUH PHWKRG
EC (rank 2) IC (rank 2) IR (rank 3)

WRWDO
100000 100000 100000
100000 200000 300000 30.00 CU

&8
7.00 CU 7.00 CU 0.00 CU

&8
12.33 CU (**)13.50 CU 12.33 CU (**)13.50 CU 12.33 CU

&8
10.00 CU
&8
In this example, the rank of the fixed supplements is considered. (**) Because the ranks are equal, only the highest supplement (here: 7.00 CU) is charged. According to method 1, the basic fare and the supplements are distributed evenly to all transport systems. According to method 2, the 7.00 CU are distributed to the two transport systems, because they have the same rank.
9-65
5HYHQXH FDOFXODWLRQ XVLQJ WKH WDULII PRGHO LQ &K For the revenue calculation using the tariff model in Ch. 9.1.2, the following route table provides an overview of all the required indicators including passenger trips (9RO):
)URP=RQH 7R=RQH 6XEOLQH 9RO 1XP76= 1XP7= RQHZD\ WLFNHW 6XSSOHPHQW )DUH 5HY 9RO[IDUH
A village A village A village X town X town X town X town X town B village B village C village C village
X town X town C village A village A village B village B village C village X town X town A village X town
BUS1 1 O BUS1 1 O, RAIL 1 O BUS1 1 O BUS1 1 B RAIL 1 B, BUS1 1 B BUS1 1 B BUS2 1 B RAIL 1 B BUS1 1 O BUS2 1 O BUS1 1 B RAIL 1 O
140 60 20 140 60 100 100 500 100 100 20 500
5 5 3 5 5 2 2 3 2 2 3 3
2 2 1 2 2 1 1 2 1 1 1 2
3.00 3.00 2.00 3.00 3.00 1.00 1.00 3.00 1.00 1.00 2.00 3.00
0.00 3.00 0.00 0.00 3.00 0.00 0.00 3.00 0.00 0.00 0.00 3.00
3.00 6.00 2.00 3.00 6.00 1.00 1.00 6.00 1.00 1.00 2.00 6.00 Total
420.00 360.00 40.00 420.00 360.00 100.00 100.00 3000.00 100.00 100.00 40.00 3000.00 = 8040.00
Method of calculation for the distribution of the daily fare revenues on the sublines:
6XEOLQH )URP=RQH 7R=RQH /LQ7ULSV )DUH 5HY /LQ7ULSV[)DUH
BUS1 1 O
A village A village A village B village
X town X town C village X town X town A village A village A village B village B village C village A village X town X town
140 60 20 100 100 140 60 20 100 100 500 60 500 60
3.00 6.00 2.00 1.00 1.00 3.00 6.00 2.00 1.00 1.00 6.00 6.00 6.00 6.00
420.00 360.00 x = 180.00 40.00 100.00 Total = 740.00 100.00 Total = 100.00 420.00 360.00 x = 180.00 40.00 100.00 Total = 740.00 100.00 Total = 100.00 3000.00 360.00 x = 180.00 Total = 3180.00 3000.00 360.00 x = 180.00 Total = 3180.00 Total = 8040.00
BUS2 1 O BUS1 1 B
B village X town X town C village X town
BUS2 1 B RAIL 1 B
X town X town X town
RAIL 1 O
C village A village
9-66
Revenue gearing is performed using the following formula:

6KDUH.P 6KDUH3DUW5RXWHV 6KDUH/LQH /HQJWK56/HQJWK7RWDO 1XPEHURISDUWLDOURXWHV 6KDUH.P[:HLJKW.P6KDUH3DUW5RXWHV[:HLJKW3DUW5
Num-PartR Length-PR Length-Total WeightKm WeightPR
Number of partial routes per passenger trip Length of partial route Total length of passenger trip Kilometer weighting partial route weighting
:HLJKW.P:HLJKW3DUW5RXWH
Distribution of the revenues must now be performed for those passenger trips using more than one line. In the example given, this applies only to 2 x 60 passengers who travel by bus and rail between A village and X town. As the route section lengths for both bus (A village - C village) and for rail (C village - X town) add up to 10 km, there is a distribution factor of 0.5 in each case.
6KDUH.P%XV2 6KDUH3DUW5RXWH%XV2 6KDUH/LQH%XV2 NPNPNP
[[
As a result, an indication of fixed costs per route section is not required for revenue gearing. This equal distribution of revenue gearing also applies to the following example of a calculation using a standard fare. A detailed example to illustrate revenue gearing including fixed costs is described in Ch. 2.
9-67

5HYHQXH FDOFXODWLRQ E\ VSHFLI\LQJ D IL[HG EDVLF UHYHQXH SHU SDVVHQJHU WULS

Revenue calculation is to be executed with a fixed basic revenue of 4.00 CU per passenger trip The revenue can then be distributed as in the case of revenue distribution according to a tariff model using a distribution key resulting from :HLJKW .LORPHWHUV and/or :HLJKW 1XPEHU RI URXWH VHFWLRQV.
9-68
The following route table provides an overview of all necessary indicators including passenger trips (/LQ7ULSV) for the revenue calculation:
6XEOLQH )URP=RQH 7R=RQH /LQ7ULSV )DUH 5HY /LQ7ULSV[)DUH
BUS1 1 O
X town X town C village X town
140 60 20 100
4.00 4.00 4.00 4.00
560.00 240.00 x = 120.00 80.00 400.00 Total = 1160.00
BUS2 1 O
B village
X town
100
4.00
400.00 Total = 400.00
BUS1 1 B
X town X town C village X town
140 60 20 100
4.00 4.00 4.00 4.00
560.00 240.00 x = 120.00 80.00 400.00 Total = 1160.00
BUS2 1 B
X town
B village
100
4.00
400.00 Total = 400.00
RAIL 1 B
X town X town
C village A village
500 60
4.00 4.00
2000.00 240.00 x = 120.00 Total = 2120.00
RAIL 1 O
C village A village
X town X town
500 60
4.00 4.00
2000.00 240.00 x = 120.00 Total = 2120.00 Total = 7360.00
9-69

5HYHQXH FDOFXODWLRQ E\ VSHFLI\LQJ D IL[ UHYHQXH SHU SDVVHQJHU NLORPHWHU

The revenue shall be calculated using a fixed revenue amount of 0.20 CU per transport kilometer. The revenue results from EDVLF UHYHQXHNP multiplied by SDVVHQJHU NLORPHWHUV. As the passenger kilometers are given for each line, no revenue distribution details are required. The following subline list shows the necessary indicators as well as the total revenue for revenue calculation:
Method of calculating the total revenue for subline %XV2:

%DVLFUHYHQXH3DVV.P 5HY7RW' 5HY7RW< &83DVV.P &83DVV.P[3DVV.P &8
%DVLF5HY3DVV.P[3DVV.P' 5HY7RW'[ &8
9-70

5HYHQXH FDOFXODWLRQ E\ VSHFLI\LQJ D WRWDO UHYHQXH

5HYHQXH FDOFXODWLRQ Enter the total revenue. Via the /LQH VHOHFWLRQ EXWWRQ the total revenue can be assigned to a selection of lines. 6HOHFWHG OLQHV GLDORJ /LQH VHOHFWLRQ button Mark the bus sublines: %XV), %XV%, %XV) and %XV%. $OO OLQHV button: selects all lines total revenue calculation. $SSO\ ILOWHU button: consider active line filter.
)XUWKHU RSWLRQV
9-71
5HYHQXH GLVWULEXWLRQ The revenue distribution can be carried out as follows: )L[HG DPRXQW SHU OLQH WULS: A fixed amount can be entered for each line trip. The fixed amount total from the total number of line trips is then subtracted from the total revenue and thus not considered in the revenue distribution. :HLJKW 3DVVHQJHUNP DQG :HLJKW /LQH WULSV: The distribution of the total revenue to the lines can result from the share of passenger kilometers or the share of line trips or from a weighted combination of passenger kilometers and line trips.
5HYHQXH FDOFXODWLRQ ZLWK D GDLO\ WRWDO UHYHQXH RI &8 IRU DOO OLQHV Distribution of a daily total revenue of 10000 CU for all lines based on passenger kilometer (Weight Passenger-km: 100 %). The following subline list shows the indicators as well as the distribution of the total revenue:
Method of calculating the basic revenue per line trip:

%DVLFUHYHQXHOLQHWULS 5HYHQXH'1HWZRUN/LQ7ULSV'1HWZRUN &8
&8SHUOLQHWULS
Method of calculating the revenue of subline %XV):

5HYHQXH'%XV) 5HYHQXH<%XV) %DVLFUHYHQXHOLQHWULS[/LQ7ULSV'%XV) 5HYHQXH'%XV)[ &8
a&8[ &8
9-72
7RWDO UHYHQXH RI &8 IRU WKH EXV OLQH QHWZRUN The distribution of the daily total revenue of 6000 CU for the bus line network to the sublines is carried out as described above and is shown in the following list:
9-73
&DOFXODWLRQ RI FRVW FRYHUDJH

For cost coverage calculation total revenues have to be compared with total costs: + = revenue of lines cost of lines Cost coverage
Cost coverage total: CC7RW CC3HUF

= 5HY7RW CRVWV
Cost coverage percentage:

= (5HY7RW/ FRVWV x 100
Cost coverage for each line trip: CC/LQ7ULS = CC7RW / Num/LQ7ULS
/LVW RI LQGLFDWRUV
0HQX /,67,1*6 38775$1632576<67(06 /,1(6 68%,1(6 $5($6 /LQHV OLVW
([DPSOH For the example of application in Ch. 9.1.1, the cost coverage calculation for all lines is based on the total costs in Ch. 9.1.7.5 and on the revenue calculation using a tariff model (Ch. 9.1.8), and then projected over a period of one year by multiplying by a factor of 300 (for indicators: see list). Method of calculation for line %XV:
&&7RW' &&3HUF< &&/LQ7ULS' 5HY7RW'&RVWV' 5HY7RW'&RVWV'[ 5HY7RW'/LQ7ULSV' &8&8 &8 &8
9-74
Analysis of transfer quality
$QDO\VLV RI WUDQVIHU TXDOLW\
The PuT Transfer quality function analyzes the arrival and departure timetable at stops, i.e. it compares the arrival and departure times of line services and then calculates the transfer waiting times. The purpose of the calculation is to obtain an overview of the connections available at particular stops. Furthermore the transfer quality for services of selected lines can be compared. This offers the possibility of obtaining details on transfers that were just missed. The WUDQVIHU ZDLWLQJ WLPH 7:7 indicator is calculated from the assignment for all connections, and aggregated to the mean indicator P7:7 subsequently, which can be saved as indicator matrix or displayed as node attribute (basic VISUM functionality). Since the transfer waiting time is an aggregate value after applying this calculation method, in contrast to the calculation with the PuT TRANSFER QUALITY function, it includes neither information on the lines concerned nor a frequency distribution. There is also no information included on narrow or missed connections.
9-75
%DVLF DSSURDFK
0HQX&$/&8/$7( 387 75$16)(548$/,7< &DOFXODWH WUDQVIHU TXDOLW\ GLDORJ
&DOFXODWLRQ 3DUDPHWHUV EXWWRQ Enter calculation parameters for the transfer quality (see Ch. 9.2.2). (YDOXDWLRQ 3DUDPHWHUV EXWWRQ Enter evaluation classes for the calculated transfer waiting times (see Ch. 9.2.3). 2XWSXW The results of the calculation are saved in output files in the form of ASCII lists for further processing using database or spreadsheet software tools. Two output files are generated (see also Ch. 9.2.5): 7UDQVIHU ZDLWLQJ WLPH This file (*.att) contains - for each line service - all line services which may serve as a connection. Each data record in the list contains the name and arrival time of the FromSubline, the name and departure time of the ToSubline, and the resulting transfer waiting time. 7UDQVIHU IUHTXHQF\ This file (*.att) contains both mean transfer waiting time and frequency of transfer waiting time for each relation )URP6XEOLQH7R6XEOLQH. 2SHQ6DYH EXWWRQV Open or save transfer quality parameters file *.apa (calculation, evaluation and output parameters; see Ch. 9.2.4). &DOFXODWH EXWWRQ Start calculation.
9-76
6HWWLQJ FDOFXODWLRQ SDUDPHWHUV
0HQX&$/&8/$7( 387 75$16)(548$/,7< &DOFXODWH WUDQVIHU TXDOLW\ GLDORJ &DOFXODWLRQ 3DUDPHWHUV button &DOFXODWLRQ RI WUDQVIHU TXDOLW\ DW VWRSV GLDORJ
7LPH LQWHUYDO Time interval for timetable analysis. All line services arriving within this given interval are subject to the analysis. 0LQLPXP WUDQVIHU WLPH Minimum time required for transfers (between arrival and departure). If walk links are required for transfers walking time is considered additionally. :DLWLQJ WLPH For waiting time T:7 there are two calculation methods available: 7:7 'HSDUWXUH WLPH $UULYDO WLPH :DONLQJ WLPH (minimum 7:7 'HSDUWXUH WLPH $UULYDO WLPH 0$; transfer time; walking time)
9-77
&RQQHFWLRQV Transfers available for the calculation: All connections; evaluation is based on Class Type 1 (see Ch. 9.2.3). Only connections which are defined in the VHOHFWLRQ ILOH GDW may be calculated. The selection file contains data for specific analyses, in which only selected connections are to be considered. For the evaluation, Class Types other than Type 1 can be included (see Ch. 9.2.5). Only connections which are "relevant". Irrelevant are transfer relations: for which no transfer option was found within the given time interval. for which several departures were found for an arrival. Only the first possible connection is then relevant. for which several arrivals were found for a departure. Only the first possible connection is then relevant. Additional connections using walk links from/to stops. *URXSLQJ The following line services are compared in the calculation: of different sublines, or in different line directions. )LOWHU Only active stops are regarded for calculation.
9-78
'HILQLQJ HYDOXDWLRQ FODVVHV IRU &ODVV 7\SHV

A Class Type consists of evaluation classes for the calculated transfer waiting times. By defining Class Types, it is possible to classify the transfer waiting times differently at different stops. It can be useful, for example, to consider a waiting time of 0 to 120 seconds to be the ideal for bus stops, whereas at railway stations a longer waiting time of 120 to 600 seconds may be ideal.
0HQX&$/&8/$7( 387 75$16)(548$/,7< &DOFXODWLQJ WUDQVIHU TXDOLW\ GLDORJ (YDOXDWLRQ 3DUDPHWHUV button 7\SHV RI FODVVHV GLDORJ
VISUM always uses Class Type for the evaluation of the transfer quality. ,QVHUW EXWWRQ RU 0RGLI\ EXWWRQ Define evaluation classes.
Use an external text editor to assign the Class Types for evaluation of transfers at selected stops in the ASCII selection file *.dat (see example in Ch. 9.2.5.). If only the transfer quality of the stops specified in the selection file is to be calculated, the option RQO\ WUDQVIHUV IURP must be selected in the dialog box "Calculation of transfer quality at stops".
9-79
,QVHUWPRGLI\ W\SH RI FODVV GLDORJ
For the evaluation of the transfer quality, the calculated transfer waiting time is classified. Up to 8 evaluation classes can be defined. Classes 1 to 6 classify possible connections, whereas Classes 7 and 8 represent missed connections.
9-80
)LOH PDQDJHPHQW

&RGH *.apa 'HVFULSWLRQ 7UDQVIHU TXDOLW\ SDUDPHWHUV ILOH The binary file contains the entries for the calculation and evaluation parameters and the file output of the calculation. Open file: *.att Menu FILE - OPEN: 7UDQVIHU SDUDPHWHUV or Menu CALCULATE - PUT TRANSFER QUALITY: 2SHQ Menu FILE - SAVE: 7UDQVIHU SDUDPHWHUV Menu CALCULATE - PUT TRANSFER QUALITY: 6DYH. 7UDQVIHU ZDLWLQJ WLPH ILOH the ASCII file contains - for each line service - all line services which may serve as a connection. Each data record in the list contains the name and arrival time of the FromSubline, the name and departure time of the ToSubline, and the resulting transfer waiting time. Save file: Menu CALCULATE - PUT TRANSFER QUALITY, Output option 7UDQVIHU ZDLWLQJ WLPH 7UDQVIHU IUHTXHQF\ ILOH the ASCII file contains both mean transfer waiting time and frequency of transfer waiting time distribution for each relation )URP6XEOLQH7R6XEOLQH. Save file: Menu CALCULATE - PUT TRANSFER QUALITY, Output option WUDQVIHU IUHTXHQF\ *.dat 6HOHFWLRQ ILOH The ASCII file contains data for specific analyses, in which only selected connections are to be considered. The file is created using a text editor. Open file: Menu CALCULATE - PUT TRANSFER QUALITY, &DOFXODWLRQ SDUDPHWHUV button, Option RQO\ FRQQHFWLRQV IURP
Save file:
2XWSXW ILOHV
9-81
$SSOLFDWLRQ H[DPSOH

An extended version of the application example from Ch. 9.1.1 is shown here as an example of a network used for transfer analysis. At the railway station a transfer can be made from %XV (20-minute service frequency) to two regional express lines 5( and 5( (each with a 60-minute service frequency):
7KH DSSURDFK XVHG WR DQDO\VH WKH WUDQVIHU TXDOLW\ RI VSHFLILF WUDQVIHUV DW 6WRS UDLOZD\ VWDWLRQ Create selection file: stop20.dat: The selection file is created using an external text editor. Define and select Class Type : Menu CALCULATE - PUT TRANSFER QUALITY, (YDOXDWLRQ 3DUDPHWHUV button, Selection &ODVV 7\SH and 0RGLI\ button Transfers with 0 to 120 seconds waiting time TransferClass 1 Transfers with 121 to 240 seconds waiting time TransferClass 2 Transfers with 241 to 540 seconds waiting time TransferClass 3
9-82
Transfers with 541 to 900 seconds waiting time Transfers with 901 to 1800 seconds waiting time Transfers with over 1800 seconds waiting time Transfers with -1 to -60 seconds waiting time Transfers with -61 to -120 seconds waiting time
TransferClass 4 TransferClass 5 TransferClass 6 TransferClass 7 TransferClass 8
Open selection file: Menu CALCULATE - PUT TRANSFER QUALITY, &DOFXODWLRQ 3DUDPHWHUV button, Option RQO\ FRQQHFWLRQV IURP stop20.dat.
Specify output files: Menu CALCULATE - PUT TRANSFER QUALITY, options 7UDQVIHU ZDLWLQJ WLPH twt.att and 7UDQVIHU IUHTXHQF\ freq.att.
Save transfer parameters file: Menu CALCULATE - PUT TRANSFER QUALITY, 6DYH button example.apa 6WDUW FDOFXODWLRQ: Menu CALCULATE - PUT TRANSFER QUALITY, &DOFXODWH button
6HOHFWLRQ ILOH VWRSGDW The selection file contains data for specific analyses, in which only selected connections are to be considered. In the example given, the connections at Stop of %XV) to the line group 5DLO only (consisting of the regional express lines 5( and 5() are analysed; the transfers are evaluated on the basis of Class Type 1:
$VISION $VERSION:VersNr;FileType;Language 1.0;Dat;E * * $NETPARA:Timeformat Min * *Grouping of Lines $ConnQClassif:Name;LinName Rail;RE1 Rail;RE2 * $CONNLINES:StopNr;FromName;FromDir;ToName;ToDir;FromNode;ToNode;MinTWT;ClType 20;Bus1;F;Rail;;;40;2;1
9-83
1(7:25. 3$5$0(7(56 WDEOH The time format attribute (min, sec) indicates whether the attribute 0LQ7:7 in the connection lines is to be interpreted as minutes (e.g. 2) or as seconds (e.g. 120). &2114&/$66,) WDEOH Lines can be grouped in this optional table, e.g. 5( and 5( to form the line group 5DLO. &211/,1(6 WDEOH Selection of stops to be analysed. For each stop (6WRS1U), an indication is given from which line ()URP1DPH) and direction ()URP'LUHFWLRQ), and to which line (7R1DPH) and in which direction (7R'LUHFWLRQ)
connections are to be analysed. For each of these possible connections a particular minimum transfer time (0LQ7:7), and the Class Type (&O7\SH) to be included
can be specified. The attributes )URP1RGH and 7R1RGH are optional. They are used to filter a particular direction of grouped lines (e.g. the connections from %XV) to all trains serving Stop . 7UDQVIHU ZDLWLQJ WLPH RXWSXW ILOH 2XWSXW ILOH H[WUDFW LI DOO FRQQHFWLRQV DUH FDOFXODWHG WZWDWW
$+ConnList:StopNr;relevant;FromName;FromVariant;FromDir;ArrTime;FromStop;BoardStop;ToName;To Var;ToDir;DepTime;ToStop;TWT;minTWT;WT;ClType;Class;MissDepT;MissTWT;MissWTZ;MissClass 20;*;BUS1;;F;07:06:00;;20;RE1;;H;07:25:00;;1140;120;1140;1;K6;;;; 20; ;BUS1;;F;07:26:00;;20;RE1;;H;08:25:00;;3540;120;3540;1;K6;07:25:00;-60;-60;X1 20; ;BUS1;;F;07:46:00;;20;RE1;;H;08:25:00;;2340;120;2340;1;K6;;;; 20;*;BUS1;;F;08:06:00;;20;RE1;;H;08:25:00;;1140;120;1140;1;K6;;;; 20; ;BUS1;;F;08:26:00;;20;RE1;;H;09:25:00;;3540;120;3540;1;K6;08:25:00;-60;-60;X1 20; ;BUS1;;F;08:46:00;;20;RE1;;H;09:25:00;;2340;120;2340;1;K6;;;; 20; ;BUS1;;F;07:06:00;;20;RE2;;H;07:55:00;;2940;120;2940;1;K6;;;; 20; ;BUS1;;F;07:26:00;;20;RE2;;H;07:55:00;;1740;120;1740;1;K6;;;; 20;*;BUS1;;F;07:46:00;;20;RE2;;H;07:55:00;; 540;120; 540;1;K4;;;; 20; ;BUS1;;F;08:06:00;;20;RE2;;H;08:55:00;;2940;120;2940;1;K6;;;; 20; ;BUS1;;F;08:26:00;;20;RE2;;H;08:55:00;;1740;120;1740;1;K6;;;; 20;*;BUS1;;F;08:46:00;;20;RE2;;H;08:55:00;; 540;120; 540;1;K4;;;;
9-84
2XWSXW ILOH LI RQO\ WKRVH FRQQHFWLRQV GHILQHG LQ VHOHFWLRQ ILOH VWRSGDW DUH FDOFXODWHG VWRSBWZWDWW
$+ConnList:StopNr;relevant;FromName;FromVariant;FromDir;ArrTime;FromStop;BoardStop;ToName;To Var;ToDir;DepTime;ToStop;TWT;minTWT;WT;ClType;Class;MissDepT;MissTWT;MissTWT;MissClass 20;*;BUS1;;F;07:06:00;;20;Rail;;;07:25:00;40;1140;120;1140;1;K6;;;; 20; ;BUS1;;F;07:26:00;;20;Rail;;;07:55:00;40;1740;120;1740;1;K6;07:25:00;-60;-60;X1 20;*;BUS1;;F;07:46:00;;20;Rail;;;07:55:00;40; 540;120; 540;1;K4;;;; 20;*;BUS1;;F;08:06:00;;20;Rail;;;08:25:00;40;1140;120;1140;1;K6;;;; 20; ;BUS1;;F;08:26:00;;20;Rail;;;08:55:00;40;1740;120;1740;1;K6;08:25:00;-60;-60;X1 20;*;BUS1;;F;08:46:00;;20;RRail;;;08:55:00;40; 540;120; 540;1;K4;;;;
6WRS1U UHOHYDQW )URP1DPH )URP9DULDQW )URP'LUHFWLRQ $UU7LPH )URP6WRS %RDUG6WRS 7R1DPH 7R9DULDQW 7R'LUHFWLRQ 'HS7LPH 7R6WRS 7:7 PLQ7:7 :7
Number of transfer stop * indicates relevant connections Name of arriving line Variant of arriving line Direction of arriving line Time of arrival FromStopNr (from Selection file Table $ConnLines) Number of Boarding stop (only connections with transfer walking links) Name of departing line Variant of departing line Direction of departing line Time of departure Number of ToStop (from Selection file Table $ConnLines) Transfer waiting time between arrival and departure minimum transfer time Waiting time (calculation based on calculation parameters) for conn. classification:
TWT = Dep. time Arr. time Walking time TWT = Dep. time Arr. time MAX (minimum transfer time; Walking time)
arriving line service
departing line service
&O7\SH &ODVV 0LVV'HS7 0LVV7:7 0LVV:7 0LVV&ODVV
Class type Transfer wait time classification, e.g. I = narrow Departure time of missed line service Transfer wait time for missed connection Waiting time for missed connection Classification of missed transfer waiting time
9-85
7UDQVIHU IUHTXHQF\ RXWSXW ILOH 2XWSXW ILOH H[WUDFW LI DOO FRQQHFWLRQV DUH FDOFXODWHG )UHTDWW
* Conn. quality $+ConnQuality:StopNr;FromName;FromVariant;FromDir;FromStop;BoardStop;ToName;ToVar;ToDir; ToStop;meanTWT;minTWT;NumArr;NumConn;ClType;Class(1);Class(2);Class(3);Class(4);Class(5); Class(6);Class(7);Class(8) 20;BUS1;;F;;20;RE1;;F;;1140;120;6;2;1;0;0;0;0;0;2;2;0 20;BUS1;;F;;20;RE2;;F;;540;120;6;2;1;0;0;0;2;0;0;0;0
2XWSXW ILOH LI RQO\ WKRVH FRQQHFWLRQV GHILQHG LQ VHOHFWLRQ ILOH VWRSGDW DUH FDOFXODWHG VWRSBIUHTDWW
* Conn. quality $+ConnQuality:StopNr;FromName;FromVariant;FromDir;FromStop;BoardStop;ToName;ToVar;ToDir; ToStop;meanTWT;minTWT;NumArr;NumConn;ClType;Class(1);Class(2);Class(3);Class(4);Class(5); Class(6);Class(7);Class(8) 20;BUS1;;F;;20;Rail;;;40;840;120;6;4;1;0;0;0;2;0;2;2;0
6WRS1U
Number of transfer stop Name of arriving line Variant of arriving line Direction of arriving line Number of FromStop (from Selection file Table ConnLines) Number of Boarding stop (for connections with transfer walking link) Name of departing line Variant of departing line Direction of departing line Number of ToStop (from Selection file Table $ConnLines) mean transfer waiting time of relation within the analysed time interval minimum transfer time Number of line services arriving within the analysed time interval Number of connections/correspondig services found Class type Number of connections per waiting time class i departing line service arriving line service
)URP1DPH
)URP9DULDQW
)URP'LUHFWLRQ
)URP6WRS
%RDUG6WRS
7R1DPH
7R9DULDQW
7R'LUHFWLRQ
7R6WRS
PHDQ7:7
PLQ7:7
1XP$UU
1XP&RQQ
&O7\SH
&ODVVL
9-86
Passenger survey Add-on
3DVVHQJHU VXUYH\ $GGRQ
Passenger interviews and counts are essential for public transport planning. Usually the passengers route within the public transport line network is not described completely by interview data. This applies especially to passengers who have to transfer several times or need to walk for transfers. Survey personnel usually count the passengers boarding the surveyed line at the stop and ask for the following details of the trip: Origin stop of passenger trip, Boarding stop of passenger trip where passengers enter the survey line, i.e. the stop at which the passenger is interviewed by the survey personnel, Alighting stop of passenger trip where passengers will leave the survey line, Destination stop of passenger trip.
The passenger data is then verified and completed, if necessary. The departure time at the boarding stop or at the origin terminal of the survey line are also recorded in the questionnaires. The add-on 3DVVHQJHU VXUYH\ module in VISUM contains the following basic functions: Verification and completion of the survey data records containing the basic passenger trip data, Direct assignment of volumes resulting from counts and interviews (survey data records) to the public transport line network, Generation of demand matrices (*.fma) and patterns of temporal distribution of passengers (*.fga), Calculation of indicators for the each survey data record (running time, number of transfers, number of tariff zones traversed, fares, etc.).
When the direct assignment of the survey data in the passenger survey module is completed, the full range of the VISUM functionality for analysis and display of results is available, e.g. flow bundles.
9-87
%DVLF GDWD RI D SDVVHQJHU WULS

Preceding line Survey line Succeeding line
Dest. terminal Line i
Origin terminal Preceding line
2ULJLQ6WRS
1st Transfer
Dest. terminal Line j
Origin terminal Survey line
%RDUG6WRS
$OLJKW6WRS
2nd Transfer
Dest. terminal Line k
Origin terminal Succeeding line Route of passenger trip Origin or destination terminal of a line Passengers origin, boarding, transfer, alighting or destination stop
'HVW6WRS
'HVLJQDWLRQ
'HVFULSWLRQ
Survey line Preceding/Succeeding
Name of line/subline on which passenger is interviewed (e.g. %XV). Partial routes used by passenger before or after the survey line. Partial route: part of a passenger trip on a line with no transfers from boarding to alighting (number of partial routes = number of transfers +1)
Origin terminal Destination terminal OriginStop DestStop BoardStop AlightStop
First stop of a line trip. Last stop of a line trip. Starting stop (origin) of a passenger trip: first boarding stop entering a PuT line. Destination stop of a passenger trip: last alighting stop leaving a PuT line. Boarding stop of the survey line: stop at which the passenger enters the survey line. Alighting stop of the survey line: stop at which the passenger leaves the survey line. VISUM User Manual (April 2001) Version 7.50
9-88
6WDQGDUG TXHVWLRQQDLUH
4XHVWLRQQDLUH
Line: Orig.Term.: Departure: Bus 1 A village 6:10
The replies obtained in a passenger survey are noted down in TXHVWLRQQDLUHV. Such a questionnaire form usually consists of a header into which details identifying the questionnaire are entered, such as the interviewers number, vehicle class and route number, and a main section, in which codes for the boarding and alighting stops of the survey line are entered, plus information on any preceding or succeeding lines.
5RXWH
Preced. 2: Preced. 1: Boarding: Alighting: Suceed. 1: Suceed. 2: Y town Station B village 42 20 30
7LFNHW
One-Way Season Group .... Number of Persons
x
1
The figure on the left is a schematic diagram of a questionnaire. In the case of the questionnaire shown here, up to 5 partial routes (2 preceding lines + survey line + 2 succeeding lines) can be recorded.
%DVLF GDWD RI D VWDQGDUG VXUYH\ ILOH VXU In the evaluation of a passenger survey, survey data must first be transferred to storage media. Usually the survey data are then available in a database. From the database, the standard survey files *.sur required by VISUM can now be generated. In the following file example, the compulsory and optional input data for the plausibilization by the passenger module are described in detail:
$VISION $VERSION:VersNr;FileType;Language 1.0;Net;E * $PUTSURVEY:RecNr;SurLinName;SurLinVar;SurLinDir;SurLinDep;OStopNr; PreStopNr;BoardStopNr;AlightStopNr;SucStopNr;DStopNr;NumPers;ExtProjFac 1;RE1 ;1;F;07:25;10;;20;50;; ;1;5.0 2;Bus1;1;F;07:14; ;;10;30;; ;1;2.0 3;Bus1;1;F;07:14; ;;10;20;;60;1;2.0
If the results of a plausibilization are already available in partial route format (see Ch. 9.3.4), the appropriate partial route file can also be opened as a survey file for further plausibilization.
9-89
5HF1U
Number of the survey record Name of survey line Direction of survey line (optional) Variant of survey line with (optional) Identifier of preceding subline with name, variant and direction (optional) Identifier of suceeding subline with name, variant and direction (optional) Departure time of survey line service from starting stop (orig. terminal) Departure time at boarding stop of passenger in survey line (optional) Number of origin stop of passenger trip (optional) Stop Nr. where passenger boarded the survey line Stop Nr. where passenger will alight the survey line Stop Nr. of a succeeding stop (transfer stop) of passenger trip (optional) Destination stop Nr. of passenger trip (optional) Number of persons External projection factor (optional) and other optional attributes
6XU/LQ1DPH
6XU/LQ'LU
6XU/LQ9DU
3UH6/LQ,'
6XF6/LQ,'
6XU/LQ'HS
%RDUG6WRS'HS
2ULJLQ6WRS1U
%RDUG6WRS1U
$OLJKW6WRS1U
6XF6WRS1U
'6WRS1U
1XP3HUV
([W3URM)DF

9-90
*HQHUDO DSSURDFK
0HQX&$/&8/$7( 3$66(1*(56859(< 3DVVHQJHU VXUYH\V GLDORJ
Up to 10 2SHUDWLRQV can be selected and performed in sequence. For the complete survey evaluation the following operations can be selected: 1. 'HOHWH LQWHUYLHZ GDWD: remove all previously read survey data records (initialisation). 2. 5HDG LQWHUYLHZ GDWD: read the survey data records. 3. 3ODXVLELOL]DWLRQ: verify and complete survey data records. 4. *HQHUDWLQJ ]RQHV: generate automatically zones at origin and destination stops of passenger trips. 5. 'LUHFW DVVLJQPHQW: assign survey data records onto the network and generate subsequently an O-D matrix. 6. ,QGLFDWRUV: calculate PuT indicator matrix for each survey data record. 7. 6DYH YHUVLRQ WR ILOH: save version to the specified file. Enable option $FWLYH to perform an operation. With reference to the application example in Ch. 9.2.5, the individual steps when working with the passenger module are described in detail below.
9-91
/RDGLQJ VXUYH\ GDWD
Open the passenger file: passenger.sur. If necessary delete all survey data from a previous plausibilization.
G
2SWLRQV button
If the results of a plausibilization are already available in partial route format (see Ch. 9.3.4), the appropriate partial route file can be read as survey data file for further plausibilization. 2SWLRQV GLDORJ
Options, in the event that data records with identical data record number are already present when reading the new survey data: LJQRUH: data record with the identical data record number will be skipped and thus remains unchanged. RYHUZULWH: data record with the identical data record number will be overwritten with the read data record. FDQFHO: read procedure will be cancelled.
9-92
The data is verified for the first time when the survey data is being loaded: If a stop included in the data records of the network under review is not found, an error message to that effect will be displayed, with the option of either canceling the loading procedure or continuing. e.g. :
3DVVHQJHU ILOH SDVVHQJHUVXU The survey file contains 4 survey data records with incomplete information; for the compulsory attributes 26WRS1U and 'VWRS1U in particular, there are no complete details available:
R. Nr 1 2 3 4 SurLin Id RE1/1/F Bus1/1/F Bus1/1/F Bus1/1/F SurLin OSt. Pre Board Dep Nr StopNr StopNr 07:25 10 20 07:14 10 07:14 10 07:14 20 Alight Suc DSt. Num Ext StopNr St.Nr Nr Pers Pr.F. 50 1 5 30 1 2 20 60 1 2 30 1 1
3ODXVLELOL]DWLRQ RI VXUYH\ GDWD UHFRUGV

For plausibility purposes the correctness of the route stated by the passenger is verified for each survey record. By comparing each survey record with the timetable information of a VISUM network model it is possible to identify and correct survey records which state an incorrect route. Furthermore, additional data are added to each data record: Times of departure and of arrival, used sublines, ride distance.
3UHFRQGLWLRQ IRU YDOLGLW\ FKHFN The boarding and alighting stops stated in the interview data records of the surveyed line must exist in the checked network. If this is not the case, the record in question is ignored.
9-93
%DVLF DSSURDFK As a rule, the validity check is carried out in the following steps: 1. check the survey line interview data, 2. check previous line survey data 3. check succeeding line survey data For all these steps, the validity check can be run several times, in order to check the survey data successively with hard-to-meet criteria, which become easier and easier with each run. 9DOLGLW\ FKHFN RI VXUYH\ OLQH
3DUWLDOURXWHVXUYH\OLQH IRXQGLQGDWDUHFRUG
( ( ( ( SODXVLEOH 6WDWXVRIVXUYH\OLQHSODXVLELOL]DWLRQ
(
(
(
QRWSODXVLEOH
6XE/LQH %RDUG6WRS $OLJKW6WRS
Check: Find Survey line with listed , , and matching time of departure.
QR
\HV
(
Other criteria for check?

\HV
Check: Find 6XUY/LQH with %RDUG6WRS, $OLJKW6WRS(matching dep. time) in sublines line and/or all lines.
QR
( \HV
( QR
Conn. search permitted?
\HV
Check: Find connection from %RDUG6WRS to $OLJKW6WRS with matching dep. time.
QR
( \HV
QR
QRW SODXVLEOH
SODXVLEOH
9-94
9DOLGLW\ FKHFN RI WKH SUHFHGLQJ URXWH

3ODXVLELOLW\VWDWXVRISUHFHGLQJURXWH
6XUYH\OLQHLVSODXVLEOH 'HSWLPHDQGSUHFHGLQJ VWRSVPRUHGHWDLOV DYDLODEOH L

9 QRWSODXVLEOH 9 9 9 9 SODXVLEOH
3URFHVVLQJWKHLSUHFHGLQJURXWH 3UH6WRSL3UH6WRSL RU3UH6WRS%RDUG6WRS
Check: Are there more data available for partial route (dep. time, subline etc.)?
\HV
Check: Is there another veh. trip from 3UH6WRS to 3UH6WRS available, arriving at 3UH6WRS before or at dep. time and having a minimum wait time at 3UH6WRS with the given constraints.
L L L L
QR
QR
\HV
Check: Is there a veh. trip from 3UH6WRS to 3UH6WRS , available, arriving at 3UH6WRS before or at dep. time and having a minimum wait time at 3UH6WRS .
L L L L
\HV
Another preceding stop available?
\HV
9
QR
QR
Connection search permitted?
\HV
Search for connection from 2ULJ7HUP to 3UH6WRS , arriving at 3UH6WRS before or at dep. time and having a minimum wait time at 3UH6WRS .
L L L
9
QR
QR
\HV
9
QRW SODXVLEOH
SODXVLEOH
RSWLRQ&KHFNLIGHWRXU VKDUHRIDSODXVLEOHSUH FHGLQJURXWHLVRND\
QR
9
DXWRP DWLF5HSODFH SUHFHGLQJURXWHZLWK WUDQVIHUVE\GLUHFW FRQQHFWLRQLIDYDLODEOH
9
5HSODFHWKHSODXVLEOH SUHFHGLQJURXWHE\DQ LQGLUHFWFRQQHFWLRQ ZKLFKUHTXLUHVOHVVWLPH
9-95
9DOLGLW\ FKHFN RI WKH VXFFHHGLQJ URXWH The validity check of the succeeding route is carried out in the same way as the validity check of the preceding data. 6WDWXV LQGLFDWRUV RI WKH YDOLGLW\ FKHFN TXDOLW\ The quality of a validity check is described in a result file with a status indicator between 0 and 9 for each survey record: for the total survey record (T) for the survey line (E), for the preceding route (P) and for the succeeding route (S).
6WDWXV LQGLFDWRUV IRU WKH VXUYH\ OLQH ( 0 1 not yet checked. plausible: The survey line is replaced with an identical subline (with the same name, variant and direction) , which serves the connection between the boarding and alighting stop at the given departure time. plausible: The survey line is replaced with another subline with the same name, which serves the connection between the boarding and alighting stop at the given departure time. plausible: The survey line is replaced with any subline, which serves the connection between the boarding and alighting stop at the given departure time. lausible: The survey line is replaced with an indirect connection found via a timetable-based search (with transfers including walk links). implausible, because the boarding or alighting stop of the survey line is wrong. implausible, because no departure time can be found for the survey line. implausible with the given criteria (except status 7 or 8).
5 7 8 9
9-96
6WDWXV LQGLFDWRUV IRU WKH SUHFHGLQJ URXWH 3 0 1 4 does not exist. plausible: The line sequence for all preceding route sections could be read directly from the timetable. plausible: The preceding route with transfer stop(s) (3UH6WRS) in the survey record is replaced by the direct connection of any subline between 2ULJLQ6WRS and %RDUG6WRS. plausible: The preceding route is replaced with an indirect connection found via the timetable-based search (with transfers including walk links). plausible: The direct connection between 2ULJLQ6WRS and %RDUG6WRS (status 4), which exceeds the predefined detour tolerance, is replaced by a shorter indirect connection found via the timetable-based search. implausible, because no route section (sequence) was found using the current validity check criteria. does not exist. plausible: The line sequence for all succeeding route sections could be read directly from the timetable. plausible: The succeeding route with transfer stop(s) (6XF6WRS) in the survey record is replaced by the direct connection of any subline between $OLJKW6WRS and 'HVW6WRS. plausible: The succeeding route is replaced with an indirect connection found via the timetable-based search (with transfers including walk links). plausible: The direct connection between $OLJKW6WRS and 'HVW6WRS (status 4), which exceeds the predefined detour tolerance, is replaced by a shorter indirect connection found via the timetable-based search. implausible, because no route section (sequence) was found using the current validity check criteria. not processed. plausible: All existing sections (preceding route, succeeding route and/or survey line) are plausible. implausible, because at least one of the existing sections (preceding route, succeeding route and/or survey line) is implausible.
5 6
6WDWXV LQGLFDWRUV IRU WKH VXFFHHGLQJ URXWH 6 0 1 4
5 6
6WDWXV LQGLFDWRUV IRU WKH WRWDO VXUYH\ UHFRUG 7 0 1 9
9-97
*HQHUDO VHWWLQJV IRU SODXVLELOL]DWLRQ SDUDPHWHUV
3DUDPHWHUV button 3ODXVLELOL]DWLRQ SDUDPHWHUV GLDORJ 3DUDPHWHUV
3URWRFRO To examine the results of the plausibility check, a protocol can be saved either to the error file or to a separate protocol file. If, for example, the subline 5() of data record no. 1 in the passenger.sur survey file is not found in the network under review, the following error will be listed in the protocol file prot.txt:
9-98
5HVXOWV The results can be saved in partial route format with different information relating to plausibilization quality: LQ SDUWLDO URXWH ILOH: output with validated partial route partrout.txt o LQ SDUWLDO URXWH ILOH: no output of results. FRQILUP WR RYHUZULWH: if the results are to be saved in an existing file, a prompt appears.
Partial route files can also be opened as survey files for a further plausibility check. ([WHQW RI SODXVLELO DOO GDWD UHFRUGV: All data records even those previously checked can be subjected to a plausibility check with the selected parameters. WARNING! Since this process requires a considerable amount of computing time, the option should be used with caution, e.g. only when several data records with different evaluation standards have been given separate plausibility checks, in order to finally carry out a plausibilization on all the survey data collectively using standardized parameters. RQO\ GDWD UHFRUGV ZKLFK DUH QRW SODXVLEOH: Plausibility checks are only carried out on data records which have not yet been checked (plausibilization status *) or which are "implausible", i.e. in the previous plausibility check the parameters had been too stringent (plausibilization status *). RQO\ GDWD UHFRUGV WKDW KDYH QRW EHHQ SODXVLELO \HW: Only data records which have not yet been checked, i.e. only with plausibilization status * are given a plausibilization
9-99
3ODXVLELOL]DWLRQ RI VXUYH\ OLQH 3ODXVLELOL]DWLRQ RI VXUYH\ OLQH GLDORJ 6XUY/LQH button
6XUYH\ OLQH The following parameters are provided for selecting a survey line: Search for the subline name of the survey line in the network: identifier: VXEOLQH PD[ SHUP GHSDUWXUH WLPH GHYLDWLRQ . Thus, a survey record is only plausible if a subline is found in the network which fulfils the following criteria: Name, variant and direction are the same. The line trip lies within the departure time tolerance (referring to %RDUG6WRS'HS). In this case, the survey record receives the plausibility status (.
9-100
Search for another subline of the survey line in the network: identifier: OLQH RWKHU YDULDQW RI VXUYH\ OLQH SHUPLWWHG. PD[ SHUP GHSDUWXUH WLPH GHYLDWLRQ . Thus, a survey record is also plausible if another subline of the survey line is found in the network. To this line, the following still applies: The line trip lies within the departure time tolerance (referring to %RDUG6WRS'HS). The departure time is the next possible time as compared to the other sublines of the survey line. In this case, the survey record receives the plausibility status (. Search for a subline of another line in the network: identifier: OLQH RWKHU OLQH SHUPLWWHG PD[ SHUP GHSDUWXUH WLPH GHYLDWLRQ . Thus, a survey record is also plausible if any other subline of another line is found in the network. To this line, the following still applies: The line trip lies within the departure time tolerance (referring to %RDUG6WRS'HS). The departure time is the next possible time as compared to other sublines. In this case, the survey record receives the plausibility status (.
'HSDUWXUH WLPH The search for a suitable vehicle trip for the found subline is controlled by entering a maximum departure time deviation: PD[ SHUP GHSDUWXUH WLPH GHYLDWLRQ default 1 min. Thus, a survey record, for which a subline was found in the network, is only plausible if the departure time deviation of the vehicle trip (referring to %RDUG6WRS'HS) lies within the tolerated deviation.
9-101
&RQQHFWLRQ VHDUFK If no subline is found for the survey line of the survey record, then a timetable-based search for an indirect connection in the network can be carried out: &RQQHFWLRQ VHDUFK %RDUG6WRS$OLJKW6WRS ZKHQ QR VXEOLQH H[LVWV 6HDUFK button: Specification of parameters for the timetable-based method 1 connection search (see below). Thus, a survey record is also plausible if an indirect connection (including walk links) within the specified departure time tolerance period referring to %RDUG6WRS'HS (see connection search parameters: PLQ WUDQVIHU WLPH and PD[ ZDLW WLPH for node types) is found between the boarding and alighting stop. In this case, the survey record receives the plausibility status (. 3ODXVLELOL]DWLRQ RI SUHFHGLQJ DQG VXFFHHGLQJ VHFWLRQ 3ODXVLELO SUHFHGVXFFHHG GLDORJ 3UH6XF button
9-102
3UHFHGLQJ6XFFHHGLQJ OLQH FRQVLGHU FRGH : When complete timetable data is available, e.g. in a route section file as a result of a preliminary validity check, then a GLUHFW SODXVLELOLW\ FKHFN can be carried out by searching for the code (line identifiers): LGHQWLILHU: VXEOLQH Searches for identical subline names of the preceding and/or succeeding lines in the network, i.e. with the same name, variant and direction. LGHQWLILHU: OLQH Other variant of preceding/succeeding line permitted. Searches for any subline names of the preceding and/or succeeding lines in the network. LGHQWLILHU: OLQH other line permitted. Searches for any subline in the network. o FRQVLGHU FRGH Usually, a survey record contains no information on sublines or times of the preceding and/or succeeding route sections. In this case, it is necessary to disable the search for line identifiers (code) and carry out a timetable-based connection search instead (see below). 'HSDUWXUH WLPH FRQVLGHU VSHFLILHG WLPHV RI GHSDUWXUHV In the GLUHFW SODXVLELOLW\ FKHFN, it is possible to specify a maximum permitted departure time deviation in a search for a suitable vehicle trip. If several vehicle trips are possible, then the vehicle trip with the next possible departure time (referring to %RDUG6WRS'HS) is selected. Thus, a survey record, for which suitable sublines for the preceding and succeeding routes were found in the network, is only plausible if the departure time deviation of the vehicle trip lies within the tolerated deviation (max. perm. depart. time deviation). If it was possible to determine the line sequence directly from the timetable, then the survey record receives the plausibility status 9 RU 1.
9-103
&RQQHFWLRQ VHDUFK A timetable-based connection search in the network is carried out: when a preceding or succeeding route with the plausibility status 9 or 1 could be found. In this case, a timetable-based connection search for a GLUHFW FRQQHFWLRQ between 3UH6WRS and %RDUG6WRS or between $OLJKW6WRS and 6XF6WRS LV FDUULHG RXW DXWRPDWLFDOO\:
Replacing a preceding route with transfer stop (PreStop2) by a direct connection (subline OrigTerminal BoardStop) Replacing a succeeding route with transfer stop (SucStop1) by a direct connection ( subline AlightStop DestTerminal) SurvLin BoardStop AlightStop SucStop1 SucStop2 (DTerm)
PreStop1 (OTerm)
PreStop2
The survey record receives the plausibility status 9 RU 1. when no direct plausibility could be found. Thus, a survey record is also plausible when an indirect connection (with transfers including walk links) between the boarding or alighting stop (%RDUG6WRS or $OLJKW6WRS) of the last plausible partial route and the origin or destination stop is found for the preceding or succeeding route and when the departure time lies within the specified maximum deviation referring to %RDUG6WRS'HS (depending on the minimum transfer time and the maximum wait time; see search parameters).
Thus, the system searches for the next possible subline, which arrives on time at the boarding stop of the last plausible partial route. The survey record then receives the plausibility status 9 RU 1.
3UHFHGLQJURXWH 6XFFHHGLQJURXWH
Timetable-based connection search from BoardStop of verified preceding route (PreStop2) for OriginTerminal.
Timetable-based connection search from AlightStop of verified succeeding route (SucStop1) to DestinationTerminal. SurvLine
PreStop1 (OTerm)
PreStop2 BoardStop AlightStop
SucStop1
SucStop2 (DTerm
9-104
if the inconvenience of the direct connection is greater than a specified value. Thus, a survey record is also plausible if an indirect, but shorter connection is found instead of the previously found direct connection (status ; see above), which exceeds the specified inconvenience tolerance range (default: 1.5):
Fahrplanfeine Verbindungssuche, weil die direkt plausible Verbindung eine zu groe Umwegigkeit besitzt, z.B.: VorHst1 (QHst)
8
)DKUWZHLWH 4+VW(LQ+VW /XIWOLQLHQ OlQJH 4+VW(LQ+VW

VorHst2 ErhLin EinHst
AusHst
The survey record receives the plausibility status 9 RU 1. 3DUDPHWHU VHWWLQJV IRU VW WLPHWDEOHEDVHG DVVLJQPHQW SURFHGXUH VHDUFK 3DUDPHWHUV VW WLPHWDEOHEDVHG DVVLJQPHQW SURFHGXUH 6HDUFK 6HDUFK button Specification of parameters for the connection search of survey line, preceding and succeeding lines on the basis of WLPHWDEOHEDVHG SURFHGXUH . Detailed description: Parameters: see Ch. 7 and Timetable-related assignment: see Ch. 2.
9-105
2XWSXW RI SODXVLELOL]DWLRQ UHVXOWV
3DUWLDO URXWH ILOH SDUWURXWW[W

R. G V E N IN Typ LinName/ B. Board
Nr DEX 1 1 1 1 0 1 T 1 1 1 1 0 2 E 2 3 3 4 1 1 1 1 0 0 0 0 1 1 1 1 0 1 1 0 1 1 2 1 E E T E
A. Alight
Num Ext
Pers Pr.Fac 1 5 1 5 1 1 1 1 2 2 2 1
Var/Dir St. StopDep St. StopArr BUS1/2/F 10 07:04:00 20 07:16:00 RE1/1/F 20 07:25:00 50 08:11:00 BUS1/1/F BUS1/1/F RE2/1/F BUS1/1/F 10 10 20 20 07:14:00 07:14:00 07:55:00 07:26:00 30 20 60 30 07:46:00 07:26:00 08:41:00 07:46:00
The output file includes details on the quality of the completed plausibility check for the individual partial routes, i.e. all the survey data records: 7\SH F = Survey data record with indication of origin and destination stop of passenger trip. E = Survey part. route with stops where passengers enter and leave the survey line (boarding and alighting stop of passenger trip). T = Other partial route with boarding and alighting stop of passengers trip. 3ODXVLELOLW\ FKHFN VWDWXV T = Total P =Preceding S =Succeeding E =Survey line
The status indicators of the plausibility check quality (0 to 9 ) are described above under the description of the general procedure.
9-106
9HULILFDWLRQ RI SODXVLELOL]DWLRQ UHVXOWV 3ODXVLELO YHULILFDWLRQ GLDORJ 9HULI\ button 9HULILFDWLRQ RI SODXVLELOLW\ FKHFN FRPSDUH VXUYH\ GDWD DQG WLPHWDEOHEDVHG FRQQ VHDUFK: For verification purposes, a connection search is performed at the starting time which is obtained from the plausibility check. The results are recorded and saved either in the error file or in a separate protocol file (see dialog box "Plausibil. parameters"), to provide a comparison with the survey data.
*HQHUDWLQJ ]RQHV

For direct assignment zones are required which are the origins and destinations of passenger trips. If the network model does not contain any zones or not all of the zones required by demand (at origin/destination stops of passenger trips) zones can be generated automatically.
3DUDPHWHUV button
9-107
3DUDPHWHUV IRU JHQHUDWLQJ ]RQHV GLDORJ
Parameters for the generation of zones: Generate zones from all stops, served stops (default setting) or survey stops: only from origin and destination stops, in order to produce an interim result without excessive computing time, in order to obtain an initial estimate of the number of zones required.
Accept stop numbers (and names) for generated zones. The stop numbers can only be transferred if there are no zones in the network model. Set zone type and connector type. Set connection time and connector length.
9-108
'LUHFW $VVLJQPHQW RI VXUYH\ GDWD UHFRUGV

'LUHFW DVVLJQPHQW assigns all plausible survey records to the network. For this it is necessary to specify a demand segment to which the survey records shall relate. The process of direct assignment initializes existing assignment results and replaces an existing O-D matrix.
'6HJ EXWWRQ Select one or several demand segments (e.g. PuT or more precisely PuT time cards) to which the survey records shall relate. 3DUDPHWHUV EXWWRQ Parameter settings for direct assignment 3DUDPHWHUV IRU GLUHFW DVVLJQPHQW GLDORJ 3DUDPHWHUV button Parameters for direct assignment: Specify assignment period. Select origin zones (interim analysis selected zones).
When the direct assignment process has been completed, the volumes can be displayed in the form of a bar diagram or as boarding and alighting columns at stops. The traffic flows can be evaluated with the aid of flow bundles.
During direct assignment any previous assignment will be deleted complete with the associated matrix. A warning message to this effect will be displayed. In the survey file *.sur an external projection factor can be indicated for each data record (([W3URM)DF). This allows passenger weighting carried out outside VISUM to be included in the assignment via 1XP3HUV x ([W3URM)DF. For example, data record no.1 in the passenger.sur file will be included with five and data record no. 2 with two passengers in the assignment.
&DOFXODWLQJ LQGLFDWRUV

Indicators of the connection are calculated for each data record and output to file: Time: In-vehicle time, ride time, transfer wait time, walking time. Distance: In-vehicle distance, ride distance, walking distance. Speed: In-vehicle speed, direct distance speed. Number of transfers. Fares and traversed fare zones.
3DUDPHWHUV button and '6HJ button 3DUDPHWHUV IRU LQGLFDWRU RXWSXW GLDORJ 3DUDPHWHUV EXWWRQ
Selection of the various indicators is carried out individually by setting to Active or collectively with the (QDEOH DOO LQGLFDWRUV button.
6WDUWLQJ SDVVHQJHU DGGRQ PRGXOH SURFHGXUHV
0HQX&$/&8/$7( 3$66(1*(56859(< 3DVVHQJHU VXUYH\V GLDORJ &DOFXODWH button: Starting all actions set to $FWLYH .
6DYLQJ YHUVLRQ DQG SDVVHQJHU SDUDPHWHUV

The result of the assignment can be saved as a version file. The passenger survey parameters set for the different RSHUDWLRQV can also be saved. Survey data is not saved.
2SHUDWLRQ Select 6DYH YHUVLRQ WR ILOH. 2SHQ6DYH EXWWRQ Opens or saves *.sup passenger parameters file. Further options: Menu FILE-OPEN: VXUYH\ SDUDPHWHUV. Menu FILE-SAVE: VXUYH\ SDUDPHWHUV
9-111
9-112
LISTINGS AND STATISTICS
/,67,1*6 $1' 67$7,67,&6
Listings are separate windows which contain network object data and the results of network analyses in tabular form.
The /,67,1*6menu contains the following list types:
Network object-specific list display
Evaluations
10-1
List handling
/LVW KDQGOLQJ
/,67,1*6 PHQX Select list type: VISUM opens list menus with standard layout columns and list headers which contain the names of list types and the running nos. of lists. 6XEPHQXV LQ WKH OLVW ZLQGRZ
List header (Index) Submenus Additional bar
The submenus of the current list can be used to design the layout print the list on the printer and export the list to an ASCII file (attribute file *.att) or via clipboard.
)LOH VXEPHQX
2SWLRQV VXEPHQX
10-2
List handling
$ERXW OLVWV Several list types can be opened simultaneously. VISUM provides a standard layout for every list type. Several list windows of a list type can be open simultaneously. It is possible to switch between list windows with <Alt-Tab>. The layout of every list can be designed separately. For every list window of a list type, VISUM displays the running no. in the list header.
10-3
List handling
6HOHFWLQJ FROXPQV

&2/8016in 237,216VXEPHQX $WWULEXWHV All attributes of current network object are listed with their long names. Attributes for add-on modules which are not active are not listed.
,QVHUW EXWWRQ Select desired attribute from attribute list ,QVHUW button inserts attribute into column list. Attribute is inserted directly in front of attribute highlighted in colour in column list.
For some attributes, a VXEDWWULEXWH has to be selected, e.g. "Car" or "Bus" for Volume-TSys, before ,QVHUW can be activated. Subattributes are transport systems (C for "Car", T for "Tram" etc.) or transport types (PrT or PuT) a demand segment (commuters, car-private etc.) or time reference (time interval, day or year).
10-4
List handling
&ROXPQV All attributes selected for list display are listed with their long names. The attributes are displayed in the list according to their position in the column list: Upper-most entry as first column on the left etc. Last entry as last column on the right. In the list display, short names of attributes are used as column identifiers.
'HOHWH EXWWRQ Select desired attribute in column list 'HOHWH button deletes marked attribute from column list.
8S'RZQ EXWWRQV Modify order of attributes in column list. $OLJQPHQW For every selected column, the justification of the listed values can be specified: left, right or centred. Standard justification of displayed attributes: Digits are right-justified (e.g. no., type etc.) Letters are left-justified (e.g. TSysCode, line name etc.)
'HFLPDO SODFHV For every column with attribute values which are real numbers, the 'HFLPDO SODFHV option is active ("none" or numbers: 0..9).
In the list, the FROXPQ ZLGWK must be modified with the mouse cursor. By default, the column width corresponds to the length of the short attribute name in the column header. For numerical attribute values which are longer, $$$$ is displayed in the list on the screen to avoid misinterpretations.
10-5
List handling
'HILQLQJ OLVW OD\RXWV

List header
Additional bar
Column statistics Status line
8
/LVW KHDGHU
/,67+($'(5LQ 237,216VXEPHQX The list header consists of three parts: VISUM program name user-defined headline with max. 20 characters running number of every list type.
$GGLWLRQDO EDU
$'',7,21$/%$5 LQ 237,216 VXEPHQX Toggles visibility of additional bar. The functionality provided by the additional bar sometimes varies depending on the list type, and, therefore, is described along with the list type.
8
6WDWXV OLQH
67$786/,1( in 237,216VXEPHQX Toggles visibility of status line at lower margin of list on screen. The status line displays VISUM messages for work on lists.
10-6
List handling
8
&ROXPQ VWDWLVWLFV
&2/80167$7,67,&6in 237,216VXEPHQX
Toggles display of one or more statistics lines in lower margin. Statistics lines provide column-specific information on all list lines:
Sums and mean values are not displayed for all attributes, e.g. not for zone numbers etc..
If on-screen statistics lines are switched on, they will also be printed on the printer along with the list display.
10-7
List handling
8
)RQW
)217 in ),/(VXEPHQX With this option any font can be selected from all installed fonts on the system. The 6\VWHP font is used by default:
Example: Times New Roman true type font
The selected font is used for list display on the screen and for printing. The current font is not saved together with the layout.
10-8
List handling
6DYLQJ OLVW OD\RXW

/D\RXW DQG VWDQGDUG OD\RXW RI OLVWV Internally, VISUM manages a standard layout for every list type. The standard layout of an open list can be modified and overwritten by the user. In addition to this, users can save or read special list layouts by name. The layout and the standard layout have the following parameters: Number and order of displayed attribute columns including decimal places and justification Additional bar, statistics lines, status lines, list headers. The layout and the standard layout do not include parameters on column widths or fonts.
6$9(67$1'$5'/$<287 in ),/(VXEPHQX VISUM saves the current list type under std*.lla, e.g. stdzone.lla for zones. The user-defined standard layout is used for every new list window of a given list type and must be deleted if the internal VISUM standard layout is to be used again for a particular list type.
6$9(/$<287in ),/(VXEPHQX Save layout file (*.lla). Because layout files for all list types are managed under the same file extension, a unique filename should be specified which describes the current list type. Path settings for layout files must be modified under PATHS in the FILE menu, as is the case for all VISUM file types.
5($'/$<287in the ),/(VXEPHQX Select layout file. If the layout file was saved for a different list type than the current one, the following warning is displayed:
3ULQWLQJ OLVWV

List handling
35,17(56(783in ),/(VXEPHQX Select output device Select characteristics: Select format depending on number of columns and lines, column widths, and selected font and font size.
35,17 in ),/(VXEPHQX VISUM print information:
1XPEHU RI SDJHV: Depends on font, data size, and paper format 1XPEHU RI OLQHV: Number of listed objects or displayed list lines 1XPEHU RI REMHFWV QRW RXWSXW WR SULQWHU these are passive objects if 2QO\ DFWLYH is active for list, and )LOWHU 5HIHUHQFH DUHD etc. are also being used.
Set option &DOFXODWH FROXPQ ZLGWK SULRU WR SULQWLQJ. 3ULQW button: Confirm print information and start output.
10-10
List handling
5HDGLQJ DQG VDYLQJ DWWULEXWH ILOHV

Attribute files (*.att) are ASCII files which contain the data sets displayed in list windows. They can be used for data exchange between VISUM and other programs. The network attributes saved in the attribute files can be read again. 6DYLQJ DWWULEXWH ILOHV
LISTINGS menu: open list window Set options, design layout SAVE ATTRIBUTES in FILE submenu: Save listed data in attribute file. 6DYLQJ DWWULEXWHV GLDORJ
$WWULEXWH GDWD ILOH LV OHJLEOH Attribute data files of the following network objects can be read by VISUM, if a VHPLFRORQ or WDEXODWRU is used as separator: Zones Global zones Connectors Turning relations Links Nodes - Basic 6HSDUDWRU 6HPLFRORQ, 6SDFH 7DE.
10-11
List handling
/LVW VWDWLVWLFV 2EMHFWV WRWDO: number of objects in network 2EMHFWV OLVWHG: number of active network objects , 2EMHFWV QRW OLVWHG: number of passive network objects. ,GHQWLILHUV Identifiers serve to identify listed network objects. VISUM inserts columns into the attribute file if they are not in the list window. Identifiers cannot be overwritten by reading *.att file. 6HOHFWLRQ ,GHQWLILHUV IRU Links /LQNVSHFLILF 1RGHVSHFLILF
/LQN1U)URP1RGH2QHZD\
Turning relations
)URP/LQN7R/LQN9LD1RGH
)URP1RGH7R1RGH2QHZD\
)URP1RGH7R1RGH9LD1RGH
For all other network objects, permanent identifiers have been defined in VISUM, e.g. 6XE/LQ,' = /LQ1DPH + /LQ9DULDQW + 'LUHFWLRQ
G
([DPSOH
Attribute files are saved by default in the directory specified by file management ($WWULEXWH ILOHV under DIRECTORIES... in FILE menu). ]RQHVDWW DWWULEXWH ILOH
$VISION $VERSION:VersNr;FileType;Language 1.0;Att;E * $+ZONE:Nr TYPE OTRAFFIC(X) OTRAFFIC(P) OTRAFFIC(L) OTRAFFIC(Z) NumSLines NUMLINES NUMSERVICE(D) NUMSERVICE(TI) 100 2 1500 3000 750 220 2 1 19 19
10-12
List handling
5HDGLQJ DWWULEXWH ILOHV
Select OPEN in FILE menu and $WWULEXWH file type The *.att file extension is used for all attribute files independent of the list type with which they were created. For this reason, the filename should in some way indicate the list type. The relevant network object type is identified by the identifier which is saved in block $+ before the respective short attribute names, when the attribute file is read. 5HDGLQJ /LQN $WWULEXWHV GLDORJ
If the read attribute file has more than 10 columns, higher column numbers can be displayed by scrolling.
10-13
List handling
&ROXPQ Q VISUM numbers columns which have been read. The order corresponds to the arrangement in the 6DYH DWWULEXWH list and in the attribute file. If the list does not contain identifiers for identifying individual network objects during saving, VISUM inserts columns for the corresponding identifiers into the attribute file while the file is being saved. By default, the columns are inserted on the left. Exception: link identifiers The attribute 2QHZD\5RDG is added to LinkNo)URP1RGH1U and )URP1RGH1U7R1RGH1U in the last column for every link and direction.
2ULJLQ DWWULEXWH The column identifiers from the previously read attribute file are displayed as origin attributes. For 6DYH DWWULEXWHV, VISUM uses the so-called attribute-ID which is the short name of the attribute (max. 8 characters, no spaces, no umlauts). 7DUJHW DWWULEXWH The target attribute specifies for which attribute the read values of the respective origin attribute are to be used: Empty bar: attribute values are not read. Target attribute = origin attribute: copies origin attribute values, Target attribute differs from origin attributes: origin att. values copied to selected target attribute. If the same target attribute, e.g. "Type", is selected for several origin attributes, VISUM only accepts the attribute values of the last origin attribute read, as "type data" (highest ColumnNr with "Type" target attribute), whose value range corresponds to the value range of the target attribute. When attribute files are read, the attribute values of the previous network state are overwritten. To avoid data loss, save previous network state beforehand. The following attributes cannot be overwritten by reading: identifiers of network objects (/LQN1U, )URP1RGH1U etc.) and calculated results (9RO9HK3U7, 1RLVH etc.).
10-14
List handling
Expanded When reading link attributes with FromNodeNr and ToNodeNr as link identifiers instead of LinkNr and the links are not to be found in network, shortest route search for relevant links can be performed between the given )URP1RGH and 7R1RGH QXPEHUV. 5HDG OLQN DWWULEXWHV 6HDUFK SDUDPHWHUV GLDORJ
Options: ,JQRUH OLQN: Attribute values, which cannot be assigned to links with the relevant )URP1RGH-7R1RGH numbers in the network, are ignored. 6HDUFK IRU VKRUWHVW URXWH: Shortest route search between )URP1RGH7R1RGH is performed by the following search parameters. 6HDUFK FULWHULRQ For route search either GLVWDQFH or AddValue ($GG9DO, $GG9DO or $GG9DO) can be selected as search criterion. $WWULEXWH YDOXHV Options for assignment of attribute values to links found in network: XVH IRU DOO OLQNV: the attribute value is assigned to all all links between )URP1RGH and 7R1RGH. XVH IRU ILUVW OLQN RQO\: the attribute value is only assigned to the first link of the link sequence found in network. 7UDQVSRUW V\VWHP Select the transport system for route search.
10-15
List handling
$WWULEXWHV LQ &OLSERDUG

For direct data exchange between VISUM and other software tools attribute data can be exported via clipboard without saving data to file.
),/( VXEPHQX LQ DQ RSHQ OLVW LQ WKH/,67,1*6PHQX ATTRIBUTES IN CLIPBOARD command 5HDGLQJ DWWULEXWHV IURP FOLSERDUG For attribute data import from e.g. ([FHO into VISUM the command ATTRIBUTES FROM CLIPBOARD is provided in the EDIT menu. For data import into other software programs see Ch. 15.3.5.
10-16
List types
/LVW W\SHV
&RPPDQGV LQ /,67,1*6 PHQX
List output by network object type
PuT relations List of calculated routes (assignment result). List of routes determined via ROUTE SEARCH in GRAPHICS menu.
Statistics on network objects, link types, PuT assignment and vehicle blocks. Plausibility state of survey data records (Passenger survey Add-on)
10-17
List types
=RQHV
8
=RQHV
=21(6in the /,67,1*6PHQX
$FWLYH ]RQHV RQO\
Passive zones are not listed.

Passive and active zones are listed. =RQH EXWWRQ ?
Search according to number or name in list. Line for searched zone is displayed.
To activate both buttons, activate SINGLE SELECT mode and ZONES network object. 'LVSOD\ ]RQH VHOHFWHG LQ QHWZRUN LQ OLVW ZLQGRZ Select zone in network. Activate button. The searched zone is displayed in the list window.
'LVSOD\ ]RQH VHOHFWHG LQ OLVW LQ QHWZRUN Select zone in list: search for zone within list ? or position mouse cursor in any attribute column of zone. Activate button. VISUM highlights the zone in the network display. Warning: The current network section is not modified. If no zone is highlighted in current network display, HQODUJH VHFWLRQ RU GLVSOD\ IXOO SDJH QHWZRUN VHFWLRQ.
10-18
List types
*OREDO ]RQHV
8
*OREDO ]RQHV
*/2%$/=21(6in /,67,1*6PHQX
$FWLYH JOREDO ]RQHV
Passive global zones are not listed.

Passive and active global zones are listed. *OREDO ]RQH EXWWRQ ? Search for name or number in list. Line for searched global zone is displayed.
To activate the following two buttons, activate SINGLE SELECT mode and GLOBAL ZONES network object. 'LVSOD\ JOREDO ]RQH VHOHFWHG LQ QHWZRUN LQ OLVW ZLQGRZ Select global zone in network. Activate button. Searched for global zone is displayed in list window. 'LVSOD\ JOREDO ]RQH VHOHFWHG LQ OLVW LQ QHWZRUN Select global zone in list: search for global zone within list or position mouse cursor in any attribute column of global zone. Activate button. VISUM highlights the global zone in the network display. Warning: The current network section is not modified. If no global zone is highlighted in current network display, HQODUJH VHFWLRQ RU GLVSOD\ IXOO SDJH QHWZRUN VHFWLRQ.
10-19
List types
1RGHV
8
1RGHV
12'(6in /,67,1*6PHQX
By default, VISUM opens the %DVLF GLVSOD\ node list. Further node lists can be selected. All node attributes can be listed. Node lists which only display PuT attributes only refer to nodes. OLVWHG DWWULEXWHV PrT + PuT PuT PuT PuT PuT IRU all nodes 1 node 1 node 1 node 1 node/all
6HOHFWLRQ RI D QRGH OLVW Basic display Display by subline Timetable at stop Timetable - Arrivals/Departures Transfers
10-20
List types
1RGHV %DVLF GLVSOD\
8
1RGHV %DVLF GLVSOD\
%DVLF GLVSOD\ XQGHU 12'(6LQ WKH /,67,1*6PHQX
List all node attributes for all nodes. $FWLYH QRGHV RQO\
Passive nodes are not listed.

Passive and active nodes are listed. 6WRSV RQO\
Nodes which are not stops are not listed.

All nodes are listed. This option does not influence standard layout (displayed columns) of 1RGHV %DVLF GLVSOD\ list. 1RGH EXWWRQ ? Search for identifier or number in list. Line for searched for node is displayed.
To activate the two following buttons, activate SINGLE SELECT mode and NODES network object. 'LVSOD\ QRGH VHOHFWHG LQ QHWZRUN LQ OLVW ZLQGRZ Select node in network. Activate button. The searched for node is displayed in list window. 'LVSOD\ QRGH VHOHFWHG LQ OLVW LQ QHWZRUN Select node in %DVLF GLVSOD\ list or select node-specific list display Activate button. VISUM highlights node in network display. Warning: current network section is not modified. If no node is highlighted in current network display, HQODUJH VHFWLRQ RU GLVSOD\ IXOO SDJH QHWZRUN VHFWLRQ.
1RGHV 'LVSOD\ RI VXEOLQHV

List types
8
1RGHV 'LVSOD\ RI VXEOLQHV
6XEOLQH GLVSOD\ under12'(6in /,67,1*6PHQX
Node-specific list: All sublines which serve the selected stop. The following attributes can be listed: Subline (name, variant, direction) TSysCode OrigTermNr., Name, Code DestTermNr., Name , Code StopNr. PassBoard PassAlight
$FWLYH QRGHV RQO\

List can be displayed for passive and active nodes. 2QO\ VWRSV
This option should be active, because lines only serve stops.

1RGH EXWWRQ
Search for node (by name, nr, or code). List for searched for node is displayed.
10-22
List types
1RGHV 7LPHWDEOH DW VWRSV
8
7LPHWDEOH DW VWRS
7LPHWDEOH DW VWRSV under 12'(6 in /,67,1*6PHQX
Node-specific list: Departure times of subline at selected stop. $FWLYH QRGHV RQO\
Passive nodes are not displayed.

Display list for active and passive nodes. 2QO\ VWRSV
Because this node list refers to current settings (nodes DQG subline), the search functions are limited to all sublines which serve the currently selected node or all nodes which are served by the current subline. 1RGH EXWWRQ ? Selection from all stops which are served by the subline. Search for node code or number. The list is displayed for the selected node and the subline. 6XEOLQH EXWWRQ (e.g. S2 1R) Selection from all sublines which serve ? node. Search for name. The list is displayed for the selected subline and the node. The +DOW option only becomes active if the selected subline serves the selected node in the line route several times. Open selection box with mouse click. Select desired halt for list display.
List types
1RGHV 7LPHWDEOH$UULYDO'HSDUWXUH
8
1RGHV 7LPHWDEOH $UU'HS
7LPHWDEOH $UULYDO'HSDUWXUH XQGHU 12'(6,1 /,67,1*6PHQX
Node-specific list: chronological list of arrival and departure times of all sublines at/from selected stop. The following attributes can be listed: SLine ID (name, variant, direction) Transport system OTermNr., Name, Code DTermNr., Name, Code Arrival Departure $FWLYH QRGHV RQO\

List can be displayed for active and passive nodes. 2QO\ VWRSV

1RGH EXWWRQ
Search for node code or number. The list is displayed for searched for node.
10-24
List types
1RGHV /LVW RI WUDQVIHUV
8
1RGHV /LVW RI WUDQVIHUV
/LVW RI WUDQVIHUVXQGHU12'(6LQ/,67,1*6 PHQX
Node-specific list: Transfers at selected stop or at all stops. The following attributes can be listed: Stop FromSLinID ToSLinID TransDir StopNr, Name or Code Subline which passengers alight from. Subline which passengers board. Number of passengers who transfer directly at selected stop without using walk link.
TrnsfAlightWalk Number of passengers who alight "FromLine" at selected stop and board "ToLine" (via walk link) th which leaves from different stop. TrnsfWalkBoard Number of passengers who alight "FromLine" at different stop and reach selected stop via walk link where they then board "ToLine".
$FWLYH QRGHV RQO\

List can be displayed for active and passive nodes. 2QO\ VWRSV

1RGH EXWWRQ
Search for node name, code or number. List is displayed for searched for node.
10-25
List types
/LQNV
8
/LQNV
/,1.6in /,67,1*6PHQX
$FWLYH OLQNV RQO\
Passive links are not listed.

Passive and active links are listed. /LQN EXWWRQ
"
Search for link number in list. The line for the searched for link is displayed in list window.
&URVVVHFWLRQ
cross-section values (= attribute values of both directions summed

up) are displayed for every link. attribute values are displayed for each direction of a link separately. The FromNodeNr. and ToNodeNr. in the cross-sectional link list are listed this way: FromNodeNr < ToNodeNr. Cross-sectional display of link attribute values which can be different for the two directions of a link: 7\SH = higher ranking link type (even if it is only valid for opposite direction which is identified by FromNodeNr > ToNodeNr). $OO WLPHV, VSHHGV = (ValueForth+ValueBack) : 2 6DWXUDWLRQ = VolumeCross : CapCross $GG9DOXHV FDSDFLWLHV YROXPHV ValueForth + ValueBack 76\V&RGH all transport systems (logical OR) which are permitted for at least one direction.
The length values of both directions of a link are identical.
10-26
List types
If cross-section values for links were saved in an attribute file, VISUM reads the following cross-section values for every direction: 7\SH WLPHV VSHHGV = ValueCross &DSDFLWLHV YROXPHV = ValueCross 6DWXUDWLRQ $GG9DOXHV = ValueCross 76\V&RGH = TSysCross.
This procedure applies equally to connectors (origin/destination) can be used to balance a network.
VISUM issues a warning when it reads cross-sectional attribute values to avoid unintentionally overwriting direction-specific data. To activate the following two buttons, activate SINGLE SELECT mode and LINKS network object. 'LVSOD\ OLQN VHOHFWHG LQ QHWZRUN LQ OLVW ZLQGRZ Select link in network. Activate button. The searched link is displayed in list window. 'LVSOD\ OLQN VHOHFWHG LQ OLVW LQ QHWZRUN Select link in list: search for link within list or position mouse cursor in any attribute column of the link. Activate button. VISUM highlights link in network display. Warning: current network section is not modified. If no link is highlighted in current network display, eQODUJH VHFWLRQ RU GLVSOD\ IXOO SDJH QHWZRUN VHFWLRQ
10-27
List types
7XUQLQJ UHODWLRQV
8
7XUQLQJ UHODWLRQV
7851,1*5(/$7,216LQ /,67,1*6PHQX
2QO\ DFWLYH WXUQLQJ UHODWLRQV
Passive turning relations are not listed.

All turning relations are listed.
A turning relation is passive if it is not permissible for any transport system or it was set passive by filters, areas, etc..
10-28
List types
&RQQHFWRUV
8
&RQQHFWRUV
&211(&7256 in /,67,1*6PHQX
$FWLYH FRQQHFWRUV RQO\
Passive connectors are not listed.

Active and passive connectors are listed.
A connector is passive if it was set passive by filter, areas, etc. does not exist if is not permissible for any transprot type and direction (even if is was defined previously). =RQH EXWWRQ
Search for name or number in list. The connectors of the selected area are displayed in list.
&URVVVHFWLRQ
attribute values of both directions are displayed as a cross-section

for every connector: Zone Node attribute values are listed separately for every direction of a connector: Origin connector: Zone Node Destination connector: Node Zone
10-29
List types
Cross-sectional display of connector attribute values which can differ by direction (access and egress to/from zone):
'LUHFWLRQ = O or D or OD 7\SH = higher type /HQJWK = larger value $OO WLPHV, ,PS3U7 = (ValueForth + ValueBack) $GG9DOXHV YROXPHV = ValueForth + ValueBack 3HUPLWWHG IRU 3U7 RU 3X7 = 1 (connected by OR) if connector between zone and node is permissible for the transport type for at least one direction.
If cross-section values for connectors were saved in attribute file, VISUM reads the following cross-section values for every connector between zone and node: DOO WLPHV $GG9DOXHV W\SH OHQJWK SHUPLWWHG ValueCross This procedure can also be used for links is used to balance a network.
10-30
List types
To activate the following two buttons, activate SINGLE SELECT mode and CONNECTORS network object 'LVSOD\ FRQQHFWRU VHOHFWHG LQ QHWZRUN LQ OLVW ZLQGRZ Select connector in network. Activate button. The searched connector is displayed in list window. 'LVSOD\ FRQQHFWRU VHOHFWHG LQ OLVW LQ QHWZRUN Select connector in list: search for connectors of zone in list and position mouse cursor in any attribute column of connector. Activate button. VISUM highlights connector in network display. Warning: current network section is not modified. If no connector is highlighted in current network display, eQODUJH VHFWLRQ RU GLVSOD\ IXOO SDJH QHWZRUN VHFWLRQ.
10-31
List types
6XEOLQHV
8
6XEOLQHV
68%/,1(6in /,67,1*6PHQX
By default, %DVLF GLVSOD\ list is opened. All attributes of sublines can be listed. Further subline lists can be selected. Except for %DVLF GLVSOD\ list, all subline lists only refer to one subline. /LVWHG DWWULEXWHV all subline attributes for all sublines all attributes of line route of subline departure times from stop of subline departure times from every stop of subline transfers at transfer stop of subline
6XEOLQH OLVWV Basic display: Line route: Timetable at stop: Timetable booklet: Transfer list:
Further subline data can be listed in form of node lists.
10-32
List types
6XEOLQHV %DVLF GLVSOD\
8
%DVLF GLVSOD\
%DVLF GLVSOD\ under 68%/,1(6in /,67,1*6PHQX
List of all attributes of all sublines. $FWLYH VXEOLQHV RQO\
Passive sublines are not listed.

Active and passive sublines are listed. 6XEOLQH EXWWRQ (e.g. Bus11H) ? Selection from all sublines. Search for name. The searched for subline is displayed in list window.
To activate the two following buttons, activate SINGLE SELECT mode and SUBLINES network object 'LVSOD\ VXEOLQH VHOHFWHG LQ QHWZRUN LQ OLVW ZLQGRZ Select subline in network. Activate button. The searched for subline is displayed in list window. 'LVSOD\ VXEOLQH VHOHFWHG LQ OLVW LQ QHWZRUN Select subline in list: search for subline in list ? and position mouse cursor in any attribute column of subline. Activate button. VISUM highlights subline in network display. Warning: current network section is not modified. If subline is not highlighted in current network display, HQODUJH VHFWLRQ or display IXOO SDJH QHWZRUN VHFWLRQ.
10-33
List types
6XEOLQHV /LQH URXWH
8
/LQH URXWH
/LQH URXWH under 68%/,1(6in /,67,1*6PHQX
Attributes of line route of selected subline or of all sublines $FWLYH VXEOLQHV RQO\

Active and passive sublines are listed. ? 6XEOLQH EXWWRQ (e.g. BUS1 1 F) Selection of a subline from all sublines. Search for name. List is displayed for searched for subline.
10-34
List types
6XEOLQHV 7LPHWDEOH DW VWRS
8
7LPHWDEOH DW VWRS
7LPHWDEOH KXQJ RXW DW VWRS under 68%/,1(6in /,67,1*6PHQX
Departures of selected subline from selected stop. $FWLYH VXEOLQHV RQO\

Active and passive sublines are listed. 6XEOLQH EXWWRQ (e.g. BW 1) Selection from all sublines. Search for name. List is displayed for searched for subline. ?
6WRS EXWWRQ
Select stop which is served by subline. Search for node code or number. Subline list is displayed for searched for node.
The +DOW option only becomes active if the selected subline serves the selected node in line route several times. For this purpose, there may be separate timetables at stops available for every partial route of line route. Open selection box with mouse click. Select desired halt for list display.
10-35
List types
6XEOLQHV 7LPHWDEOH ERRNOHW
8
7LPHWDEOH ERRNOHW
7LPHWDEOH ERRNOHW under 68%/,1(6in /,67,1*6PHQX
Lists all departures of subline from all served stops. $FWLYH VXEOLQHV RQO\
Passive sublines cannot be listed.

Active and passive sublines can be listed. 6XEOLQH EXWWRQ (e.g. BW 1) Selection from all sublines. Search for name. List is displayed for searched for subline. ?
10-36
List types
6XEOLQHV /LVW RI WUDQVIHUV
8
/LVW RI WUDQVIHUV
/LVW RI WUDQVIHUV under 68%/,1(6in /,67,1*6PHQX
List of transfers on line route of selected subline. Only transfer stops of sublines are listed i.e. stops at which passengers transfer. The listed number of transfers contains transfers without walking links (directly at listed stop) and with walking links (between the selected stop and different stop)
The following attributes can be listed: StopNr StopCode StopName TransfSLinID No. of transfer stop. Short name of transfer stop. Name of transfer stop. Line ID of transfer line for transfers between selected subline and transfer line.
TSys-TransfSLin Transport system of transfer line. PassBoard PassAlight Passengers who board selected subline coming from TransfLin. Passengers alighting selected subline who are going to TransfLin.
$FWLYH VXEOLQHV RQO\ Passive sublines cannot be listed. Active and passive sublines can be listed. 6XEOLQH EXWWRQ (e.g. BW 1) Selection from all sublines. ?
Search for name. List is displayed for searched for subline.
10-37
List types
/LQHV
8
/LQHV
/,1(6in /,67,1*6 PHQX Display of aggregated values for subline attributes of a line and attributes of line revenue calculation for sublines of a line
This means that in addition to the input attributes, results of assignment, roster generation, revenue calculation, and projection values for every line are aggregated and listed as well.
$FWLYH OLQHV RQO\
Passive lines are not listed.

Active and passive lines are listed. The listed line attributes can be divided into the following categories: *HQHUDO LQGLFDWRUV Number of sublines Number of stops Mean speed Mean vehicle trip length Mean running time First departure Last arrival etc. The calculation is carried out automatically after every modification to line data does not require demand data. 7UDQVSRUW VXSSO\ LQGLFDWRUV Performance indicators (per day, per year, per time interval): VehTrips Vehicle kilometers Service time Operation time Seat kilometers
10-38
List types
The calculation of performance indicators is carried out automatically after every modification to line data does not require demand data. 9HKLFOH UHTXLUHPHQW LQGLFDWRUV Indicator (per day): Number of required vehicles. The calculation: requires vehicle roster generation with 5RVWHUV under LINE REVENUE CALCULATION in CALCULATE menu &RVW LQGLFDWRUV Indicators (per day, per year): operational cost vehicle cost hourly cost kilometer cost link cost operator cost The calculation is carried out automatically for hourly and kilometer costs after every modification to line data or cost rates. Vehicle costs require roster generation. No demand data are required. 7UDYHO GHPDQG LQGLFDWRUV Indicators (per day, per year): Line trips (Passengers transported by line) Passenger kilometers. Calculation: indicators are calculated automatically during assignment. this requires demand data. 5HYHQXH FDOFXODWLRQ LQGLFDWRUV Indicators (per day, per year): Total revenue Revenue per line trip Cost Coverage. Cost Coverage per line trip. The calculation requires revenue calculation using the 3X7UHYHQXHV operation under PROCEDURES... in CALCULATE menu.
10-39
List types
0DLQ OLQHV
8
0DLQ /LQHV
0$,1/,1(6 in /,67,1*6PHQX Attributes of main lines correspond with line attributes:
3X7 WUDQVSRUW V\VWHPV
8
3X7 7UDQVSRUW V\VWHPV 76\V 7UDQVIHUV
387 75$1632576<67(06 in /,67,1*6PHQX 76\V7UDQVIHUV Display of calculation results Passenger transfers FromTSys - ToTSys
3X7 7UDQVSRUW V\VWHPV %DVLF GLVSOD\
%DVLF GLVSOD\ Aggregated values for subline attributes of transport system and attributes of line revenue calculation for lines of TSys This means that in addition to the input attributes, the results of assignment, roster generation, revenue calculation, and projection values for every PuT transport system are aggregated and listed as well.
10-40
List types
$FWLYH VXEOLQHV RQO\
Passive sublines are not considered for list.

Active and passive sublines are considered. The transport system attribute categories correspond to line attribute categories. Demand and performance-specific indicators of PuT transport system are aggregated per day. The listed PuT transport system attributes can be divided into the following categories:
*HQHUDO LQGLFDWRUV Indicators: Network length per direction (the lengths of both directions of link which are permissible for transport system are added) Cross-sectional network length (the lengths of every link permissible for transport system are considered only once even if both directions are permitted) Line network length (traversed length = lengths of line routes) with regard to direction Line network length (lengths of line routes) with regard to crosssection Mean vehicle trip length Mean vehicle trip time Number of served stops Number of sublines Number of lines The calculation is carried out automatically after modifications to network or line data. No demand data necessary. 7UDQVSRUW VXSSO\ LQGLFDWRUV Performance indicators (per day): Number of vehicle trips Vehicle kilometers Service time Operation time Seat kilometers. The calculation is carried out automatically after every modification to line data No demand data necessary.
10-41
List types
9HKLFOH UHTXLUHPHQW LQGLFDWRUV Indicator (per day): Number of required vehicles. The calculation requires line blocking calculation using the /LQH%ORFNLQJ operation under PROCEDURES... in CALCULATE menu. &RVW LQGLFDWRUV Indicators (per day): Operational cost Vehicle cost Hourly cost Kilometer cost Link cost Operator cost The calculation is carried out automatically for hourly and kilometer costs after every modification to line data or cost rates. Vehicle costs require roster generation. No demand data required. 7UDYHO GHPDQG LQGLFDWRUV Indicators (per day) : Number of line trips Passenger kilometers. Calculation: Indicators are calculated automatically during assignment. This requires demand data. 5HYHQXH FDOFXODWLRQ LQGLFDWRUV Indicators (per day): Total revenue CostCoverage The calculation requires revenue calculation using the 3X7UHYHQXHV operation under PROCEDURES... in CALCULATE menu.
10-42
List types
3X7 RSHUDWRUV
8
3X7 2SHUDWRUV
387 23(5$7256 in /,67,1*6PHQX Display of attributes for every PuT operator in network:
*HQHUDO LQGLFDWRUV Indicators: Number of sublines The calculation is carried out automatically after modification to line data no demand data required. 7UDQVSRUW VXSSO\ LQGLFDWRUV Performance indicators (per day): No. of vehicle trips Vehicle kilometers Service time Seat kilometers. The calculation is carried out automatically after every modification to line data no demand data necessary. &RVW LQGLFDWRUV Indicators (per day): Operator cost. The calculation is carried out automatically after every modification to cost rates. No demand date required.
10-43
List types
/LQN W\SHV
8
/LQN W\SHV
/,1.7<3(6 in /,67,1*6PHQX
All link type attributes can be listed. For the following attributes, a transport system for the respective transport type must be selected as subattribute: vMax-PrT and v-PuT
$UHDV
8
$UHDV
$5($6 in /,67,1*6PHQX
%XWWRQ &DOFXODWH Display of area attributes After changing an option &DOFXODWH has to be activated once again: only active/all areas, only active/all links, only active/all lines.
10-44
List types
'LVSOD\ RI VXEOLQHV Public transport indicators calculated for each area according to the area polygon are listed in detail. $UHDV 'LVSOD\ RI VXEOLQHV
Atributes listed by subline and area: 9HK.P3X7 6HDW.P3X7 6HUYLFH7LPH3X7 ,QDFWLRQ7LPH3X7 3DVVHQJHU.P3X7 3DVVHQJHU+RXUV3X7 3DVV%RDUGLQJ 3DVV$OLJKWLQJ &RVW3X7 &RVWK &RVW.P &RVW9HK 5HYHQXH WRWDO &RVW&RYHUDJHU WRWDO Calculation can be performed for all or RQO\ DFWLYH DUHDV RQO\ DFWLYH VXEOLQHV
10-45
List types
/LQN VHTXHQFHQFHV
/,1.6(48(1&(6 in /,67,1*6PHQX Road toll is listed for each section of predefined link sequences:
/LQN VHTXHQFHV
&HQVXV SRLQWV
8
&HQVXV 3RLQWV
&(168632,176 in /,67,1*6PHQX Display of attributes of census points
10-46
List types
3X7 5HODWLRQV
387 5(/$7,216in /,67,1*6PHQX The PuT relations list corresponds to a timetable information system. It helps to understand the assignment procedure.
3X7 5HODWLRQV
The list provides timetable information including assignment for an origin zone with demand=10000 or from matrix/passenger distr. pattern, with selected PuT assignment procedure/parameters for the selected PuT demand segment as well as list display of results for every origin-destination UHODWLRQ (aggregated indicators) or for every route or FRQQHFWLRQ to one/all destination zone(s) or for every partial route or SDUWLDO FRQQHFWLRQ to one dest. zone. Relations: Indicators aggregated via found routes or connections for every origin/destination relation Display: from one origin zone to one/all destination zone(s). Connections: Attributes for every found route or connection for every o-d relation Display: from one origin zone to one/all destination zone(s). Partial connections: Attributes of found partial routes for every route or connection of one o-d relation Display: from one origin zone to one destination zone.
6HOHFWLRQ OLVW 'LVSOD\ YDOXHV IRU
Compare chapter 7: PuT assignment procedures and their parameters PuT indicator matrices: aggregated indicators for every relation.
10-47
List types
6HOHFWLRQ OLVW $VVLJQPHQW SURFHGXUH /LQHEDVHG 7LPHWDEOH 7LPHWDEOH 7LPHWDEOH 76\VEDVHG
6HOHFW a 'HPDQG segment PuT and 0DWUL[ or . For thinly populated matrices, it is better to use a constant to avoid repeated rounding to 0. Parameters The assignment parameters described in Chapter 7 apply to every procedure including WLPH LQWHUYDO DQG PD[ QXPEHU RI GHSDUWXUHV, and can be modified for every list of type 3X7 UHODWLRQV 2SWLRQ )URP ? WR ? $OO From: select origin zone for calculation and display To: button depends on procedure. Select destination zone (for all procedures) or Activate DOO (not for SDUWLDO FRQQHFWLRQV display).
The number of the currently selected origin zone is displayed next to )URP %XWWRQ. Next to 7R %XWWRQ, corresponding Nr. or $OO is displayed. Start ... Start search (calculation and list display) for current settings. Every modification to current parameter settings in open list of type "3X7 UHODWLRQV", deletes currently listed values. To compare the effects of different assignment procedures, several lists can be opened.
G
10-48
List types
'LVSOD\
3X7 UHODWLRQ DWWULEXWHV
3URFHGXUH TT1 TT2 Line TSys
For every relation
OZoneNr DZoneNr OZoneName DZoneName O-D trips total O-D trips PuT O-D trips without c NT SF AT OWT IVT WT TWT ET RT JT PJT AD IVD WD ED DD IVD RD RV LV
Orig.ZoneNr Destin.ZoneNr Orig.ZoneName Destin.ZoneName O-D trips total O-D trips with PuT O-D trips without conn. Number of transfers Service frequency Access time Wait time at dep. stop In-vehicle-time Walking time Transfer wait time Egress time Ride time Journey time Perceived journey time Access distance In-vehicle-distance Walking distance Egress distance Direct distance In-vehicle-distance Ride distance Ride speed Direct distance speed
X X X X X X X X X X X X X X X X X X X X X X X X X X
X X X X X X X X X X X X X X X X X X X X X X X X X X X
X X X X X X X X X X X X X X X X X X X X X X X X X X X
X X X X X X X X X X X X X X X X X X X X X X X X
O-D trips without PuT O-D trips without PuT
O-D trips = Passenger trips. Compare chapter 10.2.13 (PuT routes).
10-49
List types
'LVSOD\ For every
&RQQHFWLRQ DWWULEXWHV OZoneNr OZoneName DZoneName ConnNr O-D trips NT SF AT OWT IVT WT TWT ET RT JT PJT AD IVD WD ED DD RD JD JV DDV Fare SStoptNr SStoptName SStopCode DStopNr DStopName DStopCode Dep. Arr. OriginZoneNr DestinationZoneNr OriginZoneName destinationZoneName Connection number Passenger line trips Number of transfers Service frequency Access time Wait time at dep. stop In-vehicle-time Walking time Transfer wait time Egress time Ride time Journey time Perceived journey time Access distance In-vehicle distance Walking distance Egress distance Direct distance Ride distance Journey distance Journey speed Direct distance speed Fare StartStopNr. StartStopName StartStopCode Destin.StopNr. Destin.StopName Destin.StopCode Departure time Arrival time X X X
3URFHGXUH TT1 TT2 Line TSys X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X =1 X X X X X X X X X X X X X X X X X X X X X X X X X
connection DZoneNr
X X X X X X X X =1 =1 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
10-50
List types
'LVSOD\ For every
$WWULEXWHV RI SDUWLDO FRQQHFWLRQV OZoneNr Orig.ZoneNr Destin.ZoneNr Destin.ZoneName Connection number Passenger trips Number of transfers Service frequency Access time Origin wait time at dep. stop In-vehicle-time Walking time Transfer wait time Egress time Ride time Journey time Perceived journey time Access distance In-vehicle-distance Walking distance Egress distance Direct distance Journey distance Ride distance Journey speed Direct distance speed Partial connection number (0=total) StartStopNr. StartStopName StartStopCode Destin.StopNr. Destin.StopName Destin.StopCode Name of subline or TSys i.e. access or egress X X X
3URFHGXUH TT1 TT2 Line TSys X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X =1 X X X X X X X X X X X X X X X X X X X X X X X X X
connection DZoneNr DZoneName ConnNr O-D trips NT SF AT OWT IVT WT TWT ET RT JT PJT AD IVD WD ED DD JD RD JV DDV For every PConnNr partial SStopNr connection SStopName SStopCode DStopNr DStopName DStopCode SLinID
OZoneName Orig.ZoneName
X X X X X X X X =1 =1 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
10-51
List types
'LVSOD\
$WWULEXWHV RI SDUWLDO FRQQHFWLRQV Dep Arr Time WaitT Distance PDD v PDV Departure time Arrival time Time Wait time Distance Partial direct distance speed Partial direct distance speed X X X X X X X X
3URFHGXUH TT1 TT2 Line TSys X X X X X X X X X X X X X X X X X X X X X X X X
10-52
List types
5RXWHV
8
5RXWHV
5287(6in /,67,1*6PHQX The route list contains the routes determined during assignment. Listed columns depend on the current transport type (PuT or PrT). ? )URP 7R ? RSWLRQ By default, "From all" - "To all" zones is predefined. )URP: select origin zone for display 7R: seIect destination zone for display 6HOHFW '6HJ Select demand segment of PuT or PrT. 6HOHFW IURP VHOHFWLRQ OLVW $OO URXWHV: from assignment (routes or connections) )ORZ EXQGOH URXWHV: routes of current flow bundle display 5HODWLRQ ILOWHU: routes of current relation filter.
5RXWHV 3U7
$WWULEXWH FromZone ToZone Index Imp Vol Length t0 tCur v0 vCur
'HVFULSWLRQ Number of FromZone Number of ToZone Index number of route for every O-D relation Route impedance Route volume Route length Time per route in unloaded network Time per route in loaded network Speed in unloaded network Speed in loaded network
AddVal1,2,3 Sum of AddValues of traversed network objects

List types
5RXWHV 3X7
$WWULEXWH for every relation for every route FromZone ToZone Route Vol JTX
'HVFULSWLRQ Number of FromZone Number of ToZone IndexNr. of route for every O-D relation Route volume Journey time X of route including access and egress time, that is, sum of all partial route times. Waiting times are not included. Ride time X: sum of partial routes without connectors, that is, for every walking link or subline (or TSys for TSys-based assignment) between origin and destination connector node. Waiting times are not included. IndexNr. of partial route: 1 = access etc. Partial routes are listed per column (Index1..n). Time for every partial route: Access or egress time In-vehicle-time_1 or walk_1, ..... etc. Depends on procedure: TSys or subline/WalkLink. Node number of stop = End of partial route. StopNr. for index = 1, is boarding/connecting stop. End of last partial route = destination zone. Node code Long name of node
RTX
every part. Index route Time
SLinID StopNr
StopCode StopName
10-54
List types
5RXWH VHDUFK
8
5RXWH 6HDUFK
6($5&+5287( in /,67,1*6PHQX
, Prerequisite: route search under ROUTE SEARCH in GRAPHICS menu For route search, select origin and destination zone/node. Destination node can be origin node for further route search. /LVW GLVSOD\ RI IRXQG URXWH IRU HYHU\ PRGH PrT mode: PuT mode: one line per route. one line per partial route.
If zone was selected as origin or destination of PuT route, VISUM adds corresponding data line to list display: first partial route: origin connector from selected zone to found connecting node or last partial route: destination connector from found connecting node to selected zone. $WWULEXWH Mode FromObjCat ToObjCat FromNr FromName ToNr ToName 'HVFULSWLRQ PrT or PuT Zone or node: Network object type of origin of route/partial route. Zone or node: Network object type of destination of route/partial route. Number of FromNetworkObject Name of FromNetworkObject Number of ToNetworkObject Name of ToNetworkObject
10-55
List types
$WWULEXWH
'HVFULSWLRQ PrT PuT-TSys-based PuT-TimeT-based
LinID Distance
TSysCode of selected PrT-TSys. Sum of link lengths; if FromZone or ToZone including access and egress distance.
Name of deterName of determined PuT-TSys. mined subline. Sum of link lengths FromObj - ToObj or access or egress length. Sum of subline lengths between stops or access or egress length.
DistTot Dep
Total distance: accumulated length of partial routes traversed so far within route. 00:00:00 am for Departure time is )URP=RQH: first partial route. not determined. departure time = 1.dep. - access_t. 'HSDUWXUH WLPH of VISUM detern. partial route = mines latest time DUULYDO WLPH of nafter beginning of 1. partial route. time interval which makes it possible to reach first departure from connected stop of selected zone taking origin connector time into account )URP1RGH First departure from selected stop within time interval.
Arr
Arrival time at ToObj = departure + tCur
Arrival time is not Arr. = Dep. + JT determined.
10-56
List types
$WWULEXWH
t0/RT
Travel time in un- Ride time in means of transport loaded network. including waiting times: Sum of traversed links (t0-PrTSys) and connectors and turning rel. (t0-PrT). connector time t-PuT or sum of timePuTSys of traversed links. connector time t-PuT or sum of running times Stop-Stop of subline or walking time.
tCur/JT
Ride time in loaded network
Journey time of traversed network objects. JT = AT + RT + TWT + WT + ET Start wait time=0 (both procedures) The transfer time at end of partial route is included in JT. TWT=GHSDUWXUH of next partial route Connector time t-PuT or sum t-PuT of traversed links. Connector time t-PuT or walking time + TWT or sum of RT Stop-Stop + TWT
Sum of traversed: links (tCurPrTSys) connectors, and turning relations (tCur-PrT ).
Impedance calculated accor- Impedance = ding to current TSys-based JT PrT assignment parameters. t0/RTtot
Impedance = timetable-based JT
Sum RT/t0 of partial routes traversed so far: Accumulated t0 Accumulated tsys-based RT Accumulated timetable-based RT
tCur/JTtot
Sum JT/tCur of partial routes traversed so far Accumulated tCur Accumulated TSys-based JT Accum.timetablebased JT
10-57
List types
$WWULEXWH
ImpTot
Sum of impedances for every mode and search procedure accumulated by partial routes traversed so far. Mean speed of traversed network objects for every route or partial route. In unloaded state: Calculated for Calculated for v0 = (t0 of all connectors connectors connectors + t0 from t-PuT from t-PuT of all turning and length of and length of relations + t0connector connector PrTTys of all sections from Stop-Stop links) : t-PuT and sections (Lengths of all lengths of Stop-Stop connectors + traversed times and lengths of all links. Stop-Stop links). lengths.
v0
vCur
Mean speed of traversed network objects for every route or partial route. In loaded state: vCur = v0 vCur = (tCur of all connectors + t0 of all turning relations + tCurPrTSys of all links) : (lengths of all connectors + lengths of all links) vCur = v0
v0 mean
For very mode/search procedure: mean speed v0 of traversed network objects from beginning of route including partial route. For every mode/search procedure: mean speed vCur of traversed network objects from beginning of route including current partial route.
vCur mean
10-58
List types
$WWULEXWH
AddV1,2,3
Sum of respective AddValues of traversed network objects for every current route or partial route: AddValues of origin connector + links + turning relations + destination connector AddValue of origin connector or AddValue of destination connector or Sum of link AddValues.
AddV1Sum Sum of AddValues of the partial routes of the route AddV2Sum traversed so far. AddV3Sum
6WDWLVWLFV
67$7,67,&6 in /,67,1*6PHQX 6WDWLVWLFV VHOHFW OLVW W\SH Network information Link types PuT assignment statistics LineBlocks (/LQH UHYHQXH FDOFXODWLRQ add-on module)
10-59
List types
6WDWLVWLFV 1HWZRUN LQIRUPDWLRQ
8
6WDWLVWLFV 1HWZRUN ,QIRUPDWLRQ
1HWZRUN LQIRUPDWLRQ under 67$7,67,&6in /,67,1*6PHQX
&XUUHQW QHWZRUN WUDQVSRUW VXSSO\ (in network): Number of objects for every network object type in current network (license): max. number of objects for current VISUM license (maximum): max. number of objects for largest VISUM license. Also, further detailed information on network such as mode-specific display of number of network objects, e.g. number of origin connectors of PrT and PuT transport system-specific display of number of network objects, e.g. number of one-way roads (P) or (L).
9,680 YHUVLRQ VL]HV 6HH FKDSW
10-60
List types
6WDWLVWLFV /LQN W\SHV
8
6WDWLVWLFV /LQN W\SHV
/LQN W\SHV under 67$7,67,&6in /,67,1*6PHQX
Selection: display for every link type between 00-99 or global link type between 0*-9* $WWULEXWH Number of Length AddVal1, AddVal2, AddVal3 Perf-PrT VehHour-PrT RoadToll-PrTSys RoadToll-PrTSys revenue PKm-PuT VehKm-PuT EmissDat: CO, NOx, HC, SO2 MLuS: CO, HC, SO2, NO, Pb 'HVFULSWLRQ Number of links for every type/global type Sum of link lengths Sum for every link-AddValue vehicle-km (assignment result) vehicle-h (assignment result) Sum of RoadToll-PrTSys for links Volume (number of vehicles) for every link multiplied by RoadToll-PrTSys of link Passenger kilometers (assignment result) PuT vehicle kilometers Environmental impact according to Emiss Environmental impact according to MLuS
10-61
List types
6WDWLVWLFV $VVLJQPHQW VWDWLVWLFV 3X7
8
$VVLJQPHQW VWDWLVWLFV 3X7
$VVLJQPHQW VWDWLVWLFV 3X7 under /,67,1*6in 67$7,67,&6PHQX Prerequisite: 3X7 DVVLJQPHQW under ASSIGNMENT in CALCULATE menu
10-62
List types
$WWULEXWH O-D trips total O-D trip with PuT
'HVFULSWLRQ Sum of transport demand in assignment interval. O-D trips total = O-D trip with PuT + O-D trip without PuT + O-D trip without connection PuT passengers (assignment result) O-D trip with PuT = sum of all PuT trips, i.e. O-D trip with PuT = 0 transfers + 1 transfer + 2 transfers + >2 transfers Part of demand which reaches destination from origin without using PuT lines, that is, pedestrians via origin connector-destination connector or via origin connectorwalkLink-destination connector.
O-D trip without PuT
O-D trip Non-assigned trips which were demanded (Assignment without result: no connection found). connection LinPass total No. of transfers Mean transfer frequency 0 transfers 1 transfer 2 transfers > 2 transf. Number of line trips = O-D trip with PuT+ transfer frequency Number of transfers (assignment results). Mean number of transfers for every O-D trip with PuT (assignment result) NT + 1 = mean number of sublines per O-D trip Number of transfers) passengers on direct route (without
Number of passengers who use connections with 1 transfer. Number of passengers who use connections with 2 transfers. Number of passengers who use connections with more than 2 transfers.
10-63
List types
6WDWLVWLFV /LQH%ORFNV
8
5XQQLQJV
/LQH%ORFNV under 67$7,67,&6in /,67,1*6PHQX Prerequisite: 9HKLFOH EORFNLQJ see PROCEDURES in CALCULATE menu
$WWULEXWH LineBlockNr VehTripNr Dep OTermName OTermCode OTermNr Subline Arr DTermName DTermCode DTermNr Length Run time MinLayoverT LayoverT Purpose
'HVFULSWLRQ Calculated No. of vehicle runnings (1, 2, 3 etc.); For every running, 1 vehicle is required. Number of vehicle trips, counted in ascending order per block Departure time of VehTripNr. from StartStop Name of start stop for every VehTripNr of running Identifier of start stop for every VehTripNr Number of start stop for every VehTripNr Name of subline for every VehTripNr Arrival time of TripNr at DestinationStop Name of dest. stop for every VehTripNr of running Identifier of destination stop for every VehTripNr Number of destination stop for every VehTripNr Ride distance per VehTripNr (RD) of running Ride time per VehTripNr. (RD) includ. wait. times Minimum layover time per subline Actual layover time, calculation result Service = operational line trip (not yet implemented: assignment trip)
10-64
List types
3DVVHQJHU 6XUYH\ OLVW
3DVVHQJHU VXUYH\ in /,67,1*6PHQX Prerequisites:
3DVVHQJHU VXUYH\
Passenger survey Add-on, and verified data records.
The current state of plausibilization is displayed (see Chapter 9.3).
10-65
List types
10-66
GRAPHIC ANALYSES
*5$3+,& $1$/<6(6
11-1
GRAPHIC ANALYSES
Difference network and difference display
'LIIHUHQFH QHWZRUN DQG GLIIHUHQFH GLVSOD\
The calculation of a difference network makes it possible to compare different volumes of a traffic network to each other, the (QYLURQPHQW add-on module, furthermore, allows the comparison of noise and air pollution volumes. Volume changes arise, for example, when modifications to a network or to network attributes relevant to volumes are made or if an assignment with modified assignment parameters is carried out. A difference network is created by comparing the volumes of two version files: Version file 1: Version file 2: Difference network: State 1 State 2 State1 - State2

The results of difference creation affect link and line volumes, node flows, the number of boarding, alighting, and transfer passengers as well as through traffic at stops, the respective listings
G
8
PREREQUISITES: Open a network state 1 which is to be compared as a version file Version1.ver: 2SHQ YHUVLRQ in the FILE menu 'LIIHUHQFH QHWZRUN in the CALCULATE menu. Set difference network calculation active by opening version file Version2.ver Initialize difference network
11-2
GRAPHIC ANALYSES
Version files created with a VISUM version older than 6.90 cannot be used for difference network calculation without the following: read the old version file in VISUM 7.00 and save the version file then with a new file name. It is not possible to create a difference network if the relation filter is active (traffic types between zones: 5HODWLRQV under )LOWHUV in the EXTRAS menu). If the current network (VWDWH contains links or turning relations which are not contained in the version file which was opened (VWDWH these volumes are regarded as volume increases. Links contained in the version file which was opened (VWDWH ), but which are not contained in the current network (VWDWH ) are not considered in the difference network calculation and display. These links, therefore, should not be deleted, but instead should be closed to traffic i.e. the speed or capacity should be set to "0.
*UDSKLF GLVSOD\ RI GLIIHUHQFH YDOXHV
0HQX *5$3+,&6 3$5$0(7(56 /LQNV %DUV $WWULEXWHV The links difference value can be calculated from the values of the same attribute in two network versions or the values of two attributes in the current network version. 'LIIHUHQFH GLVSOD\ option and 6HYHUDO EDUV option
For graphical display of difference values two options are provided:
11-3
GRAPHIC ANALYSES
3DJH /LQNV %DUV $WWULEXWHV DQG 'LIIHUHQFH GLVSOD\ RSWLRQ Option Prerequisite: Call DIFFERENCE NETWORK command in CALCULATE menu.
'LIIHUHQFH The volume bar indicates the positive or negative difference of the GLVSOD\ selected attribute calculated by link direction.
'LIIHUHQFH QHWZRUN DWWULEXWH Select 1 of the attributes provided for difference network calculations: VolVeh-PrT VolPers-PrT VolPCU-PrT VolSat-PrT VolPers-PuT VolVeh-Sys VolPers-Sys VolVeh-DSeg VolPers-DSeg VolPers-DSeg-Sys
PLQ PD[ Display of the minimum and maximum difference values calculated for the selected attribute. 6FDOLQJ Enter PLQ PD[ scaling values as absolute values. Example: Enter 0200 if min = -200 and max = 150 have been calculated. Link labels indicate negative values. Additionally different bar colors and styles can be specified for positive/negative values.
11-4
GRAPHIC ANALYSES
Difference value display: max. bar width for values user-defined MaxValue appropriate bar width for values > MinValue < MaxValue, no bar display if difference value < user-defined MinValue.
PD[ EDU ZLGWK Specify in [mm]. 5RXQG Enter factor for Rounding of displayed link label values! %DVLF 9RO Enable Option 'UDZ to highlight the identical range of attributes values (basic volume) within the attribute bar, specify color and fill style. 'LII Specify bar color and fill style for difference values > 0. 'LII Specify bar color and fill style for difference values < 0.
'LIIHUHQFH QHWZRUN GLVSOD\ VHH H[DPSOH SDUDPHWHUV DERYH
'LIIHUHQFH QHWZRUN GLVSOD\ ZLWK %DVLF 9RO 'UDZ
11-5
GRAPHIC ANALYSES
3DJH /LQNV %DUV $WWULEXWHV DQG 6HYHUDO DWWULEXWH EDUV RSWLRQ Option VHYHUDO DWWULEXWH EDUV
Enable 'LVSOD\ option. 6HH Chapter 12.7.3 for 6WDQGDUG.
'LIIHUHQFH QHWZRUN GLVSOD\ VHH SDUDPHWHUV DERYH 6WDQGDUG
)XUWKHU RSWLRQV IRU GLVSOD\LQJ GLIIHUHQFH YROXPHV 1RGH IORZ GLVSOD\: PrT-volumes. Negative values are displayed with a minus sign, but cannot be highlighted in color. 1RGHV: PrT-volumes in form of a diagram. 6WRSV: boarding, alighting, and transfer passengers, through traffic with halt at stop, through traffic without halt at stop in form of a diagram.
11-6
GRAPHIC ANALYSES
/LVW GLVSOD\ IRU GLIIHUHQFH YDOXHV
Links (LINKS in the LISTINGS menu): Volume-PrT, Volume-PuT, Volume-TSys; Volume-DSeg. Nodes (NODES in the LISTINGS menu): Volume-PrT, boarding, alighting, and transfer passengers, through traffic with stop, through traffic without stop. Turning relations (TURNING RELATIONS in the LISTINGS menu): Volume-PrT, Volume-TSys. Connectors (CONNECTORS in the LISTINGS menu): Volume-PrT, Volume-PuT. Line routes of sublines (/LQH URXWH under SUBLINES in the LISTINGS menu): boarding and alighting passengers, Volume-PuT.
Reductions can be identified by the minus sign. The mean, minimum, and maximum volume difference can be displayed via &ROXPQ 6WDWLVWLFV in the OPTIONS menu which can be actuated in each open list. 6DYLQJ YROXPH GLIIHUHQFHV
Save as version file *.ver. Save as attribute file *.att for the listing types OLQNV, QRGHV WXUQLQJ UHODWLRQV, FRQQHFWRUV and VXEOLQHVOLQH URXWHV.
11-7
GRAPHIC ANALYSES
'LIIHUHQFH YDOXH FDOFXODWLRQ &RPSDULVRQ RI WZR OLQN DWWULEXWHV Two link attributes of the current network version can be selected for difference value calculation and display. *5$3+,&6 3$5$0(7(56 /LQNV %DUV $WWULEXWHV 'LIIHUHQFH GLVSOD\ RSWLRQ
Option Prerequisite: No active difference network. 'LIIHUHQFH The volume bar indicates the positive or negative difference between GLVSOD\ the selected attributescalculated by link direction
3OXV Select link attribute, the values of the attribute selected under Minus are to be subtracted from. 0LQXV Select link attribute to be subtracted from the Plus values. For other graphics parameters see 'LIIHUHQFH GLVSOD\
'LVSOD\ RI GLIIHUHQFH YDOXHV VHH SDUDPHWHU VHWWLQJV DERYH
11-8
GRAPHIC ANALYSES
'LVSOD\ RI GLIIHUHQFH YDOXHV %DLVF 9RO 'UDZ
*5$3+,&6 3$5$0(7(56 /LQNV %DUV $WWULEXWHV 2SWLRQ 'LIIHUHQFH GLVSOD\ DQG RSWLRQ &ODVVLILFDWLRQ Option Define value classes for graphical display of attribute values. 'LIIHUHQFH GLVSOD\
For &ODVVLILFDWLRQ see Chapter 12.7.3 Display as &ODVVHV
11-9
GRAPHIC ANALYSES
Flow bundles
)ORZ EXQGOHV
Flow bundles may use numerous criteria to filter loaded routes between origin and destination in the current network, and to display them in the network display and in the respective listing. Loaded routes are the result of assignment calculation and consist of the course of a route from an origin zone to a destination zone, refer to the private or public transport type, and show a volume (passengers, vehicles).
Flow bundles consists of all routes whose course traverses selected network objects. Network object selection thus constitutes the route filter criterion of a flow bundle. Important: Every route can only be found once. The type of flow bundle is determined by the selected network object type: Node and stop flow bundle (SINGLE SELECT nodes or stops). Link flow bundle (SINGLE SELECT links) Zone and global zone flow bundle (SINGLE SELECT zones or global zones) Traffic type flow bundle (Define active links via MULTI SELECT, AREA and/or FILTER)
The flow bundle can be created by selecting one or several objects of a network object type; but it can also be specified by any combination of selected network objects of different network object types. In the graphic display, the route courses highlighted in color and the respective flow bundle volumes for each traversed link describe the spatial and quantitative distribution of traffic of the specified flow bundle.
If a flow bundle is active, the trips belonging to the flow bundle can be saved as a flow bundle matrix. The flow bundle considers the active settings of the relation filter. This makes flow bundle analyses for particular types of zones (e.g. only internal zones) possible.
11-10
Flow bundles
GRAPHIC ANALYSES
0HQX *5$3+,&6 )/2:%81'/( )ORZ EXQGOH GLDORJ Select Private or Public Transport Select Network object type: Link, Node, Zone or Global zone.
The $FWLYH /LQNV button is only active, if at least 1 link is passive.
6HOHFW QHWZRUN REMHFWV IRU )ORZ EXQGOH VSHFLILFDWLRQ Select OLQNV by left-click on FromNode and ToNode (indicating the link direction) or right-click to Search for link Nr. Select QRGHV by left-click on the node or right-click for Search. )ORZ EXQGOH 76\V VSHFLILFDWLRQ GLDORJ PuT: Select demand segment(s) and/or PuT-TSys. PrT: Select demand segemnt(s).
Select VWRSV by left-click on the stop or right-click for Search. "Flow bundle of stop dialog: Select passenger type(s). For "Flow bundle TSys specification": see above.
11-11
GRAPHIC ANALYSES
Flow bundles
Select a ]RQH or a JOREDO ]RQH by left-click on the centroid/label or right-click for Search. "Flow bundle dialog: Select type(s). Zones" Traffic
For "Flow bundle TSys specification": see above.
Zones cannot be traversed. They can only be selected as the first (origin zone) or last search object (destination zone) of a route or as a zone with origin and destination traffic.
If not all PuTSys are selected, then the following rules apply: )ORZ EXQGOH RI OLQN: only routes which use the selected PuTtransport systems on the selected link are selected. )ORZ EXQGOH RI VWRS: %RDUGLQJ SDVVHQJHUV: the boarding line must correspond to the selected transport system. $OLJKWLQJ SDVVHQJHUV: the last PuT-line must correspond to the PuT-system. 7UDQVIHU SDVVHQJHUV: both lines must correspond to the selected PuT-system. 7KURXJK SDVVHQJHUV ZLWK VWRS: the line must correspond to the selected PuT-system. Through passengers with stop are passengers who use a line which halts at the stop, but who continue their journey. The corresponding routes are selected, e.g. the special case access-StopA-Line1-StopB-Footpath1StopC-Footpath2-StopD-Line2-StopE-egress at stop C is also selected. 7KRXJK SDVVHQJHUV ZLWKRXW VWRS: the same as through passengers with stop, but without "footpath through passengers".
11-12
Flow bundles
GRAPHIC ANALYSES
)ORZ EXQGOH 7\SHV RI WUDIILF based on active links: MULTI SELECT or LINK FILTER settings required, Click $FWLYH OLQNV button (at least 1 link needs to be in the passive state), )ORZ EXQGOH 7\SHV RI WUDIILF GLDORJ Select up to 4 type(s) of traffic.
&RQQHFW VHYHUDO QHWZRUN REMHFWV IRU IORZ EXQGOH VSHFLILFDWLRQ Define AND-Term (sequence of network objects) Select first network object as described above, select next network object etc.
Any number of nodes and/or links can be connected by AND. Zones and global zones may be origin and/or destination of routes. The flow bundle therefore describes DOO routes from origin to destination which traverse DOO selected network objects in exactly the order in which they were selected.. Define an OR-operation by ending an AND-Term ([HFXWH EXWWRQ executes flow bundle (AND-Term). The subsequent object selection is combined with the previous object selection through an OR-operation. 1HZ $1'7HUP EXWWRQ combines the subsequent object selection with the previous object selection through an ORoperation without executing the specified flow bundle. $FWLYH OLQNV EXWWRQ activating this button automatically ends the AND-operation since multiple links cannot be combined with a further object selection through an AND-operation.
11-13
GRAPHIC ANALYSES
Flow bundles
6HOHFWLQJ D GHVWLQDWLRQ ]RQH since zones can only be selected as the first (origin traffic) or last search object of a route, an AND-operation is automatically ended if a zone is either selected as the first search object with destination traffic or as at least the second search object.
Any number of AND-terms can be combined by OR-operations. The flow bundle thus describes all routes which fulfil at least one route filter criterion i.e. one AND-term. Every route is only output once with the flow bundle, even if it is found for several AND-terms. )ORZ EXQGOH GLDORJ In the SURWRFRO ILHOG the flow bundle specification is recorded along with all selected objects (object type and No.), (type of traffic for zones) transport type PrT/PuT, and AND/OR operation type. See example settings: PuT demand originating from Zone 1U OR PuT passengers traversing Stop 1U OR PrT routes traversing Link Nr. 3 AND Node 30.
G
8
By double clicking a network object in the protocol field, the selection of demand segments for all network objects of the specified ANDTerm and the specification of PuT transport systems for the selected network object can be modified. After flow bundle specification the following actions can be carried out: ([HFXWH EXWWRQ searches for all routes which traverse the selected network objects as specified by the flow bundle specification, and outputs the found routes graphically or in a list with volume information. &ORVH EXWWRQ closes the dialog box. The flow bundle specification and the already executed flow bundle remain active. ,QLWLDOL]H EXWWRQ deletes flow bundle specification and previously executed flow bundle.
11-14
Flow bundles
GRAPHIC ANALYSES
*UDSKLF GLVSOD\ RI IORZ EXQGOHV
8
)ORZ EXQGOHV
0HQX *5$3+,&6 3$5$0(7(56 )ORZ EXQGOHV 0RGLI\ *UDSKLFV SDUDPHWHUV
/D\HU )ORZ %XQGOH Acivate the layer for graphical display of flow bundles. 6FDOLQJ Set minimum and maximum according to the given value range, Enter max. bar width for graphical display of flow bundle volumes max. scaling value. /DEHOV Flow bundle volume labels are displayed according to current Multiply and Round settings. Both entries are only considered for labelling, internally the calculated volume values remain unchanged. 6HOHFWHG QHWZRUN REMHFWV 3U7 IORZ EXQGOH 3X7 IORZ EXQGOH Select color to highlight selected network objects and for labels. PrT: Select bar color and fil style and text color, PuT: Select bar color and fil style and text color.
11-15
GRAPHIC ANALYSES
Flow bundles
0RGLI\ *UDSKLFV SDUDPHWHUV /D\HUV GLDORJ /D\HU Flow bundle volume display without total volume: Draw IORZ EXQGOH layer Do not draw /LQN EDU layer. Displaying flow bundle volumes in relation to the total volume: Draw )ORZ EXQGOH layer and /LQN EDU layer. So that the flow bundle volume is drawn above the total volume, the layer order needs to be arranged correspondingly (8S or 'RZQ button).
G
8
To label flow bundle link volumes, the OLQN ODEHOV OD\HU must be active, and volume labels must be set to 'UDZ on the /DEHO page.
/LVW RXWSXW RI IORZ EXQGOH YROXPHV Route list (ROUTES in the LISTINGS menu, Select: )ORZ EXQGOH URXWHV for 3U7URXWHV or 3X7URXWHV): The number of found routes for each origin/destination relation is counted in ascending order Q, the index numbers 1..n by route No. refer to the route sections. Link list (LINKS in the LISTINGS menu): )ORZ EXQGOH YROXPH 3X7 )ORZ EXQGOH YROXPH 3U7 Zone and global zone list (ZONES/GLOBAL ZONES in the LISTINGS menu): )ORZ EXQGOH RULJLQ WUDIILF 3X7 )ORZ EXQGOH GHVWLQDWLRQ WUDIILF 3U7
6DYLQJ IORZ EXQGOH YROXPHV
The current flow bundle specification is saved along with the graphic parameters. If it is opened for a different version of the network, VISUM carries out a new route search for this network. The flow bundle volumes can be saved as Link-AddValues. The O-D-matrix for the active flow bundle must be saved as a flow bundle matrix via )ORZ EXQGOH PDWUL[ under 2' PDWUL[ under SAVE in the FILE menu. Save as attribute file *.att for the respective list types.
11-16
Flow bundles
GRAPHIC ANALYSES
([DPSOH 7UDIILF W\SH IORZ EXQGOH IRU WKURXJK WUDIILF A traffic type flow bundle can be created for origin, destination, internal, through, and external traffic. Which routes are found for the different traffic types of the flow bundle depends on the selection of active links: 2ULJLQ WUDIILF 'HVWLQDWLRQ WUDIILF ,QWHUQDO WUDIILF 7KURXJK WUDIILF

([WHUQDO WUDIILF

Prerequisites for flow bundle display based on active links are grey-shaded: Fist link of route active. Last link of route inactive. Other links of route inactive or active. 3URFHGXUH $FWLYDWH MULTI SELECT mode IRU DQ\ QHWZRUN REMHFW First link of route inactive. Last link of route active. Other links of route inactive or active. First link of route active. Last link of route active. Other links of route inactive or active. First link of route inactive. Last link of route inactive. At least one of the other links of the route active. DOO links of route inactive.
Specify MULTISELECT polygon. FLOW BUNDLE in the GRAPHICS menu. )ORZ EXQGOH GLDORJ Select transport type: 3U7. $FWLYH OLQNV button. 7\SHV RI WUDIILF IORZ EXQGOH GLDORJ Select traffic type: 7KURXJK WUDIILF )ORZ EXQGOH 76\V VSHFLILFDWLRQ GLDORJ Select demand segment(s).
GRAPHIC ANALYSES
Flow bundles
)ORZ EXQGOH GLDORJ The flow bundle specification is recorded in the SURWRFRO ILHOG: / $PRXQW 7 3U7 stands for: all flow bundles showing the PrT7hroughTraffic with regard to active /inks.
([HFXWH EXWWRQ Find all routes which traverse the active links and then output the found routes with volume information in a list or graphically on the screen.
1HWZRUN GLVSOD\ Traffic type flow bundle with route volumes only within the specified MULTI SELECT polygon:
Traffic type flow bundle with all route volumes within and outside the specified MULTI SELECT polygon by closing the "Flow bundle" dialog box. and initializing the specified MULTI SELECT polygon.
11-18
Isochrones
GRAPHIC ANALYSES
,VRFKURQHV
Based on one or several selected nodes or stops, isochrones visualize the accessibility of PrT and PuT destinations in up to ten intervals highlighted in color: PrT-Isochrones visualize reachability intervals for link sections. PuT-Isochrones visualize reachability intervals for stops.
The reachability of destinations and the corresponding division into intervals can be specified according to different criteria for PrT and PuT: for PuT: temporal reachability (based on transport system or timetable) connection search, can be modified through different search parameters and by specifying a time interval. Number of transfers can also be regarded. for PrT: reachability according to different search criteria (tCur, t0, distance, impedance or AddValue1..3) for the selected PrT-System.
The reachability of destinations can be displayed VLPXOWDQHRXVO\ for both PuT and PrT in the network.
11-19
GRAPHIC ANALYSES
Isochrones
3U7,VRFKURQHV
0HQX *5$3+,&6 ,62&+521(6 ,VRFKURQHV GLDORJ Select transport type: 3U7. Select route choice criterion: W&XU: travel time in loaded network W: travel time in free network 'LVWDQFH: link length $GG9DOXH. ,PSHGDQFH: impedance as specified under assignment parameters.
Select PrT-transport system e.g KHDY\ JRRGV YHKLFOH
6HOHFW RQH RU VHYHUDO QRGHV Mark with left mouse click or Search with right mouse click.
A node is deselected if it is marked again. *UDSKLF GLVSOD\ RI 3U7,VRFKURQHV The isochrone calculation and display is switched on by selecting a node. The graphic display is based on the interval ranges and colors specified by the graphic parameters.
11-20
Isochrones
GRAPHIC ANALYSES
,VRFKURQHV GLDORJ &ORVH EXWWRQ Exit command; without initialization, the isochrone display remains active. ,QLWLDOL]H EXWWRQ Switch off isochrones display.
6SHFLI\LQJ FDOFXODWLQJ DQG GLVSOD\LQJ IXUWKHU 3U7LVRFKURQHV Specify new route choice criterion or transport system in the "Isochrones" dialog box: the modifications are immediately considered for the current isochrones display. Selecting further nodes for isochrone output: without ,QLWLDOL]H: combine isochrone display with previous node selection. The individual link sections are all output with the smallest interval. with ,QLWLDOL]H: new isochrone display ZLWKRXW combining previous node selection.
&RPELQLQJ 3UW DQG 3X7,VRFKURQHV See example, page: )HKOHU 7H[WPDUNH QLFKW GHILQLHUW.
3X7,VRFKURQHV
0HQX *5$3+,&6 ,62&+521(6 ,VRFKURQHV GLDORJ Select PuT type and one of the PuT modes. Select search criterion: -RXUQH\ WLPH according to procedure: 1R 7UDQVIHUV: Number of transfers from/ to sublines or TSys, according to route search procedure. 7LPHWDEOHEDVHG or 76\VEDVHG assignment.
Select procedure for route search calculation:
11-21
GRAPHIC ANALYSES
Isochrones
Isochrones dialog
Specific "Search parameters" Dialog
TSys-based
Timetable
G
8
See Chapter 7: "PuT-Assignments procedures. 6HOHFW VWRSV Mark stop by left-click on stop or Right-click to search for stop Nr.
Deselect a marked stop by another left-click.
11-22
Isochrones
GRAPHIC ANALYSES
*UDSKLF GLVSOD\ RI 3X7LVRFKURQHV Calculation and display of isochrones is called up by by selecting a stop for TSys-based route search selecting a stop and mouse-click on ([HFXWH for timetable-based connectin search. The graphic display is based on the interval ranges and colors specified in the graphic parameters.
6SHFLI\LQJ FDOFXODWLQJ DQG GLVSOD\LQJ IXUWKHU 3X7LVRFKURQHV Specify new parameters and/or new time interval in the "Isochrones dialog box.. Then start calculation. Select further stops for displaying isochrones: without ,QLWLDOL]H: combine isochrone display with previous stop selection. The individual stops are displayed with the smallest interval. with ,QLWLDOL]H: new isochrone display ZLWKRXW combining with previous stop selection.
,VRFKURQHV GLDORJ &ORVH EXWWRQ exit command; without initialization, the isochrone display remains active. ,QLWLDOL]H EXWWRQ initializes current isochrones display.
11-23
GRAPHIC ANALYSES
Isochrones
([DPSOH IRU FRPELQHG 3U7 DQG 3X7LVRFKURQHV PrT and PuT-isochrones can be superimposed (see illustration) by switching from one transport type to the other in the "Isochrones" dialog box during isochrone specification:
11-24
Isochrones
GRAPHIC ANALYSES
6SHFLI\LQJ LQWHUYDO UDQJHV DQG FRORUV
0HQX *5$3+,&6 3$5$0(7(56 ,VRFKURQHV 0RGLI\ *UDSKLFV SDUDPHWHUV ,VRFKURQHV
&ULWHULRQ ,VRFKURQHV Display of the criteria currently selected for PrT and PuT. 9DOXH UDQJHV ,VRFKURQHV 0XOWLSO\ EXWWRQ Specify a factor for multiplying isochrone value ranges (Upper limits of intervals). &ODVVLILFDWLRQ Specify Prt interval ranges: W&XU W [h, min or s], Distance [m], ,PSHGDQFH $GG9DOXH [no unit].
or PuT interval ranges: 7LPH [h, min or s], 1R 7UDQVIHUV.
Select color for each user-defined interval. 6WRSV QRW UHDFKHG Select color to highlight PuT stops which have not been reached.
11-25
GRAPHIC ANALYSES
Isochrones
6DYLQJ LVRFKURQHV
Save isochrone specifications in the graphic parameters file *.gpa (6DYH JUDSKLF SDUDPHWHUV under SAVE in the FILE menu). Save all of current editing as version file *.ver (6DYH YHUVLRQ in the FILE menu).
7DEXODU RXWSXW RI ,VRFKURQHV
Node list: LISTINGS -NODES: Basic display 3U7,VRFKURQHV7LPH DV VHOHFWHG W RU W&XU, 3X7,VRFKURQHV7LPH DFFRUG WR SURFHGXUH, 3X7,VRFKURQHV1R7UDQVIHUV.
11-26
Search for routes
GRAPHIC ANALYSES
6HDUFK IRU URXWHV
With the 6HDUFK IRU URXWHV command, the best routes from a chosen origin (node/zone) to a chosen destination (node/zone) in the PrT and PuT network are determined according to different route search criteria, and then displayed in graphic and tabular form. The determination of the routes depends on the specified search criteria: for PuT: best connection time based on a connection search, can be modified by specifying different search parameters and a start time. for PrT: search for the best route according to different route search criteria (tCur, t0, distance, Impedance or AddValue1..3).
The route search can be carried out VLPXOWDQHRXVO\ for both PuT and PrT in the network.
11-27
GRAPHIC ANALYSES
Search for routes
0HQX *5$3+,&6 5287(6($5&+ 6HDUFK IRU URXWHV GLDORJ Select transport type: 3U7: search only PrT-routes. 3X7: search only PuT-routes. 3U7 DQG 3X7: search PrT- and PuTroutes. network object type for start/end of route: 1RGH =RQH.
3DJH 3U7 Select route choice criterion: W&XU: travel time in loaded network, W: travel time in unloaded network, GLVWDQFH: length of traversed links, LPSHGDQFH: according to assignment parameters. $G9DO. Seelect private transport system, e.g. Car.
3DJH 3X7 Select one of the PuT modes and assignment procedures and Specify search parameters. 76\VEDVHG route search. 7LPHWDEOHEDVHG connection search: Enter start time for search [hh:mm:ss]. The first connection which departs from the selected node/zone at or after the time entered under 6WDUW DW is output.
11-28
Search for routes
GRAPHIC ANALYSES
Open dialog box and specify "Search" parameters for route search Search parameters according to the selected procedure.
G
8
For 6HDUFK parameters see Chapter 7: PuT-Assignment procedures. 6HOHFW RULJLQ DQG GHVWLQDWLRQ RI WKH URXWH by marking an origin zone or a start node by marking a destination zone or an end node.
If a node is chosen as a destination, the total route can be extended by a further route section by selecting an additional destination etc..
Zones can only be origins and/or destinations of routes; they cannot be traversed. If zones are origin and/or destination of routes, the respective origin or destination connector times are contained in the output times. 6HDUFK IRU URXWHV GLDORJ &ORVH EXWWRQ exit command; without initialization, the route search display remains active. ,QLWLDOL]H EXWWRQ initializes current route search display.
11-29
GRAPHIC ANALYSES
Search for routes
'LVSOD\ URXWH VHDUFK Call up calculation and graphic display of the route search: Select end/destination of the route, press ([HFXWH for timetable-based procedure. The graphic display is based on the specified colors for PrT and PuT-route courses in the graphic parameters. The list for the tabular display is opened via SEARCH ROUTES in the LISTINGS menu.
6HDUFK IRU IXUWKHU URXWHV Specify new PrT-route search criterion, new PrT-transport system and/or new PuT-search parameter in the "Search for routes" dialog box: the modifications are immediately implemented in the current graphic and tabular display. Select further nodes or zones for route search: without ,QLWLDOL]H: adds a new destination and thus a new partial route to the previous route specification. with ,QLWLDOL]H: new route search ZLWKRXW combining previous route specification. When a destination zone is selected, the route specification cannot be extended. If capacities or percentages for connectors were specified for assignment or if a link type was blocked by the assignment parameters and this was not specified as hard blocking, the time penalties included in the calculation must be taken into account to interpret the route times.
11-30
Search for routes
GRAPHIC ANALYSES
6SHFLI\LQJ JUDSKLF SDUDPHWHUV IRU GLVSOD\LQJ WKH URXWH VHDUFK
8
6HDUFK IRU 5RXWHV
0HQX *5$3+,&6 3$5$0(7(56 6HDUFK IRU URXWHV 0RGLI\ *UDSKLFV SDUDPHWHUV 5RXWH VHDUFK
Select color for display of selected network objects, PrT routes, PuT routes. 0RGLI\ *UDSKLFV SDUDPHWHUV %DVLF %DVLF To highlight selected zones and connectors from/to selected zones the color selected for 0DUNLQJ is used.
Arrows indicate the direction of the route and transfer stops.
11-31
GRAPHIC ANALYSES
Search for routes
/LVW GLVSOD\ IRU URXWH VHDUFK
Route search list (SEARCH ROUTES in the LISTINGS menu) The list optionally either displays only the PrT-route (with specified route sections), only the PuT-route (generated and specified route sections) or both the PrT and the PuT-routes together.
6DYLQJ WKH URXWH VHDUFK
Save as attribute file *.att for the corresponding list type.
11-32
Node flows
GRAPHIC ANALYSES
1RGH IORZV
Node flows visualize PrT-volumes at individual nodes for the respective turning relations. Node flows can be displayed for nodes with at least 2 and a maximum of 6 neighbouring nodes. By clicking nodes one after another, up to 100 node flow plans can be displayed in one plot. The volumes of turning relations can also be displayed in a turning relation list (TURNING RELATIONS in the LISTINGS menu).
11-33
GRAPHIC ANALYSES
Node flows
0HQX *5$3+,&6 12'()/2:6 1RGH IORZ GLDORJ 6HOHFW WKH WUDIILF YROXPH DWWULEXWH VolumeVeh-PrT, AddVal1..3 of turning relations, Difference between VolVeh-PrT and AddVal
$FWLYDWHGHDFWLYDWH QRGH IORZ GLVSOD\ 2Q2II5DGLXV: activate command to switch on or off display of node flows by selecting a node by mouse-click; the radius of a displayed node flow may be modified. 2Q2II5DGLXV: command is deactived as soon as the "$OO 7H[WV" or "7H[W EORFN" label command is activated. $FWLYDWHGHDFWLYDWH QRGH IORZ ODEHOV Labelling DOO turning relations of a node: $OO WH[WV: activate command. Click on node to display/remove label. $OO texts: deactivate command. Labelling particular turning relations of a node: 7H[W EORFN: activate command. If option is active, the label of a marked node can be displayed or removed by clicking the text block (toggle functionality). 7H[W EORFN: deactivate command. 6ZLWFKLQJ RQ QRGH IORZ GLVSOD\ DW DOO QRGHV 6ZLWFK RQ DOO YLVLEOH button in "1RGH IORZ" dialog box. DW SDUWLFXODU QRGH: click node in network display DW VHYHUDO QRGHV: mark nodes one after the other.
The node flow display of particular nodes can be switched off by clicking the relevant nodes.
11-34
Node flows
GRAPHIC ANALYSES
0RGLI\LQJ WKH QRGH IORZ UDGLXV for particular nodes: in the 1RGH IORZ dialog box: enter radius in meters in "5DGLXV >P@ input field, and then click on node in network display. In the network display: increase or decrease radius of node flow by dragging the "rubber band" with pressed mouse key. for all nodes: Enter radius in meters in the "5DGLXV >P@ input field in the "1RGH IORZ dialog box, then click on 5DGLXV YDOLG IRU DOO button. The radius is displayed in [m] according to the scale of the network. In this way, node flows are always displayed in the same proportion to the link length independent of the network section or output device (Screen display identical to plot). New radius entries are only considered for newly selected nodes. The size of node flow plans which have already been displayed remains the same. It is advisable to first display a node flow plan using the default radius, to change the default in [m] if necessary, and then to call up all desired node flow plans. Necessary size adjustments of particular node flow plans can be carried out later in the network display. 1RGH IORZ GLDORJ ER[ &ORVH EXWWRQ exit command; without the 6ZLWFK RII DOO button, the graphic display remains active. 6ZLWFK RII DOO button: exit command Prerequisite for the graphic display of node flows are the graphic parameter settings under PARAMETERS in the GRAPHICS menu: 1RGHV 1RGH IORZ display type (see description below). Node flow plans are not drawn if: the radius is too small to display the turning relation flows with the selected width of volume bars one half goes beyond the window the node lies outside of the current window (in this case the remaining node arms are not displayed either) To set node filters or turning relation filters or to activate list display, the 1RGH IORZV command need not be exited.
11-35
GRAPHIC ANALYSES
Node flows
6HW JUDSKLF SDUDPHWHUV IRU QRGH IORZ GLVSOD\
8 8
1RGHV 1RGH IORZV
0HQX *5$3+,&6 3$5$0(7(56 1RGHV 3$5$0(7(56LQ WKH *5$3+,&6 PHQX 0RGLI\ *UDSKLFV SDUDPHWHUV 1RGH IORZV
See Chapter 12 "Modify Graphics parameters Layer:" Enable option /D\HU 1RGH IORZV. For graphical display of link volumes together with node flow volumes both scaling range and bar width should match.
11-36
Node flows
GRAPHIC ANALYSES
6SHFLDO FDVH GLVSOD\LQJ QRGH IORZV LQ FOLSV
6ZLWFK RQ QRGH IORZ GLVSOD\ DW QRGH /D\HU XQGHU 3$5$0(7(56 LQ WKH *5$3+,&6 PHQX 0RGLI\ JUDSKLF SDUDPHWHUV /D\HU
draw in clip: node flows. ,16(5702'( 2EMHFW W\SH &/,36 Open clip and desired node flow. Graphic display of node flow in clip:
G
8
Maximally three clips can be displayed.
/LVW GLVSOD\ IRU QRGH IORZV Turning relation list (TURNING RELATIONS in the LISTINGS menu) If the 1RGH IORZ display is switched on, only the volumes of the turning relations of displayed node flows are displayed in the list.
6DYLQJ QRGH IORZV
Active node flow plans are saved along with the graphic parameters. Save as attribute file *.att for the corresponding list type.
11-37
GRAPHIC ANALYSES
O-D flow
2' IORZ
The O-D flow command provides a visual display of the demand of each FromZoneToZone relation from one O-D matrix or summed up from several O-D matrices for one or more than one relation. connecting line between zone centroids. bars for proportional demand display per o-d relation (by direction or crosssection). bar labels (similar to link labels, according to selected demand segment(s)).
Graphical display:
11-38
O-D flow
GRAPHIC ANALYSES
For o-d flow display one, several or all o-d relations can be selected. Call in GRAPHIKCS menu PARAMETERS.. to select relations and demand segemnt(s), O-D FLOW for idividual relations (additionally). Select relations: PARAMETERS..- 2' )ORZ: Specify graphical parameters, O-D FLOW : Click on 2 zones (both are FromZone and ToZone). Select demand matrix (by demand segment): only via Graphics- Parameters...- 2' IORZ. For graphical display the following settings are regarded: GRAPHICS- PARAMETERS.. 2' IORZ: Line, bar, scaling range, labels, /D\HU: Display on screen and/or in clips, )RQWV: Fonts selected for screen/plot output. Note: For o-d flow display called via GRAPHICS - O-D FLOW the current option 'UDZ 2' 0DWUL[ OD\HU setting is not regarded.
0HQX *5$3+,&6 3$5$0(7(56 2' IORZ Activate display and select demand segment(s) Set graphics parameters. 0RGLI\ *UDSKLFV SDUDPHWHUV 2' IORZ
2' IORZ
See settings under GRAPHICS PARAMETERS LAYERS: Enable option /D\HU 2' IORZ.
GRAPHIC ANALYSES
O-D flow
'HPDQG VHJPHQWV Select one or more demand matrices (left-click - <Ctrl>). 6HOHFW 2' UHODWLRQV DFWLYH ]RQHV RQO\: display the O-D flow only for relations whose FromZone and ToZone are active. DFWLYH UHODWLRQV RQO\: display the O-D flow only for relations which according to the relation filter are active. RQO\ YDOXHV !: display no O-D flow for relations with demand < minimum value. 0D[LPXP QXPEHU Enter number of relations to be displayed (e.g. highest demand). *UDSKLFDO GLVSOD\ &URVVVHFWLRQ &URVVVHFWLRQ: display demand between 2 zones as the sum of both directions. o &URVVVHFWLRQ: display by direction. %DUV colour and shading of value bar along connecting link. %DU VFDOLQJ indicate range of scale (FromValue-ToValue) Demand value < FromValue = ToValue > ToValue > FromValue and < ToValue Display of demand no display with max. bar width with max. bar width with proportionally matched bar width
/DEHO The label is displayed for those relations currently representing the O-D flow only. 'UDZ: display label with selected colour/text size RQO\ YDOXHV !: indicate minimum value; No label for relations with demand < minimum value /LQNV type of display used for the connecting line between zone centroids. =RQHV Draw zones for displayed relations only: only the origin and destination zones of the relations selected for display of o-d flows are displayed. Prerequisite: 'UDZ ]RQHV OD\HU needs to be active.
O-D flow
GRAPHIC ANALYSES
2' IORZ GLDORJ Mark relation with left-click on FromZone and ToZone.
The options are not active until origin and destination are selected. 'UDZ: o-d relation will be drawn 7H[W: o-d relation will be labelled 6KLIW WH[W button: click on new label position.
Data file management: Save current settings as graphics parameters, demand values as version and/or o-d matrix files. To switch off display o-d flow call GRAPHICS-PARAMETERS.. Dialog box 2' IORZ o 2' IORZ OD\HU or Dialog box Layer 'UDZ o 2' IORZ ODyer.
11-41
GRAPHIC ANALYSES
PuT Vehicle animation
3X7 9HKLFOH DQLPDWLRQ
The PUT-VEHICLE ANIMATION function provided in the GRAPHICS menu allows to vizualize the flow of PuT vehicles through the network. Each vehicles location is calculated precisely from the timetable.
0HQX *5$3+,&6 387 9(+,&/($1,0$7,21 3X79HKLFOH $QLPDWLRQ GLDORJ
6LPXODWLRQ VWDUW DQG HQG Start continuous simulation run (both directions in terms of time). Start simulation in steps according to specified time intervals (both directions). Go to start or end state of simulation Interrupt. Enter 6WDUW WLPH, (QG WLPH and 6HFRQGV SHU VWHS .
11-42
GRAPHIC ANALYSES
'LVSOD\ RQ VFUHHQ
EDFNZDUG IRUZDUG
The color of a vehicle indicates the particular PuT line, since linespecific colors from line bar settings under GRAPHICS + PARAMETERS + LINES + BARS are used for the on-screen display of animated vehicles. For a vehicle touched with the mouse pointer (no mouse-click!) the subline name is displayed in the status line.
11-43
GRAPHIC ANALYSES
11-44
GRAPHICS PARAMETERS

*5$3+,&6 3$5$0(7(56
The graphic parameters are called up via the GRAPHIC - PARAMETERS menu.
The graphic parameters relevant to special applications have already been described in the respective chapters along with the VISUM command, e.g. Chapter 11: Isochrones, flow bundle, route search, O-D flows, difference network Chapter 14: Printing page.
12-1
GRAPHICS PARAMETERS
Basics
%DVLFV
%DVLFV
&RPPHQW Users comments on graphic parameters. 'UDZ /HJHQG Switch on for plot display! Displaying the legend specified by the user can cover parts of the network. 7H[W VFDOLQJ RQ VFUHHQ Text size on screen = text scaling factor * text size per network object/graphic object; Text size of plot = text size in mm. 5LJKW KDQG WUDIILF /HIW KDQG WUDIILF Display of volume bars at link in direction of travel.
12-2
Basics
GRAPHICS PARAMETERS
0DUNLQJ Select color and line thickness: VISUM marks a selected network object in 0DUNLQJ color and further enabled network objects in 0DUNLQJ color. &RRUGLQDWHV Display coordinates of current network, current network section and clips on screen. Section coordinates can be modified via the Windows scroll bar or via the =RRP command. Clip coordinates can be copied as selection coordinates.
12-3
GRAPHICS PARAMETERS
Layers
/D\HUV
'HILQLQJ OD\HUV IRU JUDSKLFDO GLVSOD\ /D\HUV Via the graphic parameter Layers the user can define whether a graphic layer should be displayed on screen and in the plot or whether it should be displayed within clips; as well as the sequence for drawing enabled layers.
Enabling / disabling layers and changing their sequence: Select layer with mouse click (colored bar) Click on 'UDZ i.e. 'UDZ ZLWKLQ FOLS.
12-4
Layers
GRAPHICS PARAMETERS
Clicking on
or
moves the selected layer up or down.
The first layer to be drawn by VISUM is the upper layer and the last is the lowest layer; every layer can cover parts of layers which were drawn earlier.
12-5
GRAPHICS PARAMETERS
Nodes and stops
1RGHV DQG VWRSV
*UDSKLF GLVSOD\ RI QRGHV 3U7 DQG VWRSV 3X7 1RGHV and VWRSV The graphic parameters are used to control the display of nodes and stops. Nodes can be displayed with their number, their abbreviated name, as a circle or square or as an AddValue. In addition, a Stop symbol can be selected or created for stops. Attributes of nodes or stops (e.g. number of line trips, boarding and alighting passengers) can be displayed as bar charts or pie charts. Furthermore, graphic parameters for PrT-node flows and for stop catchment areas can be specified.
12-6
Nodes and stops
GRAPHICS PARAMETERS
3DUDPHWHUV IRU QRGHV DQG VWRSV
The following graphic parameters are identical for nodes and stops and can be selected individually. /D\HU 6WRSV RU /D\HU 1RGHV activates the graphic display. When this option is disabled, stops / nodes are not displayed. For DFWLYH QRGHVVWRSV set &RORU and 'UDZ parameters per global node type (e.g.: 0* includes 00-09) or the same for all node types: set $OO active. Node type can be disabled with 'UDZ o; this setting is type-specific and also works for $OO . For SDVVLYH QRGHVVWRSV VHOHFW FRORU, if 'UDZ is enabled 'LVSOD\LQJ QRGHV DQG VWRSV Select identifier and size in [mm] (for plots): Screen display = text size [mm] * text scaling factor.
12-7
GRAPHICS PARAMETERS
Nodes and stops
2YHUODSSLQJ ODEHOV This option is only relevant if 1DPH &RGH or 1XPEHU is selected as a label. VISUM first draws the node with the lowest number n, then n+1, n+2 ... up to the highest NodeNo.: when this option is active, a node can be overlapped by any node with a higher NodeNo. in the network display (including stops). Overlaps depend on the number of displayed nodes in the current network section. For plot display the scale and text size are considered, and for the screen the text enlargement factor is also considered.
'LVSOD\ LVRODWHG When this option is not active, only those nodes are displayed graphically where at least one link begins or ends. Recommendation: activate this option for INSERT NODE.
The graphic parameters for nodes and stops are almost the same. Node labels: alphanumeric: 1R 1DPH &RGH or an $GG9DOXH graphic: FLUFOH or VTXDUH, for stops also V\PERO. Additional option for labeling stops in the network: FLUFOH and VTXDUH can be used to obtain a labeled stop symbol; the letter and its color are user-defined. Node labels are only displayed if size > 0.00 mm. Selected nodes can be displayed, for example, with their number, and selected stops with their name.
Only for 'LVSOD\ PDMRU IORZ PrT nodes When this option is active, the major flow of marked nodes is displayed at the respective nodes. To display the major flow at all nodes in the network, activate 'UDZ PDMRU IORZ under %DVLF in the GRAPHIC PARAMETERS menu. Only for &URVVHG VWRSV ZKHQ D VLQJOH OLQH LV VHOHFWHG PuT Stops When a subline is selected, the stops crossed by that subline are marked with a preset identifier.
12-8
Nodes and stops
GRAPHICS PARAMETERS
&KDUW SDUDPHWHUV IRU QRGHV DQG VWRSV
G
1RGH or VWRS FKDUW
The chart parameters control the display of up to 5 node attributes. &KDUW SDUDPHWHUV IRU QRGHV DQG VWRSV
'UDZ Enable/disable chart display. 'LVSOD\ PRGH RI WKH VHOHFWHG DWWULEXWHV 3LH (scaling per pie chart with max. 5 parts) or %DUV (next to each other or overlapping, scaling per attribute). &KDQJH WKH VHTXHQFH RI EDUV Place the cursor over one of the line handles 1-5. Click and hold the left mouse button. Drag the selected parameter line to the preferred position. When 'UDZ in the 6WRS FKDUW dialog is not checked, the attributes currently set under 1RGH FKDUW are displayed for all active nodes, including stops.
G G
12-9
GRAPHICS PARAMETERS
Nodes and stops
%DUV GLVSOD\ %DUV /DEHOV Activate 'UDZ Enter VL]H in mm Select FRORU from palette or confirm same color as bar
Labels which are longer than the bar length are displayed above the bar. Labels which are higher than the bar width are not displayed. %DU ZLGWK Width of each bar when parallel (no base), width of bar when base display (overlapping). Select $WWULEXWH for the bar values from list of attributes. To display each attribute: Activate 'UDZ Select &RORU from palette %DVH Base display (bars overlapping). o No base display (bars next to each other). Adapt VFDOLQJ to display value range Enter KHLJKW in mm for max. scaling value Enter URXQGLQJ factor for labels. According to the current dialog settings, the 9ROXPH3U7 attribute with bar width = 15 mm is displayed above the node number. 'UDZ is not active for attribute 1R. The AddValues , are displayed as 3 parallel bars on the base (9RO3U7). The width of the parallel bars on a base results from the current bar width and the number of parallel bars: 15 : 3 = 5 mm.
([DPSOH
12-10
Nodes and stops
GRAPHICS PARAMETERS
3LH GLVSOD\ 3LH
/DEHO (option disabled). 6HOHFW $WWULEXWH YDOXHV for pie chart from the list of attributes. To display each attribute: $FWLYDWH 'UDZ 6HOHFW &RORU from palette (QWHU URXQGLQJ factor for labels. HQWHU WKH PD[ SLH DUHD for max. scaling factor in [mm]. VHOHFW 6FDOLQJ for the displayed range of values.
12-11
GRAPHICS PARAMETERS
Nodes and stops
1RGH IORZ SDUDPHWHUV IRU 3U7 QRGHV
9ROXPH W\SH 1RGH IORZV Select the attribute of turning relations to be displayed: Vol[Veh]-PrT turning relation AddVal1, 2 or 3 difference of volume and TurAddVal1, 2 or 3 1RGHV 6FDOLQJ Enter IURP and WR YDOXH. 0D[ EDU ZLGWK: for values ToValue; display of values < ToValue and FromValue with proportional bar width. For a clear graphic display, it is recommended to select the scaling of the node flow bar according to the respective settings for the link volume display. /DEHOV GUDZ: node flow display ZLWK labels. FRORU: select label color. VL]H: text size for node flow labels [mm]. For node flow displays with labels and text size > 0 mm, labels can be switched on/off in the 1RGH IORZ dialog (GRAPHICS - NODE FLOW menu) for every node flow plan or for every text block.
Nodes and stops
GRAPHICS PARAMETERS
&XW D OLQN Switch off base network display within node flow radius. o Switch on base network display within node flow radius. 7H[W FRYHUV YROXPH EDUV Text block overlaps link volume bars. Advisable if volume bars on /D\HU page were switched off. o Text block is displayed above or below link volume bars.
0XOWLSO\ E\ Multiply volume values per turning relation by specified factor. Only applies to label display. Bar widths are not adjusted, internally VISUM uses the actual values. 5RXQG Round the volume values for every turning relation. Only applies to label display. Bar widths are not adjusted, internally VISUM uses the actual values. If 5RXQG ! the sum of the node flow volumes must not necessarily be identical to the rounded link volumes. 'LVWDQFH WH[WV Line spacing of turning relation values in individual text block in % of current text size. Does not affect the distance between the sum and the relevant reference level (link or volume bar). The current text enlargement factor is not considered here. &RORU: Select color and shading for turning relation bars for positive and negative values. ZLWK DUURZ: Display node flow ZLWK direction arrows.
%DUV
&LUFOH 'UDZ: node flow display ZLWK enclosing circle (size = current radius). &RORU: Select circle color. 5DGLXV The radius entry is the default value for all node flows. The value entered last is used as the new default value. A modification to the radius is only considered for newly marked nodes.
12-13
GRAPHICS PARAMETERS
Nodes and stops
&DWFKPHQW DUHD SDUDPHWHUV IRU 3X7 VWRSV

6WRSV FDWFKPHQW DUHDV *UDSKLF GLVSOD\ RI 3X7 VHUYLFH TXDOLW\ LQ WKH QHWZRUN The catchment area of each stop is displayed as a circle with a specified radius, color and shading. Beside a radius in [m], other attributes for the stop circle diagram can be used. The radius is then specified by the attribute value.
Radius from length
Radius from attribute
12-14
Nodes and stops
GRAPHICS PARAMETERS
&DWFKPHQW DUHDV: switch display of stop circle diagrams on. $FWLYDWH UDGLXV IURP OHQJWK to display catchment areas; the radius must be entered in [m]. $FWLYDWH UDGLXV IURP DWWULEXWHs to display an attribute per stop with proportional circle area. A multiplication factor can be specified for the attribute values for the graphic display. Select FRORU and pattern, specify OD\HU, activate GUDZ Enter UDGLXV in [m], if UDGLXV IURP OHQJWK is active. Select DWWULEXWH and possibly subattribute, if UDGLXV IURP DWWULEXWH is active. The attribute value is converted into [m]. Specify IDFWRU for multiplication with attribute values.
Set parameters per JOREDO VWRS W\SH or for $OO
12-15
GRAPHICS PARAMETERS
Turning relations
7XUQLQJ UHODWLRQV
Graphic parameters for the display of valid turning relations in the node. 7XUQLQJ UHODWLRQV
/D\HU 7XUQLQJ UHODWLRQV activates the graphic display. When this option is disabled, turning relations or turning prohibitions, major flows and U-turns are not displayed. For the turning relations, turning prohibitions, U-turns and major flows in the network: select color and line type, enable 'UDZ , set the $UURZKHDG size in [mm], select a 7UDQVSRUW V\VWHP or $OO transport systems (not for major flows).
12-16
Zones, global zones, areas
GRAPHICS PARAMETERS
=RQHV JOREDO ]RQHV DUHDV
*UDSKLF GLVSOD\ RI ]RQHV JOREDO ]RQHV DQG DUHDV =RQHV JOREDO ]RQHV DUHDV The graphic parameters are used to control the display of zones, global zones and areas in the network . Zones and global zones can be displayed with their name or their short ID, areas can be displayed with their number or name. number,
Additionally, specify if and how zonal boundaries are to be displayed.
G
=RQHV
The same parameters can be used both for displaying zones and global zones. Note: Areas cannot be displayed in the form of charts.
12-17
GRAPHICS PARAMETERS
3DUDPHWHUV IRU ]RQHV JOREDO ]RQHV DQG DUHDV
$UHDV
The following graphic parameters are the same for zones, global zones and areas and can be selected individually. /D\HU =RQHV*OREDO ]RQHV$UHDV activates the graphic display. When this option is disabled, zones/global zones/areas are not displayed. For DFWLYH ]RQHVJOREDO ]RQHVDUHDV set &RORU parameters individually for each type or the same for all node types: check $OO . and 'UDZ
A zone type can be disabled with 'UDZ o; this setting is typespecific and also works for $OO . For SDVVLYH DFWLYH ]RQHVJOREDO ]RQHVDUHDV: set color, if 'UDZ is active ; if 'UDZ o is not active, no identifiers are displayed.
A network object of a type, for which 'UDZ o is disabled, is not displayed even if 'UDZ and VDPH FRORU IRU DOO are selected for active network objects.
12-18
GRAPHICS PARAMETERS
*UDSKLF GLVSOD\ RI ]RQHV JOREDO ]RQHV DQG DUHDV Select identifier and size in [mm] (for plots): Screen display = text size [mm] * text scaling factor. 2SWLRQ OLVW Select identifier for label. Zones / global zones: name, code, number areas: name or number 7H[W VL]H Size if labels in [mm]. 7H[W FRORU Select from palette if the option o &RORU is unchecked. /DEHO ZLWK IUDPH the label is framed; DUHD FRORU
VHOHFWHG ]RQHV JOREDO ]RQHV DUHDV Select identifier, enter text size in [mm] Only for 'UDZ SRO\JRQ zones existing polygons are displayed. and global zones
&KDUW SDUDPHWHUV IRU ]RQHV DQG JOREDO ]RQHV
All attributes can be displayed as a pie or bar chart at the coordinates of the identifier. For this, the same parameters as for nodes and stops are used.
12-19
GRAPHICS PARAMETERS
Connectors
&RQQHFWRUV
Graphic parameters for the display of connectors from and to zones. &RQQHFWRUV
/D\HU &RQQHFWRUV activates the graphic display. When this option is disabled, connectors are not displayed.
12-20
Connectors
GRAPHICS PARAMETERS
For DFWLYH FRQQHFWRUV Set &RORU and 'UDZ parameters for PrT+PuT: displaying connectors, which are valid for both PrT and PuT. PrT: PuT: displaying connectors, which are valid for both PuT only. displaying connectors, which are valid for PuT only.
For SDVVLYH FRQQHFWRUV Select color and line type, if 'UDZ is enabled $UURZKHDG Displays all drawn connector as arrows, when arrowhead > 0 mm.
12-21
GRAPHICS PARAMETERS
Links
/LQNV
The following layers can be switched on and off to display the graphic link network volume: basic network (uncharged network), link bars (link attributes, e.g. volumes), labels. The link drawing sequence can be defined depending on the link type by means of link type layers. Link type layers are defined separately for the basic network and the link bars.
G
12-22
If volume bars are displayed along the link, the basic network display can be switched off.
Links
GRAPHICS PARAMETERS
%DVLF OLQN QHWZRUN
/LQNV
/D\HU %DVLF QHWZRUN activates the graphic display. When this option is disabled, the link network is not displayed. $FWLYH OLQNV The parameters can be specified for DOO link types or for every JOREDO W\SH: For every JOREDO W\SH: select FRORU OLQH WKLFNQHVV and OLQH W\SH, also set 'UDZ and /D\HU (order), or for DOO global types: select FRORU OLQH W\SH OLQH WKLFNQHVV and activate $OO (the active types are drawn). 3DVVLYH OLQNV can also be switched on and off in the /D\HU dialog; select FRORU OLQH WKLFNQHVV and W\SH, if /D\HU is active .
2QHZD\ URDGV When 'UDZ is active, then one-way roads are displayed as arrows, when arrowhead > 0.0 mm. Select transport system if necessary. 3ODQQHG OLQNV The PlanNr attribute is used to specify whether a link is a planned link (e.g. planned bypass). Here, the bar display for planned links can be selected.
12-23
GRAPHICS PARAMETERS
Links
In order to label the basic link network, select a link attribute (bar width 0.0 mm) in the $WWULEXWHV dialog and the font size etc. in the /DEHOV dialog.
/LQN EDUV
%DUV
/D\HU /LQN EDUV must be active, so that the parameters from the dialogs $WWULEXWHV and /D\HUV can be considered for the screen display. Otherwise, only the basic link network is displayed. &URVVVHFWLRQ YDOXHV Bars and labels are displayed as a sum of both directions. Bars and labels are displayed separately for the two directions. 'LVWDQFH EHWZHHQ EDUV Enter the distance between bars in [mm].
12-24
Links
GRAPHICS PARAMETERS
$WWULEXWHV PXOWLSOH EDUV
1 5 volume bars for the graphic display of link attributes can be defined. The first activated bar is drawn directly on the link, then the other bars are drawn. Changing the bar sequence: Place the cursor over one of the line handles 1-5. Click and hold the left mouse button. Drag the selected parameter line to the required position. Standard: unified bar color. Types: different bar color for every link type. Classes: bar color depends on user-defined class. Lines: different bar color for each PuT-TSys, main line, line, subline.
3UHVHQWDWLRQ
$WWULEXWH Select a link attribute to be displayed as a bar. If necessary, select a sub-attribute, e.g. for Volume-TSys. For attributes with the subattribute time interval (7,) it is necessary to define a time filter for the graphic display (TOOLS - FILTERS - TIME INTERVAL menu). The values are calculated from the line trips which depart from the origin stop within the selected time interval.
12-25
GRAPHICS PARAMETERS
Links
6FDOLQJ PLQ PD[ Usually the UDQJH RI WKH VFDOH (min - max) for bar width should be adapted to the displayed value range of the selected attribute: For links with DWWULEXWH YDOXH )URP6FDOLQJ no bar is displayed, only the label with the attribute value For links with DWWULEXWH YDOXH ! 7R6FDOLQJ, the bar is displayed with the max. width, labeling is correct. For constant bar width: )URP6FDOLQJ 0LQ9DOXH.
6FDOLQJ IRU QHJDWLYH YDOXHV For bars with attribute values < 0.0 the scaling range must be adapted: the maxValue is absolute, i.e. for values between -200 and +100 the maxValue = 200 must be entered. :LGWK Enter bar width in [mm]. If EDU ZLGWK = 0 mm, no bar is displayed at the link but only a label with the attribute value, if labeling is active.
6FDOLQJ FURVVVHFWLRQ YROXPHV A cross-section volume to be displayed is automatically divided by two, so that half of the cross-section value is the upper limit for scaling. For example, if the scaling range is 1-1000 and the bar width is 10 mm, a cross-section volume of 2000 is displayed with a volume of 1000 on each side and a bar width of 10 mm. Cross-section volumes of one-way roads (roads closed in one direction for all transport systems) are labeled GLUHFWLRQEDVHG in the bar. 7/ Specify the text level . The lowest level is initially discarded if there is not enough room along the link for the horizontal label display. 5RXQG Attribute values can be displayed as rounded bar labels (only applies to network display, internally VISUM uses the exact values). &RORU Specify color and pattern, positive and negative values.
12-26
Links
GRAPHICS PARAMETERS
Display 7\SHV
%DU FRORU E\ OLQN W\SH
With Bar color by link type, a specific bar color and pattern can be defined for each link type. The rounding value applies to the labels of all bars.
12-27
GRAPHICS PARAMETERS
Links
Display &ODVVHV
8VHUGHILQHG DWWULEXWH YDOXH FODVVHV IRU YROXPH EDUV
With Bar color by class, the attribute values can be classified. For each class, a bar color and pattern as well as a specific class value can be specified. /LPLW Upper limit for the class. &RORU Color of the class. &O9DOXH Optional value which can be displayed as class identifier. 5RXQG Rounding value of the class (only for labels, internally VISUM always uses the exact values).
12-28
Links
GRAPHICS PARAMETERS
5RXQGLQJ IRU DOO Unified rounding value for all classes, if this option is active. %DU ODEHOV with attribute value or class limit = max. attribute value per class (ascending) class value (optional)
*UDSKLF GLVSOD\ DQG FODVV ODEHOV ZLWK DWWULEXWH YDOXH
ZLWK FODVV OLPLW
With this setting the class > should not be used, but a value > max. attribute value should be specified as the class limit or VISUM will use the current max. attribute value of the class > as the class limit. ZLWK FODVV YDOXH
For bar display, the range of the scale must be adapted to the current class values.
12-29
GRAPHICS PARAMETERS
Links
Display /LQHV
3X7 OLQH EDUV With Line bar, the attribute values can be differentiated according to the following display levels. transport systems, main lines, lines, sublines.
For the calculation of attribute values and their graphic display as bars only the activated list entries and further Multi Select specifications are considered.
12-30
Links
GRAPHICS PARAMETERS
0XOWL 6HOHFW Draw
0XOWL VHOHFW GUDZ
For DOO sublines the 'UDZ option is set when the selected filter rules apply. With the option 212)) OLNH OLQH etc. the 'UDZ option of the corresponding line can be adopted.
12-31
GRAPHICS PARAMETERS
Links
0XOWL 6HOHFW Color
&RORU EXWWRQ
RQH FRORU The selected color is applied to all sublines which comply with the defined filter rules. 6KDGH FRORU XVH VWHS ZLGWK A color is applied to all sublines which comply with the defined filter rules. The color results from the selected color (= initial value) and the step width. The step width defines the number of color fields with ascending color number, starting from the initial value. &RORU 76\V 0DLQ OLQH /LQH FRORU
The color specified in the line dialog is applied to all sublines which comply with the defined filter rules.
12-32
Links
GRAPHICS PARAMETERS
'LIIHUHQFH GLVSOD\
$WWULEXWHV 'LIIHUHQFH GLVSOD\
Comparison of two attribute values (plus/minus) and graphic display of the basic value as well as the difference as Diff+ and Diff- with a bar. The displayed volume bar represents the common basic value range and the resulting difference between the compared attributes. 3OXV: select link attribute or subattribute, if necessary. 0LQXV: select link attribute or subattribute, if necessary. 6FDOLQJ: adapt scaling range to displayed value range (Plus), VSHFLI\ PD[ EDU ZLGWK in [mm]. 5RXQG: specify rounding factor. %DU: select FRORU and SDWWHUQ for %DVLF 9RO 'LII and 'LII. o 'UDZ The basic volume, i.e. the common value range of the compared attributes is neither considered in the displayed value range nor is it displayed graphically, only the differences are displayed.
When the option &ODVVLILFDWLRQ is active, value classes can be defined and displayed differently for the resulting Diff- and Diff+ values. See Chapter 12.7.2: &ODVVHV display.
12-33
GRAPHICS PARAMETERS
Links
/D\HUV
/D\HUV
12-34
Links
GRAPHICS PARAMETERS
7\SH For every link type it is possible to specify whether the link bar is to be drawn and in what order. &ODVVLI\ DWWULEXWH YDOXHV For the class limits of a bar 1-5 it is possible to specify whether the link bar is to be drawn and in what order.
12-35
GRAPHICS PARAMETERS
Links
/DEHOV
/DEHOV
/D\HU /LQN ODEHOV activates the graphic display. When this option is disabled, links are not labeled. A text size > 0.0 mm must be defined. 6HOHFWLRQ Horizontal Vertical Vertical with sum 7H[W VL]H Enter text size in [mm]; when the text size is 0.0 mm, no link labels are displayed. 7H[W FRORU 6HOHFW WH[W FRORU or FRORU YRO EDU FRORU recommended for multiple bars. )UDPH FRORU 6HOHFW )UDPH FRORU. For labels without frames select White (palette). /DEHO ZLWKLQ YROXPH EDU o Labels outside bar. Labels within bar.
Links
GRAPHICS PARAMETERS
7LWOH ZLWK WLWOH: label with attribute identifier and value o ZLWK WLWOH: label with attribute value without identifier RQO\ WLWOH: label with attribute identifier, no value. 1R ODEHO LI YDOXH Enter a minimum value as absolute amount 0XOWLSO\ E\ Factor for attribute values (only for labels, internally VISUM always uses the exact attribute value). 'LVWDQFH RI ODEHOV Distance of labels in [mm] to the bar, when o /DEHO ZLWKLQ YROXPH EDU is not active, to the link, when /DEHO ZLWKLQ YROXPH EDU is active. 'LVWDQFH RI YHUWLFDO ODEHOV Specify line spacing in percent of current text size. /DEHO OLQN SRO\JRQV DORQJ ORQJHVW VHFWLRQ (default position for digitized links; reduce text size if necessary, because if text length > section length in the network display, labels are not displayed) or DW RI SRO\JRQ OHQJWK: the link labels are displayed regardless of available space.
Horizontal without title outside bar
Vertical with title within bar
Vertical with sum (only meaningful for same unit)
12-37
GRAPHICS PARAMETERS
PuT Lines
3X7 /LQHV
/LQHV
The graphic parameters for line bars are defined via menu GRAPHICS - PARAMETERS - LINKS - BARS - ATTRIBUTES with /LQHV display (see Chapter 12.7.2). 'UDZ OLQH URXWHV activates the graphic display. When this option is disabled, line routes are not displayed. 6HOHFW PuT line routes can be displayed on 4 levels. For the current selection, all transport systems, main lines, lines or sublines existing in the network are listed. Links which are traversed by several sublines/lines/transport systems are displayed in a neutral color.
12-38
PuT Lines
GRAPHICS PARAMETERS
6ZLWFK JUDSKLF GLVSOD\ RQRII LQGLYLGXDOO\ Draw line routes (select line type and color). o Do not draw line routes. 1HXWUDO FRORU Display links which are traversed by several sublines/lines/transport systems. 0XOWL 6HOHFW Draw
0XOWL 6HOHFW Color
VZLWFK DOO RQ with 'UDZ checked. VZLWFK DOO RII with o 'UDZ unchecked. 212)) OLNH Use corresponding settings.
12-39
GRAPHICS PARAMETERS
PuT Lines
)LOWHUV Select lines/sublines according to attributes: DOO: Select all active lines or sublines etc. 76\V&RGH and 76\V1DPH: Select according to transport system. 1DPH 2S1DPH 9HK1DPH 26WRS&RGH 26WRS1DPH '6WRS&RGH '6WRS1DPH: Enter a full string or a partial string using * as a wildcard. The attributes YDULDQW and GLUHFWLRQ are used to identify a subline, e.g.: %XV 5 (return direction 5 of the variant of the line called %XV). all remaining attributes: select according to value ranges.
After each confirmation with 2. it is possible to enter a further selection criterion (AND link). 'LVSOD\ one color Use one color for all filtered sublines. 6KDGH FRORU XVH VWHS ZLGWK The selected color applies to the first selected line or subline; all other selected lines or sublines automatically receive the following color from the palette, which results in a color shading. &RORU Use the respective color.
12-40
Census points
GRAPHICS PARAMETERS
&HQVXV SRLQWV
/D\HU &HQVXV SRLQWV activates the graphic display. When this option is disabled, census points are not displayed. &HQVXV SRLQWV 'LVSOD\ active census points: select symbol or identifier. 6L]H display size in [mm]. &RORU color for display. SDVVLYH FHQVXV SRLQWV select color, if 'UDZ . ([DPSOH /DEHOV IRU DFWLYH FHQVXV SRLQWV For displaying max. 5 texts per census point activate 'UDZ for each label attribute. select color, size, distance from census point and distance between text fields.
12-41
GRAPHICS PARAMETERS
Census points
&HQVXV SRLQWV FKDUW
The handling of graphic parameters for census point chart is the same as for node chart. 'LVSOD\ PD[ FHQVXV SRLQW DWWULEXWHV DV EDUV For each defined census point attribute, one bar can be displayed. By default, its position is above the census point, but can be moved. Enter KHLJKW in [mm] Display the values ToValue of specified value range are displayed with max. bar height. values < ToValue with proportional bar height; values FromValue: display with bar height = 0 mm. Enter EDU ZLGWK in [mm] Adapt bar width to label size! If no bar label is displayed: either increase width or decrease text size. 6FDOLQJ enter FromValue ToValue depending on the min max attribute values. The uniform value range for all bars maintains proportionality when several bars are displayed.
12-42
Census points
GRAPHICS PARAMETERS
&RORU per attribute: select color / pattern if 'UDZ /DEHOV enter VL]H in [mm]: text, which is higher than the bar width is not displayed. longer than the bar height is displayed above the bar.
Census points AddValues can also be selected as link attribute for the graphic display.
12-43
GRAPHICS PARAMETERS
Flow bundles, isochrones, route search, O-D flows
)ORZ EXQGOHV LVRFKURQHV URXWH VHDUFK 2' IORZV
See Chapter 11: Graphic analyses The relevant graphic parameters are described together with the functionality of the respective function.
12-44
Printing page
GRAPHICS PARAMETERS
3ULQWLQJ SDJH
See Chapter 14: Graphics: Printing, interfaces That chapter contains the relevant graphic parameters for printing or plotting the current network display.
12-45
GRAPHICS PARAMETERS
Fonts
)RQWV
)RQWV
Beside Windows fonts, VISUM offers a simple VISUM font for labels, which enables a particularly fast screen display. In this dialog you can select the font for different layers. 6FUHHQ Use selected Windows font for screen display. o Use VISUM font for screen display. 3ULQWHUV Use selected Windows font for printing. o Use VISUM font for printing. )RQW Modify current setting by selecting layer with left mouse click (colored bar), clicking the &KDQJH IRQW button.
12-46
Fonts
GRAPHICS PARAMETERS
Font
Select font
12-47
GRAPHICS PARAMETERS
Reading/saving graphic parameters
5HDGLQJVDYLQJ JUDSKLF SDUDPHWHUV
6DYLQJ
Saving graphic parameters as graphic parameters file *.gpa (binary format) via 6DYH JUDSKLF SDUDPHWHUV in the FILE menu. With *.ver version file via 6DYH YHUVLRQ in the FILE menu. as a graphic parameters file *.gpa via 2SHQ JUDSKLF SDUDPHWHUV in the FILE menu. With *.ver version file via 2SHQ YHUVLRQ in the FILE menu. 6HOHFWLYH ORDGLQJ If graphic parameters are read from file, the user can select which data are to be read. The option UHDG RQO\ VHOHFWHG SDUDPHWHUV must be active, in order to select parameters by a mouse click.
5HDGLQJ
Reading graphic parameters
12-48
NETWORK-INDEPENDENT GRAPHIC OBJECTS
1(7:25.,1'(3(1'(17 *5$3+,& 2%-(&76
Network-independent graphic objects can improve the clarity of a network by providing additional information, such as graphic texts or borders of areas. In contrast to network objects, network-independent graphic objects are not part of the network model, i.e. they have no influence on the calculations carried out by VISUM. The basic version of VISUM includes the following network-independent graphic objects: clips and texts.
The %DFNJURXQG add-on module additionally includes: legends polygons background objects and static backgrounds.
13-1
Clips
&OLSV
A clip is a rectangular section in the network display on screen which is specified by the user. Within such a section the graphic display can be modified by hiding or displaying individual graphic layers independent of the global network display. Clips, therefore, highlight sections of the graphic display in order to emphasise particular facts.
A maximum of 3 clips can be set. Clips may partly overlap each other. Clips can only be edited individually in SINGLE SELECT mode.
,QVHUW D FOLS

Activate INSERT mode. Activate CLIPS object.
Specify clip section: Drag pointer while pressing mouse button to create rectangle. Release mouse button at desired diagonal corner. Display or hide graphic layers in the clip via Menu GRAPHICS PARAMETERS -/D\HU.
13-2
Clips
/D\HU GLDORJ All network-dependent DQG network-independent graphic objects are listed in the dialog box which can be displayed or hidden within the currently set clips.
In this example all object types - except zones - for the on-screen network display are switched on (x = Draw layers). The display within the clips is only set for background node flows, objects and texts.
Network objects and network-independent graphic objects are only drawn in clips if they are also drawn in the total network display on screen. The layer definition applies to all clips which are set.
13-3
Clips
6HOHFW D FOLS

Activate SINGLE SELECT mode and CLIPS object.
Select with mouse click on clip. Then call up the desired editing command.
'HOHWH D FOLS

Activate SINGLE SELECT mode and CLIPS object.
Select with mouse click on clip. Shortcut <Del> or 'HOHWH in the EDIT menu
To delete several clips they must be deleted one after the other.
(GLW D FOLS

&OLS FRRUGLQDWHV
The position and the size of the section are specified during insertion. The coordinates of the current clips are inserted automatically by VISUM as graphic parameters (Menu GRAPHICS -PARAMETERS - %DVLF):
An existing clip cannot be edited. If the clip section or the position are to be modified, the clip must be deleted and then reinserted. The selection of layers which are drawn in the clips remains the same.
13-4
Clips
$GDSW FOLS VHFWLRQ DV FXUUHQW ZLQGRZ RQ VFUHHQ

The display area on the screen can be adapted to the clip section by specifying a window. Specify window.
Drag pointer to any corner of selected clip; the corner transforms into a red circle. Hold down left mouse button. Drag pointer to the diagonally opposite corner; the corner transforms into a red circle. Release mouse button.
The clip now becomes the display area. The VISUM window adapts automatically to this area.
Return to the previous section of the network display by activating the symbol button (Reset to previous window).
13-5
Texts
7H[WV
Texts serve to additionally label network displays. Two text types can be distinguished: %DFNJURXQG WH[WV: texts which are inserted into the network display or into a clip section. /HJHQG WH[WV: Texts which are inserted into a legend (only with %DFNJURXQG addon module; see chapter 13.6).
Graphic texts are network-independent graphic objects and therefore must be distinguished from: Labels of network objects (set via Menu GRAPHICS - PARAMETERS) and Labels for plot output (Headline and Comment, set via Menu GRAPHICS PARAMETERS 3ULQW SDJH.
13-6
Texts
,QVHUW D WH[W

Activate INSERT mode. Activate TEXTS object.
Specify position of text on screen display by marking the central point with a mouse click. 7H[W SDUDPHWHUV GLDORJ
7H[W Enter text into input field. 6L]H Enter text size in [mm]. &RORU Select label color from color palette. $QJOH Specify rotation angle for the rotation of the text block in []. )L[ SRLQW Specify central point of text block. Centring specifies: the insertion point of the text block at the pointer and the pivot for a possible rotation of the text block. 3RVLWLRQ co-ordinates of the point marked by mouse-click.
13-7
Texts
6HOHFW D WH[W

Activate SINGLE SELECT mode and TEXTS object.
Select with mouse click on text block. Then call up the desired editing command.
'HOHWH D WH[W

Select with mouse click on text block. Shortcut <Del> or 'HOHWH via EDIT menu
$OO legends and background texts are deleted in MULTI SELECT mode with Shortcut <Del> or 'HOHWH in the EDIT menu.
(GLW D WH[W

1st mouse click: Select text block to be edited. With pressed mouse button: Specify new text position by shifting (horizontal or rotated orientation remains unchanged). 2nd mouse click: Rotate text block with mouse click on one of the four "handles" and drag while pressing mouse button; the pivot is the central point marked during insertion.
Double-click or press <Enter>: Call up "Text parameters" dialog.
13-8
Texts
3URFHVVLQJ DOO WH[WV

'HOHWH DOO WH[WV
Activate MULTI SELECT mode and TEXTS graphic object.
Delete all background and legend texts with Shortcut <Del> or 'HOHWH in the EDIT menu. 'HOHWH WH[WV GLDORJ
6HOHFWLRQ 'HOHWH background texts: all graphic texts in the network display are deleted. 'HOHWH OHJHQG WH[WV: all graphic texts in the legend are deleted. If the option is deactivated, the respective text types are not deleted.
13-9
Texts
(QODUJH RU UHGXFH VL]H RI DOO WH[WV

Activate MULTI SELECT mode and TEXTS graphic object.
Call up (QODUJH5HGXFH WH[WV command: 0RGLI\ in the EDIT menu Shortcut <Enter> or Double-click mouse. (QODUJH5HGXFH WH[WV GLDORJ
2SWLRQV: 0RGLI\ EDFNJURXQG texts: all texts in the network display are scaled. 0RGLI\ OHJHQG WH[WV: all texts in the legend are scaled.
(QODUJHPHQW IDFWRU Specify a factor for scaling the text size.
13-10
Texts
5HDG DQG VDYH WH[WV

Texts can be saved as one of two file types (as background texts or as legend texts) in *.txt files in ASCII format. In addition to this, they are saved along with the graphic parameters in *.gpa-files.
0HQX),/( 6$9(7H[WV 6DYLQJ WH[WV WR ILOH GLDORJ
0HQX),/( 23(17H[WV 5HDGLQJ WH[W ILOH GLDORJ
7H[WV IURP Background WH[WV: save background text file.
7H[WV LQWR background: read background texts.
/HJHQG WH[WV: save legend text OHJHQG: read legend texts. file.
13-11
Backgrounds
%DFNJURXQGV
VISUM backgrounds are graphic files of the %DFNJURXQG add-on module which contain area or network information and are loaded into VISUM with fixed coordinates and are displayed with a traffic network. A graphic background can complement a road network display with more content by putting, for example, a zoning plan or city map "into the background". It is possible to put several backgrounds on top of each other. Backgrounds are managed in the same way as objects (see chapter 13.4) in a VISUM-specific graphic format and can be exchanged with other graphics programs via a DXF interface. This makes it possible, for example, to import graphic files from geographical information systems (GIS). In contrast to objects, backgrounds are opened with fixed co-ordinates and, therefore, can neither be moved in the network display nor can their size be changed. This means that the scale of background co-ordinates has to be adapted to a VISUM network display.
,QVHUW D EDFNJURXQG

Activate INSERT mode. Activate BACKGROUNDs object.
Open background file: Click mouse anywhere in network display. Select *.hgr-file (filename/directory). The size of background files is unrestricted. The number of background files which can be displayed with one network is unlimited. VISUM only saves *.hgr files in version and graphic parameters files by reference. For this reason, referenced *.hgr files should not be deleted, renamed or moved to a different directory.
13-12
Backgrounds
([DPSOHV VISUM network display without background:
VISUM network display with background:
See Chapter 14: Import of DXF grafics files and transformation of coordinates.
13-13
Backgrounds
6HOHFW D EDFNJURXQG

Activate SINGLE SELECT mode and BACKGROUNDS object.
Press right-hand mouse button somewhere in the network display to call up list box. 6HOHFW EDFNJURXQG GLDORJ List box selection: Select the desired background by mouse-click.
Then call up the desired editing command by pressing the relevant button in the dialog box.
'HOHWH D EDFNJURXQG

Mouse click in network display to select background. 6HOHFW EDFNJURXQG GLDORJ Mark the background to be deleted in the list box Press 'HOHWH button.
Only one background can be marked at a time. The selected background is deleted from the network display without deleting the corresponding *.hgr background file from the hard disk.
13-14
Backgrounds
(GLW D EDFNJURXQG

Mouse click on network display to select background. 6HOHFW EDFNJURXQG GLDORJ
8S DQG 'RZQ EXWWRQV modify order in which backgrounds are drawn from top to bottom. &RORUV EXWWRQ call up "Background color assignment" dialog.
13-15
Backgrounds
%DFNJURXQG FRORUV DVVLJQPHQW GLDORJ &RORUV button
/LVW ER[ select individual layers of background (sections drawn with one color) and specify new color assignment as pen number (left value: RULJLQDO FRORU; right value: QHZ FRORU). 6HW LQ ZKLWH GLDORJ: Background with white fill pattern (useful for graphics with detail within frame to cover other graphic objects) o transparent background.
transparent
set in white (filled)
2ULJLQDO FRORU optical display of original color. 1HZ FRORU select new color from color palette.
6DYLQJ EDFNJURXQG ILOHV

In VISUM, individual backgrounds or objects cannot be saved. It is, however, possible to save the entire current network display as a plot file in hgr format (for a description of this function see chapter 14). A *.hgr plot file thus includes all network objects and network-independent graphic objects of the network display. Opening a *.hgr plot file as a background object can be used to include the contained network display as a map section in a different network display. A detailed map section of the town centre in any size, for example, can be integrated into the display of the total link network of a city.
13-16
Objects
2EMHFWV
VISUM "objects" are graphic files of the %DFNJURXQG add-on module which - in contrast to "fixed" backgrounds - can be inserted in any size, anywhere in a VISUM network display, i.e. position and size are determined by virtual, modifiable coordinates. Objects facilitate graphic design, by making it possible, for example, to insert traffic signs, company logos or direction arrows etc.. Two object types can be distinguished: %DFNJURXQG REMHFWV: objects which are inserted into the network display or into a clip section. /HJHQG REMHFWV: Objects which are inserted into a legend.
*UDSKLF LPSRUW LQWHUIDFH

VISUM offers a graphic import feature for the following formats: By default, VISUM reads VISUM background files, Windows bitmaps and Windows metafiles. With the help of the $SSOH Freeware 4XLFN7LPH-3LFWXUH9LHZHU, it is possible to import all formats supported by this software.
Graphics of this type can be imported into the VISUM network view by inserting file objects or pasted from the clipboard.
13-17
Objects
The following table is an overview of the most important graphic formats, which can be imported into VISUM: )LOH W\SH 'HVFULSWLRQ
Standard graphic import of the additional module %DFNJURXQG: BMP (DIB) "%LWPDS": pixel-based Windows standard format HGR "%DFNJURXQG": internal vector-based VISUM graphic format, which can also be generated by means of the ';) LQWHUIDFH from a DXF file (AutoCad format) ":LQGRZV 0HWDILOH": both vector- and pixel-based Windows graphic format (standard and HQKDQFHG format).
WMF (EMF)
Additional EDFNJURXQG graphic import (with 4XLFN7LPH): GIF JPG PNG "*UDSKLFV ,QWHUFKDQJH )RUPDW: pixel-based standard format by &RPSXVHUYH for internet applications. "-RLQW 3KRWRJUDSKLF ([SHUWV *URXS": standard pixel-based format for internet applications developed by an ,62 experts group "PRUWDEOH 1HWZRUN *UDSKLFV: license-free pixel-based format for internet applications, developed by the :RUOG :LGH :HE &RQVRUWLXP (:&) to replace GIF and JPG "3KRWRVKRS": popular pixel-based format by $GREH for professional image processing on PC "7DJ ,PDJH )LOH": pixel-based standard format by $OGXV & 0LFURVRIW for DTP and scanning software "7DUJD": pixel-based format by 7UXHYLVLRQ for professional image processing on Workstations Beside the formats described in the table above, one should also mention such less popular formats as 6*, 6LOLFRQ *UDSKLFV ,PDJH) and PCT (0DFLQWRVK 3LFWXUH). 4XLFN7LPH is available from ZZZDSSOHFRP TXLFNWLPHGRZQ ORDG. After installing QuickTime, just restart VISUM, so that it can read the formats supported by 4XLFN7LPH .
PSD TIF TGA
13-18
Objects
,QVHUW REMHFW IURP ILOH

Activate INSERT mode. Activate OBJECTS object.
Mouse click anywhere in network display. Select graphic file (filename/directory). Mark bottom left corner with mouse click left in network display for object to be inserted. Expand window to the top right while holding down mouse button. In this way, the position (fixed point) and the maximal extension (per direction) are specified in the network display. The proportion of length and width of the respective expanded window is determined by the virtual object co-ordinates and cannot be modified during opening. Objects can be placed both into the network display and into legends and clips (Note: switch on /D\HUV. VISUM only saves graphic files in version and graphic parameters files by reference. For this reason, referenced *.hgr files should not be deleted, renamed or moved to a different directory.
13-19
Objects
,QVHUW REMHFW IURP FOLSERDUG
G
8
3UHUHTXLVLWH The grafics image needs to be copied to the clipboard. Activate OBJECTS object. EDIT Menu INSERT FROM CLIPBOARD Mouse click anywhere in network display. Mark bottom left corner with mouse click left in network display for object to be inserted. Expand window to the top right while holding down mouse button.
VISUM saves the complete path/filename for objects inserted from file. Graphic images inserted from clipboard are saved with the version or graphics parameter file, which enlarges those files significantly.
6HOHFW DQ REMHFW

Activate SINGLE SELECT mode and OBJECTS object.
Select with mouse click on object. Then call up the desired editing command.
13-20
Objects
'HOHWH DQ REMHFW

Select with mouse click on object. Shortcut <Del> or 'HOHWH in the EDIT menu $OO background and legend objects are deleted in MULTI SELECT mode with Shortcut <Del> or 'HOHWH in EDIT menu.
&RS\ DQ REMHFW

Select with mouse click on object Shortcut <F9> or &RS\ in the EDIT menu. Mark position in network display with mouse click for object to be inserted.
0RGLI\ REMHFW SRVLWLRQVL]H

First mouse click: Select object to be edited. Specify new position by moving object while holding down mouse button. Rotate object (Drag "rotation handle" while holding down mouse button). Enlarge or reduce object size (drag one of the four corners of the object in the desired direction while holding down mouse button). The proportions of the sides are preserved. Shrinking and extending is not possible.
Second mouse click:
13-21
Objects
0RGLI\ FRORU DVVLJQPHQW RI DQ REMHFW

Select object to be edited. Double-click mouse or press <Enter>: Call up "%DFNJURXQG FRORU DVVLJQPHQW (see chapter 13.3.4).
'HOHWH DOO REMHFWV

Activate MULTI SELECT mode and OBJECTS graphic object.
Remove all background and legend objects from the network display with Shortcut <Del> or 'HOHWH in the EDIT menu. 'HOHWH EDFNJURXQG REMHFWV GLDORJ
6HOHFWLRQ: 'HOHWH background objects: all objects in the network display are deleted. Delete legend REMHFWV: all objects in the legend are deleted. If option is deactivated, the corresponding object types are not deleted.
13-22
Objects
6\PERO OLEUDU\

In conjunction with the %DFNJURXQG add-on module, a palette of more than 150 *.hgr files is provided by PTV system. These files consist of pictograms, logos, and traffic signs, and can be integrated into the current network display at any position and in any size.
13-23
Objects
13-24
Objects
13-25
Objects
13-26
Objects
13-27
Objects
13-28
Objects
13-29
Polygons
3RO\JRQV
The polygons of the %DFNJURXQG add-on module are a type of graphic object which facilitate the free design of drawings. Polygons can be edited in many ways: Drawing lines or areas Choice of color Position of lines and line types Patterns for areas.
&UHDWH D SRO\JRQ

Activate INSERT mode. Activate POLYGONS object.
5HFWDQJOH Expand rectangle by dragging diagonally while holding down mouse button. )UHHO\ GHILQHG SRO\JRQ RSHQFORVHG Hold down <Ctrl> key: First mouse click: specify starting point of line in network display. Move pointer: drag line. Further mouse clicks: specify line course with intermediate points. After releasing <Ctrl>-key: Specify end point of line with last mouse click.
13-30
Polygons
3RO\JRQ SDUDPHWHUV GLDORJ
3RO\JRQV &ORVHG SRO\JRQ: create SRO\JRQ or UHFWDQJOH by specifying color, pattern and distance. 2SHQ polygon: create OLQH by specifying color and line type. &RORU ILHOG Call up dialog boxes "Select pattern, distance of lines and color " for closed polygons (see below). "Select line type and color" for open polygons. by clicking mouse. 6HOHFW SDWWHUQ GLVWDQFH RI OLQHV DQG FRORU IRU FORVHG SRO\JRQV
thin/thick line thin: dotted line? Select fill pattern for distance > 0.0 mm
Polygons can be placed into the network display and into legends and clips (Note: switch on /D\HUV). VISUM saves polygons along with the graphic parameters.
13-31
Polygons
6HOHFW D SRO\JRQ

Activate SINGLE SELECT mode and POLYGONS object.
Select with mouse click on polygon. Then call up the desired editing command.
'HOHWH D SRO\JRQ

Select with mouse click on polygon Shortcut <Del> or 'HOHWH in the EDIT menu $OO background and legend polygons in the network display are deleted in MULTI SELECT mode with Shortcut <Del> or 'HOHWH in the EDIT menu.
&RS\ D SRO\JRQ

Select with mouse click on polygon Shortcut <F9> or &RS\ in the EDIT menu. Mark position in network display with mouse click for polygon to be copied.
13-32
Polygons
'HOHWH DOO SRO\JRQV

Activate MULTI SELECT mode and POLYGONS graphic object.
All background and legend polygons are deleted with Shortcut <Del> or 'HOHWH in the EDIT menu. 'HOHWH EDFNJURXQG SRO\JRQV GLDORJ
6HOHFWLRQ: Delete EDFNJURXQG SRO\JRQV: all polygons in the network display are deleted. 'HOHWH legend SRO\JRQV: all polygons in the legend are deleted. If option is deactivated, the corresponding polygon types are not deleted.
13-33
Legend
/HJHQG
With the legend the %DFNJURXQG add-on module provides a user-defined field in the network display making it possible to display additional information in the VISUM plot (explanations/descriptions). Texts, objects, and polygons can be inserted into a legend. A background legend is placed into the network display independent of the standard plot legend.
,QVHUW WKH OHJHQG

Activate INSERT mode. Activate LEGEND object.
Click mouse anywhere in network display. Only one legend can be inserted.
13-34
Legend
/HJHQG GLDORJ &RUQHU OHJHQG: 0DUJLQ OHJHQG: Legend position at a corner of the Legend position at a margin of window. the window.
)L[HG FRUQHU: specify the window corner which determines the legend position. Specify the OHJHQG KHLJKW and ZLGWK and the KRUL]RQWDO DQG WKH YHUWLFDO GLVWDQFH to the margins of the reference corner. 6SHFLILFDWLRQ DLG GRWV
)L[HG PDUJLQ: specify the window corner which determines the legend position. Specify the OHJHQG KHLJKW (if upper or lower margin is fixed) and the GLVWDQFHV to the reference margins. Specify the OHJHQG ZLGWK (if left or right margin is fixed).
'UDZ: activate grid to support positioning of objects, polygons or texts in the legend. The SRLQW GLVWDQFH in [mm] can be modified. The grid is not output on plots.
13-35
Legend
The height and width of the legend are represented 1:1 in plot outputs. The distance to the margin refers to the respective output format. In the network display on screen the legend is represented is too large. For correct output (possible correction if there are covered network objects) switch to 3DJH SUHYLHZ with symbol button .
'HOHWH WKH OHJHQG

Activate SINGLE SELECT mode and LEGEND object.
Select with mouse click in network display. Shortcut <Del> or 'HOHWH in the EDIT menu
(GLW WKH OHJHQG

Activate SINGLE SELECT mode and LEGEND object.
Call up "Legend" dialog to modify legend parameters (see chapter 13.6.1) via: Double-click Shortcut <Del> or MODIFY in the EDIT menu.
13-36
GRAPHICS: PRINTING, INTERFACES

*5$3+,&6 35,17,1* ,17(5)$&(6
The current network display is printed either to a connected output device and output in printed form or to a file to save the graphic display for later modifications with VISUM or an external graphics program. VISUM provides several graphics interfaces (see Ch. 14.6): Post-Script-Format, DXF format which is used by $XWR&DG programs, HPGL format (Hewlett Packard Graphic Language), the VISUM %DFNJURXQG graphics format (binary *.HGR; ASCII format *.HGT).
Furthermore graphics objects of various types (WMF, BMP, JPG, GIF, TIF etc.) can be imported into VISUM (see Chapter 13).
Printing requires: 1. Define print area (see Ch. 14.1), 2. Set parameters for print output (to device/file, page size, etc.; see Ch. 14.2), 3. Design print page (see Ch. 14.3), 4. Check print page layout: Call 3UHYLHZ (see Ch. 14.4), 5. Start print output (see Ch. 14.5).
14-1
Define print area
'HILQH SULQW DUHD
The 3ULQW DUHD can be the current VISUM screen display with maximum scale or specified via parameters.
'HILQLQJ SULQW DUHD
0HQX ),/( 35,17$5($ 3ULQW DUHD GLDORJ
While the Print area dialog is active the print area rectangles size 3ULQW DUHD and position can be modified by mouse click.
14-2
Define print area
.HHS VFDOH VISUM will keep the scale when size or position of the print area are modified interactively. Red figures (see Size [mm]) indicate that paper format size is exceeded, when enlarging the print area size. .HHS VL]H VISUM will keep the vertical/horizontal dimensions for print output in case of interactive modifications of print area size. Scale will be adapted appropriately. 6L]H >PP@ ; < Width and Height of the print area. Red figures indicate that paper size was exceeded. WR SDJH VL]H This button exceeds the print area size to maximum size with regard to selected paper format and specified margins.
6FDOH Current scale. When scale entry is edited and option .HHS VL]H is active, the print area will include a different section of the network. If option .HHS VFDOH is active width and height will be different. :LQGRZ Output of print area coordinates. 8S 'RZQ /HIW 5LJKW EXWWRQV These buttons take next section of the same size (tile) in the specified direction as print area. 3ULQW DUHD IURP ZLQGRZ sets print area to current screen window size. WR PD[ VFDOH For the selected network window the maximum scale for print output to the selected paper format is used. $XWR]RRP selects zoom factor to make print area visible.
14-3
Define print area
6HOHFW SULQW DUHD RU FXUUHQW VHFWLRQ 9,680 ZLQGRZ
0HQX *5$3+,&6 3$5$0(7(56 3ULQW SDJH or ),/(PHQX 6(735,173$*( or ),/(PHQX 35,17 *3DU EXWWRQ
3ULQW SDJH
Select network area in the on-screen display which is to be printed: 3ULQW DUHD: Prints network section located within the print area. 3ULQW FXUUHQW VHFWLRQ: Prints entire network displayed in VISUM window at maximum scale, with the option of exceeding the "current section" to the maximum page size entered for the selected printer driver.
The option 3ULQW FXUUHQW VHFWLRQ is equivalent to selecting the IURP ZLQGRZ and WR PD[ VFDOH button combination in the dialog box "Print area" (FILE menu PRINT AREA...). The additional option H[SDQG WR SDJH VL]H is equivalent to the WR SDJH VL]H button.
14-4
Define print area
+LJKOLJKW SULQW DUHD LQ QHWZRUN GLVSOD\
0HQX *5$3+,&6 3$5$0(7(56 3ULQW SDJH or 0HQX ),/( 6(735,173$*( or 0HQX ),/( 35,17 *3DU EXWWRQ
0DUN SULQW DUHD: displays the print area in the VISUM window as a rectangle with broken lines (see below).
14-5
Printer settings
3ULQWHU VHWWLQJV
There are numerous devices available for printing: Windows printer drivers are recommended. Furthermore VISUM printer drivers are provided (cf. 14.6).
Printer drivers provide flexible import and export of graphics data. 3ULQW SDJH settings define orientation, paper size and the output device.
:LQGRZV SULQWHU GULYHUV
3ULQW SDJH
Option :LQGRZV button 6SHFLI\

Printer settings
3ULQW VHWXS GLDORJ
1DPH Select Windows printer driver. According to the printer settings (driver installed) either file or device is displayed for :KHUH (Output interface). According to printer settings (driver installed) either file or device is displayed for 7\SH (output interface). Print files serve for graphics export (Postscript format) and further external processing (e.g. DTP). Therefore, Windows drivers providing a 3RVW6FULSW interface are recommended. 3DSHU 2ULHQWDWLRQ 3URSHUWLHV EXWWRQ Configure print settings (Size, font types etc.).
1RWHV RQ :LQGRZV WH[W IRQWV Windows text fonts are selected via the )RQWV button in the GRAPHICS PARAMETERS menu (see chapter 12). For optimum graphics printing with Windows text fonts it is advisable to use TrueType fonts and, if possible, to activate the "Print TrueType fonts as graphics" option of the respective printer driver.
14-7
Printer settings
9,680 SULQWHU GULYHUV

Print output from VISUM serves for graphics data export to +HZOHWW 3DFNDUG *UDSKLF /DQJXDJH format (HPGL), $XWR&DG format (DXF) or VISUM %DFNJURXQG JUDSKLFV format (HGT/HGR).
Though mostly Windows printer drivers are used, in some cases one of the VISUM drivers might be advantageous. 0HQX *5$3+,&6 3$5$0(7(56 3ULQW SDJH Option 9,680 Button 6HWWLQJV 3ORW GLDORJ
3ORW
2XWSXW 3ULQWHU print data are sent to the output devices supported by VISUM. After the parameters have been specified with the 3ULQW command, the graphic output is sent directly via the device interface of the selected device defined in the std.zsk device file. EXCEPTIONS: for the HGRD, DXFOUT and &DOFRPS device settings (only with %DFNJURXQG add-on module): automatic standardised file output in the corresponding file formats. )LOH: print data are saved to plot files in HPGL format. A filename must be specified in the "File" input field. EXCEPTIONS: if HGRD or DXFOUT (only with %DFNJURXQG addon module) and &DOFRPS device settings are used, files are output in the corresponding file formats (see Ch. 14.6).
14-8
Printer settings
'HYLFH Select output device or graphic data interface. &KDQQHO)LOH Print output: the device interface defined in std.zsk is displayed (com1, lpt1 etc.) or File output: specify filename and path. If no filename is entered here, the filename may also be entered when saving the file (PRINT command in the FILE menu). )RUPDW Select paper size from A4 to A0 (if provided by the printer driver) . 5RWDWH Optimum adjustment of network section to portrait paper format, if the Y-axis is longer than the X-axis. 3HQ VHWWLQJV Only applicable to pen plotters; screen colors can be assigned to available pens. Default: Identical colors on screen and plot. For modifications: Open "Convert colors" dialog box with mouse click in list box.
3ULQWLQJ GHYLFHV VXSSRUWHG E\ 9,680 VISUM device files for output to plotter or printer: std.zsk std.zgi std.tgi
14-9
Printer settings
The std.zsk ASCII file in the ..\exe directory contains a list of output devices: 7\SH HP LaserJet III,lpt1; HP LaserJet 5p,lpt1; HP LaserJet 4V,lpt1; HPA3,lpt2; HPGLA0,lpt2; 'HVFULSWLRQ Raster plotter (D) Raster plotter (D) Raster plotter (D) HP pen plotter (V): all formats except A2, A1, A0. HP pen plotter (V): all formats.
For printing to max. A3 format, +3$ is recommended because it has a larger printable area and +3*/$ requires a relatively wide margin for the paper feed. +3$ i.e. +3*/$ must be used for HP pen plotters which in contrast to +3 'UDIW3UR do not have an area filling function. Pen plotter (D) Pen plotter (D) Pen plotter (D) Raster plotter (D) Raster plotter (D) Pen plotter (D) Pen plotter (V) Pen plotter (V) Raster plotter (D) Pen plotter (V) Pen plotter (V) Pen plotter (V) Pen plotter (V)
HP DraftPro DXL,lpt2; HP DraftPro EXL,lpt2; HP PaintJet XL300,lpt2; HP DeskJet 1200C,lpt2; HP DesignJet 650C,lpt2; Canon BJC-880,lpt2; Seiko Colorpoint,lpt2; IBM PS 4079,lpt2; HP PaintJet XL,lpt2; GraphTec,lpt2; Schlumberger 1835-SR,lpt2; OCEA0A3,lpt2; PinPlotA3,lpt2
G
D= V=
For pen plotters "Optimize HPGL" is switched on. In this way, graphics are sorted according to colors or pens which avoids continuously having to change pens.
Output device ZLWK area filling function. Output device ZLWKRXW area filling function. VISUM fills areas by shading. This results in larger plot files. VISUM User Manual (April 2001) Version 7.50
14-10
Printer settings
Only for %DFNJURXQG Add-on users: The device file also includes information on the following graphic file interfaces: 7\SH DXFOUT,..\dxfout.dxf; HGRD,..\hgrdout.hgt; 'HVFULSWLRQ Graphic file output in DXF format with standard filename and path. Graphic file output in VISUM-specific background text format with standard filename and path.
In addition to the =6. device file, the binary std.zgi =JUDSK device file also manages the settings of the devices supported by VISUM in the ..\exe directory. It contains detailed descriptions of the individual devices and can be edited as an std.tgi ASCII text file. After modifications have been made, the std.tgi text file can be converted to the std.zgi binary file by calling up the tgizgi.exe DOS conversion program in the ..\exe directory: tgizgi std std
The standard files std.zgi and std.tgi should be saved under a different filename because correct program execution is not guaranteed if the newly created *.zgi file contains errors.
14-11
Print page parameters

3ULQW SDJH SDUDPHWHUV
The print area of a print page is specified by printer settings depending on the selected driver (page size, orientation etc.) paper margins and the space required for headline and/or comment.
For texts and frames also colors can be selected.
14-12
3ULQW SDJH
3DSHU PDUJLQ >PP@ The paper margin limits the printable area of current output device (top/bottom/left/right in [mm]). If all margins are set to 0 mm, VISUM regards the bottom left corner as a fixed point and adjusts the scale so that the printable area is utilised to the maximum in one direction and the relation between the height and the width of the plot remains the same. Value range: 0.00 to 300.00 3ULQW IUDPH 'UDZ Print frame (with plot headline and plot comment) is drawn. 'UDZ: Print frame is not drawn. Input fields for SORW KHDGOLQH WRS and SORW FRPPHQW ERWWRP are inactive. &RORU color of frame. 7H[W FRORU: color of plot headline (top) and plot comment (bottom).
14-13
3ORW +HDGOLQH 7RS 'UDZ Plot headline is drawn. 'UDZ: Plot headline is not drawn. ,QSXW OLQH: up to 80 characters of text can be entered per line. /LQH KHLJKW: Prerequisite for displaying headline: height > 0 mm. The line height should be greater than the text size otherwise VISUM sets the line height twice as large as the text size where 25% of the total height above and below the text are left empty. If height = 0, no headline is displayed. Value range: 0.00 to 100.00 7H[W VL]H: maximum character size of headline in [mm] (size may be reduced due to the text length) Value range: 0.00 - 50.00 &HQWHUHG: Text is centered. o Text is left justified. The headline is placed at the upper plot margin using the full width. 3ORW &RPPHQW %RWWRP VISUM always uses the full width of the bottom margin of the plot to display a two-line footer. The upper line contains the program name, operator, and the name of the version file. The bottom line contains a comment, the date, and the scale. 'UDZ Plot comment is drawn. 'UDZ: Plot comment is not drawn. 7RWDO KHLJKW OLQHV Height of the two-line plot comment in [mm]. If total height = 0 the plot comment is not drawn. Value range: 0.00 to 100.00 Accept 9,680 379 $* DV SURJUDP QDPH Accept suggestion. Display entry in "Program name" input field. 3URJUDP QDPH: Enter program name. 2SHUDWRU Enter operator or department. The "Operator" default entry can be modified. 'DWH The standard "Date" entry can be modified to, for example, "Updated:". The date of the plot output is appended to the entry automatically. &RPPHQW Free text field for plot legend. The text size is adjusted automatically to line height and length.
G
14-14
The standard plot legend i.e. plot header/footer should not be confused with the background legend which can be inserted next to a margin or in a corner of the plot (only with %DFNJURXQG add-on module).
Preview before Printing
3UHYLHZ EHIRUH 3ULQWLQJ
Before a network display is printed to a printer or file, a preview of the plot output graphics is displayed by activating 3DJH 3UHYLHZ mode. The page preview displays the network display on-screen based on the current settings of the plot output parameters. All network and graphic objects are represented in the correct scale because the text enlargement factor for on-screen displays is not applied to plot outputs. Page preview shows up possible shortcomings in the graphics (overlapping objects, texts which are difficult to read etc.). Corrections can be made directly in SUHYLHZ mode because all relevant editing commands (e.g. modifying text size, modifying the position of objects etc.) are active in this mode.
35(9,(: in the ),/(menu or icon in tool bar.
This button is a toggle button with which the 3UHYLHZ function can be switched on and off.
14-15
Preview before Printing
([DPSOH RI 3UHYLHZ PRGH
All functions remain active in this mode, e.g. marking and listing links (listings are not adapted to 3UHYLHZ PRGH display).
The active 3UHYLHZ mode is not saved along with the graphic parameters or in the version file. Execute print output: PRINT... in the FILE menu.
14-16
Start print output
6WDUW SULQW RXWSXW
8
3URJUDP 6WDWXV
FILE menu 35,17 6WDWLVWLFV UHJDUGLQJ WKH FXUUHQW QHWZRUN VWDWH
The Program Status provides details on the current network version which is to be printed. Check: Are there - due to current filter settings - passive network objects which actually should be printed? Do current link label options (Multiply, Rounding, min. attribute value) match the operators intentions? Is a Difference network active? Is the network scale correct (Factor)?
Start print output
Set the default printer via Windows printer settings:
*3DU EXWWRQ Opens the "Modify Graphics parameters (Print page)" dialog box. 2. EXWWRQ Prints the page.
Print output to file or device, as specified. A missing file name and/or path will be queried for. Print page parameters parameters (*.gpa). are managed with the graphics
14-18
Graphics interfaces
*UDSKLFV LQWHUIDFHV
In VISUM, graphic file management can be carried out in four different graphic formats: PostScript printer file (ASCII format) HPGL (+HZOHWW 3DFNDUG *UDSKLF /DQJXDJH). DXF ($XWR&DG format); only with %DFNJURXQG add-on module. HGT/HGR (ASCII and binary format for internal VISUM graphics); only with %DFNJURXQG add-on module. General graphics interface for various common graphics data formats, %DFNJURXQG add-on required (see Chapter 13:. Insert Object).
14-19
Graphics interfaces
3RVW6FULSW3') H[SRUW

PostScript and PDF files have an advantage over the original format in that they are platform-independent, that no loss of formatting occurs and that the reader does not need to have the software version in which they were created. The exported images can be edited and processed without any restrictions whatsoever. VISUM network images can thus be easily made accessible for further flexible processing in DTP, layout and image editing software. In a PDF file imported into, for example, 0DFURPHGLD )UHH+DQG , all lines, surfaces, labels etc. can be freely edited. There are also no problems using them for displaying on the Internet and in interactive media. A PDF file can contain hyperlinks, comments and bookmarks and supports various compression formats such as JPEG or LZW. Last but not lease, PDF files can be indexed by search engines such as ([FLWH IRU :HE 6HUYHUV. Because of these advantages, the PDF format has recently become the main standard for the document exchange on the Internet.
VISUM does not offer a direct graphic export into the PDF format, because this is only possible by using a commercial software ($FUREDW 3') :ULWHU as a module of $GREH $FUREDW). A cost-efficient way to create a PDF file from a VISUM display is to export it into a PostScript file using a PostScript-enabled Windows printer driver, and then to convert it to PDF.
14-20
Graphics interfaces

3RVW6FULSW JUDSKLF ILOH
:LQGRZV SUHUHTXLVLWHV IRU 9,680 3RVW6FULSW H[SRUW
Install PostScript printer driver (e.g. HP Deskjet 1200/36 or HP Paintjet XL300/36), e.g. under Windows 95: SETTINGS menu - PRINTERS Select printer FILE menu - PROPERTIES 'HWDLOV 3URSHUWLHV GLDORJ As output interface the setting to create a file is selected. In addition, "EPS (Encapsulated PostScript)" must be selected as the PostScript print format via the 3RVW6FULSW button in the appropriate dialog box.
The printer does not have to be physically connected to the computer, since the printer driver only is required to save the print output to file.
14-21
Graphics interfaces
9,680 3RVW6FULSW H[SRUW
0HQX *5$3+,&6 3$5$0(7(56 3ULQW SDJH or 0HQX ),/( 6(735,173$*( or 0HQX ),/( 35,17 *3DU EXWWRQ 0RGLI\ *UDSKLFV SDUDPHWHUV 3ULQW SDJH WDE
3ULQW SDJH Option :LQGRZV 6HWWLQJV button 3ULQW GLDORJ DQG 3URSHUWLHV GLDORJ
Select PostScript printer. Depending on the printer settings entered during setup, "FILE" will be displayed as the print output target.
),/( PHQX 35,17 3ULQW WR ILOH GLDORJ Enter filename and directory path.
By simply changing the suffix *.prn into *.ps , the file can be read by Adobe Photoshop and Adobe Illustrator.
14-22
Graphics interfaces
3ULQWHU 6HWWLQJV WR EH UHFRPPHQGHG The PostScript Output Option: (QFDSVXODWHG 3RVW6FULSW (36 is required in order to "encapsulate" the PostScript file into another file. By entering the file extension *.eps, the file is directly readable by many text and layout programs such as Word 97. PostScript functions overview: Use the 36 /HYHO format whenever possible. Compared to /HYHO , these files have a higher compression rate and are thus processed faster. Problematic fonts: If you use standard fonts, you do not need to include these. However, if you work with exotic or, for example, Corel Draw fonts, you should include them in the PS file! Missing or unsuitable fonts are the most frequent problem in exchanging files wth external service providers! Resolution: For internet use, a resolution of GSL is suitable. However, when the data are mainly used for printing, a higher resolution of at least GSL is required.
VISUM graphics are now prepared for conversion to modern, standardised data transfer formats offering full editing capabilities in DTP, page layout and image processing programs. The graphics can be processed further e.g. with the following commercial programs (tested for the stated versions onwards): Drawing and graphics programs: Corel Draw 7+, Macromedias, Freehand 7.0, Adobe Illustrator 7.0 Word processing and page layout programs: MS Word 6.0, Pagemaker 6.5, Quark X Press 4.0 Image processing systems: Corel Photopaint 7+, Adobe Photoshop 3.0 Presentation programs: PowerPoint 97 ([DPSOHV IRU IXUWKHU SURFHVVLQJ RI 3RVW6FULSW ILOHV The PostScript file can be opened directly in &RUHO 'UDZ as vector graphic. It must be noted, however, that using Corel Draw figures and text can no longer be edited as a string.. In $GREH 3KRWRVKRS the file can be opened as a raster image by entering target parameters such as definition and color system. After editing, the image can then of course be saved in the popular *.bmp format. The raster images that have been generated can also be saved in this case as JPG or GIF files for Internet applications. With the *.eps extension the PostScript file can be opened with several text or layout processing tools, e.g. Winword 97. Output
Graphics interfaces
to any printer supporting PostScript is possible. The file can only be displayed on screen when preview functionality is provided (e.g. TIF). Rather use a graphic converter or another suitable graphics tool to generate either a raster graphics (e.g. *.bmp) file or a vector graphics (e.g. *.wmf format, which is supported bz Windows) from the PostScript file first and open it then. Also OLE functions can be used.

3') JUDSKLF ILOH
There are several ways to create a PDF file from a VISUM network display: Direct export to PDF format: In order to do this, you need the commercial software $FUREDW 3') :ULWHU as a module of $GREH $FUREDW. After installing 3') :ULWHU , it is used by VISUM just like any other Windows printer driver. Export as a PostScript file using a PostScript-enabled Windows printer driver and subsequent conversion to the PDF format.
using noncommercial software (e.g. the functional freeware tool $ODGGLQ *KRVWYLHZ*KRVWVFULSW)or using noncommercial online conversion services provided on the internet by various universities.
+3*/ JUDSKLF ILOH

For HPGL plot outputs to file, VISUM saves a *.plt graphic file in the widely used +HZOHWW 3DFNDUG *UDSKLF /DQJXDJH standard graphic format. This export file can be imported and processed by all graphic programs which have an HPGL interface.
0HQX *5$3+,&6 3DUDPHWHUV 3ULQW SDJH RU 0HQX ),/( 6(735,173$*( RU 0HQX ),/( 35,17 *3DU EXWWRQ
3ULQW SDJH Option 9LVXP 6HWWLQJV button 3ORW GLDORJ
14-24
Graphics interfaces
2XWSXW )LOH. With the exception of +*5' and ';)287 all device types can be used for generating HPGL graphic files.
G
8
If 9LVXP 3ULQWHU output option is activated, print data with the exception of +*5', ';)287 and &DOFRPS device settings are output directly to connected device. In case of HGRD or DXFOUT the preset file format will be used for output. 0HQX )LOH 35,17 9,680 GLDORJ
2. EXWWRQ Start print output to specified file.
Import and processing by external graphic program which has an HPGL interface.
14-25
Graphics interfaces
';) LQWHUIDFH

The DXF interface provides, on the one hand, the option of editing the graphic network display with other graphics programs by exporting VISUM plots in DXF format. On the other hand, graphic files which were saved in DXF format by other graphics programs such as geographical information systems (GIS) can be imported via the same interface. In this way, graphic backgrounds which cannot be produced with VISUM can be utilised as valuable, graphic, and informative additions to the network display.
The export format complies with $XWR&DG-Version 12. Data import works up to the $XWR&DGVersion 14 data format with undefined data blocks being ignored. Thus check carefully, if data have been imported completely. Only graphic objects without links to relevant factual data (attributes) can be exchanged via the DXF interface. For linking spatial and factual data, such as zone boundaries (spatial data) and attribute values (factual data, e.g. AdValues), PTV provides particular conversion software.

([SRUWLQJ JUDSKLFV
0HQX *5$3+,&6 3DUDPHWHUV 3ULQW SDJH RU 0HQX ),/( 6(735,173$*( RU 0HQX ),/( 35,17 *3DU EXWWRQ
3ULQW SDJH Option 9LVXP 6HWWLQJV button
14-26
Graphics interfaces
3ORW GLDORJ
)LOH 'HYLFH: ';)287. Enter name and path of DXF file.
3ULQWHU 'HYLFH: ';)287. Standard name and path of DXF file determined by VISUM from current std.zsk file.
G
8
If no file extension is specified, VISUM appends the *.plt file extension automatically. 0HQX )LOH 35,17 9,680 GLDORJ
2. EXWWRQ Start print output to specified file.
Import and processing by any external graphic program which has an HPGL interface.
14-27
Graphics interfaces

,PSRUWLQJ JUDSKLFV
Program execution of dxfkonv.exe conversion program in DOS box under Windows.
&RQYHUWLQJ D ';) ILOH LQWR D +*7 ILOH
A background text file in ASCII format is created from a file in $XWR&DG format. The program is started with the following command structure and possibly the following options: DXFKONV <Input > [<Output>][Options]
<Input> [<Output>] Filename of DXF file to be opened. Filename of background text file for the complete output of all graphic layers. The HGT file type is QRW compulsory, but is recommended for uniquivocal identification.
[Options]: /L
Screen display of layers contained in DXF file. A conversion is not carried out, so no output file has to be specified. Conversion of the individual /LQNV! DXF layers which were each saved in the RXWQDPH! file, e.g.: /sLinks Roads.hgt. Text conversion; switched off by default. Filename of *.imp parameters file in which the above options are saved line by line.
/S<Links><outname>
/T+ @<Parameter file>
Every conversion procedure creates a separate ASCII color file with the name of the DXF file and the *.frb file extension. In this file color identifiers for the converted layers are listed. The user can edit graphic VISUM backgrounds in the generated background text file with the %DFNJURXQG language.
14-28
Graphics interfaces
([DPSOH RI VHSDUDWH FRQYHUVLRQ RI VHYHUDO ';) OD\HUV XVLQJ D SDUDPHWHUV ILOH The city.dxf file consists of different layers (buildings, streets etc.) which are to be converted separately into background files: The following conversion options are thus inserted into the City.imp parameters file:
/sLinks /sRoads /sBuildings /sOtherAreas citlink.hgt citname.hgt citbldg.hgt citarea.hgt
Generating the specified background text files from the DXF file for different layers using the parameters file: dxfkonv city.dxf city @city.imp
&RQYHUWLQJ D +*7 ILOH LQWR D +*5 ILOH
&219(57%$&.*5281'),/(LQ WKH (;75$6PHQX "6HOHFW LQSXW ILOH dialog box: enter desired HGT file. "6HOHFW RXWSXW ILOH" dialog box: enter desired HGR file. 7UDQVIRUP EDFNJURXQG GLDORJ 2. EXWWRQ Convert background text format into binary background format which can be read by VISUM. During the conversion process of the background compiler the separate FRB color files are integrated. For Point co-ordinates see below.
If no entries are made in the empty fields of the "Transform background" dialog box, the co-ordinates of the generated background file are not adjusted to fit the current network display.
14-29
Graphics interfaces
,QVHUWLQJ WKH ELQDU\ EDFNJURXQG ILOH LQWR WKH QHWZRUN GLVSOD\ Insert background file as 2EMHFW (Select OBJECTS in INSERT mode) and edit. If the object to be inserted can be scaled freely, a background file can be adjusted to fit the network display without co-ordinate transformation. Adapt co-ordinates of background file to VISUM network (see section below) .
,PSRUWLQJ D ';) ILOH LQWR D 9,680 QHWZRUN ZLWK DGMXVWPHQW RI FRRUGLQDWHV
&RQYHUWLQJ D ';) ILOH LQWR D +*5 ILOH Initially the conversion is carried transformation (see sections above). out ZLWKRXW co-ordinate
'HWHUPLQH IL[ SRLQWV IRU FRRUGLQDWH WUDQVIRUPDWLRQ Insert generated HGR file as %DFNJURXQG (Select BACKGROUNDS in INSERT mode). Enlarge window (symbol button (QWLUH QHWZRUN) if inserted background is to be placed far outside the network display area due to strongly incongruent co-ordinates. Specify background co-ordinates: specify position of the three significant points of the loaded background with ,QVHUW QRGH command. The points have to be arranged in triangular form and must be far apart as much as possible. Write down x/y-background co-ordinates for P1, P2 and P3. Specify objective co-ordinates: specify position of the three points which are to overlap background points by using the ,QVHUW QRGH or 6HOHFW QRGH commands in the network display Write down the x/y objective co-ordinates for P1, P2 and P3.
&219(57%$&.*5281'),/( LQ WKH (;75$6PHQX
14-30
Graphics interfaces
7UDQVIRUP EDFNJURXQG GLDORJ
%DFNJURXQG FRRUGLQDWHV 7DUJHW FRRUGLQDWHV Enter co-ordinates written down previously into relevant fields. ,QLWLDOL]H EXWWRQ Delete values and parameter calculation. &DOFXODWH EXWWRQ Carry out parameters calculation required for co-ordinate transformation. 7UDQVIRUPDWLRQ SDUDPHWHUV The six calculated transformation parameters are displayed. 2. EXWWRQ Convert HGR file with co-ordinate adjustment based on calculated transformation parameters.
Insert binary background file as %DFNJURXQG into network display (Select BACKGROUNDS in INSERT mode) and edit. Congruency can only be approached with this method if both the background file and the network file use the same co-ordinate system such as Gauss Krger co-ordinates. Inaccuracies are usual because distortions of different map projections cannot be avoided. Exact co-ordinate congruency can only be reached with conversion programs integrated into GIS systems.
14-31
Graphics interfaces
+*5' EDFNJURXQG ILOHV

During HGRD plot output VISUM saves an editable *.hgt ASCII background text file. This file is then converted automatically into a *.hgr binary background file which can be inserted as a %DFNJURXQG or an 2EMHFW (see chapter 13) in VISUM.

2XWSXW WR EDFNJURXQG ILOH

0HQX *5$3+,&6 3DUDPHWHUV 3ULQW SDJH RU 0HQX ),/( 6(735,173$*( RU 0HQX ),/( 35,17 *3DU EXWWRQ 0RGLI\ JUDSKLFV SDUDPHWHUV SULQW SDJH GLDORJ
Option 9LVXP 6HWWLQJV button 3ORW GLDORJ
)LOH 'HYLFH: HGRD. Enter filename and path for HGT file.
3ULQWHU 'HYLFH: HGRD Standard name and path for HGT file determined by VISUM: ..\hgrd\hgrdout.hgt.
If no file extension is specified, VISUM appends the *.plt file extension automatically.
14-32
Graphics interfaces
0HQX ),/( 35,17 9,680 GLDORJ
2. EXWWRQ Start print output to specified file and converts HGT file to HGR file. 6DYH ELQDU\ EDFNJURXQG ILOH GLDORJ
Conversion of existing HGT file into binary HGR file by means of background compiler (see EXTRAS menu). Insert binary background file as %DFNJURXQG or 2EMHFW into network display (Select BACKGROUNDS or OBJECTS in INSERT mode) and edit. Opening a *.hgr plot file as a background object can be used to embed the contained network display in a different network display as a map section. A detailed inner-city map section of any size can be integrated, for example, into a representation of the entire road network of a city.
14-33
Graphics interfaces

(GLWLQJ EDFNJURXQG WH[W ILOHV
Backgrounds are described outside the VISUM program in the HGT background text file (ASCII format) in the %DFNJURXQG language. The background compiler then translates these instructions into binary HGR format. %DVLF VWUXFWXUH RI EDFNJURXQG WH[W ILOH {$XLATPARAMS} BACKGROUND SCALE OBJECT SCALE BEGIN
Description of graphic objects and/or subobjects. Co-ordinate transformation instruction; optional Background name Scaling factor Object name Scaling factor
END BEGIN
Display and positioning of texts, polygons, and of objects defined by background.
END
In the very first line six transformation parameters have to follow ^ ;/$73$5$06 for converting background co-ordinates into VISUM network co-ordinates, if the background and the network do not overlap. The parameters must not be specified because VISUM can calculate these with the &RQYHUW EDFNJURXQG command. The entire background is defined via the key word %$&.*5281'. The scaling factor is a positive number. When the object is drawn, the co-ordinates are multiplied by factor. For embedded objects (definition of subobjects), the scales are multiplied with each other. The basis of the %$&.*5281' language are objects which are defined via the key word 2%-(&7. An object is a user-defined geometrical figure which can be placed in different sizes and orientations at different positions in a background. Where objects and texts are displayed in the background depends on their co-ordinates. Objects are displayed at x,y coordinates from the x1,y1 origin. The rotation angle must be specified in degrees and makes it possible to rotate objects and texts: Object name x,y rotation angle
14-34
Graphics interfaces
(OHPHQWDU\ JUDSKLF EXLOGLQJ EORFNV
POLYGON
fill pattern boundary
x1, y1
x2, y2...xn, yn;
This command is used to draw a polygon through points xi,yi, 1 <= i <= n. Fill pattern and boundary values must be logical values (TRUE or FALSE). They specify if the polygon area is to be filled or outlined.
COLOR
color index;
This command is used to select a color from the palette for drawing polygons and texts (pen attachment: see 3HQ DWWDFKPHQW list box via 3ORWWHU button in the GRAPHICS - GRAPHICS PARAMETERS menu).
TEXT x,y text orientation "text to be displayed" rotat.angle;

This command is used to display text at the specified co-ordinates. It can be rotated by a positive rotation angle. Text orientation specifies the position of the text with reference to point (x,y):
BottomRight CentreRight TopRight CentreBottom CentreCentre CentreTop BottomLeft CentreLeft TopLeft = 9; = 8; = 7; = 6; = 5; = 4; = 3; = 2; = 1;
TEXTSTYLE
Height
Width
Base Line;
This command is used to specify absolute mm values for the text height and width. The base line is either BOTTOM or CENTER. This specifies if the height is either determined by the virtual base line underneath letters like g or j or by the virtual base line underneath letters like G and J.
FILLSTYLE
User Vertical Horizontal Grid Diagonal GridDiagonal Chequered
Pattern
= 0; = 1; = 2; = 3; = 4; = 5; = 6;
Color index
Distance;
Patterns have the following input values:
This command is used to specify the fill pattern and color as well as the distance in mm between the individual lines of the polygon. A distance of 0 fills the entire area. (See color index &2/25)
Graphics interfaces
LINESTYLE
Line type
Line thickness;
This command is used to specify the lines used for polygons. On the screen the number corresponds to the number of pixels, and on the plot it corresponds to the thickness of the pen. Millimetres can only be specified for electrostatic plotters or laser printers:
Continuous Short Medium Long LongShort MediumShort MediumShortShort = 0; = 1; = 2; = 3; = 4; = 5; = 6;
FRAMESTYLE
Frame
HFact
VFact
Color index;
This command is used to specify if the displayed text is to be framed. The distance of the frame from the text is determined by HFact and VFact. The frame is displayed in the color determined by the color index (compare &2/25). The frame value must be a logical value i.e. TRUE or FALSE.
14-36
Graphics interfaces
'HFODULQJ FRQVWDQWV Constants are declared to increase the legibility of object descriptions. A constant declaration begins with the key word CONST and ends with the key words OBJECT or BEGIN. Example:
CONST no yes bottom centre bottomleft {...} darkblue green {...} bleu pi = = = = = false; true; bottom; center; 1; {logical values} {text base line types} {text orientation} {pen colors}
= 1; = 2; = darkblue; = 3.14159;
To the right of the equations are either predefined constants (false, true, centre,...), numerical values or constants defined previously (darkblue). Texts enclosed in curved brackets are called comments are ignored during compilation. They can extend over various lines; embedded comments, however, are not allowed. Constants declared in this way are only valid for, or known to the object for which they were defined as well as their subobjects. Example:
OBJECT A CONST Blue=1; Green=2; OBJECT B CONST Bblue=blue; Green=3; BEGIN END BEGIN {Here green is 2 again as defined in A.} {Bblue is not visible here.} END
{If constants of the same name have already been} {declared somewhere else, they are redefined here} {This Object is placed in A, visible only there.} {This is the blue defined in A.} {Here, a new green is defined.} {Here green is = 3)
14-37
Graphics interfaces
&RPSLOHU RSWLRQV Compiler options are used to control the conversion procedure. The options are integrated directly into the background and have the following format: {$OPTION PARAMETER} It is important here that there is no space between the dollar sign and the comma because this option would otherwise be treated as a comment.
DEFAULTSCALE
The DEFAULTSCALE option makes it possible to specify a standard scale for all objects which can, however, be overwritten if necessary. The specified scaling factor must not be zero. Example: {$DEFAULTSCALE 1}{Objects are not scaled down by default.} This option must be entered before the key word BACKGROUND.
INCLUDE
This option makes it possible to integrate additional files so that standard libraries do not have to be copied into the current background file, but can be kept in one central location. Example: {$INCLUDE "GERCONST"} {Integrate German identifiers.}
This option is allowed to contain embedded commands i.e. files integrated via INCLUDE can in turn contain INCLUDE options. The maximum embedding depth can usually be up to 10 levels.
MESSAGE
This option makes it possible to display control messages on screen during conversion. Example: {$MESSAGE} {German identifiers are always integrated.}
14-38
Graphics interfaces

(UURU PHVVDJHV GXULQJ EDFNJURXQG FRQYHUVLRQ
The Backcomp.exe background compiler is hidden behind the &RQYHUW EDFNJURXQG command. If difficulties arise during the conversion of a HGT file into a HGR file, the compiler displays the error messages listed and explained below.
... expected:
In this place the compiler expected the key word or character displayed above. Usually the actual source of the error is found in one of the lines above.
Cannot create Output file:

An error occurred during the creation of the binary file. Typical sources of error are missing access rights or not enough space on the hard disk. Write access and permission to create new files is required.
Identifier has already been defined:

This error occurs if an object or a constant has already been defined on the same level. Example:
OBJECT abc SCALE 1 CONST rotation angle = 0; {...} rotation angle = 0; OBJECT def SCALE 1 CONST rotation angle = 13; BEGIN . END BEGIN . END
{Here is an error!} {This is possible!}
It is advisable to indent individual objects according to their level so that these kinds of error can be recognised easily.
Cannot open file:

The file accessed via INCLUDE or specified as a background cannot be opened. Most of the time this is due to a simple typing error. In network environments make sure that you are allowed to access and open the file.
This OBJECT is not defined:

This object has not been recognised or has been spelled incorrectly.
Basic graphic object or object instantiation expected:

Here an object or a basic graphic object should have been called up.
Only x,y are valid here:

Only x and y values are permitted.
Graphics interfaces
Incorrect maximum value:

The specified value exceeds the meaningful maximum value. Rotations of more than 360 degrees, for example, cause this error message to be displayed.
Polygon has too many points:

The specified polygon has more than 1024 points. It must be divided into several smaller polygons.
Recursive call of infinite loop:

This error occurs if an object calls itself up or a if subobjects call up parent objects. Example:
OBJECT A SCALE 1 OBJECT B SCALE 1 BEGIN A 0,0,0;{This is not possible!} END BEGIN A 1,2,3; {Not possible, either!} {Here A has to be defined.} END
Wrong syntax:
The marked character has no meaning at this point.
Texts may not exceed one line:

A text which starts with " must end in the same line.
Unknown or invalid compiler option:

The displayed compiler option has either not been defined or is no longer valid at this point.
Unexpected end of file:

More text was expected. A comment was probably not ended correctly in one of the lines above.
Value must not be zero:

This error message is displayed with regard to SCALE definitions. Zero values are not allowed in this context and thus result in an error message.
Number or constant expected:

Either the marked characters do not make up a valid number or no such constant exists.
String too long:

Strings may not contain more than 235 characters. Longer texts must be divided into several separate instructions.
14-40
Graphics interfaces
*HQHUDO JUDSKLFV LPSRUW LQWHUIDFH

Using the ,QVHUW2EMHFW command VISUM can import graphic files of various common data formats. Overview: )LOH W\SH 'HVFULSWLRQ
Standard graphic import of the additional module %DFNJURXQG: BMP (DIB) "%LWPDS": pixel-based Windows standard format HGR "%DFNJURXQG": internal vector-based VISUM graphic format, which can also be generated by means of the ';) LQWHUIDFH from a DXF file (AutoCad format) ":LQGRZV 0HWDILOH": both vector- and pixel-based Windows graphic format (standard and HQKDQFHG format).
WMF (EMF)
Additional EDFNJURXQG graphic import (with 4XLFN7LPH): GIF JPG PNG "*UDSKLFV ,QWHUFKDQJH )RUPDW: pixel-based standard format by &RPSXVHUYH for internet applications. "-RLQW 3KRWRJUDSKLF ([SHUWV *URXS": standard pixel-based format for internet applications developed by an ,62 experts group "PRUWDEOH 1HWZRUN *UDSKLFV: license-free pixel-based format for internet applications, developed by the :RUOG :LGH :HE &RQVRUWLXP (:&) to replace GIF and JPG "3KRWRVKRS": popular pixel-based format professional image processing on PC by $GREH for
PSD TIF TGA
"7DJ ,PDJH )LOH": pixel-based standard format by $OGXV & 0LFURVRIW for DTP and scanning software "7DUJD": pixel-based format by 7UXHYLVLRQ for professional image processing on Workstations Beside the formats described in the table above, one should also mention such less popular formats as 6*, 6LOLFRQ *UDSKLFV ,PDJH) and PCT (0DFLQWRVK 3LFWXUH). 4XLFN7LPH is available from ZZZDSSOHFRP TXLFNWLPHGRZQORDG. After installing QuickTime, just restart VISUM, so that it can read the formats supported by 4XLFN7LPH .
14-41
Graphics interfaces
14-42
DATA FORMATS, DATA IMPORT AND EXPORT

'$7$ )250$76 '$7$ ,03257 $1' (;3257
This chapter describes data formats for input files (network *.net and O-D matrix *.fma). Data formats which can be created and opened by VISUM are also introduced. Please also refer to the section on file management in Chapter 3.
15-1
Network file
1HWZRUN ILOH
6WUXFWXUH RI D QHWZRUN ILOH

1HWZRUN WDEOHV In the VISUM network file, data on network objects are stored in tables. The necessary attributes for describing a network object can be contained in one or more tables. The data of e.g. a link object, are all contained in the LINK table, whereas SUBLINE, LINEROUTE, and LINETIMETABLE tables are necessary to describe a line object. /LVW QDPH
VERSION INFO NETPARA TSYS MODE DEMANDSEGMENT NODE NODETYPE ZONE ZONEPOLY GLOBALZONE GLOBALZONEPOLY GLOBALZONETOZONE LINKTYPE TURNINGSTANDARD
&RQWHQWV Information on version number and file type. User information on network file. General network parameters (e.g. scale). Definition of transport systems. Definition of transport types Definition of demand segments Nodes which represent intersections and/or stops. Definition of node types. Zones (traffic cells). Zone boundaries. Global zones (combined zones). Global zone boundaries. Assignment of global zones and zones.
76\V7\SH PrT+PuT PrT+PuT PrT+PuT PrT+PuT PrT+PuT PrT+PuT PrT+PuT PrT+PuT PrT+PuT PrT+PuT PrT+PuT PrT+PuT PrT+PuT
Specifying link types: default parameters for links. PrT+PuT Default parameters for turning relations. PrT
15-2
Network file
/LVW QDPH
LINK LINKPOLY CONNECTOR MAJORFLOW TURNINGRELATION OPERATOR VEHICLETYPE MAINLINE LINID SUBLINE LINEROUTE LINETIMETABLE TSZ STOPTOTSZ TZ TZTOTSZ TICKETTYPE FARE_BY_DIST FARE_BY_ZONE FARE_SUPPL FARE_DIST_ SUPPL AREA AREAPOLY CENSUSPOINT
&RQWHQWV Links of the transport network. Link course.
76\V7\SH PrT+PuT PrT+PuT
Access/egress routes linking zones to nodes/stops. PrT+PuT Information on rights of way at nodes. Permitted TSys, time penalties/capacities (PrT). PuT-operators (transport companies) PuT-vehicle types (seats, cost structure). Main lines Subline name settings (number of characters). Name of line variants (sublines). PrT PrT+PuT PuT PuT PuT PuT PuT
Sequence of traversed nodes, with running times. PuT Vehicle trips (timetable). List of tariff subzones Allocation of stops to tariff subzones List of tariff zones Allocation of tariff zones to tariff subzones Ticket types Distance-based tariffs Zone-based tariffs TSys-specific supplements Distance-based TSys-specific supplements List of areas Polygons of areas Census points Lists in the VISUM network file PuT PuT PuT PuT PuT PuT PuT PuT PuT PuT PrT+PuT PrT+PuT PrT
7DEOH
15-3
Network file
To describe transport supply, not all VISUM tables listed in 7DEOH are always required. A simple PrT network model, for example, does not require PuT-line information, and a PuT network model does not require information on rights of way. The following list contains the tables required for a PrT or PuT network model. For PuT, the LINKS list is not necessary because the links can be generated from the line route. 3U7 QHWZRUN PRGHO NETPARA TSYS MODE DEMAND SEGMENT NODE ZONE LINK CONNECTOR 3X7 QHWZRUN PRGHO NETPARA TSYS MODE DEMAND SEGMENT NODE ZONE (LINK) CONNECTOR SUBLINE LINEROUTE LINETIMETABLE
15-4
Network file
*HQHUDO VWUXFWXUH RI QHWZRUN WDEOHV In a network file, a list is defined by specifying the key character $ and a list name. These are followed by the identifiers of the columns of the list for the input data. The identifier of a list column is the abbreviated name of the attribute, with no special characters permitted. Chapter 4 ("The network editor"), however, contains the complete attribute lists for all VISUM object types where the abbreviated name and the full name of an attribute may contain special characters because data storage is not taken into account. The following example defines the Node list in which node objects (intersections, stops) are described by providing a unique node number, a node name, the node coordinates, and other attributes.
* Comment line $NODE:Nr;CODE;NAME;TYPE;X-Coord;Y-Coord;STOP 10;NewTown;NewTown;1;50.0000;100.0000;1
7DEOH
Example showing NODE list in the VISUM network file
&RPSXOVRU\ DQG RSWLRQDO DWWULEXWHV Usually a table contains FRPSXOVRU\ DWWULEXWHV and RSWLRQDO DWWULEXWHV While compulsory attributes are necessary for constructing a consistent network model, optional attributes can be complemented by standard parameters during the construction of the network model. To define a link, for example, the attributes FromNode, ToNode, and LinkType are sufficient. In this case, the link length is set to the direct distance, and the default values for PrT-capacity, PrT-speed, and PuTrunning times are set via the link type.
15-5
Network file
*HQHUDO QHWZRUN SDUDPHWHUV

In the Netpara table, the following general parameters are specified for the network data: $WWULEXWH 'HVFULSWLRQ
Scale Conversion factor to adjust length of links to the scale of map (compulsory) Range: Real Timeformat Definition of the time format for time-related data: min or sec. (compulsory) Range: Text3 Decimalplaces Indication of decimal places for network coordinates. (compulsory) Range: 0 bis 8 7DEOH Attributes of network parameters
$NETPARA:SCALE;TIMEFORMAT;DECIMALPLACES 200.00;Sec;8
7DEOH
Netpara table
6HW QHWZRUN SDUDPHWHUV LQ 9,680
0HQX (;75$6 1(7:25.3$5$0(7(56 6HW QHWZRUN SDUDPHWHUV GLDORJ
15-6
Network file
'HFLPDO SODFHV IRU FRRUGLQDWHV Input of decimal places for the network coordinates (max. 8) 1HWZRUN VFDOH Input of a conversion factor to adjust length of links to the scale of the map. Depending on how an network scale (max. 100000) is changed, the lengths of the links and connectors also change. 5HFDOFXODWH EXWWRQ Starts the required recalculation depending on the following options: 5HFDOFXODWH OHQJWK RI OLQNV DQG FRQQHFWRUV: If this option is inactive, no recalculation is performed. Furthermore OLQH URXWH OHQJWK can be recalculated IURP OLQN OHQJWK. Recalculation can be restricted to links, connectors and lines, which have been set to active by: &RQFLGHU RQO\ DFWLYH OLQNV FRQQHFWRUV DQG OLQHV The length calculation from GLUHFW GLVWDQFH [ QHWZRUN VFDOH IDFWRU either takes into consideration the distance between )URP1RGHV and 7R1RGHV or in the case of digitised links, also the distance between intermediate points.
CAUTION! By changing the length of the links, the link impedance and thus the assignment result may also change.
15-7
Network file
0HQX ),/( 6$9( 1HWZRUNV ILOH W\SH 2SWLRQV 6DYH QHWZRUN
7LPH IRUPDW VHFRQGV: save time values in seconds. PLQXWHV: save time values in minutes.
By using the minutes time format, the indicated values are rounded to minute values in the network file, e.g. 1:00:45 -> 61 min. Time values, which have been entered interactively with no time indication, are interpreted by VISUM according to the setting via 7LPH IRUPDW button IN EXTRAS MENU - OPTIONS.
15-8
Network file
7UDQVSRUW V\VWHPV

The transport supply consists of several transport systems. A transport system is defined by a type of transport: Private (PrT) or Public (PuT) transport or PuTWalk and a means of transport, e.g. car, tram, bike.
Basic characteristics of transport types are: 3ULYDWH WUDQVSRUW Travel times of a private transport system depend on the max. speed of the means of transport, e.g. 100 km/h for trucks, the speed permitted on the link used, e.g. 80 km/h, the capacity of the link used.
3XEOLF WUDQVSRUW Running times of vehicles of a public transport system and the dwell times at stops are determined by the timetable. 3X7:DON This mode serves to model walking transfer links between stops; This mode may be specified for one transport system only in a network model. 76\V7\SH PrT+PuT PrT+PuT PrT+PuT $WWULEXWH TSysCode (compulsory) TSysName (compulsory) TSysMode (compulsory) 'HVFULSWLRQ Code of the transport system. Range: one character, A..Z or 0..9 Name of the transport system. Range: Text30 Type of the transport system: PR: Private transport, PU: Public transport PW: PuT - Walking transfer link. Range: PR or PU or PW Passenger car units to describe the impact of one vehicle of a private transport system on the capacity. Default value: 1.0 Range: 0.0 to 9.9 Default speed of a transport system. Range: Long Int
PrT
PCU (optional)
PrT+PuT 7DEOH
TSys-v (optional)
Attributes of a transport system
15-9
Network file
* List of Transport Systems * Transport system type specification: * PR for PrT * PU for PuT * PW for PuT-WalkLink $TSYS:TSysCode;TSysName;TSysMode;TSys-v;PCU B;T_Bus;PU;50;1.000 Z;T_Rail;PU;50;1.000 F;T_Walklink;PW;4;1.000 P;T_Car;PR;200;1.000 L;T_HGV;PR;100;2.000
7DEOH
TSYS table in the network file
15-10
Network file
0RGHV
A mode connects one or several transport systems. A mode can include either one private transport system or several public transport systems. Several public transport modes can be defined. This way it is possible to model that e.g. long-distance passengers (Mode PuT-Longdist) may use all public transport systems (Intercity, Regional train, Bus, etc.) whereas e.g. commuters (Mode PuT-Local) may use only particular transport systems (Regional train, Bus). 76\V7\SH PrT+PuT PrT+PuT $WWULEXWH Code (compulsory) Name (compulsory) 'HVFULSWLRQ Mode code (brief identifier). Range: Text1 (A..Z, 0..9) Mode name, e.g.: PuT longdist (Code D), PuT local (Code L). Range: Text30 List of codes of permissible transport systems. Standard value: empty character string Range: defined transport systems
PrT+PuT
TSysCode (compulsory)
7DEOH
* List of modes
Mode attributes
$MODE:CODE;NAME;TSysCode P;M_Car;P L;M_HGV;L O;M_PuT;BZF
7DEOH
Mode table in the network file
15-11
Network file
'HPDQG VHJPHQWV

A demand segment belongs to exactly one mode. This way a demand segment is the link between transport supply and transport demand. As several demand segments can be defined for each mode, different types of demand can be combined in the transport model. Demand segments can be used for differentiation among: Population groups: Employed-PrT (car drivers), Empl-PuT, Students-PuT, etc. Ticket types: Single trip ticket, Monthly Pass, etc. Vehicle types: Car-Diesel, Car-Petrol, etc. For each demand segment a demand matrix has to be specified. Usually private transport demand matrices contain the demand in car units, whereas passenger units are used for public transport demand matrices. For calculation of O-D trips (PrT) from car units the occupancy rate can be specified for each demand segment. 76\V 7\SH PrT+PuT PrT+PuT $WWULEXWH Code (compulsory) Name (compulsory) 'HVFULSWLRQ Brief identifier of demand segment. Range: Text1 (A..Z, 0..9) Name of demand segment, e.g.: private car - private (Code P), private car - business (Code B). Range: Text30 Code of assigned mode Range: defined modes (Text1) Occupancy rate = factor for calculation of number of travellers from of matrix values in [vehicle units]. Range: Real
PrT+PuT PrT+PuT
Mode (compulsory) OccRate (optional)
7DEOH
Attributes of a demand segment
* List of demand segments $DEMANDSEGMENT:CODE;NAME;MODE;OCCRATE X;D_Car (business);P;1.000 P;D_Car (private);P;1.000 L;D_HGV ;L;1.000 Z;D_PuT;O;1.000
7DEOH
15-12
DEMANDSEGMENT table in network file
Network file
1RGHV
Nodes describe intersections and stops. They are the beginning and end of links. 76\V7\SH PrT+PuT PrT+PuT $WWULEXWH Nr (compulsory) Code (optional) Name (optional) Type (optional) XCoord, YCoord (compulsory) Stop (optional) 'HVFULSWLRQ Number of node Range: 1-999999999 Code of node Default value: empty string Range: Text8, no number as first character Name of node Default value: empty string Range: Text50 Type of node Default value: 0 Range: 0-99 X-, Y-Co-ordinate Range: Real Node is a PuT stop (0=No/ 1=Yes) Default value: 0 Range: 0/1 for depreciation,
PrT+PuT
PrT+PuT
PrT+PuT
PuT
PuT
StopCost1, 2, 3 Public transport stop cost maintenance or link usage. (optional) default: 0 range: Real Attributes of a node
7DEOH
$NODE:Nr;CODE;NAME;TYPE;X-Coord;Y-Coord;STOP;STOPCOST1;STOPCOST2;STOPCOST3 10;A;A village;1;50.0000;100.0000;1;0.0000;0.0000;0.0000 11;A;A stop;10;75.0000;100.0000;1;0.0000;0.0000;0.0000 12;;;0;50.0000;50.0000;0;0.0000;0.0000;0.0000 20;CS;Central station;1;75.0000;75.0000;1;0.0000;0.0000;0.0000 21;;;10;75.0000;50.0000;0;0.0000;0.0000;0.0000 30;B;B village;1;100.0000;50.0000;1;0.0000;0.0000;0.0000 31;;;10;125.0000;50.0000;0;0.0000;0.0000;0.0000
7DEOH
NODE table in the network file
15-13
Network file
=RQHV
Zones are point objects which describe the location of particular land uses (e.g. residential areas, places of work, shopping centres, schools). They are the origin and destination of trips in the network i.e. of trips by private or public transport, and are linked to the network with connectors. 76\V7\SH PrT+PuT PrT+PuT $WWULEXWH Nr (compulsory) Name (optional) Code (optional) Type (optional) 'HVFULSWLRQ Number of zone. Range: 1-999999999 Name of zone. Default value: empty string Range: Text50 Code of zone. Default value: empty string Range: Text20 Type of zone. Default value: 0 Range: 0 to 9
PrT+PuT
PrT+PuT
PrT+PuT
X-Coord, Y-Coord X-, Y-Co-ordinate of zones centroid. (optional) Default value: from connector Range: Real Perc_O, Perc_D (optional) Distribution of PrT (origin/destination) travel demand to the zones PrT connectors: DEVROXWH: free distribution of travel demand to the zones connectors. SHUFHQWDJH: proportional distribution of travel demand according to the automatically calculated capacity of the zones connectors. Default value: 0 Range: 0/1
PrT
7DEOH
Attributes of a zone
* List of zones $ZONE:Nr;NAME;Code;TYPE;X-Coord;Y-Coord;PERC_O;PERC_D 100;A village;A-vill;2;50.3655;105.8924;0;0; 400;C village;;0;62.2794;75.1608;0;0;
7DEOH
15-14
ZONE table in the network file

Network file
=RQDO ERXQGDULHV 76\V7\SH PrT+PuT PrT+PuT PrT+PuT $WWULEXWH Nr (compulsory) Index (optional) XCoord (compulsory) YCoord (oumpulsory) 'HVFULSWLRQ Number of zone the polygon was specified for. Range: defined ZoneNr Index number of the polygon point Range: Long Int X-coordinate of the polygon point. Default value: from mouse position Range: Real Y-coordinate of the polygon point. Default value: from mouse position Range: Real
PrT+PuT
7DEOH
Attributes of zonal boundaries
* Zonal Boundaries $ZONEPOLY:Nr;INDEX;X-Coord;Y-Coord 100;1;45.0000;115.0000 100;2;55.0000;115.0000 100;3;55.0000;105.0000 100;4;45.0000;105.0000 200;1;130.0000;80.0000 200;2;140.0000;80.0000 200;3;140.0000;70.0000 200;4;130.0000;70.0000 $
7DEOH
ZONEPOLY table in the network file
15-15
Network file
*OREDO =RQHV

Global zones are units which include several zones, whereby each zone may only be a part of one global zone. Global zones can be used when working with AddValues and for displaying flow bundles. Global zone polgon data are stored separately, see table GlobalZone in the network file. Zones belonging to a Global zone are saved in the GLOBALZONETOZONE table in the network file. 76\V7\SH PrT+PuT PrT+PuT $WWULEXWH Nr (compulsory) Name (optional) Code (optional) Type (optional) 'HVFULSWLRQ Number of global zone. Range: 1-999999999 Name of global zone. Default value: empty string Range: Text50 Code of global zone. Default value: empty string Range: Text20 Type of global zone. Default value: 0 Range: 0 to 9
PrT+PuT
PrT+PuT
PrT+PuT
X-Coord, Y-Coord X-, Y-Co-ordinate of the global zones center of (optional) gravity. Default value: from mouse position Range: Real Attributes of a global zone
7DEOH
* List of global zones $GLOBALZONE:Nr;NAME;CODE;TYPE;X-Coord;Y-Coord 1;;;0;4504373.0892;5705585.2971 2;;;0;4493854.6835;5701058.7195 *etc. $
7DEOH
GLOBALZONE table in the network file
15-16
Network file
*OREDO ]RQH SRO\JRQV ERXQGDULHV 76\V7\SH PrT+PuT PrT+PuT PrT+PuT $WWULEXWH Nr (cumpulsory) Index (optional) XCoord (cumpulsory) YCoord (cumpulsory) 'HVFULSWLRQ Number of global zone the polygon was specified for. Range: defined GlobalZoneNr Index number of the polygon point Range: Long Int X-coordinate of the polygon point. Default value: from mouse position Range: Real Y-coordinate of the polygon point. Default value: from mouse position Range: Real
PrT+PuT
7DEOH
Attributes of a global zone polygon
* List of global zone polygons $GLOBALZONEPOLY:Nr;INDEX;X-Coord;Y-Coord 1;1;4504608.5759;5702550.1353 1;2;4507041.9385;5706317.9224 1;3;4504425.4196;5708280.3115 1;4;4502646.1868;5708227.9812 1;5;4502436.8653;5702497.8049 2;1;4494194.8309;5700561.5809 2;2;4496209.5504;5703099.6042 2;3;4498459.7567;5702523.9701 2;4;4500108.1635;5702550.1353 *etc. $
7DEOH
GLOBALZONEPOLY table in the network file
15-17
Network file
$OORFDWLRQ RI ]RQHV WR D JOREDO ]RQH 76\V7\SH PrT+PuT $WWULEXWH GZoneNr (compulsory) ZoneNr (compulsory) 'HVFULSWLRQ Number of global zone. Range: 1-999999999 PrT+PuT Number of zone. Range: 1-999999999 7DEOH Attributes of the allocation of a global zone and zones
* Allocation of global zones and zones $GLOBALZONETOZONE:GZoneNr;ZONENR 1;902 1;841 1;340 2;600 2;230 2;220 2;210 2;200 2;190 2;150 2;130
7DEOH
GLOBALZONETOZONE in the network file
/LQN W\SHV

VISUM distinguishes between link types 00-99 which serve to classify transport networks and facilitate type-specific assignment of default values for: the permitted transport systems PrT-capacity PrT-speed for free flow and PuT-running times which result from the link lengths and the transport systemspecific speed.
Network file
76\V7\SH PrT+PuT PrT+PuT PrT+PuT PrT PrT PrT PrT
$WWULEXWH Nr (compulsory) Name (compulsory) TSysCode (compulsory) Cap-PrT (compulsory) v0-PrT (compulsory) vMax-PrT (compulsory) vMin-PrT (compulsory) v-PuT (compulsory) Rank (compulsory)
'HVFULSWLRQ Number of link type. Range: 00..99 Name of link type. Range: Text20 List of permitted transport systems. Range: defined transport systems. Capacity of private transport within a time interval. Range: Long Int, >0 Free flow speed of private transport. Range: Long Int, >0 Maximum speed for each private transport system. Range: Long Int, >0 Minimum speed by link type (so-called congestion speed). Range: Long Int, >0 Default speed for a public transport system, which is used to calculate running times of a link. Range: Long Int, >0 Rank defines the hierarchy of link types which is used to determine major flows. Range: Long Int, >0
PuT
PrT
7DEOH
Attributes of a link type
$LINKTYPE:Nr;NAME;Cap-PrT;v0-PrT;vMin-PrT;TSysCode;vMax-PrT(P);vMaxPrT(L);v-PuT(B);v-PuT(Z);v-PuT(F);Rank * 16;ExpressWay;24000;130;0;PL;150;100;0;0;0;1 17;ExpressWay;24000;130;0;PL;150;100;0;0;0;1 18;ExpressWay;24000;130;0;PL;150;100;0;0;0;1 19;ExpressWay;24000;130;0;PL;150;100;0;0;0;1 20;FederalRoad;12000;100;0;BPL;100;80;60;0;0;2 21;FederalRoad;12000;100;0;BPL;100;80;60;0;0;2 * etc.
7DEOH
Linktype table in the network file

Network file

/LQNV
Links describe roads or railway tracks in the transport network. They connect nodes i.e. intersections of private transport or PuT-stops. A link is represented as a directed edge and is thus described by the FromNodeNr and the ToNodeNr. The two directions of a link are two separate objects in the network model which have been assigned the same link number. For every link, the permitted transport systems of PrT and PuT mode which may use the link must be specified. 76\V7\SH PrT+PuT PrT+PuT PrT+PuT PrT+PuT $WWULEXWH Nr (optional) FromNode (compulsory) ToNode (compulsory) Type (compulsory) 'HVFULSWLRQ Number of a link. Range: 1-99999999 Number of the FromNode of a link. Range: defined node number Number of the ToNode of a link. Range: defined node number Type of link for network classification; specifies type-specific default values. Default value: 0 Range: 00 to 99 Link length. Default value: Direct distance Range: Long Int., >0 List of permitted transport systems. Default value: from link type Range: defined transport systems PrT-Capacity in PCU/time interval. Default value: from link type Range: Long Int. Link-related maximum speed of private transport (free flow). Default value: from link type Range: Long Int. Running time for each PuT system. Default value: from link type, length Range: time interval One-way road identifier. Range: 1=yes / 0=no
PrT+PuT
Length (optional) TSysCode (optional) Cap-PrT (optional) v0-PrT (optional)
PrT+PuT
PrT
PrT
PuT
t-PuT (optional) Oneway (optional)
PrT+PuT
15-20
Network file
76\V7\SH PuT
$WWULEXWH Cost1,2,3PuTSys (optional)
'HVFULSWLRQ Cost by for each PuT system (depreciation etc.). Default value: 0 Range: Real
7DEOH
Attributes of a link
$LINK:Nr;FROMNODE;TONODE;TYPE;LENGTH;Cap-PrT;TSysCode;v0-PrT; t-PuT(B);t-PuT(T);t-PuT(W);ONEWAY;Cost1-PuTSys(Z);Cost2-PuTSys(Z); Cost3-PuTSys(Z) 1;10;11;20;5000;1200;BPL;100;360;0;0;1;0.0000;0.0000;0.0000;0.0000;0. 0000;0.0000 3;20;21;20;5000;1200;BPL;100;600;0;0;1;0.0000;0.0000;0.0000;0.0000;0. 0000;0.0000 3;21;20;20;5000;1200;BPL;100;600;0;0;1;0.0000;0.0000;0.0000;0.0000;0. 0000;0.0000 4;40;50;90;5000;0;Z;0;0;480;0;1;0.0000;0.0000;0.0000;0.0100;0.0000;2. 0000 4;50;40;90;5000;0;Z;0;0;480;0;1;0.0000;0.0000;0.0000;0.0100;0.0000;2. 0000 5;21;30;20;5000;1200;BPL;100;600;0;0;1;0.0000;0.0000;0.0000;0.0000;0. 0000;0.0000
7DEOH
LINK table in the network file
15-21
Network file
/LQN SRO\JRQV 76\V7\SH PrT+PuT PrT+PuT PrT+PuT PrT+PuT $WWULEXWH FromNode (compulsory) ToNode (compulsory) Index (optional) XCoord (compulsory) YCoord (compulsory) 'HVFULSWLRQ Number of the FromNode of the specified link. Range: defined node number Number of the ToNode of the specified link. Range: defined node number Index number of the polygon point Range: Long Int X-coordinate of the polygon point. Default value: from mouse position Range: Real Y-coordinate of the polygon point. Default value: from mouse position Range: Real
PrT+PuT
7DEOH :
Attributes of a link polygon
List of link polygons $LinkPOLY:FromNode;ToNode;INDEX;X-Coord;Y-Coord 11;20;1;80.4803;97.1922 11;20;2;81.9491;89.5546 11;20;3;82.6835;83.9734 11;20;4;78.1303;80.4484 * etc.
7DEOH
Table Linkpoly in the network file
15-22
Network file

7XUQLQJ UHODWLRQV
Turning relations specify if turning is permitted at a node. For PrT-transport systems, turning time penalties and capacities can be specified which describe the influence of the intersection on the performance of the network. Turning prohibitions for PuTtransport systems are considered during the construction of line routes, and turning prohibitions for PrT-transport systems are considered during the route search. 76\V7\SH PrT+PuT PrT+PuT $WWULEXWH FromNode (compulsory) ViaNode (compulsory) ToNode (compulsory) TSysCode (compulsory) Type (optional) 'HVFULSWLRQ FromNode-number of link, which leads to the node. Range: defined node number Node-number, where the turning movement takes place. Range: defined node number ToNode-number of link, which leaves from the node. Range: defined node number List of permitted transport systems. Range: defined transport systems Turning relation type calculated from turning relation geometry: 0 not specified 1 right (>0 - 120) 2 straight (121 - 240) 3 left (241 - <360) 4 U-Turn (360) 5..9 for particular turning relations Range: 0-9 PrT turning time penalty (free flow). Range: time interval Private transport capacity of turning relation in [PCU/time interval]. Range: Long Int., >0
PrT PrT
t0-PrT (compulsory) Cap-PrT (compulsory)
7DEOH
Attributes of a turning relation
15-23
Network file
$TURNINGRELATION:FROMNODE;VIANODE;TONODE;TSysCode;t0-PrT;Cap-PrT;TYPE 10;11;20;BCH;0;10000;1 10;11;41;BCH;0;10000;2 11;10;11;CH;0;99999;4 11;20;21;BCH;0;99999;2 20;11;10;BCH;30;1000;3 20;11;41;BCH;0;5000;1 20;21;30;BCH;0;10000;3
7DEOH
TURNINGRELATION table in the network file

7XUQLQJ VWDQGDUGV
By specifying turning standars, turning time penalties and turning capacities can be generated automatically. In this way, the turning relations can be edited, for example, as follows: Set the turning penalty for all left-hand turns which turn at a node of type 10 from a lower ranking link to a higher ranking link to 30 sec.. Node type Turning relation Turning type Time penalty = = 10 -+ from a lower ranking link to a higher ranking link (left-hand turns)
= 3 = 30 s
Set the turning penalty for all right-hand turns to 5 seconds. Node type Turning relation Turning type Time penalty = ?? = ?? = 1 = 5s (all nodes) (all relations) (right-hand turns)
15-24
Network file
VISUM can determine major flows with right of way and minor flows with no right of way from the ranks of crossing links. The turning type is calculated from the geometry of the intersection. 76\V7\SH PrT PrT $WWULEXWH NodeType (compulsory) TurnRel (compulsory) 'HVFULSWLRQ Type of ViaNode. Range: Text2 (00 - 99, ??, 0? - 9?) Priority of turning relations:
++ +-+ -From major flow to major flow, From major flow to minor flow, From minor flow to major flow, From minor flow to minor flow
Range: Text2 (++ , +- , -+ , -- , ??) PrT TurnType (compulsory) Turning relation type calculated from geometry:
0 1 2 3 4 not specified right straight left U-Turn (> 0 - 120) (121 - 240) (241 - < 360) (360)
Range: Text1: (0 - 9, ?) PrT t0-PrT t0 Time-PrT (compulsory) Cap-PrT (compulsory) PrT time penalty for turning movement (free flow). Range: time interval Private transport capacity of turning relation in [PCU/time interval]. Range: Long Int.
PrT
7DEOH
Attributes of turning relation standards
$TURNINGSTANDARD:NODETYPE;TURNREL;TURNTYPE;t0-PrT;Cap-PrT ??;??;?;0;99999 1?;++;1;5;10000 1?;++;2;0;10000 1?;++;3;5;10000 1?;+-;1;5;10000 1?;+-;2;5;10000
7DEOH
TURNINGSTANDARD table in the network file
15-25
Network file

&RQQHFWRUV
Connectors connect zones to the link network. They represent the access and egress routes between the zone centroid and PuT-stop or PrT-node. 76\V7\SH PrT+PuT $WWULEXWH ZoneNr (compulsory) NodeNr (compulsory) Type (optional) Direction (optional) 'HVFULSWLRQ Number of the zone which is connected by the connector. Range: defined zone number Number of the node which is connected by the connector. Range: defined node number Type of connector. default: 0 range: 0 - 9 Connector open for O origin traffic, D destination traffic, OD both. default: OD = both directions permitted range: O, D, OD Length of connector. default: direct distance range: Long Int. Connector open for PrT (0 = No, 1= Yes). default: permitted range: 0/1 Connector open for PuT (0 = No, 1 = Yes). default: permitted range: 0/1 Private transport access and egress time. default: connector speed PrT range: time interval Public transport access and egress time. default: connector speed PuT range: time interval Percentage of PrT volume which uses connector. range: 0 - 100 %
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT
Length (optional) PrT-Mode (optional) PuT-Mode (optional) t0-PrT (optional) t-PuT (optional) Perc (optional)
PrT
PuT
PrT
PuT
PrT 7DEOH

15-26
Attributes of a connector
Network file
$CONNECTOR:ZONENR;NODENR;Direction;TYPE;LENGTH;PrT-Mode;PuT-Mode;t0PrT;t-PuT;PERC(PR) 100;10;O;1;300;1;1;180;180;0 100;10;D;1;0;1;1;180;180;0 200;40;OD;1;0;1;1;300;300;0
7DEOH
CONNECTOR table in the network file
15-27
Network file

6XEOLQHV
A PuT-line consists of one or more line variants (sublines) whose line route or running times between stops can vary. A subline is defined by the name of the line, the variant identifier, the direction, the line route (node sequence with served and traversed stops) with running times between stops and the timetable (list of departure times). $WWULEXWH Name (compulsory) Variant (compulsory) Direction (compulsory) TSysCode (compulsory) OpNr (optional) VehType (optional) LayoverT (optional) MainLine (optional) 7DEOH 'HVFULSWLRQ Name of line. All sublines with identical line names belong to the same line. A subline name may consist of max. 20 characters. range: max. Text 18 (Standard: Text6) Variant of the line. range: max. Text 18 (Standard: Text2) Direction of subline (line variant), e.g. F = Forth, B = Back. range: Text1 Code of the transport system, all sublines of the line belong to. range: defined transport system. Number of operator. range: defined operator numbers Number of vehicle type. range: defined vehicle types Layover time, required after each vehicle trip for driver breaks, slack time and turn back. range: time interval Name of the assigned main line. range: defined main line SUBLINE table: Definition of sublines
15-28
Network file
$WWULEXWH Name (compulsory) Variant (compulsory) Direction (compulsory) NodeNr (compulsory) Board, Alight (optional)
'HVFULSWLRQ Name of line. All sublines with identical line names belong to the same line. range: defined line name Variant of the line. range: defined line variant Direction of subline (line variant), e.g. F = Forth, B = Back. range: defined direction Node number of current stop. range: defined node numbers 0 Passengers may not board/alight 1 Passengers may board/alight default values: 1 range: 0/1 Running time from departure from origin terminal till arrival at current stop. Running time from departure from origin terminal till departure from current stop. Length between two stops (from current stop to next served stop). default value: Values from link network range: Long Int. LINEROUTE table: node sequence with served and non-served stops.
Arr (compulsory) Dep (compulsory) Length (optional) 7DEOH
15-29
Network file
$WWULEXWH Name (compulsory) Variant (compulsory) Direction (compulsory) Dep (compulsory) Headway (optional) LastDep (optional) VehType (optional) VehRunNr (optional) 7DEOH
'HVFULSWLRQ Name of line. All sublines with identical line names belong to the same line. range: defined line name Variant of the line. range: defined line variant Direction of subline (line variant), e.g. F = Forth, B = Back. range: defined direction Departure time at origin terminal or first departure within time interval with fixed rhythm headway. range: hh:mm:ss Headway between two departures. range: time interval Last departure time in an interval with a fixed rhythm headway. range: hh:mm:ss Number of vehicle type range: defined vehicle type Number of the vehicle running, resulting from line blocking. range: Long Int. LINETIMETABLE table: list of departure times from origin terminal.
15-30
Network file
* Compounds of a line name $LINID:LINNAMELENGTH;LINVARLENGTH;DIR1CODE;DIR2CODE 6;2;F;B * * List of line variants (= Lines in VISUM-DOS) $SUBLINE:NAME;Variant;Direction;TSysCode;OPNR;LAYOVERT;VEHTYPE;MainLine BUS1;1;F;B;2;300;1;ML_1 BUS1;1;B;B;2;300;1;ML_2 Train;1;F;T;1;600;2;ML_1 Train;1;B;T;1;600;2;ML_2 * * Line route with running times (stop -> stop) $LINEROUTE:NAME;Variant;Direction;Index;NODENR;BOARD;ALIGHT;Arr;Dep;Length BUS1;1;F;1;10;1;1;00:00:00;00:00:00;0 BUS1;1;F;2;11;0;0;00:00:00;00:00:00;0 BUS1;1;F;3;20;1;1;00:12:00;00:12:00;10000 BUS1;1;F;4;21;0;0;00:00:00;00:00:00;0 BUS1;1;F;5;30;1;1;00:32:00;00:32:00;10000 BUS1;1;F;6;31;0;0;00:00:00;00:00:00;0 BUS1;1;F;7;40;1;1;00:45:00;00:45:00;7500 BUS1;1;B;1;40;1;1;00:00:00;00:00:00;0 BUS1;1;B;2;31;0;0;00:00:00;00:00:00;0 BUS1;1;B;3;30;1;1;00:13:00;00:13:00;7500 BUS1;1;B;4;21;0;0;00:00:00;00:00:00;0 BUS1;1;B;5;20;1;1;00:33:00;00:33:00;10000 BUS1;1;B;6;11;0;0;00:00:00;00:00:00;0 BUS1;1;B;7;10;1;1;00:45:00;00:45:00;10000 TRAIN;1;F;1;20;1;1;00:00:00;00:00:00;0 TRAIN;1;F;2;40;1;1;00:16:00;00:16:00;10000 TRAIN;1;B;1;40;1;1;00:00:00;00:00:00;0 TRAIN;1;B;2;20;1;1;00:16:00;00:16:00;10000 * * List of line services $LINETIMETABLE:NAME;Variant;Direction;INDEX;Dep;HEADWAY;LASTDEP;VEHTYPE;VehRunNr BUS1;1;F;1;06:10:00;;;0;0 BUS1;1;F;2;06:55:00;;;0;0 BUS1;1;F;3;07:25:00;;;0;0 BUS1;1;F;4;08:10:00;01:00:00;18:10:00;0;0 BUS1;1;B;1;06:20:00;;;0;0 BUS1;1;B;2;07:05:00;;;0;0 BUS1;1;B;3;07:45:00;;;0;0 TRAIN;1;F;1;06:25:00;;;0;0 TRAIN;1;F;2;07:05:00;;;0;0 TRAIN;1;F;3;07:45:00;;;0;0 TRAIN;1;B;1;06:45:00;;;0;0 TRAIN;1;B;2;07:25:00;;;0;0 TRAIN;1;B;3;08:05:00;;;0;0
7DEOH
A subline is defined in the network file with the tables SUBLINE, LINEROUTE and LINETIMETABLE
15-31
Network file

0DLQ OLQHV
Various sublines using different transport systems can be selected to form a main line. In the $Subline table the attribute PDLQOLQH indicates the allocation of a subline to a mainline. $WWULEXWH 'HVFULSWLRQ
Name Name of a main line (compulsory) Range: Text50 7DEOH Attributes of a main line
*List of main lines $MAINLINE:NAME;COMMENT A-X-Main line; outbound 0:00 3:00 a.m.
7DEOH
Mainline table in the network file

3X7 2SHUDWRUV
3X7 YHKLFOH W\SHV DQG RSHUDWRUV
The Operator table indicates which PuT operators (transport companies) operate the lines of the network. The operators are defined by operator name and number and assigned to sublines by their number (in sublines table). The operators can also have up to three cost values for general operating costs, which are required for the calculation of line costs (add-on module /LQH FRVWLQJ). $WWULEXWH 'HVFULSWLRQ
OpNr Number of operator. (compulsory) range: 1-32767 OpName Name of operator. (compulsory) range: Text50 Cost1,2,3 (optional) Three public transport operator cost values for depreciation and fixed costs. default value: 0 range: Real Attributes of operators
7DEOH
15-32
Network file
*List of operators $OPERATOR:OPNR;OPNAME;Cost1;Cost2;Cost3 1;Railway company;100000.0000;0.0000;0.0000 2;Municipal services;100000.0000;0.0000;0.0000
7DEOH
Operator table in the network file
3X7 9HKLFOH 7\SHV Vehicle types are assigned to just one transport system and include data relating to vehicle costs (hourly costs, kilometre costs and fixed vehicle cost) and to vehicle capacity (total capacity and seat capacity). The vehicle types are defined in the $VEHICLETYPE table by vehicle type name and number and assigned to the sublines by their number (in the sublines table). $WWULEXWH VehType (compulsory) VehCode (optional) VehName (compulsory) TSysCode (compulsory) SeatCap (optional) TotalCap (optional) NumVeh (optional) 'HVFULSWLRQ Type of public transport vehicle. range: 1-32767 Code of public transport vehicle type. Standard value: empty character string range: Text8 Name of public transport vehicle type. range: Text20 Code of the PuT system to which the vehicle type belongs. range: defined transport systems Seat capacity: Number of seats by vehicle. default value: 0 range: 0-32767 Total capacity: Seats and standing capacity by vehicle. default value: 0 range: 0-32767 Number of available vehicles default value: 0 range: 0-32767
15-33
Network file
$WWULEXWH KmCost (optional) HourCost (optional) VehCost (optional) RefTime (optional)
'HVFULSWLRQ Cost per vehicle-kilometer. default value: 0 range: Real, 0 Cost per out-of-depot hour. default value: 0 range: Real, 0 Cost per vehicle. default value: 0 range: Real, 0 Cost per vehicle refer to: 0 = one year 1 = one day default value: 1 range: 0-1 Attributes of a vehicle type
7DEOH
*List of vehicle types *RefTime: Year = 0, Day = 1 $VEHICLETYPE:VEHTYPE;VEHNAME;VEHCODE;SEATCAP;TOTALCAP;TSysCode;NUMVEH; KMCOST;HOURCOST;VEHCOST;REFTIME 1;Bus;Bus;35;90;B;10;1.0000;42.0000;100.0000;1 2;Rail;Rail;200;400;Z;10;5.0000;42.0000;200.0000;1
7DEOH
VEHICLETYPE table in the network file
15-34
Network file

7DULII ]RQHV
The information on tariff zones (required for fare calculation) is found in four separate tables. The TZ and TSZ tables contain a list of all tariff zones and tariff subzones of a network which are defined by numbers. These numbers are used in the TZTOTSZ table for the allocation of tariff subzones to tariff zones and in the STOPTOTSZ table for the allocation of stops to tariff subzones. 7DULII ]RQHV $WWULEXWH Nr (compulsory) Type (optional) Code (optional) Name (optional) 7DEOH 'HVFULSWLRQ Number of Tariff zone. Range: 1 999999999 Type of Tariff zone. Range: 00 99 Code of Tariff zone. Default value: empty string Range: Text8 Name of Tariff zone. Default value: empty string Range: Text50 Attributes of a tariff zone
*List of tariff zones $TZ:Nr;TYPE;CODE;NAME 100;1;TZ100;TZ100_Inner 200;1;TZ200;TZ200_Greater
7DEOH
TZ table in the network file
15-35
Network file
7DULII VXE]RQHV $WWULEXWH Nr (compulsory) Type (optional) Code (optional) Name (optional) 7DEOH 'HVFULSWLRQ Number of Tariff subzone. Range: 1 999999999 Type of Tariff subzone. Range: 00 99 Code of Tariff subzone. Default value: empty string Range: Text8 Name of Tariff subzone. Default value: empty string Range: Text50 Attributes of a tariff subzone
*List of tariff subzones $TSZ:Nr;TYPE;CODE;NAME 110;1;TSZ110;TSZ110 111;1;TSZ111;TSZ111 120;1;TSZ120;TSZ120 130;1;TSZ130;TSZ130 150;1;TSZ150;TSZ150 230;1;STZ230;TSZ230 240;1;TSZ240;TSZ240 250;1;TSZ250;TSZ250
7DEOH
TSZ table in the network file
$OORFDWLRQ RI WDULII ]RQHV WR WDULII VXE]RQHV $WWULEXWH TZNr (compulsory) TSZNr (compulsory) 7DEOH 'HVFULSWLRQ Number of tariff zone. Range: defined TZNr (Long Int) Number of tariff subzone. Range: defined TSZNr (Long Int) Attributes of allocation of tariff zones to tariff subzones
15-36
Network file
*Allocation of tariff zones to tariff subzones $TZTOTSZ:TZNR;TSZNR 100;110 100;111 100;120 100;130 100;150 200;230 200;240 200;250
7DEOH
TZTOTSZ table in the network file
$OORFDWLRQ RI VWRSV WR WDULII VXE]RQHV $WWULEXWH StopNr (compulsory) TSZNr (compulsory) 7DEOH 'HVFULSWLRQ NodeNr of allocated stop. Range: defined NodeNr (1 999999999) Number of tariff subzone. Range: defined TariffSubzoneNr (1 999999999) Attributes of allocation of stops to tariff subzones
*Allocations of stops/nodes to tariff subzones $STOPTOTSZ:TSZNR;STOPNR 110;10 111;11 120;20 130;30 150;50 230;30 240;40 250;50
7DEOH
STOPTOTSZ table in the network file
15-37
Network file

7LFNHW W\SHV
The definition of ticket types is found in the Tickettype table, in which the tariff type (zone-based or distance-based tariff), utility rate and supplement factor are indicated. The ticket types are indicated by means of a determinate number. A list of fare categories is maintained for distance-based tariffs in the Fare_by_Dist table and for zone-based tariffs in the Fare_by_Zone table. Supplements for transport systems can additionally be fixed in the Fare_Suppl table. The fare categories and supplements are allocated to the various ticket types by means of the ticket type Nr. 7LFNHW W\SH $WWULEXWH Nr (compulsory) Name (optional) ZTariff (optional) DTariff (optional) SupplFac (optional) UtilityRate (optional) 7DEOH 'HVFULSWLRQ Number of ticket type. Range: Long Int Name of ticket type. Default value: empty string Range: Text50 Zone-based tariff applied to ticket type: 0 = no, 1 = yes Range: 0-1 Distance-based tariff applied to ticket type: 0 = no, 1 = yes Range: 0-1 Supplement factor is considered for fare calculation. Default value: 0.0 Range: Real Utility rate of ticket type. Default value: 1.0 Range: Real Attributes of ticket types
* List of ticket types $TICKETTYPE:Nr;NAME;ZTARIFF;DTARIFF;SUPPLFAC;UTILITYRATE 1;Single ticket;1;0;0.0000;1.0000 2;Multiple trips;1;0;0.0000;4.0000 3;Monthly season ticket;1;0;0.0000;50.0000
7DEOH
15-38
Tickettype table in the network file
Network file
'LVWDQFHEDVHG WDULIIV $WWULEXWH TicketNr (compulsory) Distance (compulsory) Fare (compulsory) 7DEOH 'HVFULSWLRQ Number of ticket type. Range: Long Int Maximum distance in [m] the fare is valid for (Fare levels). Range: Long Int Fare charged until distance limit (fare levels ref. to distance). Range: Real Attributes of distance-based tariffs
* List of dist.-based tariffs $FARE_BY_DIST:TICKETNR;DISTANCE;FARE 1;2000;0.2000 1;4000;0.4000 *...etc.
7DEOH
Fare_by_Dist table in the network file.
=RQHEDVHG WDULIIV $WWULEXWH TicketNr (compulsory) NumTSZ (compulsory) NumTZ (compulsory) Fare (compulsory) 7DEOH 'HVFULSWLRQ Number of ticket type. Range: Long Int Number of tariff subzones. Range: 0-32767 Number of tariff zones. Range: 0-32767 Fare for zones traversed. Range: real Attributes of zone-based tariffs
15-39
Network file
* List of zone-based tariffs $FARE_BY_ZONE:TICKETNR;NUMTSZ;NUMTZ;FARE 1;1;0;1.0000 1;2;0;1.0000 1;0;1;2.0000 1;0;2;3.0000 2;1;0;0.8000 *...etc.
7DEOH
Fare_by_Zone table in the network file
76\VEDVHG VXSSOHPHQWV $WWULEXWH TSysCode (compulsory) Supplement (compulsory) Rank (optional) DistSupp (optional) 7DEOH 'HVFULSWLRQ Code of the PuT system. Range: 1 character, A-Z or 0-9 Fare supplement in monetary units. Range: Real Rank which defines the hierarchy of the fare supplement. Range: Integer Use fare supplement (yes/no). Range: yes/no TSys supplement attributes
* List of TSys-spec. Supplements $FARE_SUPPL:TSysCode;SUPPLEMENT;Rank;DISTSUPP B;0.0000;2;0 T;0.0000;1;0 S;5.0000;1;0
7DEOH
Fare_Suppl table in the network file.
15-40
Network file
'LVWDQFHEDVHG VXSSOHPHQWV $WWULEXWH TSysCode (compulsory) Distance (compulsory) Fare (compulsory) 7DEOH 'HVFULSWLRQ Code of the transport system. Range: one character, A..Z or 0..99 Distance [m] limit valid for one fare. Range: Long Int Fare of the distance-based supplement in monetary units. Range: Real Attributes of distance-based supplements
* List of distance-based supplement by TSys $FARE_DIST_SUPPL:TSysCode;DISTANCE;FARE Z;1000;0.0500 Z;2000;0.1000 Z;3000;0.1500 Z;4000;0.2000 Z;5000;0.2500 *etc.
7DEOH
FARE_DIST_SUPPL table in the network file
15-41
Network file

$UHDV
Areas are network objects which may represent e.g. districts or counties. The area boundaries are maintained separately in the AREAPOLY network table. An area boundary may have a maximum of 1022 polygon points. For each area, indicators are calculated and can be displayed in an area list. 76\V7\SH PrT+PuT PrT+PuT $WWULEXWH Nr (compulsory) Name (optional) Type (compulsory) X-Coord (compulsory) Y-Coord (compulsory) 'HVFULSWLRQ Number of area Range: 1-99999999 Name of area. Default value: empty string Range: Text20 Type of area. Default value: 0 Range: 0 - 9 X-coordinate (Label position). Range: Real Y-coordinate (Label position). Range: Real
PrT+PuT
PrT+PuT PrT+PuT
7DEOH
Attributes of an area
* List of areas $AREA:Nr;NAME;TYPE;XCOORD;YCOORD 10;Inner city;0;4497802.9600;5705261.0700 20;North East;0;4499554.6700;5709214.8900 30;South East;0;4502668.5800;5699223.3000 40;South West;0;4490781.5600;5700116.8500 50;North West;0;4490944.0200;5708862.8900
7DEOH
AREA table in the network file
15-42
Network file
$UHD ERXQGDULHV 76\V7\SH PrT+PuT PrT+PuT PrT+PuT $WWULEXWH Nr (compulsory) Index (optional) X-Coord (compulsory) Y-Coord (compulsory) 'HVFULSWLRQ Number of the area the polygon was specified for. Range: defined ZoneNr Index number of the polygon point ( 1022). Range: Long Int X-coordinate of the polygon point. Default value: from mouse position Range: Real Y-coordinate of the polygon point. Default value: from mouse position Range: Real
PrT+PuT
7DEOH
Attributes of area boundaries
* Polygons of areas $AREAPOLY:Nr;INDEX;X-Coord;Y-Coord 10;1;45.1273;110.3258 10;2;45.0000;54.0000 10;3;85.0000;54.0000 10;4;85.0000;107.0000 20;1;85.0000;54.0000 20;2;145.0000;45.0000 20;3;146.0000;87.0000 *...etc.
7DEOH
AREAPOLY table in the network file
15-43
Network file

&HQVXV 3RLQWV
Census points serve for data management and display of counted link data. Census points are independent network objects allocated with reference to the direction to a particular link at a particular position. Several census points can be defined per link. 76\V7\SH PrT+PuT $WWULEXWH Nr (compulsory) Name (optional) Code (optional) PrT+PuT Type (optional) FromNodeNr (compulsory) FromNodeCode (optional) FromNodeName (optional) ToNodeNr (compulsory) ToNodeCode (optional) ToNodeName (optional) 'HVFULSWLRQ Number of census point. default: max. CPNr+1 range: 1-999999999 Name of census point. default: empty string range: Text50 Code of census point. default: empty string range: Text8, no number as first character Type of census point. default: 0 range: 00 - 99 Number of the FromNode of a link. default: selected with mouse range: defined node numbers Code of the FromNode of a link. Name of the FromNode of a link. Number of the ToNode of a link. default: selected with mouse range: defined node numbers Code of the ToNode of a link. Name of the ToNode of a link.
PrT+PuT
PrT+PuT
PrT+PuT
PrT+PuT PrT+PuT
15-44
Network file
76\V7\SH PrT
$WWULEXWH TextShift (optional)
'HVFULSWLRQ Place census point label at census point (=0) or shift label position (=1). default: 0 range: 0=no, 1=yes X-Coordinate. default: from mouse position range: Real Y-Coordinate. default: from mouse position range: Real Relative position of census point on link (0.0 ... 1.0). default: 0 range: 0-1 AddValue1. range: Long Int AddValue2. range: Long Int AddValue3. range: Long Int AddValue4. range: Long Int AddValue5. range: Long Int Number of link. range: 1-999999999
PrT
TextX-Coord (optional) TextY-Coord (optional) RelPos (optional)
PrT
PrT
PrT PrT PrT PrT PrT PrT 7DEOH
AddVal1 (optional) AddVal2 (optional) AddVal3 (optional) AddVal4 (optional) AddVal5 (optional) LinkNr (optional)
Attributes of census points
* Census points $CENSUSPOINT:Nr;FROMNODE;TONODE;NAME;CODE;TYPE;RELPOS;TEXTSHIFT; TextX-Coord;TextY-Coord;ADDVAL1;ADDVAL2;ADDVAL3;ADDVAL4;ADDVAL5 1;11;41;Censuspoint 1;CP1;0;0.2640;1;93.4415;84.1182;1300;350;0;0;0 2;41;11;Censuspoint 2;CP2;0;0.7510;1;83.1758;105.2464;1500;370;0;0;0
7DEOH
CENSUSPOINT table in the network file
15-45
Network file

([DPSOH RI D 9,680 QHWZRUN ILOH
$VISION $VERSION:VersNr;FileType;Language 1.0;Net;E * * 03/10/00 *FileInfo $INFO:TEXT Manual network $ * Scale and Time format * Time specifications * 00:06:30 -> 6 min 30 sec * 00:06.30 -> 6 min 30 sec * 06:30 -> 6 hours 30 min * 06.30 -> 6 min 30 sec * 6 -> 6 min, if Time format = Minutes * 6 -> 6 sec, if Time format = Seconds $NETPARA:SCALE;TIMEFORMAT;DECIMALPLACES 200.00;Sec;4 * * List of Transport Systems * Transport system type specification: * PR for PrT * PU for PuT * PW for PuT-WalkLink $TSYS:TSysCode;TSysName;TSysMode;TSys-v;PCU B;T_Bus;PU;50;1.000 Z;T_Rail;PU;50;1.000 F;T_Walk link;PW;4;1.000 P;T_Car;PR;200;1.000 L;T_HGV;PR;100;2.000 * * List of modes $MODE:CODE;NAME;TSysCode P;M_Car;P L;M_HGV;L O;M_PuT;BZF * * List of demand segments $DEMANDSEGMENT:CODE;NAME;MODE;OCCRATE X;D_Car (business);P;1.000 P;D_Car (private);P;1.000 L;D_HGV ;L;1.000 Z;D_PuT;O;1.000 * * List of node types 0-99 $NODETYPE:TYPE;NAME * * List of nodes $NODE:Nr;CODE;NAME;TYPE;X-Coord;Y-Coord;STOP;STOPCOST1;STOPCOST2;STOPCOST3 10;A;A village;1;50.0000;100.0000;1;0.0000;0.0000;0.0000 11;A;A stop;10;75.0000;100.0000;1;0.0000;0.0000;0.0000 12;;;0;50.0000;50.0000;0;0.0000;0.0000;0.0000 20;CS;Central station;1;75.0000;75.0000;1;0.0000;0.0000;0.0000 21;;;10;75.0000;50.0000;0;0.0000;0.0000;0.0000 30;B;B village;1;100.0000;50.0000;1;0.0000;0.0000;0.0000 31;;;10;125.0000;50.0000;0;0.0000;0.0000;0.0000
15-46
Network file
40;X;X town;1;125.0000;75.0000;1;1000.0000;0.0000;0.0000 41;;;10;125.0000;100.0000;0;0.0000;0.0000;0.0000 50;T50;Tarifknoten;50;100.0000;75.0000;0;0.0000;0.0000;0.0000 * * List of zones $ZONE:Nr;NAME;TYPE;X-Coord;Y-Coord;PERC_O(PR);PERC_D(PR);PERC_O(PU);PERC_D(PU) 100;A village;2;50.3655;105.8924;0;0;0;0 200;X town;2;137.6857;75.0155;0;0;0;0 300;B village;0;99.8857;44.1435;0;0;0;0 400;C village;0;62.2794;75.1608;0;0;0;0 * * Zonal Boundaries $ZONEPOLY:Nr;INDEX;X-Coord;Y-Coord 100;1;45.0000;115.0000 100;2;55.0000;115.0000 100;3;55.0000;105.0000 100;4;45.0000;105.0000 200;1;130.0000;80.0000 200;2;140.0000;80.0000 200;3;140.0000;70.0000 200;4;130.0000;70.0000 * * List of link types 0-99 $LINKTYPE:Nr;NAME;Cap-PrT;v0-PrT;TSysCode;vMax-PrT(P);vMax-PrT(L);v-PuT(B);vPuT(Z);v-PuT(F);Rank 00;PuT-Walklink;0;4;F;0;0;0;0;4;1 01; PuT-Walklink;0;4;F;0;0;0;0;4;1 * etc. 99;Rail;0;0;Z;0;0;0;60;0;1 * * List of links $LINK:Nr;FROMNODE;TONODE;TYPE;LENGTH;Cap-PrT;TSysCode;v0-PrT;t-PuT(B);t-PuT(Z);tPuT(F);ONEWAY;Cost1-PuTSys(B);Cost2-PuTSys(B);Cost3-PuTSys(B);Cost1-PuTSys(Z);Cost2PuTSys(Z);Cost3-PuTSys(Z) 1;10;11;20;5000;1200;BPL;100;360;0;0;1;0.0000;0.0000;0.0000;0.0000;0.0000;0.0000 1;11;10;20;5000;1200;BPL;100;360;0;0;1;0.0000;0.0000;0.0000;0.0000;0.0000;0.0000 2;11;20;20;5000;1200;BPL;100;360;0;0;1;0.0000;0.0000;0.0000;0.0000;0.0000;0.0000 2;20;11;20;5000;1200;BPL;100;360;0;0;1;0.0000;0.0000;0.0000;0.0000;0.0000;0.0000 3;20;21;20;5000;1200;BPL;100;600;0;0;1;0.0000;0.0000;0.0000;0.0000;0.0000;0.0000 3;21;20;20;5000;1200;BPL;100;600;0;0;1;0.0000;0.0000;0.0000;0.0000;0.0000;0.0000 4;40;50;90;5000;0;Z;0;0;480;0;1;0.0000;0.0000;0.0000;0.0100;0.0000;0.0000 4;50;40;90;5000;0;Z;0;0;480;0;1;0.0000;0.0000;0.0000;0.0100;0.0000;0.0000 * *etc. * * List of link polygons $LINKPOLY:FROMNODE;TONODE;INDEX;X-Coord;Y-Coord * * List of Major Flows $MAJORFLOW:FROMNODE;VIANODE;TONODE * * List of connectors $CONNECTOR:ZONENR;NODENR;Direction;TYPE;LENGTH;PrT-Mode;PuT-Mode;t0-PrT;tPuT;PERC(PR);PERC(PU) 100;10;OD;1;0;1;1;0;0;; 200;40;OD;1;0;1;1;0;0;; 300;30;OD;0;0;1;1;0;0;; 400;20;OD;0;0;1;1;0;0;;
*
15-47
Network file
* List of default values: Turning relations *Types of turning relations 0 not used (default value, if none specified) * 1 to the right * 2 straight * 3 to the left * 4 UTurn * Attention: This time specification always in [sec] $TURNINGSTANDARD:NODETYPE;TURNREL;TURNTYPE;t0-PrT;Cap-PrT ??;??;?;0;99999 1?;++;1;5;10000 1?;++;2;0;10000 1?;++;3;5;10000 1?;+-;1;5;10000 1?;+-;2;5;10000 1?;+-;3;10;1000 1?;-+;1;10;5000 1?;-+;2;15;3000 * *etc. * * List of turning relations $TURNINGRELATION:FROMNODE;VIANODE;TONODE;TSysCode;t0-PrT;Cap-PrT;TYPE 10;11;20;BPL;5;10000;1 11;10;11;PL;0;99999;4 11;20;21;BPL;0;99999;2 20;11;10;BPL;20;1000;3 20;21;30;BPL;5;10000;3 21;20;11;BPL;0;99999;2 40;50;20;BZPL;0;99999;2 * *etc. * *List of operators $OPERATOR:OPNR;OPNAME;Cost1;Cost2;Cost3 1;Railway company;100000.0000;0.0000;0.0000 2;Municipal services;100000.0000;0.0000;0.0000 * *List of vehicle types *RefTime: Year = 0, Day = 1 $VEHICLETYPE:VEHTYPE;VEHNAME;VEHCODE;SEATCAP;TOTALCAP;TSysCode;NUMVEH;KMCOST;HOURCOST ;VEHCOST;REFTIME 1;Bus;Bus;35;90;B;10;1.0000;42.0000;100.0000;1 2;Rail;Rail;200;400;Z;10;5.0000;42.0000;200.0000;1 * * Compounds of a line name $LINID:LINNAMELENGTH;LINVARLENGTH;DIR1CODE;DIR2CODE 6;2;H;R * * List of line variants (= Lines in VISUM-DOS) $SUBLINE:NAME;Variant;Direction;TSysCode;OPNR;LAYOVERT;VEHTYPE BUS1;1;B;B;2;900;1 BUS1;1;F;B;2;900;1 BUS2;1;B;B;2;120;1 BUS2;1;F;B;2;720;1 RAIL;1;B;Z;1;240;2 RAIL;1;F;Z;1;240;2 * * * *
15-48
Network file
* Line route with running times (stop -> stop) $LINEROUTE:NAME;Variant;Direction;INDEX;NODENR;BOARD;ALIGHT;Arr;Dep;LENGTH BUS1;1;B;1;40;1;1;00:00:00;00:00:00;0 BUS1;1;B;2;31;0;0;00:00:00;00:00:00;0 BUS1;1;B;3;30;1;1;00:13:00;00:13:00;10000 BUS1;1;B;4;21;0;0;00:00:00;00:00:00;0 BUS1;1;B;5;20;1;1;00:33:00;00:33:00;10000 BUS1;1;B;6;11;1;1;00:39:00;00:39:00;5000 BUS1;1;B;7;10;1;1;00:45:00;00:45:00;5000 BUS1;1;F;1;10;1;1;00:00:00;00:00:00;0 BUS1;1;F;2;11;1;1;00:06:00;00:06:00;5000 BUS1;1;F;3;20;1;1;00:12:00;00:12:00;5000 BUS1;1;F;4;21;0;0;00:00:00;00:00:00;0 BUS1;1;F;5;30;1;1;00:32:00;00:32:00;10000 BUS1;1;F;6;31;0;0;00:00:00;00:00:00;0 BUS1;1;F;7;40;1;1;00:45:00;00:45:00;10000 * *etc. * * List of line services $LINETIMETABLE:NAME;Variant;Direction;INDEX;Dep;HEADWAY;LASTDEP;VEHTYPE;VehRunNr BUS1;1;B;1;06:20:00;00:40:00;18:20:00;0;0 BUS1;1;F;1;06:00:00;00:40:00;18:00:00;0;0 BUS2;1;B;1;06:20:00;00:40:00;18:20:00;0;0 BUS2;1;F;1;06:35:00;00:40:00;18:35:00;0;0 RAIL;1;B;1;06:45:00;00:40:00;18:45:00;0;0 RAIL;1;F;1;06:25:00;00:40:00;18:25:00;0;0 * * Cost parameters for links * Type 0 Depreciation * Type 1 Running cost * Type 2 Charge for usage $COSTLINK:Nr;TYPE;NAME;NUMYEARS;INTEREST;REFTIME;REFLENGTH 1;2;Track cost;;;;1 2;1;;;;0;0 3;2;;;;;0 * *List of tariff subzones $TSZ:Nr;TYPE;CODE;NAME 110;1;TSZ110;TSZ110 111;1;TSZ111;TSZ111 120;1;TSZ120;TSZ120 130;1;TSZ130;TSZ130 150;1;TSZ150;TSZ150 230;1;STZ230;TSZ230 240;1;TSZ240;TSZ240 250;1;TSZ250;TSZ250 * *Allocations of stops/nodes to tariff subzones $STOPTOTSZ:TSZNR;STOPNR 110;10 111;11 120;20 130;30 150;50 230;30 240;40 250;50 * *
15-49
Network file
*List of tariff zones $TZ:Nr;TYPE;CODE;NAME 100;1;TZ100;TZ100 200;1;TZ200;TZ200 * *Allocation of tariff zones to tariff subzones $TZTOTSZ:TZNR;TSZNR 100;110 100;111 100;120 100;130 100;150 200;230 200;240 200;250 * * List of ticket types $TICKETTYPE:Nr;NAME;ZTARIFF;DTARIFF;SUPPLFAC;UTILITYRATE 1;One-way ticket;1;0;1.0000;1.0000 2;multiple-trip ticket;1;0;1.0000;1.0000 3;Monthly pass;1;0;1.0000;40.0000 * * List of dist.-based tariffs $FARE_BY_DIST:TICKETNR;DISTANCE;FARE * * List of zone-based tariffs $FARE_BY_ZONE:TICKETNR;NUMTSZ;NUMTZ;FARE 1;1;0;1.0000 1;2;0;1.0000 1;0;1;2.0000 1;0;2;3.0000 2;1;0;0.8000 2;2;0;0.8000 2;0;1;1.6000 2;0;2;3.2000 3;0;1;40.0000 3;0;2;80.0000 * * List of TSys-spec. supplements $FARE_SUPPL:TSysCode;SUPPLEMENT;Rank;DISTSUPP B;0.0000;1;0 Z;3.0000;2;1 * * List of areas $AREA:Nr;NAME;TYPE;X-Coord;Y-Coord 100;TZ100;0;90.0000;110.0000 200;TZ200;1;135.0000;110.0000 * * Polygons of areas $AREAPOLY:Nr;INDEX;X-Coord;Y-Coord 100;1;100.0000;40.5000 100;2;100.0000;117.0000 100;3;40.0000;117.0000 100;4;40.0000;40.5000 200;1;100.0000;40.5000 200;2;147.1054;40.5112 200;3;147.1054;116.9103 200;4;100.0000;117.0000 * *
15-50
Network file
* Census points $CENSUSPOINT:Nr;FROMNODE;TONODE;NAME;CODE;TYPE;RELPOS;TEXTSHIFT; TextX-Coord;TextY-Coord;ADDVAL1;ADDVAL2;ADDVAL3;ADDVAL4;ADDVAL5 1;11;41;Censuspoint 1;CP1;0;0.2640;1;93.4415;84.1182;1300;350;0;0;0 2;41;11;Censuspoint 2;CP2;0;0.7510;1;83.1758;105.2464;1500;370;0;0;0 $
15-51
Network file

,GHQWLI\LQJ HUURUV
9HULI\LQJ QHWZRUN FRQVLVWHQF\
&$/&8/$7(PHQX &+(&.1(7:25. &KHFN QHWZRUN GLDORJ
2YHUYLHZ RI FKHFNLQJ SURFHGXUHV During network verification, the following items are checked: ,VRODWHG QRGHV: Identification of nodes with no connection to a link. 1RGHV ZLWK PRUH WKDQ OHJV: Identification of nodes with more than six links, as these cannot be graphically displayed correctly as node flows. =RQHV ZLWKRXW 3U7 FRQQHFWRUV: Identification of zones with no PrT connection to the network. 3U7 WXUQLQJ UHODWLRQV: Identification of PrT turning relations which have been opened for a transport system, although this is blocked for the )URP/LQN and 7R/LQN. Select transport systems for which a check is to be performed with the 76\VWHPV button
15-52
Network file
1HWZRUN FRQVLVWHQF\ 3U7: Identification of PrT origin and destination relations for the selected transport system (76\VWHPV button), for which no route can be found. 'HDGHQG URDGV 3U7: Identification of dead-end roads with no connection to the selection of transport systems (TSystems button) without U-Turn or without two-way traffic. /LQNV ZLWKRXW VXFFHHG OLQN: Identification of links with no connection to the selection of transport system (TSystems button) and with no succeeding link. =RQHV ZLWKRXW 3X7 FRQQHFWHUV: Identification of zones with no PuT connection to the network. 3X7 FRQQHFWRUV QRW YLD VWRS: Identification of PuT connectors leading to a node which is not a stop. 1R OLQHV GHSDUW IURP 3X7 FRQQ QRGHV: Identification of PuT connectors, from which no line departs. 3X7 ZDON OLQNV ZLWK WLPH time = 0 : Identification of PuT walk links with
6XEOLQHV ZLWKRXW WLPHWDEOH: Identification of sublines which have no timetable. Individually via selecting or o clearing the relevant check box. Collectively via the $OO 21 button. Via ([FO button: selecting the required check box and simultaneously clearing all other check boxes.
6HOHFWLRQ RI FKHFNLQJ SURFHGXUHV
9HULI\ EXWWRQ After the checking procedures have been selected, clicking the 2. button performs verification of network consistency and saves the error report in the error file indicated:
15-53
Network file
'LVSOD\LQJ DQG FRUUHFWLQJ HUURUV &KHFN QHWZRUN GLDORJ
'LVSOD\LQJ HUURUV After completion of network verification, the results of the check are displayed for the individual verification options selected: RN button: No errors found. button: Error found
&RUUHFWLQJ HUURUV button opens a dialog box displaying a description of the error found for the verification option concerned and a proposal for immediate error correction.
15-54
Network file
Example warning:
These turning relations can subsequently be blocked for the selected transport system(s)
15-55
Network file
$GGLWLRQDO YHULILFDWLRQ RI QHWZRUN FRQVLVWHQF\ IRU OLQHV If the network contains sublines of a line, which are served by different transport systems, an error correction dialog box is automatically displayed:
0HQX ),/( 23(1 1HWZRUNV &KHFN QHWZRUN /LQHV WUDQVSRUW V\VWHPV GLDORJ
&RUUHFWLQJ HUURUV The error can be eliminated in three ways: delete all sublines of the line concerned, keep the sublines of a selected transport system only, assign new line names.
This dialog box is automatically displayed when opening a version file saved from an inconsistent network version.
15-56
Opening and saving network file
2SHQLQJ DQG VDYLQJ QHWZRUN ILOH
5HDGLQJ QHWZRUN ILOH

2SHQLQJ HQWLUH QHWZRUN ILOH
0HQX ),/( 23(11HWZRUNV 2SWLRQV 5HDG QHWZRUN 5HDG QHWZRUN
'LVSOD\ PHVVDJHV RQ VFUHHQ. 'LVSOD\ HUURU PHVVDJHV RQ VFUHHQ. By switching off the display of messages and error messages on screen, the file loads more quickly. Network errors and warning messages can still be read, as they are recorded in the error.lst error file. o 5HDG QHWZRUN ILOH DGGLWLRQDOO\ Standard procedure for opening entire network file.
15-57

5HDG QHWZRUN ILOH DGGLWLRQDOO\

0HQX ),/( 23(11HWZRUNV ILOH W\SH Option 5HDG QHWZRUN ILOH DGGLWLRQDOO\ The various network tables including their network objects can be read selectively to supplement the current network. 5HDG QHWZRUN GDWD DGGLWLRQDOO\ GLDORJ
1HWZRUN REMHFWV WDEOHV The check boxes allow selective reading of individual network file tables to supplement the active network Table will be read, o Table will not be read. The 6ZLWFK DOO WDEOHV 21 and 6ZLWFK DOO WDEOHV 2)) buttons simplify the selection or exclusion of individual tables: after all tables are switched off: targeted selection of individual tables. After all tables switched on: targeted exclusion of specific tables.
15-58
,I DOUHDG\ GHILQHG When dealing with existing tables for the active network, the following options are available: LJQRUH: the network table is skipped, i.e. the existing network objects in the table remain unchanged. RYHUZULWH: the network table is replaced by the network table being added, i.e. the existing network objects in the table are overwritten. FDQFHO: the reading process is cancelled. DGG (only in the case of Timetables): the timetable of existing lines can be supplemented in that any new vehicle trips are added to the 9HK7ULS table. For tables which can be selected with , but for which the option ,I DOUHDG\ GHILQHG WKHQ is not available, then: existing attribute values are overwritten by the data being added (e.g. file information, link types). The entries for Netpara table, TSys (T6\V&RGH, 76\V1DPH, 76\V0RGH) table and LinId table must be identical in both network files and are thus only verified, but not added. The new network tables Mode and Demandsegment, now available with VISUM 7.00, are ignored during the reading process. If different data exists for the attributes Netpara table: time format, and TSys table: TSys_v, private car units, VISUM uses the values taken from the network file being added.
15-59

5HDGLQJ D QHWZRUN ZLWK LQFRPSOHWH OLQH URXWHV
When reading a network with incomplete line routes - i.e. with at least one missing or blocked link for a subline the following dialog box Is displayed: 5HDG QHWZRUN &RPSOHWH LQFRPSOHWH OLQH URXWH GLDORJ
VISUM offers the following solutions: Do not insert line, Permit link or insert link of type [1..99] or Search for shortest route. 3DUDPHWHUV IRU VKRUWHVW URXWH VHDUFK On the basis of the search criteria specified: link length, direct distance link length between FromNode and ToNode, time/link (running time of transport system; calculated from the speed of the transport system specified by the user for the link concerned) or time from speed of link type (standard running time of the transport system; calculated from the standard speed of the transport system specified by the user for the link type concerned), it is possible to determine whether blocked links and turning relations are to be considered or not.
G
15-60
When adding networks from DOS VISUM PuT, the option &RQVLGHU EORFNHG WXUQLQJ UHODWLRQV must be cleared.
In the event that no shortest route is found, or the length of the shortest route found exceeds the direct distance between the two nodes by the indicated factor (standard value: 2.00), a decision can be made once again not to insert a line, only to insert a line if the link concerned can be permitted for the transport system or to insert a line anyway; and, if necessary, to insert a link of the type indicated [1..99].

7LPHWDEOH XSGDWH
The timetable update functionality allows to read new timetable data to a VISUM network while maintaining existing line route data. Usually timetable data from vehicle and crew scheduling systems do not contain details of the line route between two stops. In this case VISUM suggests a line route calculated by a shortest path search. As manual refining and correction of line routes is very time-expensive the original line route data should be kept unchanged when adding new timetables to an outdated VISUM network. ([DPSOHV RQ LQFOXGLQJ H[LVWLQJ OLQH URXWHV
Result of automatic routings for TSys Bus Line route from recent timetable period modified manually for Bus1 Recent Bus1 line route data are used for all sublines of new Bus1 Line routes of new bus lines are specified according to old line route of Bus1
+
Bus1-1 Bus1-1 Bus1-2
Bus2-1
1100m
1000m
+
VSys Bus
15-61
$SSURDFK
Add network or version with lines of outdated timetable period. File menu - OPEN 1HWZRUNV file type Option 5HDG QHWZRUN ILOH DGGLWLRQDOO\ 5HDG QHWZRUN GDWD DGGLWLRQDOO\ GLDORJ
Reading network additionally with lines of the new timetable period: Select from VXEOLQHV, VXEOLQH URXWHV and WLPHWDEOHV tables. 'HOHWHXVH OLQH QHWZRUN GLDORJ
8VH OLQH URXWHV RI H[LVWLQJ OLQHV IRU OLQH URXWLQJ: the existing line routes are considered during reading process and, if necessary, deleted after reading.
15-62
6DYLQJ QHWZRUN ILOH
0HQX ),/( 6$9( 1HWZRUNV 2SWLRQV 6DYH QHWZRUN GLDORJ
7LPH IRUPDW 6HFRQGV: save time references in seconds. 0LQXWHV: save time in minutes; warning message:
15-63
)LOH IRUPDW The network can be saved in four formats: 6WDQGDUG IRUPDW format of the integrated network version. 8VHUGHILQHG: selection of the network tables which are to be saved to the network file: Due to the possibility of saving individual network tables, the line data of a planning scenario can be saved to a separate file, for example, so as to add them to a network again later. Same method as that for reading a network file additionally (see Ch. 15.2.1.2). 3U7 IRUPDW: Interface to preceding versions for PrT (WindowsVersion 5.xx and DOS versions 4.xx; see Ch. 15.3.1). 3X7 IRUPDW: Interface to preceding versions for PuT (DOS Version 4.5; see Ch. 15.3.2).
The dialog box "Options (Save network)" can also be opened in the following way: EXTRAS menu - OPTIONS. Dialox box "Options (trace file, error file)": 6DYH QHWZRUN button.
15-64
Network file interfaces
1HWZRUN ILOH LQWHUIDFHV
Files in ASCII format can generally be exchanged. The import/export of binary files - e.g. version files and graphic parameters files - is not supported.
,QWHUIDFH WR SUHYLRXV YHUVLRQV RI 9,680 3U7

1HWZRUN LPSRUW IURP 9,6803U7 '26 YHUVLRQV DQG :LQGRZV 9HUVLRQ [
0HQX ),/(23(1 1HWZRUNV Network files from VISUM-PrT can be read directly. 5HDG 1HWZRUN 9,6803U7 2SWLRQV GLDORJ
15-65
The result of the network check can be recorded in the fehler.lst error file. &UHDWH HUURU ILOH in the "2SWLRQV WUDFH ILOH HUURU ILOH dialog box via OPTIONS in the EXTRAS menu. &RQQHFWRUV The definition is different than in previous versions. Previously, zones were connected via links, now they are connected via nodes. The conversion from VISUM-PrT is carried out as follows: 7LPH is accepted 3HUFHQWDJHV (if available) are accepted. If the zone is connected to two or more links via the same node, the percentages are summed up. Link information is lost. The connector length is determined from the direct distance using node and zone co-ordinates. Capacities are not evaluated. /LQNV Y%LF\FOH is skipped. Y&DU becomes Y3U7. 7XUQLQJ UHODWLRQV During conversion, turns for all transport systems are opened. /LQN ODEHOV Link labels which have been switched off (no display) or shifted to another position in a VISUM-DOS version (VISUM-PrT Version 4.6) may be read using macro commands: In DOS-VISUM-PrT: Use the macro command StrT_Mak to generate a macro file; with the commands StrT_Aus and StrT_Pos all shifted and switched off link labels are recorded. Activate this macro file in VISUM to modify standard link label display and positions according to the recorded commands StrT_Aus and StrT_Pos. Otherwise this information would get lost, as binary data files (graphics parameters and network versions) generated with a VISUM-DOS version cannot be read in VISUM.
15-66
1HWZRUN H[SRUW WR 9,6803U7 '26 YHUVLRQV DQG :LQGRZV 9HUVLRQ [
0HQX ),/( 6$9( 1HWZRUNV 2SWLRQV 6DYH QHWZRUN GLDORJ Select data format: "3U7IRUPDW 9HUVLRQ . 2SWLRQV IRU 6DYH 1HWZRUN XS WR 9LVXP 3U7 GLDORJ
&RQQHFWRUV Percentages are lost. So that connecting via links proves successful, all links with FromNode y are connected. Connectors carry no information on capacities. 7XUQLQJ UHODWLRQV Transport system-specific information is lost. A turning prohibition exists if all PrT-transport systems are blocked. /LQNV Bicycle speed cannot be saved.
15-67
,QWHUIDFH SUHYLRXV YHUVLRQV RI 9,680 3X7

The following network objects and tables can be converted using the interface: Transport systems Nodes (stops) Links Link polygons Zones Zone boundaries Connectors Global zones Global zone polygons Assignment of zones to global zones Sublines Line routes Line trips (timetable).
1HWZRUN LPSRUW IURP 9,6803X7 '26 YHUVLRQV KLJKHU WKDQ
In VISUM-PuT 4.5: Data export with >+0HQ@>1HWZ@>([S9@ In VISUM: Menu FILE - OPEN 1HWZRUNV. 76\V&RGH In contrast to VISUM-PuT, transport systems are now longer specified via the number, but rather via the TSysCode (1 character A..Z or 0..9). Therefore, the correct identifiers must be set in an input mask before exporting. ([SUHVV OLQNV The integrated VISUM version no longer uses express links. For network export from VISUM-PuT, the express links are represented via the line route with traversed nodes (stops). /LQN SRO\JRQV VISUM-PuT saves link polygons for both directions. When reading, this produces the error &RXUVH IRU RSSRVLWH GLUHFWLRQ DOUHDG\ VSHFLILHG /LQH ZLOO EH VNLSSHG This warning can be ignored.
15-68
&ORVHG WXUQLQJ UHODWLRQV Do not accept prohibited turning relations when reading a network with incomplete line route data: Call up OPTIONS in the EXTRAS 5HDG QHWZRN &RPSOHWH LQFRPSOHWH OLQH URXWH dialog box and disable the option o &RQVLGHU EORFNHG WXUQLQJ UHODWLRQV.
/LQN ODEHOV Link labels which have been switched off (no display) or shifted to another position in a VISUM-DOS version (VISUM-PuT Version 4.51 and higher) may be read using macro commands: In DOS-VISUM-PuT: Use the macro command StrT_Mak to generate a macro file; with the commands StrT_Aus and StrT_Pos all shifted and switched off link labels are recorded. Activate this macro file in VISUM to modify standard link label display and positions according to the recorded commands StrT_Aus and StrT_Pos. Otherwise this information would get lost, as binary data files (graphics parameters and network versions) generated with a VISUM-DOS version cannot be read in VISUM.
1HWZRUN H[SRUW WR 9,6803X7 '26 YHUVLRQV KLJKHU WKDQ
SAVE 1HWZRUNV in the FILE menu. 2SWLRQV 6DYH QHWZRUN GLDORJ ER[ Select file format: "3X7IRUPDW LQWHUIDFH WR YHUVLRQ .
Direct reading in VISUM-PuT via the "[HMen] [Netw][Read] command. The integrated VISUM version supports spaces in the line name such as "L 30". VISUM-PuT, however, removes all spaces when reading (L 30 becomes L30). Information on PrT-transport systems, link types, etc. are lost when exporting to VISUM-PuT.
15-69
9,66,0 ([SRUW LQWHUIDFH

VISSIM input files (*.inp) are generated via the VISSIM export interface, in order to be able to perform a microscopic simulation of the traffic flow for PrT and PuT with VISSIM.
),/( PHQX 6$9( 9,66,0 QHWZRUN Export of network file as VISSIM input file. Activate check box to select particular VISSIM data, e.g. VISSIM links VISSIM parking lots etc.
$FFHVV GDWDEDVH LQWHUIDFH IRU QHWZRUN ILOHV

This database interface can be used to import VISUM network data from an Access database or export to an Access database. ([SRUW WR GDWDEDVH
),/( PHQX '$7$%$6( (;3257 'LDORJ 2SWLRQV 6DYH QHWZRUN
)LOH IRUPDW 6WDQGDUG IRUPDW: Saves the entire network file as an Access database file (*.mdb). 8VHUGHILQHG: Selective saving of individual network tables as an Access database file (*.mdb). Same method as that for selecting table in Ch. 15.2.2.
([DPSOH RI 9,680 QHWZRUN GDWD LQ DQ $FFHVVGDWDEDVH
,PSRUWLQJ IURP GDWDEDVH
),/( PHQX '$7$%$6( ,03257 2SWLRQV 5HDG QHWZRUN
Reading selected network tables additionally (see Ch. 15.2.1.2) is also possible when importing from an Access database.
15-71
,QWHUIDFH IRU DWWULEXWH ILOHV

The attribute interface serves for attribute data transfer between two VISUM networks or between VISUM and another program (see Ch. 10.1.5).
Data exchange can be performed: via attribut files (*.att): data are saved to an ASCII file in CSV format which can be read by VISUM, spread sheet or data base programs. via Windows clipboard: data are offered via the clipboard and can be imported directly into another VISUM network or other programs.

'DWD WUDQVIHU YLD DWWULEXWH ILOH

6DYH DWWULEXWH GDWD ILOH Menu LISTINGS, Submenu FILE - SAVE ATTRIBUTES ([DPSOH OLQN DWWULEXWH ILOH
$VISION $VERSION:VersNr;FileType;Language 1.0;Att;E * $+LINK:Nr;FROMNODE;TONODE;TYPE;LENGTH;Cap-PrT;Cap-PuTSeat;Cap-PuT-Seat/TI;VolVeh-Pr;v0-PrT;ONEWAY 1;10;11;20;5000;1200;665;665;5250;100;1 1;11;10;20;5000;1200;665;665;5250;100;1 2;11;20;20;5000;1200;665;665;5250;100;1 2;20;11;20;5000;1200;665;665;5250;100;1 3;20;21;20;5000;1200;665;665;7000;100;1 3;21;20;20;5000;1200;665;665;7000;100;1 4;40;50;90;5000;0;3800;3800;0;0;1 4;50;40;90;5000;0;3800;3800;0;0;1 *etc.
5HDG DWWULEXWH ILOH in VISUM: MENU FILE - OPEN -$WWULEXWHV. other programs: use CSV format.
For reading and saving attribute files see Ch. 10.1.5.
15-72

'DWD WUDQVIHU YLD FOLSERDUG

7UDQVIHU DWWULEXWH GDWD LQWR FOLSERDUG MENU LISTINGS, SUBMENU FILE - ATTRIBUTE INTO CLIPBOARD. 5HDG DWWULEXWH GDWD IURP FOLSERDUG in VISUM via Menu EDIT - INSERT FROM CLIPBOARD. other programs: Use the ,QVHUW function.
([DPSOH ([SRUWLQJ GDWD WR ([FHO
Select 7DEVWRS for data transfer to ([FHO.
Decimal points are adopted to current settings in Clipboard. A header is generated automatically, which is required by VISUM for "Read data from file".
15-73
,QWHUIDFH WR WLPHWDEOH DQG VWDII VFKHGXOLQJ V\VWHPV

Various manufacturers of timetable and staff scheduling systems (TSS systems) provide a direct interface for importing up-to-date digital timetable data into VISUM: INTERPLAN, PTV AG, Karlsruhe, DIVA, Mentz Datenverarbeitung GmbH, Munich MICROBUS, IVU Traffic Technologies AG, Berlin VIRIATO, SMA & Partner AG, Zurich.
This interface generates a VISUM network file in the ASCII format or the Access format (VIRIATO), which usually contains the following tables: TIMETABLE PERIOD (period of validity) ANNUAL TIMETABLE (traffic limitations)
When transferring data from TSS systems to VISUM, please consider the following: At present, VISUM does not recognize traffic days. A VISUM network version always consists of the traffic supply for one day. When importing the timetable data from the TSS interface, the VISUM user can select a traffic day. Some TSS systems subdivide stops in stopping points. As the VISUM network model only contains stops, any existing stopping points must be transferred in aggregated form. Some TSS systems do not contain coordinates for stops and nodes. In this case, VISUM once generates a network model with nodes (including coordinates) and links. Only line and timetable data are then imported from the TSS system. New stops must be inserted in both systems. TSS systems usually do not reflect the link network, i.e. the exact line route between two stops is not known. In this case, VISUM proposes a line route based on a best route search.
$WWULEXWH FirstDay (compulsory) LastDay (optional) 7DEOH
'HVFULSWLRQ First day of timetable period Range: dd.mm.yyyy Last day of timetable period Range: dd.mm.yyyy Attributes of a timetable period
15-74
$WWULEXWH AKey (compulsory) AKeyCode (compulsory) AKeyText (optional) 7DEOH $WWULEXWH Name (compulsory) Variant (compulsory) Dir (compulsory) Dep (compulsory) VehType (optional) OpNr (optional) BlockNr (optional) '.H\ RSWLRQDO $.H\ RSWLRQDO 7DEOH
'HVFULSWLRQ Key for annual timetable Range: Text20 Hexadecimal number describing the operating days in the annual timetable Range: Text100 Key text for annual timetable Range: Text255 Attributes of the annual timetable
'HVFULSWLRQ Name of line. Range: definierter Linienname Name of line variant. Range: definierte Linienvariante Direction of subline (e.g. I=Inbound, O=Outbound). Range: defined directions Departure time at start terminal or first departure of fixed-rhythm headway time interval. Range: time Number of vehicle type. Range: defined vehicle type Number of operator. Range: defined operator. Number of vehicle block the service belongs to. Range: Long Int 'DLO\ NH\ 0RQGD\ 6XQGD\ 5DQJH $QQXDO NH\ UHIHUV WR $QQXDO7LPHWDEOH 5DQJH 7H[W Attributes of a vehicle trip
*... * Diva-parameters $TIMETABLEPERIOD:FirstDay;LastDay 24.09.1998;01.06.1999 * $ANNUALTIMETABLE:YKEY;YKEYCode;YKEYText JFP000000;FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFF;"daily" JFP000001;7C5CF9F3E6CF9F3E7A7CF9F0E3CF9F3E7CF9F3E793E7CF9F3C3CF9F333E74F8F000000000000000000 000000000000000000; Monday Friday JFP000003;0202040810204081010204081000408102040810081020408102040808102040800000000000000000 000000000000000000; Saturday JFP000004;80A1020409102040808102070C302040810204080408102042C1020444089030000000000000000000 000000000000000000; Sunday * * List of services $VehTrip:NAME;Variant;Direction;INDEX;Dep;Head;LastDep;VehType;BlockNr;YKey BUS1;1;H;1;06:10:00;;;0;0;JFP000000 BUS1;1;H;2;06:55:00;;;0;0;JFP000001 BUS1;1;H;3;07:25:00;;;0;0;JFP000000 BUS1;1;R;1;06:20:00;;;0;0;JFP000000 BUS1;1;R;2;07:05:00;;;0;0;JFP000001 BUS1;1;R;3;07:45:00;;;0;0;JFP000000 Train;1;H;1;06:25:00;;;0;0;JFP000000 Train;1;H;2;07:05:00;;;0;0;JFP000002 Train;1;H;3;07:45:00;;;0;0;JFP000000 Train;1;R;1;06:45:00;;;0;0;JFP000000 Train;1;R;2;07:25:00;;;0;0;JFP000002 Train;1;R;3;08:05:00;;;0;0;JFP000000 $
7DEOH
Tables TimetablePeriod, AnnualTimetable, VehTrip
7LPHWDEOH GDWD LPSRUW IURP *HUPDQ ) ' V\VWHPV
),/( PHQX 23(1 1HWZRUNV Import network file. 6HOHFWLRQ RI RSHUDWLQJ GD\V GLDORJ Select operating days by marking: all vehicle trips are opened which run on the selected operating days.
15-76
Matrix files
0DWUL[ ILOHV
VISUM manages 2'PDWULFHV which contain the demand data (number of trips between zones) and calculates ,QGLFDWRU PDWULFHV which contain indicators related to O-D relations (e.g. journey time). In addition to the O-D-matrices for PuT, a WHPSRUDO GLVWULEXWLRQ RI SDVVHQJHUV SDWWHUQ ILOH can be opened, which contains the temporal distribution of PuT-demand.
0DWUL[ ILOH IRUPDWV
$6&,, IRUPDWV RI PDWUL[ ILOHV Matrices in ASCII format generally have the following data structure: Format code in the first line, e.g. $VMN;d2 $V for standard format, one or more options (R, M, N), number of decimal places (if > 0) mode identifier (or activity identifier) additional information (time interval and factor)
File header according to the chosen options, i.e. with or without
The data block is described later for each format. Comment lines are permitted in the header as well as in the data block, must begin with *, are skipped by the program.
15-77
Matrix files
&RGH )RUPDW FRGHV 9 2 7 $6&,, DQG % 9 2 7 % Standard VISUM Format (Nr of zones x Nr of zones) Individual relations (OrigZone, DestZone, matrix value > 0) Partial V-Format, contains only selected zones Binary format (saves memory and input/output time) X X X X X X X
G
1
2SWLRQDO PDWUL[ IRUPDW FRGHV These options are provided for all ASCII formats and can be combined with each another.
&RGH 2SWLRQDO IRUPDW FRGHV File header does not contain the following data specified time interval for which the matrix is valid, and factor. File format code without N: Time interval and factor are included in the matrix file header. 0 File header with specification of the number of the transport modes, and/or the activity, for which the matrix is valid. File format code without M: File header without identifier for transport mode or activity. 5 Matrix values are randomly rounded (RandomRound). File format code without R: Values are arithmetic or not rounded (if corresponding number of decimal places was chosen).
15-78
Matrix files
Input/output of a 1XPEHU RI ]RQHV! [ 1XPEHU RI ]RQHV! PDWUL[ with total number of zones (lines/columns), zone numbers, origin value per line (origin zone) and destination value per column (destination zone). The standard format is $VM (with transport mode identifier, time and factor). The data formats are compatible for VISUM, MUULI and VISEM. The following data formats are saved under Windows: 915 UDQGRP URXQG
$VNR * Number of zones 3 * Zone numbers 10 20 30 * 13 15 19 * 10 8 2 2 4 * 20 15 4 5 6 * 30 24 7 8 9 * 47
90 LQWHUY PRGH IDFWRUDULWKP

$VM * Transport mode 0 * Time interval 0.00 24.00 * Factor 1 * Number of zones 3 * Zone numbers 10 20 30 * 13 16 19 * 10 9 2 3 4 * 20 15 4 5 6 * 30 24 7 8 9 * 48
9 ZLWKRXW GHF SODFHV DULWKP

$V * Time interval 0.00 24.00 * Factor 1 * Number of zones 3 * Zone numbers 10 20 30 * 13 16 19 * 10 9 2 3 4 * 20 15 4 5 6 * 30 24 7 8 9 * 48
901 ZLWK GHFLPDO SODFHV

$VMN;D2 * Transport mode 0 * Number of zones 3 * Zone numbers 10 20 * 12.50 15.50 18.50 * 10 7.50 1.50 2.50 * 20 15.00 4.00 5.00 6.00 * 30 24.00 7.00 8.00 * 46.50
30
3.50
9.00
15-79
Matrix files
Input-output of the individual relations with unformatted specification of origin zone, destination zone, matrix value origin zone, destination zone, matrix value... Open matrix: Letter O and digit 0 are read as the same. The zone numbers of the relations must not be sorted in ascending order. Relations with value = 0 are not saved on file, but can be contained in an input file in format $O.
$OM;D2 * Mode dentifier 0 * Time interval 0.00 24.00 * Factor 1 * Origin Dest. * zone zone 10 10 10 20 10 30 20 10 20 20 20 30 30 10 30 20 30 30 $ON;D1 * Origin * zone 10 10 10 20 20 20 30 30 30 Dest. zone 10 20 30 10 20 30 10 20 30 $OMNR * Mode 0 * Origin Dest. * zone zone 10 10 10 20 10 30 20 10 20 20 20 30 30 10 30 20 30 30 $O * Time interval 0.00 24.00 * Factor 1 * Origin Dest. * zone zone 10 10 10 20 10 30 20 10 20 20 20 30 30 10 30 20 30 30
Nr. of trips 1.50 2.50 3.50 4.00 5.00 6.00 7.00 8.00 9.00 Nr. of trips 1.5 2.5 3.5 4.0 5.0 6.0 7.0 8.0 9.0
Nr. of trips 2 2 4 4 5 6 7 8 9
Nr. of trips 2 3 4 4 5 6 7 8 9
2' PDWUL[
15-80
Matrix files
O-D matrices (*.fma) can be saved in the following formats: %LQDU\ IRUPDW 2)RUPDW:, 9)RUPDW:.
([DPSOH RI 2)RUPDW
$O * Time interval the O-D matrix refers to * From Till 00.00 24.00 * Factor: Share of the demand to be assigned to one hour * Factor 1.0 * MeansOfTransportNr 3 * 3 Public transport * 4 Private transport * 100 200 180 100 300 200 100 400 170 100 500 60 100 600 120 200 100 170 200 300 190 200 400 140...
([DPSOH RI 9)RUPDW
$V * From Till 0.00 24.00 * Factor 1.00 * MeansOfTransportNr 4 * 3 Public transport * 4 Private transport * * The O-D relations are listed for each origin zone. * Several lines may be used for listing the demand from an origin zone * to each of the destination zones. * Number of zones 6 100 200 300 400 500 600 * Zon 100 Sum = 910 0 180 200 170 60 120 ... * Zon 600 Sum = 570 20 180 260 100 10 0
15-81
Matrix files
3DWWHUQV RI WHPSRUDO 3X7 GHPDQG GLVWULEXWLRQ

Different patterns of temporal distribution of PuT-demand can be specified in the ASCII passenger distribution file *.fga, and assigned to the origin zones. A pattern of temporal demand distribution specifies the percentage of trips desiring to leave the traffic zone for all time intervals of a given period. ([DPSOH 6WDQGDUG ([DPSOH
Pattern 1 specifies equal distribution for Pattern 1 specifies four half-hour the period of one day and is assigned to intervals (30%-40%-20%-10%) for the all origin zones. period between 7:00 and 9:00 a.m. and This standard passenger volume is is assigned to origin zone 100. created automatically via SAVE 7HPSRUDO Pattern 2 is assigned to origin zone 200. GHPDQG GLVWULEXWLRQ in the FILE menu.
$ * t_From t_Till 0.00 24.00 $ 1 0.00 24.00 -1 1 0 100 -1 $ 10 1 20 1 30 1 40 1 * ...etc. $ $ * t_From t_Till 07.00 09.00 $ 1 07.00 07.30 08.00 08.30 09.00 1 1 0 30 40 20 10 1 2 7.00 9.00 -2 2 0 100 -2 $ 100 1 200 2 * ....etc. $
15-82
Matrix files
,QGLFDWRU PDWULFHV

3X7LQGLFDWRU PDWULFHV
9,680 IRUPDWV PuT-indicator matrices can be saved in the following VISUM formats: %LQDU\ IRUPDW 2)RUPDW:, 9)RUPDW 3DUWLDO9)RUPDW:
The file extensions of the PuT indicator matrices depend on the output indicator, e.g. journey time matrix with the extension *.mrz. See the following example in partial V-format:
$T * Means of Transport Nr * 3 * Time interval 0.00 24.00 * Factor 1.0 * * created with: * Date: * Matrix values: * Network/VersionFile: * Assignment procedure: * Weighting: * Zone numbers Orig. 100 200 -1 * Zone numbers Dest. 100 200 300 400 -1 * 100 0 45 32 12 * 200 45 0 13 17
VISUM Version 7.510 04/30/01 Journey time C:\VISUM7\Eng-750\Manual750_engl.ver Timetable 2 with passengers
How to select O-D relations for matrices in 7 IRUPDW CALCULATE menu ,QGLFDWRU0DWULFHV operation - 3DUDPHWHUV %DVLV : Enter origin zone numbers.
15-83
Matrix files
&69 )RUPDW FRPPDVHSDUDWHG YDOXHV For further data processing the csv format is provided: Select separator: Semicolon, Tab or Blank (matching the spreadsheet program) No format code in file header. The indicators selected for calculation are listed in comment lines. Line 5HODWLRQV consists of OZonNr, DZonNr and the indicator codes.
VISUM saves all calculated indicator data to a *.csv file. Example:

$VISION $VERSION:VersNr;FileType;Language 1.0;Matrix;E * *FileInfo $INFO:TEXT Means of Transport Number 3 Time interval 0.00 24.00 created with: VISUM Version 7.510 saved on: 04/30/01 Network/VersionFile: C:\VISUM7\Eng-750\Manual750_engl.ver Assignment procedure: Timetable 2 Weighted: with passengers $ * Indicators calculated: * JT Journey time * RT Ride time * AT Access time * OWT Origin wait time * IVT In-vehicle-time * WT Walking time * TWT Transfer waiting time * ET Egress time * NT NumTransfers * SF Service frequency $Relations:OZonNr;DZonNr;JT;RT;AT;OWT;IVT;WT;TWT;ET;NT;SF 100;200;45;45;0;0;45;0;0;0;0.0;18 100;300;32;32;0;0;32;0;0;0;0.0;18 100;400;12;12;0;0;12;0;0;0;0.0;18 200;100;45;45;0;0;45;0;0;0;0.0;18 200;300;13;13;0;0;13;0;0;0;0.0;18 .... ....
15-84
Matrix files

3U7LQGLFDWRU PDWULFHV
PrT-indicator matrices are saved as binary files or as ASCII files with the file extension *.fzt (in 9)RUPDW or 2)RUPDW compare chapter 15.4.4.1). In the following example t0 is output as an indicator.
$VM * Means of transport 4 * * Time interval 0.00 24.00 * Factor 1.0 * created with : VISUM Version 7.51 * created on : 04/30/01 * Netw/VersFile: O:\mh\VISUM6\Eng-700\Manual750_engl.ver * * Demand segment : P D_Car (private) * Route choice : Assignment * * All relations * * Weighting : Mean of volumes * * Output value summed up from * Links * Orig.Connectors * Dest.Connectors * TurningRelations * * Output data type : Time0 * * Output Unit : Minutes.Hundredth * * Number of Zones 4 100; 200; 300; 400; *Zon 100 0.00; 18.25; 12.17; 6.08; *Zon 200 18.50; 0.00; 6.08; 12.17; *Zon 300 12.42; 6.08; 0.00; 6.08; *Zon 400 6.33; 12.17; 6.08; 0.00; * * Output of origin data sums (origin. traffic) * 36.50 36.75 24.58 24.58 * * Output of destination data sums (dest. traffic) * 37.25 36.50 24.33 24.33 * * Output of overall sum * 122.42 *
15-85
AddValue files
$GG9DOXH ILOHV
For each network object type up to 3 Additional Values - $GG9DO, $GG9DO and $GG9DO - are available in VISUM, which may be used for any user-selected data. AddValues are integers in VISUM, thus AddValue data may be rounded. AddValues may be saved and read as attribute files (see Ch. 10.1.5; Ch. 15.3.5) or as network object type-specific AddValue-files (only one AddValue per file).
AddValue files (ASCII format) are compatible with previous VISUM versions. File headers are not translated into any foreign language (German file type and data format identifier).
1RGHV
AddValue files for nodes are saved with the file extension *.zkn.
$VISION $KNOTEN_ZWERTE $VERSION 1 ***** Syntax : * NodeNr AddValue * 10 1549 11 1288 12 1630 13 2188 20 1891 ....
G
15-86
Node-AddValue files have the file extension *.zkn. In VISUM-PuT these are, however, saved with the file extension *.erw.
AddValue files
/LQNV
AddValue files for links can be saved in three different ASCII formats with the file extension *.str. 6)RUPDW, .)RUPDW and 9,6803X7)RUPDW. )RUPDW 6 OLQNUHODWHG )RUPDW . QRGHUHODWHG 9,6803X7)RUPDW
$S $K *Factor *Factor 1.00 1.00 *LinkNr FromNode AddVal *FromNode 101 10 43 10 101 20 44 20 102 20 56 20 ... 30 ...
$VISION $STR_ZWERTE $VERSION 1 ToNode AddVal ***** Syntax : 20 43 *FromNode ToNode AddVal 10 44 10 20 43 30 56 20 10 44 20 55 20 30 56 30 20 55 ...
The formats . and 9,6803X7)RUPDW merely vary in the standard entries in the file header.
7XUQLQJ UHODWLRQV

AddValue files for turning relations are saved with the file extension *.kno.
$S *
FromLink 3 3 3 4 4 4 .....
ViaNode 1 3 3 3 3 4
ToLink 3 3 4 3 4 4
AddVal 1 1 1 1 1 1
15-87
AddValue files
=RQHV*OREDO ]RQHV

AddValue files for zones are saved with the file extension *.zbz and for global zones with the file extension *.zob. The data structure is the same for both file types. Example of a *.zbz file.
$VISION $BEZIRKS_ZWERTE $VERSION 1 ***** Syntax : * ZoneNr AddVal * 10 800 30 1000 40 800 ...
6XEOLQHV
AddValue files for sublines contain AddValue data for each FromStop-ToStop sectiom of the line route. They are saved with the file extension *.zli. They may be saved in Standard-ASCII-Format (not implemented yet) or in DOS-VISUM-PuTFormat (see example below). AddVal1, AddVal2 and AddVal3 data generated via MODIFY SUBLINE(S) using MULTISELECT or SINGLESELECT mode are saved with the version file only. They can be saved to an attribute file from the subline list. AddValues_Lines can be used for data management and display of counted data (e.g. volumes) or for generating line route attributes (e.g. number of services).
$VISION $STRLIN_ZWERTE $VERSION 1 $V ***** Syntax : * FromStop ToStop LinName LinVar Direction 180 200 B10 2A F 200 220 B10 2A F 220 230 B10 2A F ...
AddValue 729 729 729
G
15-88
AddVal_Lines files are saved with the file extension *.zli. In DOS-VISUM-PuT they are saved with the file extension *.lbe. AddVal_Lines files created in DOS-VISUM-PuT may only be opened in VISUM if they show the 9-Format.
AddValue files
6DYLQJ $GG9DOXH GDWD WR ILOH

*HQHUDO SURFHGXUH
0HQX ),/( 6$9(
AddValue 1-3 data of connectors and of sublines may only be saved to *.att file. ([DPSOH 6DYH $GG9DOXH GDWD RI =RQHV WR ILOH
6DYH $GG9DOXH Select $GG9DO, as a AddValue file may contain only data of one of the 3 AddValues. 7KH IROORZLQJ $GG9DOV DUH XVHG List of AddVals with AddVal data > 0 in the current network display.
15-89
AddValue files
6SHFLDO IHDWXUHV ZKHQ VDYLQJ $GG9DOB/LQN GDWD
0HQX ),/( 6$9( $GG9DOXHV /LQNV. 'LDORJ ER[ 6DYLQJ $GG9DOXHVB/LQNV WR ILOH
)DFWRU Multiply the AddVal data * Factor: 6 DQG .)RUPDW: The factor (F1) is saved to the file header, current AddVal_Links data are not multiplied * factor (F1) prior to saving to file (AV_Links1 data). The factor (F1) is used for multiplication when this AddVal_Links data file is opened for reading again. Thus the new AddValue data will be AV_Links2 = AV_Links1 * F1. Internally the new Factor is F2 = 1.00 after multiplication. When AV_Links2 data are saved to file, a factor F3 different than 1.00 may be entered, which will be saved to the file header and considered later on for multiplication with AV_Links2 data. 3X7)RUPDW: Current AddVal_Links data are multiplied by the factor; the results are saved as AddVal_Links data.
2XWSXW IRUPDW Select data format for *.str file.
15-90
AddValue files
6SHFLDO IHDWXUHV ZKHQ VDYLQJ $GG9DOB7XUQ5HO GDWD
0HQX ),/( 6$9( $GG9DOXHV 7XUQLQJ UHODWLRQV. 'LDORJ ER[ 6DYLQJ $GG9DOB7XUQ5HODWLRQV WR ILOH
Also for AddValues of turning relations a factor may be specified for multiplication of the current AddValue * factor. The multiplication is carried out prior to saving the calculated results to *.kno file, similar to AddVal_Links saved with PuT-format. The total number of turning relations in the network can be reduced to only those relations via active nodes and/or active turning relations only. AddValue data can also be saved for all turning relations currently displayed as Node Flows (menu GRAPHICS NODE FLOWS). 6SHFLDO IHDWXUHV ZKHQ VDYLQJ $GG9DOB6XEOLQHV GDWD
0HQX ),/( 6$9( $GG9DOXHV /LQHV. 'LDORJ ER[ 6DYLQJ $GG9DOXHVB/LQHV WR ILOH )DFWRU Multiplication of AddValue data * Factor. This factor is not considered for 6DYLQJ WR 9,6803X7 )RUPDW.
15-91
AddValue files
5HDGLQJ $GG9DOXH GDWD IURP ILOH

*HQHUDO SURFHGXUH
0HQX ),/( 23(1
After FILE - OPEN 1HWZRUN the AddValues of each network object type are set to Zero, as AddValues are not saved with the network file. After FILE - OPEN VERSION the AddValues may be used already, as AddValues are saved with the version file. ([DPSOH 5HDGLQJ $GG9DOXHVB=RQHV GDWD
5HDGLQJ $GG9DOXH Select the AddValue $GG9DO, which the data from the selected file should be used for in the current network. 6XP XS o Current AddVal3 data are replaced by AddVal3 data from file. AddVal3 data read from file are added to current AddVal3 data. 7KH IROORZLQJ $GG9DOV DUH XVHG List of AddVals with AddVal data > 0 in the current network display..
G
15-92
Option "Sum up" is only relevant, if the the selected value is already used in the current network version, e.g. for another time interval.
AddValue files
6SHFLDO IHDWXUHV ZKHQ UHDGLQJ $GG9DOB/LQNV GDWD IURP ILOH
0HQX ),/( 23(1 $GG9DOXHV /LQNV VW GLDORJ ER[ 5HDGLQJ $GG9DOXHVB/LQNV
QG GLDORJ ER[ 5HDGLQJ $GG9DOXHVB/LQNV
FRQVLGHU RQO\ VW HQWU\: Each link may occur only once in an AddVal_Links file. If several values are listed for one link in the file: further entries are ignored, a warning is displayed. 0LQLPXP: From several values listed in a row for one link the lowest value is considered. 0D[LPXP: From several values listed in a row for one link the highest value is considered. 0HDQ YDOXH: From several values listed in a row for one link the average value is considered .
15-93
AddValue files
6SHFLDO IHDWXUHV ZKHQ UHDGLQJ $GG9DOB7XUQ5HODWLRQV GDWD IURP ILOH
0HQX ),/( 23(1 $GG9DOXHV 7XUQLQJ UHODWLRQV. 'LDORJ ER[ 5HDGLQJ $GG9DOXHVB7XUQ5HODWLRQV
5HDGLQJ 'DWD IRUPDW 9,680)RUPDW. 9,6$1RGH)RUPDW '26 Reading counted node flow volumes from a data file which has been generated and saved with the the VISA-KNOTEN software (DOS-version; file extension *.asc).
15-94
Text files
7H[W ILOHV
Text files are saved with the file extension *.txt. In the example, the following text parameters are set: "Example (1) Text size 6.5 mm (TSize: 6.5) Colour: red (pen: 12) Centre at marked point x/y: centre (Ori: 5), Flow: rotated by 45 degrees (angle: 45). "Example (2) text size 3 mm (TSize: 3.0), colour: blue (pen: 9), Centre at marked point x/y: bottom left (Ori: 1), Horizontal flow (angle: 0).
$VISION $TEDI_DATEI $VERSION 103 ***** Background - Text file * X Y TSize Pen Ori 55.186 37.092 6.50 12 5 4.663 112.685 3.00 9 1
Angle Text(max. 255 characters) 45.00 Example (1) 0.00 Example (2)
15-95
Background files
%DFNJURXQG ILOHV
Background files are saved in two formats: Binary format with the file extension *.hgr and ASCII format with the file extension *.hgt (background file). Basic data for export/import of graphic files via DXF interface (see chapter 14).
([DPSOH RI D EDFNJURXQG ILOH

{$XLATPARAMS 63.2 0 2567700 0 58.2 5609480} BACKGROUND Example SCALE 100% OBJECT Sun Beam SCALE 0.3 BEGIN FILLSTYLE 0 6 0; POLYGON true false 0,0 80,20 0,40 0,0; END OBJECT Building SCALE 0.3 OBJECT Front part SCALE 1 BEGIN COLOR 7; FILLSTYLE 1 7 0; POLYGON true 0,0 250,0 250,180 0,180 0,0; END OBJECT Triangle SCALE 1 BEGIN COLOR 4; FILLSTYLE 6 4 1; POLYGON true 0,180 125,300 250,180 ,180; END
15-96
Background files
OBJECT Square SCALE 1 BEGIN COLOR 3; FILLSTYLE 4 3 0; POLYGON true 0,0 50,0 50,50 0,50 0,0; END OBJECT Rectangle SCALE 1 BEGIN COLOR 1; FILLSTYLE 4 1 0.3; POLYGON true 0,0 50,0 50,80 0,80 0,0; END BEGIN Front part Triangle Square Square Square Square Square Rectangle END BEGIN COLOR 5; TEXT 150 130 1 "The object is rotated" 0; TEXT 150 120 1 "several times:" , 0; TEXTSTYLE 7 7 0 BOTTOM; COLOR 2; FRAMESTYLE true 1 1 5; TEXT 150 105 1 "Sun Beam",0; Building Sun Beam Sun Beam Sun Beam Sun Beam Sun Beam Sun Beam 30 110 110 110 110 110 110 30 140 140 140 140 140 140 0; 0; 60; 120; 180; 240; 300; 0 0 25 100 175 25 175 100 0 0 100 100 100 30 30 2 0; 0; 0; 0; 0; 0; 0; 0;
COLOR 2; LINESTYLE 2 1; POLYGON false true 0,0 250,0 250,180 0,180 0,0; END
15-97
Background files
15-98
MACRO COMMANDS
0$&52 &200$1'6
Macro commands initiate the execution of VISUM commands. They are saved in the form of a specific "macro language" in a macro text file and are executed serially by calling up the file. In this way, they facilitate the automatic execution of timeconsuming and often-repeated operations such as reading data, calculating assignments, starting plot outputs, and saving data etc.. Macro commands can be executed after calling up the macro file without the user having to be present. If there is sufficient working memory, a macro file can also be executed while the user starts VISUM a second time and carries out different operations.
16-1
MACRO COMMANDS
List of macro commands
/LVW RI PDFUR FRPPDQGV
The macro.lan text file is installed automatically in the ..\exe directory during the installation of VISUM. It contains all available VISUM macro commands with information on compulsory and optional parameters:
&RPPDQGFRPSXOVRU\!DQG>RSWLRQDO@SDUDPHWHUV 'HVFULSWLRQ
Net NetF Vers VerF OD
<Filename> [additional (y/n)] <Filename> <Filename> <Filename> <Filename> <DSeg> <reset(y/n)> [factor]
Read network file (additionally). Save network file. Open version file. Save version file. Open O-D matrix file for demand segment (enter code). Save O-D matrix file for demand segment (enter code). Initialize O-D matrix demand segment. of selected
ODF
<Filename> <DSeg> <Format> [decimal places] <DSeg>
IOD
GPar APar Assg
<Filename> <Filename>
Open graphic parameters file. Open assignment parameters file. Start assignment and/or indicators calculation according to current assignment parameters file. Initialize current flow bundle(s).
FlowBIni FlowBMatF <Filename> <DSeg> <Format> [decimal places]
Save flow bundle matrix for demand segment (enter code): decimal places (0..3) only ASCII
16-2
MACRO COMMANDS
&RPPDQGFRPSXOVRU\!DQG>RSWLRQDO@SDUDPHWHUV
'HVFULSWLRQ
LnkFlowB
<type(0/1/2)> <selectDSeg> <PuTSysCodes> <Link> [Node]
Calculate link flow bundle. Enter Type: 0=PrT, 1=PuT; 2=PrT+PuT. Codes (without blanks) of selected demand segment(s) (according to type) Codes (without blanks) of PuTSys for type 1 or 2 (for type 0 enter sign) Both link directions are selected, if NodeNr. is missing. Start plot output. Redraw network display on screen.
Plot Draw Diff Ret Text TRed <Filename> <Nr> <Nr> [ToNode] <Penalty> <Filename>
Calculate difference network version. Initialise difference network. Read text file. Modify PrT time penalty for turning relation in [s]. Enter FromLinkNr and ToLinkNr or FromNode-ViaNodeToNode. A closed turning relation is simultaneously opened for all TSys, otherwise TSys settings are kept. Close turning relation for all TSys (entry with 2 numbers = LinkNo. or entry with 3 numbers = NodeNo.). The options follow the order in the partial network generator dialog box. The partial network can ony be saved with one o-d matrix (DSeg). Wait time till next macro command. Modify PrT-capacity of turning relation in passenger car units (entry with 2 numbers = LinkNo. or entry with 3 numbers = NodeNo.).
TRde
<Nr> <Nr> [ToNode]
PartNet
<Filename *.net> [line route behaviour (0,1,2)] [VirtZoneNumbering cont. (y/n)] [VirtZone min Nr] [VirtZone type] [O-D file name] [DSeg] <seconds> <Nr> <Nr> [ToNode] <Capacity>
Wait TCap
16-3
MACRO COMMANDS
'HVFULSWLRQ
LnkC AVLR
<LnkNr> <FromNode> <Capacity> <AddValNr(1,2,3)> <add(y/n)> <Filename> [Factor]
Modify PrT-capacity of link. Open Link-AddValue file.
LnkD InLe InTe Filt_Read Filt_Rset AV_L_Save
<NodeNr> <NodeNr>
Delete link (both directions). Initialize legend. Initialize graphic texts.
<Filename>
Read filter parameters from file. Initialize filter.
<AddValNr(1,2,3)> <Filename> <Factor>
Save Link-AddValue file.
RPol_Rset
Delete reference polygon specified in multi select mode. <Filename> <Filename> Read text data in legend. Read path extensions). file (directories and
LegT_Read Path_Read
LnkAtt
<LnkAtt1> <LnkAtt2> <Factor> <add(y/n)>
Create link attribute from other link attribute (LinkAtt1 = LinkAtt2 * factor). Specify constant link attribute value.
LnkConst
<LnkAttribut> <Constant> <add(y/n)>
ATur_Read
<AddVNr(1,2,3)> <add(y/n)> <Filename>
Read TurnRel-AddValue file.
ATur_Save
<AddVNr(1,2,3)> <Filename> <Factor>
Save TurnRel-AddValue file.
TurAtt
<TurAtt1> <TurAtt2> <Factor> <add(y/n)>
Create turning relation attribute values from other TurnRel attr. (TurAtt1 = TurAtt2 * factor) Read link attribute file.
LnkAtt_Read
<Filename>
16-4
MACRO COMMANDS
'HVFULSWLRQ
LnkAtt_Save
<Filename> <LnkAtt1> [LnkAtt2] [LnkAtt3] [LnkAtt4] [LnkAtt5] <Filename>
Save attribute file with max. 5 link attributes. Read active network objects (*.ane file). Delete node with only 2 neighbouring nodes and connect the 2 links. LinkNo. will be max. LinkNo. in network + 1. Delete all nodes with only 2 neighbouring nodes and connect the links.
Acti_Read
Conn_Links
<NodeNr>
Conn_all_Links
NodeNr_Edit Del_all_Lines StrT_Mak
<oldNodeNr> <newNodeNr> [only active (y/n)] <Filename>
Modify node number. Delete all (active) PuT lines. Read a VISUM-PublicTransport (DOS) macro file, that contains interactive link label display specifications (shifted positions and switched off link labels), which had been carried out with that previous VISUM version. Use the StrT_Aus and StrT_Pos macro commands; otherwise those label specifications will get lost, as VISUM cannot read *.gpa files created with a VISUMDOS version. No link label direction. for specified link
StrT_Aus
<FromNodeNo.> <ToNodeNo.>
StrT_Pos
<FromNode> <ToNode> <segment> Specify label position by link direction; <pos (0.0 .. 1.0)> Segment = 1 if link course = direct distance (no intermediate points), enter appropriate segment No. in case of specified link course > direct distance. The pos value (0.0 ... 1.0) specifies to which position the label is to be shifted: 0.0 = FromNode, 0.5 = 50% of length, 1.0 = ToNode. VISUM User Manual (April 2001) Version 7.50 16-5
MACRO COMMANDS
Stop Rep End $$$$
Stop macro until any key is pressed. Repeat macro. Terminate macro. Terminate session. macro and VISUM
ProgramEnd *
Terminate VISUM session. Comment.
Not all VISUM commands can be executed as macro commands. Assignment parameters files read with the APar command are essentially also macro files. Assignment parameters *.par files contain all operations saved to file which had been called up under ASSIGNMENT in the CALCULATE menu. With this numerous macro commands can now be implemented which in the previous VISUM-PuT served to calculate indicator matrices.
16-6
Creating a macro file
MACRO COMMANDS
&UHDWLQJ D PDFUR ILOH
Macro files must be created with an external text editor. The macro commands must be entered into the macro file in the desired order by the user. The following rules apply: A macro command generally has the following structure: Command <compulsory parameter_1> <compulsory <optional parameter_1> <optional parameter_n>
parameter_n>
The parameters are entered without brackets one after another, they are only separated by spaces. For macro commands which require the specification of a network object attribute, the short identifier of the attribute has to be be used (see chapter 4: attribute descriptions of different network object types and chapter 8: environment link attributes). Target attributes can only be input attributes or AddValues. Results of calculations and attributes which are used to identify network objects cannot be target attributes. The <filename> parameter can also be a complete path (drive\folder\...\filename.ext); if only a filename is entered, VISUM uses the currently specified path and extension of the particular file type. Comment lines are marked with *. A macro file must either end with End or with $$$$. In VISUM, macro files have the standard file extension *.mac.
16-7
MACRO COMMANDS
Creating a macro file
([DPSOH RI D PDFUR ILOH PDF
* To specify the project directory for the required * files: Read corresponding directory file (example.pfd) Path_Read c:\vision\example * Read version file state1.ver: Vers state1 * Read assignment parameters file example.par: APar example * Carry out assignment according to these parameters: Assg * Save version file state2.ver: VerF state2 * Delete link (both directions) between Node 11 and Node 20 LnkD 11 20 * Carry out new assignment using same ass. parameters: Assg * Save version file state3.ver: VerF state3 * End macro: End
16-8
Execution of macros
MACRO COMMANDS
([HFXWLRQ RI PDFURV
([HFXWLQJ LQGLYLGXDO FRPPDQGV
EXTRAS menu: MACRO - ENTER COMMANDS ([HFXWH PDFUR FRPPDQG GLDORJ
Enter macro command in the input line and start with "Execute".
We recommend that you use the command dialog before creating and saving extensive command sequences because it serves to test individual macro commands.
([HFXWH PDFUR ILOH
Macros can be activated and executed in different ways: In VISUM via MACRO - 5HDG PDFUR ILOH in the EXTRAS menu or select file type 0DFURV under OPEN.. in the FILE menu. Link macro file *.mac with visum.exe, Start just like a program file by double-clicking.
in Windows:
For macro files, VISUM requires the standard file extension *.mac.
16-9
MACRO COMMANDS
Execution of macros
5HDG PDFUR ILOH GLDORJ
Macro execution can be carried out in three different ways: 1RQVWRS In 1RQVWRS mode the macro is executed without interactive interruptions. If required, the macro halts for a particular time where the command sequence contains a ":DLW command (e.g. ZDLW : automatic interrupt for 15 seconds). 7LOO VWRS In 7LOO VWRS mode the macro is executed up to a stop command and then halts at this point until it is reactivated by pressing the 1H[W button. 6WHS E\ VWHS In VWHS E\ VWHS mode the macro jumps from one command to another by pressing the 1H[W button.
The macro commands currently being executed are displayed in a message line below the buttons. The macro can be cancelled at any time by pressing the &DQFHO button. In addition to this, it is possible to switch between different macro modes at any time.
If the commands are executed incorrectly, the error messages are recorded in the fehler.lst error file. WARNING! Macro execution does not activate dialog boxes (e.g. error messages) because the automatic execution of the command sequence could otherwise not be guaranteed. This means that during macro execution commands are based on standard values and that some files may be overwritten because no confirmations are requested. A macro file cannot call up another macro file.
16-10

Visum 75 Manual

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Visum 75 Manual

Hochgeladen von

Copyright:

Verfügbare Formate

9,680 86(5 0$18$/

$QDO\VLV DQG 3ODQQLQJ RI 7UDQVSRUW 1HWZRUNV

PTV Planung Transport Verkehr AG All rights reserved

PTV AG Stumpfstr. 1 D-76131 Karslruhe Germany

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

4.1.1 4.1.2 4.1.3

4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6 4.2.7 4.2.8

4-9 4-11 4-16 4-18 4-19 4-21 4-22 4-23 4-24

4.4 4.4.1 4.4.1.1 4.4.1.2 4.4.2 4.4.3 4.4.4 4.4.5 4.4.5.1

4-48 4-49 4-49 4-51 4-57 4-59 4-59 4-60 4-60

Connectors Connector attributes

4.9.7 4.9.7.1 4.9.7.2 4.9.7.3 4.9.7.4 4.9.7.5 4.9.8

4-190 4-191 4-194 4-194 4-195 4-196 4-200

Options for Insert network object

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

 8.1 8.2 8.3 8.4 8.5

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

13.1.1 13.1.2 13.1.3 13.1.4 13.1.4.1 13.1.4.2 13.2

13.5.5 13.6 13.6.1 13.6.2 13.6.3

13-33 13-34 13-34 13-36 13-36

VISUM User Manual (April 2001) Version 7.50

15.2.1 15.2.1.1 15.2.1.2 15.2.1.3 15.2.1.4 15.2.2 15.3

15.3.1 15.3.2 15.3.3 15.3.4 15.3.5 15.3.5.1 15.3.5.2 15.3.6

VISUM User Manual (April 2001) Version 7.50

 16.1 16.2 16.3

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

$QDO\VLV RI FXUUHQW VWDWH

Evaluating the impacts of the current state

Evaluating the impact of a solution

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

 6WUXFWXUH RI WKH PDQXDO

 )RUPDW FRQYHQWLRQV

([HFXWH <Esc> <Alt-E>, <S> or <Alt>+<E>+<S>

)LOH DQG SDWKQDPH with ..\Directory\Name.Ext.

VISUM User Manual (April 2001) Version 7.50

 9,680 &DSDELOLWLHV

 9,680 GDWDEDVH

Furthermore the network may contain,

VISUM User Manual (April 2001) Version 7.50

 ,PSDFW PRGHOV

 7UDQVSRUW VXSSO\ DQDO\VLV

VISUM User Manual (April 2001) Version 7.50

)LHOGV RI DSSOLFDWLRQ IRU SODQQLQJ WDVNV LQ 3XEOLF 7UDQVSRUW

)LHOGV RI DSSOLFDWLRQ IRU SODQQLQJ WDVNV LQ 3ULYDWH 7UDQVSRUW

VISUM User Manual (April 2001) Version 7.50

 7HFKQLFDO LQIRUPDWLRQ

 $YDLODEOH 9,680 YHUVLRQV 6L]H DQG $GG2QV

VISUM User Manual (April 2001) Version 7.50

VISUM User Manual (April 2001) Version 7.50

 +DUGZDUH DQG VRIWZDUH UHTXLUHPHQWV

8.1 8.2 8.3 8.4 8.5

16.1 16.2 16.3

6WUXFWXUH RI WKH PDQXDO

)RUPDW FRQYHQWLRQV

9,680 &DSDELOLWLHV

9,680 GDWDEDVH

,PSDFW PRGHOV

7UDQVSRUW VXSSO\ DQDO\VLV

7HFKQLFDO LQIRUPDWLRQ

$YDLODEOH 9,680 YHUVLRQV 6L]H DQG $GG2QV

+DUGZDUH DQG VRIWZDUH UHTXLUHPHQWV

,QVWDOODWLRQ RI 9,680

3UREOHPV GXULQJ SURJUDP RSHUDWLRQ

1HWZRUN 0RGHO

7UDQVSRUW V\VWHPV

1RGHV LQWHUVHFWLRQV DQG VWRSV

7XUQLQJ UHODWLRQV

/LQH URXWH %XV!

/LQH URXWH %XV!